On 01/26/2015 12:32 AM, Alan Milligan wrote:
Brian,
Thanks for the detailed response.
On 01/24/2015 12:27 AM, Brian Bouterse wrote:
Hi Alan,
The PR history is a little misleading associated with BZ 1141336. The
bug target release is 2.6.0 which is correct, the rabbitMQ fix is only
in
On 01/26/2015 12:32 AM, Alan Milligan wrote:
Brian,
Thanks for the detailed response.
On 01/24/2015 12:27 AM, Brian Bouterse wrote:
Hi Alan,
The PR history is a little misleading associated with BZ 1141336. The
bug target release is 2.6.0 which is correct, the rabbitMQ fix is only
in
Brian,
Thanks for the detailed response.
On 01/24/2015 12:27 AM, Brian Bouterse wrote:
Hi Alan,
The PR history is a little misleading associated with BZ 1141336. The bug
target release is 2.6.0 which is correct, the rabbitMQ fix is only in 2.6.0. It
was merged to 2.5-dev in preparation to
-bastion.net
To: pulp-list@redhat.com
Sent: Thursday, January 22, 2015 8:46:07 PM
Subject: [Pulp-list] Pulp 2.5.x and rabbitmq bug 1141336
Hi guys,
According to https://bugzilla.redhat.com/show_bug.cgi?id=1141336:
this fix made 2.5-dev and master; however it never showed up in any of
the 2.5
Hi guys,
According to https://bugzilla.redhat.com/show_bug.cgi?id=1141336:
this fix made 2.5-dev and master; however it never showed up in any of
the 2.5 betas nor 2.5.2 released earlier this week.
Is/was that deliberate?
It is in the 2.6 betas but I'm not wishing to be quite that bleeding
