On Wed, Oct 30, 2019 at 11:35:02AM -0600, Jerome wrote:
> Dear all
> I've trying to compile deb package of SoGE, using the repo on Gitlab
> "https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.com%2Floveshack%2Fsge.git&data=02%7C01%7C%7C84d5d6edaa654f31dda808d75d60880d%7C1faf88fea9984c5b93c9210a11d9a5c2%7C0%7C1%7C637080541498659015&sdata=PlYUilnu70Egl%2BLOSTq5mP7bdkKZcvqZHQRRtT%2FiFZU%3D&reserved=0";.
> 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 ?

It's defaulting to trying to sign with Dave Love's private key which you do not 

You should be able to fix this either by using the -k option to 
dpkg-buildpackage to
specify your own key or --no-sign to specify that everything should be unsigned.


Attachment: signature.asc
Description: PGP signature

users mailing list

Reply via email to