[pkg-gnupg-maint] Problem signing packages

Daniel Kahn Gillmor dkg at fifthhorseman.net
Mon May 23 15:11:19 UTC 2016


Hi Marwan--

On Fri 2016-05-13 05:11:24 -0700, Marwan Rabbâa wrote:
> I try to create a repository for debian.
>
> I have built a package in /tmp/debian/postgrest_0.3.1_amd64.deb and
> successfully created a gpg key in ~/.gpg.
>
> This command :
> reprepro -VV --gnupghome ~/.gpg --ask-passphrase --basedir /var/repo/apt
> includedeb wheezy /tmp/debian/postgrest_0.3.1_amd64.deb
>
> five me

i don't know what "five me" means here, sorry!

> Created directory "/var/repo/apt/pool/main"
> Created directory "/var/repo/apt/pool/main/p"
> Created directory "/var/repo/apt/pool/main/p/postgrest"
> Adding reference to 'pool/main/p/postgrest/postgrest_0.3.1_amd64.deb' by
> 'wheezy|main|amd64'
> Exporting indices...
>  looking for changes in 'wheezy|main|amd64'...
>   creating '/var/repo/apt/dists/wheezy/main/binary-amd64/Packages'
> (uncompressed,gzipped)
>  generating main/Contents-amd64...
> Reading filelist for pool/main/p/postgrest/postgrest_0.3.1_amd64.deb
> gpgme gave error GPGME:11:  Bad passphrase
> ERROR: Could not finish exporting 'wheezy'!
> This means that from outside your repository will still look like before
> (and
> should still work if this old state worked), but the changes intended with
> this
> call will not be visible until you call export directly (via reprepro
> export)
> Changes will also get visible when something else changes the same file and
> thus creates a new export of that file, but even changes to other parts of
> the
> same distribution will not!
> There have been errors!
>
>
> How can I sign my package ?

what version of gpg are you running?

are you able to successfully sign an example file outside of reprepro?

you can find the answers to these questions with:

 gpg --version

and:

 echo test > test.txt
 gpg --sign test.txt



    --dkg



More information about the pkg-gnupg-maint mailing list