Phil Hagelberg <p...@hagelb.org> writes: > Aha; an easy solution! > > sudo cowbuilder --create > > I wonder why the error message didn't mention this if it's so simple? > > Well, unfortunately it doesn't actually work, and yet again neither the > error message nor the documentation give any hint as to how to clear out > the bad state or fix the root cause. (sensing a trend here!)
OK, so purging pbuilder and cowbuilder and doing a reinstall did the trick. I can see the problem is not that git is missing; it's that it needs to run from inside a git repository. This has actually been fixed upstream: https://lists.sr.ht/~technomancy/fennel/patches/54721 However, if I just apply that patch to my packaging repo, it fails due to "unexpected upstream changes". dpkg-source: warning: upstream signing key but no upstream tarball signature dpkg-source: info: using source format '3.0 (quilt)' dpkg-source: info: building fennel using existing ./fennel_1.5.1+dfsg.orig.tar.gz dpkg-source: info: local changes detected, the modified files are: fennel/test/irc.lua dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/fennel_1.5.1+dfsg-1.diff.fxl6sP I guess applying the patch directly in git is not allowed for some reason. However, placing the patch into the debian/patches directory and referencing it from debian/patches/series seems to allow "gbp buildpackage --git-pbuilder" to succeed! Great. However, now the upload to mentors is broken: $ dput mentors ../fennel_1.5.1+dfsg-1_amd64.changes Checking signature on .changes gpg: ../fennel_1.5.1+dfsg-1_amd64.changes: error 58: gpgme_op_verify gpgme_op_verify: GPGME: No data And for some reason adding the "--git-pbuilder" flag to gbp buildpackage caused it to stop even bothering to run lintian on the package? That doesn't seem good. Happy to take any advice from here. Seems like every step forward is also a step backwards. thanks, Phil
signature.asc
Description: PGP signature
