Bug#856610: unblock: sqlalchemy/1.1.5+ds1-1

2017-04-04 Thread Piotr Ożarowski
Control: tags -1 - moreinfo > that's because Thomas overwrote my NMU with another upload, please give > me some time to talk with him Thomas added my changes back, all 3 OpenStack packages have ">=" dependency only (no "<<" anymore)

Bug#856610: unblock: sqlalchemy/1.1.5+ds1-1

2017-04-03 Thread Piotr Ożarowski
[Niels Thykier, 2017-04-03] > > 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 > > > > I cannot exactly say I am trilled with this change. But starting from > the bottom, something is definitely wrong. AFAICT, the

Bug#856610: unblock: sqlalchemy/1.1.5+ds1-1

2017-04-03 Thread Niels Thykier
Control: tags -1 moreinfo Piotr Ożarowski: > 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

Bug#856610: unblock: sqlalchemy/1.1.5+ds1-1

2017-03-16 Thread Piotr Ożarowski
FYI: I plan to upload sqlalchemy 1.1.6+ds1-1 (i.e. a new upstream release in 1.1.X series). I assume if you will allow 1.1.5, then there's no reason to not allow 1.1.6 - i.e. next bug fix release in 1.1 series. Note that upstream already started working on 1.2 series which I'm not considering for

Bug#856610: unblock: sqlalchemy/1.1.5+ds1-1

2017-03-02 Thread Piotr Ożarowski
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