openSUSE Build Service

Overview Repositories Revisions Requests Users Attributes Meta

Revisions of rabbitmq-server

Fridrich Strba (fstrba) accepted request 1031341 from

Dominique Leuenberger (dimstar) about 2 years ago (revision 189)

- Update to version 3.10.10:
  + Core Server
    * Partially reverts an unsafe inter-node communication
      optimization that could affect classic mirrored queue
      operation ordering.
    * Classic mirrored queue leader replica issued to much credit
      to follower replicas, resulting in an uneven load and
      memory footprint between them.
    * Intra-cluster communication link metric collector could run
      into an exception when peer connection has just been
      re-established, e.g. after a peer node restart.
  + MQTT Plugin
    * When a node was put into maintenance mode, it closed all MQTT
      client connections cluster-wide instead of just local client
      connections.
- For updates between 3.10.5 and 3.10.9, please see
  https://www.rabbitmq.com/changelog.html

buildservice-autocommit accepted request 983568 from

Dirk Mueller (dirkmueller) over 2 years ago (revision 188)

baserev update by copy to link target

Dirk Mueller (dirkmueller) accepted request 983566 from

Fusion Future (fusionfuture) over 2 years ago (revision 187)

- Update to 3.10.5
  * Quorum queue could run into an exception when dead lettering a message
    under certain conditions.
- Changes from 3.10.4
  * Avoid seeding default user in old clusters that still use the deprecated
    management.load_definitions option.
  * Streams could run into an exception or fetch stale stream position
    data in some scenarios.
  * rabbitmqctl set_log_level did not have any effect on logging via
    amq.rabbitmq.log

buildservice-autocommit accepted request 978405 from

Fusion Future (fusionfuture) over 2 years ago (revision 186)

baserev update by copy to link target

Fusion Future (fusionfuture) accepted request 978404 from

Fusion Future (fusionfuture) over 2 years ago (revision 185)

- Update to 3.10.2
  * Default log level used a four-character severity abbreviation
    instead of more common longer format, for example, warn instead
    of warning.
  * Fix CLI tools failed to run on Erlang 25

buildservice-autocommit accepted request 976926 from

Dirk Mueller (dirkmueller) over 2 years ago (revision 184)

baserev update by copy to link target

Dirk Mueller (dirkmueller) accepted request 976488 from

Andreas Stieger (AndreasStieger) over 2 years ago (revision 183)

- add upstream signing key and verify source signature

buildservice-autocommit accepted request 975710 from

Fusion Future (fusionfuture) over 2 years ago (revision 182)

baserev update by copy to link target

Fusion Future (fusionfuture) accepted request 975709 from

Fusion Future (fusionfuture) over 2 years ago (revision 181)

- Update to 3.10.0
  * See https://github.com/rabbitmq/rabbitmq-server/blob/v3.10.x/release-notes/3.10.0.md
    for the full changelog.
  * Potentially breaking changes
    - Messages delivered by a quorum queue and negatively acknowledged
      with a requeue will be added to the back of the queue until the
      queue has redelivery limit set. With a redelivery limit, requeueing
      will use the original position of the message if possible.
    - idle_since field now uses RFC 3339 format.

buildservice-autocommit accepted request 964745 from

Fusion Future (fusionfuture) over 2 years ago (revision 180)

baserev update by copy to link target

Fusion Future (fusionfuture) accepted request 964744 from

Fusion Future (fusionfuture) over 2 years ago (revision 179)

