Excerpts from Tony Breeds's message of 2017-03-02 19:41:17 +1100:
> On Thu, Mar 02, 2017 at 06:24:32PM +1100, Tony Breeds wrote:
>
> > I know I'm talking to myself .
>
> Still.
>
> > A project on $branch without constraints is going to get pbr 2.0.0 and then
> > hit
> > version conflicts
On Thu, Mar 02, 2017 at 06:24:32PM +1100, Tony Breeds wrote:
> I know I'm talking to myself .
Still.
> A project on $branch without constraints is going to get pbr 2.0.0 and then
> hit
> version conflicts with projects that have pbr <2.0.0 caps *anyway* regardless
> of what hacking says
On Thu, Mar 02, 2017 at 06:07:47PM +1100, Tony Breeds wrote:
> On Thu, Mar 02, 2017 at 05:01:43PM +1100, Tony Breeds wrote:
>
> > And yes there are now plenty of pep8 jobs that are failing with PBR 2.0.0
> >
> > We can't revert the requirements change that landed which means that
> > projects
>
On Thu, Mar 02, 2017 at 05:01:43PM +1100, Tony Breeds wrote:
> And yes there are now plenty of pep8 jobs that are failing with PBR 2.0.0
>
> We can't revert the requirements change that landed which means that projects
> using old hacking versions are going to need an update :(
One option may
On Thu, Mar 02, 2017 at 04:41:14PM +1100, Tony Breeds wrote:
> On Thu, Mar 02, 2017 at 03:48:05PM +1100, Ian Wienand wrote:
> > On 03/02/2017 01:13 AM, Doug Hellmann wrote:
> > > Tony identified caps in 5 OpenStack community projects (see [1]) as well
> > > as powervm and python-jsonpath-rw-ext.
On Thu, Mar 02, 2017 at 03:48:05PM +1100, Ian Wienand wrote:
> On 03/02/2017 01:13 AM, Doug Hellmann wrote:
> > Tony identified caps in 5 OpenStack community projects (see [1]) as well
> > as powervm and python-jsonpath-rw-ext. Pull requests to those other
> > projects are linked from the bug [2].
On 03/02/2017 01:13 AM, Doug Hellmann wrote:
Tony identified caps in 5 OpenStack community projects (see [1]) as well
as powervm and python-jsonpath-rw-ext. Pull requests to those other
projects are linked from the bug [2].
[1] https://review.openstack.org/#/q/topic:bug/1668848
Am I nuts or
On 3/1/2017 8:13 AM, Doug Hellmann wrote:
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
On Mar 1, 2017, at 4:57 AM, Sean Dague wrote:
> I also wonder if we can grant the release team +2 permissions on
> everything in OpenStack so that fixes like this can be gotten in quickly
> without having to go chase a bunch of teams.
I would be very much opposed to this. Isn't
On Wed, Mar 1, 2017 at 2:12 PM, Doug Hellmann wrote:
> Excerpts from Doug Hellmann's message of 2017-03-01 14:04:19 -0500:
>> Excerpts from Andreas Jaeger's message of 2017-03-01 19:50:51 +0100:
>> > On 2017-03-01 17:13, Doug Hellmann wrote:
>> > > Excerpts from Andreas
Excerpts from Doug Hellmann's message of 2017-03-01 14:04:19 -0500:
> Excerpts from Andreas Jaeger's message of 2017-03-01 19:50:51 +0100:
> > On 2017-03-01 17:13, Doug Hellmann wrote:
> > > Excerpts from Andreas Jaeger's message of 2017-03-01 16:22:24 +0100:
> > >> On 2017-03-01 06:26, Tony
Excerpts from Andreas Jaeger's message of 2017-03-01 19:50:51 +0100:
> On 2017-03-01 17:13, Doug Hellmann wrote:
> > Excerpts from Andreas Jaeger's message of 2017-03-01 16:22:24 +0100:
> >> On 2017-03-01 06:26, Tony Breeds wrote:
> >>> Hi All,
> >>> Earlier today the release team tagged PBR
On 2017-03-01 17:13, Doug Hellmann wrote:
> Excerpts from Andreas Jaeger's message of 2017-03-01 16:22:24 +0100:
>> On 2017-03-01 06:26, 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
Excerpts from Andreas Jaeger's message of 2017-03-01 16:22:24 +0100:
> On 2017-03-01 06:26, 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
> >
On 2017-03-01 06:26, 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.
Can we change the sphinx==1.3.6 line in upper-constraints
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
On 01/03/2017 13:00, Sean Dague wrote:
> 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
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
18 matches
Mail list logo