This bug was fixed in the package rabbitmq-server - 2.8.4-1
Sponsored for Emile Joubert (pawnstar)
---------------
rabbitmq-server (2.8.4-1) unstable; urgency=low
* New upstream release
-- Emile Joubert <em...@rabbitmq.com> Fri, 22 Jun 2012 17:48:28 +0100
rabbitmq-server (2.8.3-1) unstable; urgency=low
* New upstream release
-- Emile Joubert <em...@rabbitmq.com> Thu, 21 Jun 2012 13:38:57 +0100
rabbitmq-server (2.8.2-2) unstable; urgency=low
* Add version numbers to plugins
-- Emile Joubert <em...@rabbitmq.com> Tue, 01 May 2012 10:48:57 +0100
rabbitmq-server (2.8.2-1) unstable; urgency=low
* New upstream release
-- Emile Joubert <em...@rabbitmq.com> Mon, 30 Apr 2012 14:07:32 +0100
rabbitmq-server (2.8.1-1) unstable; urgency=low
* New upstream release
-- Emile Joubert <em...@rabbitmq.com> Fri, 23 Mar 2012 10:05:24 +0000
rabbitmq-server (2.8.0-1) unstable; urgency=low
* New upstream release
-- Emile Joubert <em...@rabbitmq.com> Tue, 20 Mar 2012 11:55:10 +0000
** Changed in: rabbitmq-server (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/1018001
Title:
Please sync rabbitmq-server 2.8.4 from Debian
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1018001/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