- Update to 3.9.14
  * See https://github.com/rabbitmq/rabbitmq-server/blob/v3.9.x/release-notes/3.9.14.md
    for the full changelog.
  * Build time compatibility with Elixir 1.13 (gh#rabbitmq/rabbitmq-server#4019)
    - Drop Elixir-1.13-OptionParser-no-longer-supports-atom-val.patch
    - Drop Support-Elixir-1.13.patch
  * Adapt to a breaking Erlang 24.3 LDAP client change.

Fusion Future (fusionfuture) accepted request 956004 from

Fusion Future (fusionfuture) almost 3 years ago (revision 178)

- Add zsh BuildRequires to fix "directories not owned by a package"
  in zsh-completion.

Fusion Future (fusionfuture) accepted request 955988 from

Fusion Future (fusionfuture) almost 3 years ago (revision 177)

- Update to 3.9.13
  * Core Server Bug Fixes and Enhancements
    - Disk space monitor now correctly parses output on (at least
      some) systems where non-ASCII characters are used in paths.
    - Stream leader election is now deterministic when cluster is
      undergoing a rolling upgrade.
    - Queue and binding definition import can be delayed until a
      moment when at least N nodes (e.g. three) have joined the
      cluster.
- Allow building with Elixir 1.13.x
  * Support-Elixir-1.13.patch
  * Elixir-1.13-OptionParser-no-longer-supports-atom-val.patch

Fusion Future (fusionfuture) accepted request 944486 from

Fusion Future (fusionfuture) almost 3 years ago (revision 176)

- Update to 3.9.12
  * See https://github.com/rabbitmq/rabbitmq-server/blob/v3.9.x/release-notes/3.9.12.md
    for the full changelog.
  * Core Server Bug Fixes and Enhancements
    - (Fix) Authentication and authorization backend exceptions
      could potentially leak user-provided credentials to node log.
    - Unnamed parameters and policies in definition files will now
      be rejected as invalid.

Fusion Future (fusionfuture) accepted request 935226 from

Fusion Future (fusionfuture) almost 3 years ago (revision 175)

- Update to 3.9.11
- Drop upstreamed patch
  * harden_rabbitmq-server.service.patch: https://github.com/rabbitmq/rabbitmq-server/pull/3770

Fusion Future (fusionfuture) accepted request 932386 from

Fusion Future (fusionfuture) about 3 years ago (revision 174)

Update to 3.9.9

The patch has been submitted to upstream and is being processed: https://github.com/rabbitmq/rabbitmq-server/pull/3770

Fusion Future (fusionfuture) accepted request 926714 from

Johannes Segitz (jsegitz) about 3 years ago (revision 173)

Automatic systemd hardening effort by the security team. This has not been tested. For details please see https://en.opensuse.org/openSUSE:Security_Features#Systemd_hardening_effort

Fusion Future (fusionfuture) accepted request 926540 from

Fusion Future (fusionfuture) about 3 years ago (revision 172)

Update to 3.9.8

Fusion Future (fusionfuture) accepted request 921339 from

Fusion Future (fusionfuture) about 3 years ago (revision 171)

- Update to 3.9.7:
  + All Components
    * All bytecode is now compiled using the +deterministic
      compiler flag. This should eliminate the capture of some
      irrelevant build environment attributes in produced
      artifacts, improve consistency between builds, and reduce the
      file level diff between release artifacts.
  + Core Server
    * Enhancements
      - Classic queue shutdown now uses a much higher timeout (up
        to 10 minutes instead of 30 seconds).
      - In environments with many queues (especially mirrored
        queues) and many consumers this means that the chance of
        queue indices rebuilding after node restart is now
        substantially lower.
    * Bug Fixes
      - Quorum queues no longer leak memory and disk space when a
        consumer is repeatedly added and cancelled on an empty
        queue.
  + Prometheus Plugin
    * Enhancements
      - More configurability for metrics exposed via the Prometheus
        endpoint.
  + Shovel Plugin
    * Bug Fixes
      - Shovel URIs could be logged with credentials in some
        scenarios.
  + Dependency Upgrades
    * observer_cli has been upgraded from 1.6.2 to 1.7.1

Fusion Future (fusionfuture) accepted request 919608 from

Fusion Future (fusionfuture) about 3 years ago (revision 170)

Update to 3.9.6

Displaying revisions 21 - 40 of 209

Places

Revisions of rabbitmq-server

Places