>
> In the short term we only need to fix the few projects with conflicting
> requirements. In the longer term we could have a concerted effort to
> move those dependencies. Someone creative might even be able to script
> it, since we do have a list of the blacklisted items.
>
Agree this is someth
Excerpts from Jim Rollenhagen's message of 2018-04-20 09:05:23 -0400:
> On Fri, Apr 20, 2018 at 7:33 AM, Jim Rollenhagen
> wrote:
>
> > On Thu, Apr 19, 2018 at 3:21 PM, Doug Hellmann
> > wrote:
> >>
> >>
> >> Reading through that log more carefully, I see an early attempt to pin
> >> pycodestyle
Excerpts from Jim Rollenhagen's message of 2018-04-20 07:33:51 -0400:
> On Thu, Apr 19, 2018 at 3:21 PM, Doug Hellmann
> wrote:
> >
> >
> > Reading through that log more carefully, I see an early attempt to pin
> > pycodestyle <= 2.3.1 [1], followed later by pycodestyle == 2.4.0 being
> > pulled i
On Fri, Apr 20, 2018 at 7:33 AM, Jim Rollenhagen
wrote:
> On Thu, Apr 19, 2018 at 3:21 PM, Doug Hellmann
> wrote:
>>
>>
>> Reading through that log more carefully, I see an early attempt to pin
>> pycodestyle <= 2.3.1 [1], followed later by pycodestyle == 2.4.0 being
>> pulled in as a dependency
On Thu, Apr 19, 2018 at 3:21 PM, Doug Hellmann
wrote:
>
>
> Reading through that log more carefully, I see an early attempt to pin
> pycodestyle <= 2.3.1 [1], followed later by pycodestyle == 2.4.0 being
> pulled in as a dependency of flake8-import-order==0.12 when neutron's
> test-requirements.tx
Excerpts from Jim Rollenhagen's message of 2018-04-18 13:44:08 -0400:
> Hi all,
>
> We have a number of stable branch jobs failing[0] with an error about pep8
> not being importable[1], when it's clearly installed[2]. We first saw this
> when installing networking-generic-switch on queens in our m
>
> This looks like some behavior that has been pulled out as part of pbr 4
> (version 3 is being used in the stable branch). Perhaps we want to
> update the pbr constraint there to use the newer version?
>
And it looks like doing that for stable/queens, at least from an
ironic-inspector point of
Excerpts from Jim Rollenhagen's message of 2018-04-18 13:44:08 -0400:
> Hi all,
>
> We have a number of stable branch jobs failing[0] with an error about pep8
> not being importable[1], when it's clearly installed[2]. We first saw this
> when installing networking-generic-switch on queens in our m
Hi all,
We have a number of stable branch jobs failing[0] with an error about pep8
not being importable[1], when it's clearly installed[2]. We first saw this
when installing networking-generic-switch on queens in our multinode
grenade job. We hacked a fix there[3], as we couldn't figure it out and
