[openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures
doug at doughellmann.com
Wed Mar 1 14:13:49 UTC 2017
Excerpts from Sean Dague's message of 2017-03-01 07:57:31 -0500:
> On 03/01/2017 12:26 AM, Tony Breeds wrote:
> > Hi All,
> > Earlier today the release team tagged PBR 2.0.0. The reason for the major
> > version bump is because warnerrors has been removed in favor of
> > warning-is-error from sphinx >= 1.5.0.
> > It seems that several projects outside both inside and outside OpenStack have
> > capped pbr <2.0.0 so we can't actually use this release yet. The requirements
> > team will work with all projects to remove the cap of pbr in those projects.
> > The good news is that projects using upper-constraints.txt are insulated from
> > this and shouldn't be affected. However upper-constraints.txt isn't being used
> > by all projects and *those* projects will start seeing
> > ContextualVersionConflicts: (pbr 2.0.0 in gate logs. It's recommended that
> > those projects add a local ban for pbr and associate it with:
> > https://bugs.launchpad.net/openstack-requirements/+bug/1668848
> > Then once the situation is resolved we can unwind and remove the temporary caps.
> > Yours Tony.
> >  There is at least 1 corner case where the coverage job installed directly
> > from a git URL and therefore that wasn't protected.
> So, I feel like we hit a similar issue around Vancouver with a pbr bump.
> Can we stop capping pbr per rule now?
Tony identified caps in 5 OpenStack community projects (see ) as well
as powervm and python-jsonpath-rw-ext. Pull requests to those other
projects are linked from the bug .
The sqlalchemy-migrate 0.11.0 release should fix that library. The
release team will prioritize releases for the other dependencies today
as they come in.
More information about the OpenStack-dev