[all] Lower-constraints in some projects broken - update your repos
radoslaw.piliszek at gmail.com
Fri Apr 17 18:40:51 UTC 2020
Yeah. That is all true.
I just wanted to let you know that lower-constraints may break more
often when run outside of CI.
That said, what should lower-constraints really include?
I understand  that it should just explicitly ask for specific
versions of packages in requirements.txt
However, per what Sean just told me , it is seemingly not enough.
All in all, it passed CI checks successfully. :-)
On Fri, Apr 17, 2020 at 8:09 PM Jeremy Stanley <fungi at yuggoth.org> wrote:
> On 2020-04-17 19:47:22 +0200 (+0200), Radosław Piliszek wrote:
> > Sorry for lack of example, here it is:
> > https://b702c277c3869af6f0a9-3df34f04e18be629eb587340c626577b.ssl.cf5.rackcdn.com/720754/3/check/openstack-tox-lower-constraints/9960fdf/tox/lower-constraints-1.log
> > Collecting MarkupSafe==1.0
> > Downloading http://mirror.bhs1.ovh.openstack.org/wheel/ubuntu-18.04-x86_64/markupsafe/MarkupSafe-1.0-cp36-cp36m-linux_x86_64.whl
> > (31 kB)
> Yep, so in that case the job is fetching a Markupsafe wheel we
> pre-built with Python 3.6 on Ubuntu 18.04 (Bionic) for 64-bit x86
> CPU architectures. That seems normal. If we didn't provide that in
> the configured wheelhouse, pip would retrieve the Markupsafe sdist
> and build an equivalent platform-specific wheel at job runtime to
> install instead.
> The build log you linked shows a failure unrelated to the Markupsafe
> ERROR: No matching distribution found for mypy==0.6 (from -c
> (line 43))
> The output leading up to that seems to indicate that mypy==0.6 is
> not a valid/available package version on PyPI, and indeed
> https://pypi.org/project/mypy/#history confirms that to be the case.
> Jeremy Stanley
More information about the openstack-discuss