Open Stack

On 2014-12-17 22:02:26 +0800 (+0800), Thomas Goirand wrote:
> I'm not sure I get it. Is this related to newer versions of SQLAlchemy?

It's related to how Setuptools 8 failed to parse our requirements
line for SQLAlchemy because it contained multiple version ranges.
That was fixed by converting it to a single range with a list of
excluded versions instead, but we still needed to "backport" that
requirements.txt entry to a version of oslo.db for stable/juno.

> If so, then from my package maintainer point of view, keeping an older
> version of SQLA (eg: 0.9.8) and oslo.db 1.0.2 for Juno is ok, right?

In the end we wound up with a 1.0.3 release of oslo.db and pinned
stable/juno requirements to oslo.db<1.1 rather than the open-ended
maximum it previously had (which was including 1.1.x and 1.2.x
versions).

> Will Kilo require a newer version of SQLA?

In this case "older" SQLAlchemy is 0.8.x (we're listing supported
0.8.x and 0.9.x versions for stable/juno still), while Kilo may
release with only a supported range of SQLAlchemy 0.9.x versions.
-- 
Jeremy Stanley