Re: Updating Celery, Kombu, python-amqp

2017-03-24 Thread Thomas Goirand
On 03/24/2017 09:30 AM, Brian May wrote: > So if we upgrade python-amqp *and* that (worse case) requires > python-oslo.messaging be upgraded too, that is a lot of packages (listed > below) that *directly* depend on python-oslo.messaging. Eventually we > will have to deal with this, maybe during the

Re: Updating Celery, Kombu, python-amqp

2017-03-24 Thread Christopher Hoskin
4.0.2+really3.0.35+dfsg-2 has been accepted into unstable. Hopefully that sorts this mess out for now. Thanks for your patience. Christopher On 24 March 2017 at 11:22, Christopher Hoskin wrote: > Agreed - I didn't know that was an option before. I'll try it this > evening, unless someone beats

Re: Updating Celery, Kombu, python-amqp

2017-03-24 Thread Christopher Hoskin
Agreed - I didn't know that was an option before. I'll try it this evening, unless someone beats me to it. Thank you for your help. Christopher On 24 March 2017 at 11:18, Scott Kitterman wrote: > > > On March 24, 2017 4:30:12 AM EDT, Brian May wrote: > ... >>Alternative: maybe I should go to t

Re: Updating Celery, Kombu, python-amqp

2017-03-24 Thread Scott Kitterman
On March 24, 2017 4:30:12 AM EDT, Brian May wrote: ... >Alternative: maybe I should go to the other plan of uploading the old >version of kombu with an increased epoch? Please use newversion+reallyoldverssion instead of an epoch. It's generally better to avoid epochs for temporary issues like

Re: Updating Celery, Kombu, python-amqp

2017-03-24 Thread Brian May
Michael Fladischer writes: > This seems to be the best way to deal with this. I don't think that > python-amqp 2.x should be uploaded to unstable as it would potentially > break a lot of things in OpenStack. I will wait a little bit in case there is a response to https://bugs.debian.org/858586,

Re: Updating Celery, Kombu, python-amqp

2017-03-24 Thread Brian May
Christopher Hoskin writes: > I've filed a bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858586 > > Very sorry about this mess. This is what comes of trying to do > something complex and precise late at night after a long day's work :( I can't complain. I have also accidentally uploaded

Re: Updating Celery, Kombu, python-amqp

2017-03-24 Thread Michael Fladischer
On 2017-03-24 03:55, Brian May wrote: > * Upload previous Kombu to unstable, using an epoch for the version (and > all subsequent uploads). This seems to be the best way to deal with this. I don't think that python-amqp 2.x should be uploaded to unstable as it would potentially break a lot of thin

Re: Updating Celery, Kombu, python-amqp

2017-03-24 Thread Brian May
Christopher Hoskin writes: > What worries me is: > > apt-rdepends -r python-amqp I wasn't aware of this command. Thanks for this. If I understand this command correctly, it is showing everything that depends directly and indirectly on python-amqp? Hmm. Looks like a large number of these are du