[git-buildpackage] Bad command paths when installing through pip
quanah at symas.com
Thu Apr 29 17:06:47 CEST 2021
--On Thursday, April 29, 2021 11:52 AM +0200 Guido Günther
<agx at sigxcpu.org> wrote:
> You should be able to override this via the `--git-builder` option. We
> don't adjust these for the pip based installs atm.
>> I.e., the man page for buildpackage-rpm is not present. :/
> Yes, they're not being built atm. The egg is *mostly* for people wanting
> to use gbp's python classes in other projects - i've not yet heard
> that somebody using the command line tools from there (rather than
> distro packaging or building a RPM with the provided spec file).
> I'm happy to apply patches to make usage from pip better but currently
> lack the bandwidth to do so myself, sorry.
Ah, I was following the instructions from:
If not on a Debian system you can fetch the package from pypi:
pip install gbp
I would suggest an update to this page that for RPM based systems, it's
advised to build your own RPM with the provided spec file.
Additionally, it may be worthwhile setting up regular builds in the COPR
system for current versions of RHEL/CentOS and Fedora. ;) Then people
could just dnf install it without having to build out the RPM themselves
(although given what the tool is for, that may not be worth the effort).
Thanks again! I'll go the RPM route moving forward.
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
More information about the git-buildpackage