On Sun Jul 27 2014 08:51:03 AM HKT, Brian May
wrote:
> Ok, good, glad to have a second opinion on this. I couldn't see any more
> reverse dependencies myself, good to get this confirmed. Wish there was
> some way of simulating what packages would be affected if one is removed,
> but I couldn't
On 26 July 2014 17:30, Thomas Goirand wrote:
> Brian, thanks a lot for all the details that you're giving on the
> message below.
>
No problem. Glad to be able to help.
> Since python-kombu doesn't depend on anymore on python-librabbitmq, and
> that it migrated to Jessie, we don't have any re
Hi,
Brian, thanks a lot for all the details that you're giving on the
message below.
Since python-kombu doesn't depend on anymore on python-librabbitmq, and
that it migrated to Jessie, we don't have any reverse dependencies for
python-librabbitmq anymore. So probably, it'd be a good idea to just
Hello,
Thank you for your email.
I assume you are reacting to the "is marked for autoremoval from testing"
you would have received from Debian.
Unfortunately, as much as these are scary looking messages, I believe I had
already resolved the issue. I sent a email to debian-python mailing list,
ho
Hi Brian,
You wrote:
> I believe this bug makes python-amqp unusable, and as a result, Grave
> is justified.
>
> "grave: makes the package in question unusable or mostly so, or
> causes data loss, or introduces a security hole allowing access to
> the accounts of users who use the package"
thoug
severity grave
thanks
I believe this bug makes python-amqp unusable, and as a result, Grave is
justified.
"grave:
makes the package in question unusable or mostly so, or causes data loss,
or introduces a security hole allowing access to the accounts of users who
use the package"
--
Brian May
__
6 matches
Mail list logo
