Re: Can't sign my packages
On Fri, 19 Jan 2001, Neal H Walfield wrote:
> > In the mean time, can I sign them "by hand" after the package build?
>
> Do the following:
>
> # dpkg-buildpackage -B "-mMe <me@debian.org>"
Well, only if I'm doing an NMU. Actually I used the following:
dpkg-buildpackage -uc -us -rfakeroot 2>&1 |../build.log
The -uc and -us are necessary because without them the failed attempt to
sign results in no .changes file being generated.
>
> Then use debsign.
>
dwarf@dwarf:~/.outbox$ debsign ae_962-27_i386.changes
signfile ae_962-27.dsc Dale Scheetz <dwarf@polaris.net>
gpg: skipped `Dale Scheetz <dwarf@polaris.net>': secret key not available
gpg: [stdin]: clearsign failed: secret key not available
/usr/bin/debsign: GPG error occurred!
If you are using gpg version >= 1.0.3-2 and saw a gpg error message:
error loading extension: /usr/lib/gnupg/rsa(ref)
above, please remove the load-extension rsa or load-extension rsaref
line in your ~/.gnupg/options file to ensure the correct functioning of
this (and possibly other) programs.
Aborting....
dwarf@dwarf:~/.outbox$
Same error. I looked at the script but couldn't find my way.
I don't see any impediment to doing this by hand, although it doesn't
answer why the "normal" tools aren't working for me. I can:
1. gpg --clearsign the .dsc file.
2. Do md5sum on the signed .dsc file.
3. Edit .changes to reflect the new, correct md5sum.
4. gpg --clearsign the .changes file.
The package should now be ready for upload, right?
Still uncertain,
Dwarf
--
_-_-_-_-_- Author of "The Debian Linux User's Guide" _-_-_-_-_-_-
aka Dale Scheetz Phone: 1 (850) 656-9769
Flexible Software 11000 McCrackin Road
e-mail: dwarf@polaris.net Tallahassee, FL 32308
_-_-_-_-_-_- See www.linuxpress.com for more details _-_-_-_-_-_-_-
Reply to: