Your message dated Thu, 15 Mar 2018 15:58:56 +0100
with message-id <20180315145856.wonm7fblafm7y...@sar0.p1otr.com>
and subject line 1.2.5 uploaded to unstable
has caused the Debian Bug report #891331,
regarding Beta from SQLA are *not* to upload, and full of bugs
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.)
--
891331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sqlalchemy
Version: 1.2.0~b2+ds1-1
Severity: grave
Dear maintainer,
According to Mike Bayer, upstream for SQLAlchemy, you should *not* upload any
beta release of SQLAlchemy. Indeed, the version in Experimental has bugs,
for example this one:
http://docs.sqlalchemy.org/en/latest/changelog/changelog_12.html#change-dff3a469788c81a46440584406cb22be
This issue causes more than 600 unit test failures in Nova, about 32 in Manila,
and so on. This makes it impossible for me to run unit tests of OpenStack
Queens using sbuild and experimental, as this bad version of SQLAlchemy in
Experimental render unit tests as broken, when they are not (SQLA 1.2.0~b2 is).
Please upload a working version of SQLA in Experimental, for example 1.2.1,
which is accepted by OpenStack, as per this document:
https://github.com/openstack/requirements/blob/stable/queens/upper-constraints.txt#L136
Thanks for your work on SQLA,
Cheers,
Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 87334
--- End Message ---
