Your message dated Wed, 12 Apr 2017 19:19:39 +0200 with message-id <20170412171937.ga1...@ugent.be> and subject line Re: Bug#856610: unblock: sqlalchemy/1.1.5+ds1-1 has caused the Debian Bug report #856610, regarding unblock: sqlalchemy/1.1.5+ds1-1 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 856610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: release.debian.org Severity: normal User: release.debian....@packages.debian.org Usertags: unblock Please unblock package sqlalchemy 1.1 - it was in unstable for a very long time and was my plan to ship it in Strech since the first beta release of 1.1.0. Upstream author provides best unit test coverage I've seen in an Open Source project and cares about stability and compatibility a lot (+ provides very detailed migration guides). A lot of packages needed an update for 1.1 but it was mostly a rebuild & check (I was generating << X.Y+1 dependency for each package that depended on X.Y release before 1.1 one), this work was done long before freeze. It was supposed to be done even sooner, but I kept it in experimental for over a month due to miscommunication with another developer. I've missed few packages (and was busy with RL) so it didn't propagate to testing on time. Packages that blocked the migration are: ceilometer, murano, ceilometer and mistral - see below. ceilometer and murano NMUs have just a requirements.txt tiny patch to drop << 1.1 dependency. requirements.txt is used in Python world for recommended env. (in contrast to setup.py's requires.txt which is supposed to list minimum required dependencies) - unfortunately OpenStack upstream decided to not bother with it and just copy requirements.txt into requires.txt - a lot of OS packages were patched for this reason (thanks to OS team!), unfortunately I've missed two. mistral 3.0.0-2 was uploaded on 24 Oct 2016 with sqlalchemy >= 1.1 dependency so it didn't migrate to testing due to missing SA 1.1 All other python-sqlalchemy and python3-sqlalchemy rev. dependencies are already in testing because, as I mentioned before, sqlalchemy no longer generates (via dh_python{2,3}) <<X.Y dependency by default so they migrated even though SA 1.1 isn't in testing. Thanks in advance and sorry for not taking care of it more carefully before the freeze. unblock sqlalchemy/1.1.5+ds1-1 unblock murano/1:3.0.0-3.1 unblock ceilometer/1:7.0.1-1.1 unblock mistral/3.0.0-2
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Hi, On Tue, Apr 04, 2017 at 08:50:21AM +0200, Piotr Ożarowski wrote: > Subject: Re: Bug#856610: unblock: sqlalchemy/1.1.5+ds1-1 Unfortunately, it's too late to move to a new upstream version. The freeze is about limiting changes, and this change looks like the opposite. We would need a very compelling reason to accept such a change, and 'we were too late' isn't that reason. Cheers, Ivo
--- End Message ---
