[Openstack] [oslo] Issues with pbr when building custom packages

Sam Morrison sorrison at gmail.com
Wed Jun 15 00:14:50 UTC 2016


Hi Jeremy,

Setting the environment variable still doesn’t work as it is still required to meet the PBR standard.

It would be great to fix the docs and get PBR to follow PEP440 if that is intended. 

Eg. I should be able to set a version like 12.0.3.post74+gea340da

Thanks,
Sam


> On 10 Jun 2016, at 4:25 AM, Jeremy Stanley <fungi at yuggoth.org> wrote:
> 
> On 2016-06-09 08:16:11 +1000 (+1000), Sam Morrison wrote:
> [...]
>> I'm packaging nova, we have a bunch of custom commits and extra
>> back ports in our version. Having the git hash in there is
>> extremely helpful and I also don't want to conflict with the
>> official openstack release.
> [...]
> 
> I don't know whether it helps for your case, but the solution PBR
> implemented for that when it switched to PEP-440+semver (prior to
> that PBR _did_ include abbreviated Git SHAs in our version strings)
> was to store it in Python packaging metadata and add a separate
> command-line tool to list it. If the pbr library is installed into
> your environment, it includes an executable "pbr" entrypoint with a
> "freeze" subcommand with output similar to pip freeze except
> indicating the abbreviated Git SHAs included from the pbr.json file
> in each corresponding egg-info tree as an inline comment.
> -- 
> Jeremy Stanley
> 
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack





More information about the Openstack mailing list