[git-buildpackage] Bad command paths when installing through pip

Guido G√ľnther agx at sigxcpu.org
Thu Apr 29 10:52:05 CEST 2021


Hi Quanah,
On Wed, Apr 28, 2021 at 01:53:49PM -0700, Quanah Gibson-Mount wrote:
> When installing with pip, gbp defaults to the wrong path for commands like
> gbp-builder-mock:
> 
> gbp buildpackage-rpm
> 
> /bin/sh: /usr/share/git-buildpackage/gbp-builder-mock: No such file or
> directory
> gbp:error: '/usr/share/git-buildpackage/gbp-builder-mock -ba --define
> '_topdir /home/build/git/symas/rpmbuild' --define '_specdir %_topdir/SPECS'
> --define '_sourcedir %_topdir/SOURCES' openssl.spec' failed: it exited with
> 127

You should be able to override this via the `--git-builder` option. We
don't adjust these for the pip based installs atm.

> ls /usr/local/bin/
> gbp  gbp-builder-mock  git-pbuilder
> 
> Also, the man pages seem to be missing:
> 
> find . -name "*gbp*"
> ./share/git-buildpackage/gbp.conf
> ./bin/gbp
> ./bin/gbp-builder-mock
> ./lib/python3.6/site-packages/gbp
> ./lib/python3.6/site-packages/gbp-0.9.22-py3.6.egg-info
> 
> find . -name "*rpm*"
> ./lib/python3.6/site-packages/gbp/rpm
> ./lib/python3.6/site-packages/gbp/rpm/lib_rpm.py
> ./lib/python3.6/site-packages/gbp/rpm/__pycache__/lib_rpm.cpython-36.pyc
> ./lib/python3.6/site-packages/gbp/scripts/rpm_ch.py
> ./lib/python3.6/site-packages/gbp/scripts/buildpackage_rpm.py
> ./lib/python3.6/site-packages/gbp/scripts/import_srpm.py
> ./lib/python3.6/site-packages/gbp/scripts/pq_rpm.py
> ./lib/python3.6/site-packages/gbp/scripts/__pycache__/rpm_ch.cpython-36.pyc
> ./lib/python3.6/site-packages/gbp/scripts/__pycache__/pq_rpm.cpython-36.pyc
> ./lib/python3.6/site-packages/gbp/scripts/__pycache__/import_srpm.cpython-36.pyc
> ./lib/python3.6/site-packages/gbp/scripts/__pycache__/buildpackage_rpm.cpython-36.pyc
> 
> 
> 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.
Cheers,
 -- Guido

> 
> Regards,
> Quanah
> 
> 
> --
> 
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <http://www.symas.com>
> _______________________________________________
> git-buildpackage mailing list
> git-buildpackage at lists.sigxcpu.org
> http://lists.sigxcpu.org/mailman/listinfo/git-buildpackage


More information about the git-buildpackage mailing list