That looks like it's by design... he was signing the builds using his secret key. You'd have to figure out where he configured that and either insert your own details or turn off signing (if that's allowed).
On Wed, Oct 30, 2019 at 10:35 AM Jerome <jer...@ibt.unam.mx> wrote: > Dear all > > I've trying to compile deb package of SoGE, using the repo on Gitlab > "https://gitlab.com/loveshack/sge.git". > > I could generate some deb files, as sge_8.1.10-1_amd64.deb, > sge-common_8.1.10-1_all.deb. But got this issue : > > $ dpkg-buildpackage -b > > ../.. > dpkg-deb: building package 'sge-dbg' in '../sge-dbg_8.1.10-1_amd64.deb'. > dpkg-genbuildinfo --build=binary > dpkg-genchanges --build=binary >../sge_8.1.10-1_amd64.changes > dpkg-genchanges: info: binary-only upload (no source code included) > dpkg-source --after-build . > dpkg-buildpackage: info: binary-only upload (no source included) > signfile sge_8.1.10-1_amd64.buildinfo > gpg: skipped "Dave Love <dave.l...@manchester.ac.uk>": No secret key > gpg: dpkg-sign.rxsZlToR/sge_8.1.10-1_amd64.buildinfo: clear-sign failed: > No secret key > > dpkg-buildpackage: error: failed to sign .buildinfo file > > > Someone know what's this ? > > Regards! > > -- > -- Jérôme > L'adulte ne croit pas au père Noël. Il vote. > (Pierres Desproges) > _______________________________________________ > users mailing list > firstname.lastname@example.org > https://gridengine.org/mailman/listinfo/users >
_______________________________________________ users mailing list email@example.com https://gridengine.org/mailman/listinfo/users