Excerpts from Gaetan's message of 2018-01-15 19:29:01 +0100:
> >
> >
> > > I guess it somehow didn't used my build of the pbr package when
> > > running in gitlab pipeline.
> >
> > It sounds like the CE pipeline is not building packages in the same way?
> > Or is using an old version of pbr?
> >
>
>
>
> > I guess it somehow didn't used my build of the pbr package when
> > running in gitlab pipeline.
>
> It sounds like the CE pipeline is not building packages in the same way?
> Or is using an old version of pbr?
>
> I guess it was the pbr version from pypi.python.org, not my customized
build
Excerpts from Gaetan's message of 2018-01-15 17:29:01 +0100:
> First, thanks a lot for your support and your kindness ! Really appreciate
> that :)
>
> > > Do you know where I need to hack PBR to fix it?
> >
> > So 'pbr' correctly parses the prefixed tags, but it's just the output
> > packages (sd
First, thanks a lot for your support and your kindness ! Really appreciate
that :)
> > Do you know where I need to hack PBR to fix it?
>
> So 'pbr' correctly parses the prefixed tags, but it's just the output
> packages (sdists, wheels) that always unversioned? If so, this sounds
> correct. Pytho
On Tue, 2018-01-09 at 10:25 +0100, Gaetan wrote:
> Hello
>
> I have submitted this patch ([1]) that add support for v_version in
> PBR. Basically I can tag v1.0.0 instead of 1.0.0 to release 1.0.0.
>
> However, after rework it appears PBR does not behaves well, even if
> the unit tests pass:
> On
Excerpts from Jeremy Stanley's message of 2018-01-15 14:40:14 +:
> On 2018-01-09 10:25:56 +0100 (+0100), Gaetan wrote:
> > I have submitted this patch ([1]) that add support for v_version
> > in PBR. Basically I can tag v1.0.0 instead of 1.0.0 to release
> > 1.0.0.
> [...]
>
> Looks like the p
On 2018-01-09 10:25:56 +0100 (+0100), Gaetan wrote:
> I have submitted this patch ([1]) that add support for v_version
> in PBR. Basically I can tag v1.0.0 instead of 1.0.0 to release
> 1.0.0.
[...]
Looks like the patch you linked has since merged. Any issues with it
so far?
> Second point, to go
Hello
I have submitted this patch ([1]) that add support for v_version in PBR.
Basically I can tag v1.0.0 instead of 1.0.0 to release 1.0.0.
However, after rework it appears PBR does not behaves well, even if the
unit tests pass:
On tag for instance v1.0.0, the result packages in named
`-1.0.0.de
