Please sync rabbitmq-server 1.7.2-1 (main) from Debian sid (main)
Explanation of FeatureFreeze exception:
I have spoken with RabbitMQ upstream and would like to get the 1.7.2
bugfix release into Lucid. Based on my discussions with upstream I
believe this is a bugfix only release and appropriate for upload at
this time. However, because I have not yet gotten a list of the bugs
that are fixed by this upload (and there is no public RabbitMQ bug
tracker for me to look in), and I only recently got upload rights for
this package, I am asking for confirmation from the release team. I will
be asking upstream to comment on this bug report with information
about what bugs are fixed in this release and to confirm my understanding
that this is a bugfix only point release, not a new feature release.
Note that I have per-package upload permissions for rabbitmq-server.
Changelog entries since current lucid version 1.7.0-3:
rabbitmq-server (1.7.2-1) unstable; urgency=low
* New upstream release
-- John Leuner <email address hidden> Fri, 19 Feb 2010 17:30:57 +0200
The rabbitmq-server bug fixes relevant to Ubuntu in the 1.7.2 release are:
- make 'rabbitmq-multi start_all <n>' work again for n>1
- issuing a basic.qos when there are outstanding acks can no longer result in a higher limit than requested
- enforce codec size limits, thus preventing the server from sending invalid AMQP frames
- remove the explicit setting of TCP buffer sizes in the server, thus allowing auto-(re)sizing to occur. This generally results in substantially improved throughput over high-latency links, and makes manual fine-tuning easier.
- introduce declarative boot sequencing, which allows plugins to be started at arbitrary chosen points during the sequence
- add rabbitmqctl list_channels and list_consumers commands, and add exclusivity information to list_queues. Also introduce a close_connection command to allow an administrator to selectively terminate client connections. See the updated admin guide at http://
The database schema has not changed since the 1.6.0 release, so user accounts, durable exchanges and queues, and persistent messages will all be retained during the upgrade.