I've made some progress: - latest unsuccessful builds were made with "gbp buildpackage --git-builder="debuild -i -I --no-sign --build=binary" --git-verbose --git-pristine-tar" - if I build in the same environment (sid chroot) the same sources with "dpkg-buildpackage --no-sign --build=binary" instead, there is no attempt to sign anything.
This may seem to show that gbp does not pass the right option to debuild. However, when I look at the log of the first builds with gbp, there is: dpkg-buildpackage -rfakeroot -us -uc -i -I --no-sign --build=binary --build=binary The only thing strange is the repeated "--build=binary", but the "--no-sign" is there. Then, if I compare both logs, the following lines do not appear at the end of the dpkg build log: Now running lintian... W: libapr1-dev: embedded-javascript-library usr/share/doc/libapr1-dev/html/jquery.js please use libjs-jquery N: 1 tag overridden (1 warning) Finished running lintian. Now signing changes and any dsc files... signfile buildinfo apr_1.6.2-1_amd64.buildinfo 5F0C7CD8 gpg: signing failed: Permission denied gpg: /tmp/debsign.zUjNz62i/apr_1.6.2-1_amd64.buildinfo: clear-sign failed: Permission denied debsign: gpg error occurred! Aborting.... On Mon, Sep 18, 2017 at 9:55 AM, jean-christophe manciot < actionmysti...@gmail.com> wrote: > @Osamu Aoki > You say --no-sign and --unsigned-buildinfo options are unsupported by > dpkg-buildpackage, but: > # dpkg-buildpackage --help | grep -- no-sign > --no-sign do not sign any file. > # dpkg-buildpackage --help | grep -- unsigned-buildinfo > -ui, --unsigned-buildinfo unsigned .buildinfo file. > > > On Mon, Sep 18, 2017 at 1:35 AM, Osamu Aoki <osamu.a...@tc4.so-net.ne.jp> > wrote: > >> Hi, >> >> On Sun, Sep 17, 2017 at 07:58:16PM +0200, Guillem Jover wrote: >> > Control: reassign -1 devscripts >> > >> > Hi! >> > >> > On Sun, 2017-09-17 at 15:36:00 +0200, jean-christophe manciot wrote: >> > > Package: dpkg-dev >> > > Version: 1.18.24 >> > >> > > With --unsigned-buildinfo: >> > > ... >> > > Finished running lintian. >> > > Now signing changes and any dsc files... >> > > signfile buildinfo apr_1.6.2-1_amd64.buildinfo xxxxxxxxxxxxxxxxxxxxx >> > > gpg: signing failed: Permission denied >> > > gpg: /tmp/debsign.8axXeL81/apr_1.6.2-1_amd64.buildinfo: clear-sign >> failed: >> > > Permission denied >> > > debsign: gpg error occurred! Aborting.... >> > > debuild: fatal error at line 1053: >> > > running debsign failed >> > > gbp:error: 'debuild -i -I --unsigned-source --unsigned-changes >> > > --unsigned-buildinfo --build=binary' failed: it exited with 29 >> > > >> > > With --no-sign: >> > > Now signing changes and any dsc files... >> > > signfile buildinfo apr_1.6.2-1_amd64.buildinfo xxxxxxxxxxxxxxxxxxx >> > > gpg: signing failed: Permission denied >> > > gpg: /tmp/debsign.Lu3ErY9E/apr_1.6.2-1_amd64.buildinfo: clear-sign >> failed: >> > > Permission denied >> > > debsign: gpg error occurred! Aborting.... >> > > debuild: fatal error at line 1053: >> > > running debsign failed >> > > gbp:error: 'debuild -i -I --no-sign --build=binary' failed: it exited >> with 29 >> > >> > This would be a problem with debuild, which disables signing by >> > default via -us -uc, signs then by itself with debsign, and does not >> > understand itself --unsigned-buildinfo nor --no-sign. Reassigning. >> >> As I see the source of debuild, its certainly lacks this new buildinfo >> related options. But it lacks few more features including some long >> options. >> >> Supported dpkg-buildpackage options: >> --force-sign >> -us >> -uc >> >> >> Unsupported dpkg-buildpackage options: >> --no-sign >> --unsigned-source >> --unsigned-changes >> -ui >> --unsigned-buildinfo >> >> Hmmm.... not so difficult >> >> Osamu >> >> >> >> >> >> >> > Thanks, >> > Guillem >> > >> > _______________________________________________ >> > devscripts-devel mailing list >> > devscripts-de...@lists.alioth.debian.org >> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/devs >> cripts-devel >> > > > > -- > Jean-Christophe > -- Jean-Christophe
