On 11/03/2017 01:04 AM, Felipe Sateler wrote: > > > On Thu, Nov 2, 2017 at 8:25 PM, Thomas Goirand <z...@debian.org > <mailto:z...@debian.org>> wrote: > > On 11/02/2017 08:02 PM, Felipe Sateler wrote: > > On Wed, Nov 1, 2017 at 11:44 PM, Jason Pleau <ja...@jpleau.ca > <mailto:ja...@jpleau.ca>> wrote: > >> Hi Thomas > >> > >> On 11/01/2017 08:51 PM, Thomas Goirand wrote: > >>> Hi, > >>> > >>> Could you please upload the 2.x version of python-docker into Sid? > I've > >>> uploaded python-zunclient that needs it. > >>> > >> > >> It's been a while, I think what we (still) have to do is get the > >> rdepends updated to work with the latest python-docker. I don't think > >> anyone looked at that yet. > > > > Yes, this work was pending. I never filed the bugs (sorry!), but my > > earlier investigations showed that all rdeps had been fixed upstream, > > but not released yet. > > > > I see now that you have already fixed all of them! (magnum 5.0 and > > senlin 4 both work with python-docker 2.x, and you mention zunclient). > > > >> > >> We welcome help of course, I will take some time this weekend to see > >> what exactly needs to be done and start doing some work. > > > > I think all that needs to be done is to: > > > > 1. Declare Breaks: python-magnum (<< 5.0), python-senlin (<< 4.0), > > docker-compose (<< 1.10). > > 2. Same for python3 versions > > 3. Prepare docker-compose >= 1.10 > > 4. Upload python-docker to unstable > > 5. Upload docker-compose to unstable > > > > I don't have much time this week though to work on this. > > > > @zigo: if you want to move faster with 1, 2, and 4, please go ahead > > (repo is at collab-maint), but make sure to file a (serious) bug to > > docker-compose so that we don't forget to do 3 and 5. > > > >> (sorry for the delays on this (I honestly just forgot to follow up..) > > > > I had forgotten about this too. Oops! > > I don't think there's the need to declare such a break, since I uploaded > senlin 4 and magnum 5 to Sid. > > > It is still necessary because old senlin (and magnum) can't work with > new python-docker. So partial upgrades from stretch could break if they > are not added.
This issues may happen in Sid and/or testing, that you're right. I've added the Breaks: as you suggested. > I'm not sure how docker-compose is involved here... > > > Because it also depends on python-docker, and also needs a new version > to handle python-docker 2.x... Should it be an updated to the latest 1.17.0 version? Can I do it? I'm a bit scared to break anything by upgrading to the wrong version here. Otherwise I don't mind doing the work. Cheers, Thomas Goirand (zigo)
