Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package rabbitmq-server for openSUSE:Factory 
checked in at 2025-12-22 22:49:53
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/rabbitmq-server (Old)
 and      /work/SRC/openSUSE:Factory/.rabbitmq-server.new.1928 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "rabbitmq-server"

Mon Dec 22 22:49:53 2025 rev:98 rq:1324003 version:4.2.1

Changes:
--------
--- /work/SRC/openSUSE:Factory/rabbitmq-server/rabbitmq-server.changes  
2025-08-07 16:51:21.134676152 +0200
+++ 
/work/SRC/openSUSE:Factory/.rabbitmq-server.new.1928/rabbitmq-server.changes    
    2025-12-22 22:52:32.677193935 +0100
@@ -2 +2 @@
-Thu Aug  7 06:35:22 UTC 2025 - Simon Lees <[email protected]>
+Tue Dec  9 14:10:35 UTC 2025 - Guillaume GARDET <[email protected]>
@@ -4 +4,4 @@
-- Restore SLES logrotate file, (bsc#1246091)
+- Update to 4.2.1
+  * https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.1
+- Update to 4.2.0
+  * https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.0
@@ -7 +10,61 @@
-Thu Jul 31 06:06:04 UTC 2025 - Simon Lees <[email protected]>
+Thu Nov  6 04:06:19 UTC 2025 - Simon Lees <[email protected]>
+
+- Update to 4.1.5
+  * Highlights
+    Khepri, an alternative schema data store developed to replace Mnesia,
+    has matured and is now fully supported (it previously was an experimental 
feature)
+    AMQP 1.0 is now a core protocol that is always enabled. Its plugin is now 
a no-op that only exists to simplify upgrades.
+    The AMQP 1.0 implementation is now significantly more efficient: its peak 
throughput is more than double than that of 3.13.x
+    on some workloads
+    Efficient sub-linear quorum queue recovery on node startup using 
checkpoints
+    Quorum queues now support priorities (but not exactly the same way as 
classic queues)
+    AMQP 1.0 clients now can manage topologies similarly to how AMQP 0-9-1 
clients do it
+    The AMQP 1.0 convention (address format) used for interacting with with 
AMQP 0-9-1 entities is now easier to reason about
+    Mirroring (replication) of classic queues was removed after several years 
of deprecation. For replicated messaging data types,
+    use quorum queues and/or streams. Non-replicated classic queues remain and 
their development continues
+    Classic queue storage efficiency improvements, in particular recovery time 
and storage of multi-MiB messages
+    Nodes with multiple enabled plugins and little on disk data to recover now 
start up to 20-30% faster
+    New exchange type: Local Random Exchange
+    Quorum queue log reads are now offloaded to channels (sessions, 
connections).
+    Initial Support for AMQP 1.0 Filter Expressions
+    Feature Flags Quality of Life Improvements
+    rabbitmqadmin v2
+  * Breaking Changes
+    Before a client connection can negotiate a maximum frame size (frame_max), 
it must authenticate
+    successfully. Before the authenticated phase, a special lower frame_max 
value
+    is used.
+    With this release, the value was increased from the original 4096 bytes to 
8192
+    to accommodate larger JWT tokens.
+    amqplib is a popular client library that has been using
+    a low frame_max default of 4096. Its users must upgrade to a compatible 
version
+    (starting with 0.10.7) or explicitly use a higher frame_max.
+    amqplib versions older than 0.10.7 will not be able to connect to
+    RabbitMQ 4.1.0 and later versions due to the initial AMQP 0-9-1 maximum 
frame size
+    increase covered above.
+    The default MQTT Maximum Packet Size changed from 256 MiB to 16 MiB.
+    The following rabbitmq.conf settings are unsupported:
+    cluster_formation.etcd.ssl_options.fail_if_no_peer_cert
+    cluster_formation.etcd.ssl_options.dh
+    cluster_formation.etcd.ssl_options.dhfile
+    Classic Queues is Now a Non-Replicated Queue Type
+    Quorum Queues Now Have a Default Redelivery Limit
+    Up to RabbitMQ 3.13, when an AMQP 0.9.1 client (re-)published a message to 
RabbitMQ, RabbitMQ interpreted the
+    AMQP 0.9.1 x-death header in the published message's 
basic_message.content.properties.headers field.
+    RabbitMQ 4.x will not interpret this x-death header anymore when clients 
(re-)publish a message.
+    CQv1 Storage Implementation was Removed
+    Settings cluster_formation.randomized_startup_delay_range.* were Removed
+    Several Disk I/O-Related Metrics were Removed
+    Default Maximum Message Size Reduced to 16 MiB
+    RabbitMQ 3.13 rabbitmq.conf setting rabbitmq_amqp1_0.default_vhost is 
unsupported in RabbitMQ 4.0.
+    RabbitMQ 3.13 rabbitmq.conf settings mqtt.default_user, 
mqtt.default_password,
+    and amqp1_0.default_user are unsupported in RabbitMQ 4.0.
+    Starting with Erlang 26, client side TLS peer certificate chain 
verification settings are enabled by default in most contexts:
+    from federation links to shovels to TLS-enabled LDAP client connections.
+    RabbitMQ Shovels will be able connect to a RabbitMQ 4.0 node via AMQP 1.0 
only when the Shovel runs on a RabbitMQ node >= 3.13.7.
+    * See https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.0.1
+    * and https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.1.0 for 
more info
+    * Removed the following patches fixed upstream
+    - fix-CVE-2025-30219.patch
+    - fix-CVE-2025-50200.patch
+    - rabbitmq-server-allow-elixir-1.18.patch
+- Add feature-suse-reproducable-build.patch to help with repoducable builds.
@@ -9,8 +72,4 @@
-- RabbitMQ Node can log Basic Auth header from an HTTP request
-  (bsc#1245105, CVE-2025-50200)
-  * fix-CVE-2025-50200.patch
-- bad logrotate configuration allows potential escalation from 
-  rabbitmq to root, /var/log/rabbitmq ownership is now 750
-  (bsc#1246091)
-- Make build reproducable
-  * feature-suse-reproducable-build.patch
+-----------------------------------------------------------------
+Thu Aug  7 06:35:22 UTC 2025 - Simon Lees <[email protected]>
+ 
+- Restore SLES logrotate file, (bsc#1246091)

Old:
----
  fix-CVE-2025-30219.patch
  fix-CVE-2025-50200.patch
  rabbitmq-server-3.13.7.tar.xz
  rabbitmq-server-3.13.7.tar.xz.asc
  rabbitmq-server-allow-elixir-1.18.patch

New:
----
  _constraints
  rabbitmq-server-4.2.1.tar.xz
  rabbitmq-server-4.2.1.tar.xz.asc

----------(Old B)----------
  Old:    * Removed the following patches fixed upstream
    - fix-CVE-2025-30219.patch
    - fix-CVE-2025-50200.patch
  Old:    - fix-CVE-2025-30219.patch
    - fix-CVE-2025-50200.patch
    - rabbitmq-server-allow-elixir-1.18.patch
  Old:    - fix-CVE-2025-50200.patch
    - rabbitmq-server-allow-elixir-1.18.patch
- Add feature-suse-reproducable-build.patch to help with repoducable builds.
----------(Old E)----------

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ rabbitmq-server.spec ++++++
--- /var/tmp/diff_new_pack.tivk1R/_old  2025-12-22 22:52:34.517269822 +0100
+++ /var/tmp/diff_new_pack.tivk1R/_new  2025-12-22 22:52:34.517269822 +0100
@@ -1,7 +1,7 @@
 #
 # spec file for package rabbitmq-server
 #
-# Copyright (c) 2025 SUSE LLC
+# Copyright (c) 2025 SUSE LLC and contributors
 #
 # All modifications and additions to the file contributed by third parties
 # remain the property of their copyright owners, unless otherwise agreed
@@ -39,7 +39,7 @@
 %define _rabbitmq_group rabbitmq
 
 Name:           rabbitmq-server
-Version:        3.13.7
+Version:        4.2.1
 Release:        0
 Summary:        A message broker supporting AMQP, STOMP and MQTT
 License:        MPL-2.0
@@ -54,12 +54,11 @@
 Source7:        
https://raw.githubusercontent.com/rabbitmq/rabbitmq-packaging/v%{version}/RPMS/Fedora/rabbitmq-server.tmpfiles
 Source8:        README.SUSE
 Patch0:         feature-suse-reproducable-build.patch
-Patch1:         rabbitmq-server-allow-elixir-1.18.patch
-Patch2:         fix-CVE-2025-30219.patch
-Patch3:         fix-CVE-2025-50200.patch
 BuildRequires:  elixir
-# https://www.rabbitmq.com/which-erlang.html
-BuildRequires:  erlang >= 25.0
+# https://www.rabbitmq.com/docs/which-erlang
+BuildRequires:  erlang >= 26.2
+BuildRequires:  7zip
+BuildRequires:  erlang-epmd
 BuildRequires:  erlang-src
 BuildRequires:  fdupes
 BuildRequires:  hostname
@@ -70,7 +69,7 @@
 BuildRequires:  xmlto
 BuildRequires:  xz
 BuildRequires:  zip
-Requires:       erlang >= 25.0
+Requires:       erlang >= 26.2
 Requires:       erlang-epmd
 Requires:       logrotate
 Provides:       AMQP-server
@@ -102,7 +101,7 @@
 %package -n erlang-rabbitmq-client
 Summary:        RabbitMQ AMQP language bindings for Erlang
 Group:          Development/Libraries/Other
-Requires:       erlang
+Requires:       erlang27
 Provides:       erlang-amqp_client = %{version}
 Provides:       erlang-gen_server2 = %{version}
 Provides:       erlang-rabbit_common = %{version}

++++++ _constraints ++++++
<constraints>
  <hardware>
    <physicalmemory>
      <size unit="G">12</size>
    </physicalmemory>
    <disk>
      <size unit="G">80</size>
    </disk>
  </hardware>
</constraints>

++++++ feature-suse-reproducable-build.patch ++++++
--- /var/tmp/diff_new_pack.tivk1R/_old  2025-12-22 22:52:34.593272956 +0100
+++ /var/tmp/diff_new_pack.tivk1R/_new  2025-12-22 22:52:34.609273616 +0100
@@ -1,13 +1,13 @@
-Index: rabbitmq-server-3.13.7/erlang.mk
+Index: rabbitmq-server-4.1.5/erlang.mk
 ===================================================================
---- rabbitmq-server-3.13.7.orig/erlang.mk
-+++ rabbitmq-server-3.13.7/erlang.mk
+--- rabbitmq-server-4.1.5.orig/erlang.mk
++++ rabbitmq-server-4.1.5/erlang.mk
 @@ -66,7 +66,7 @@ export ERLANG_MK_TMP
  
  # "erl" command.
  
--ERL = erl +A1 -noinput -boot no_dot_erlang
-+ERL = erl +A1 -noinput -boot no_dot_erlang -enable-deterministic-build
+-ERL = erl -noinput -boot no_dot_erlang -kernel start_distribution false +P 
1024 +Q 1024
++ERL = erl -noinput -enable-deterministic-build -boot no_dot_erlang -kernel 
start_distribution false +P 1024 +Q 1024
  
  # Platform detection.
  

++++++ rabbitmq-server-3.13.7.tar.xz -> rabbitmq-server-4.2.1.tar.xz ++++++
++++ 319010 lines of diff (skipped)

Reply via email to