Bug#846399: RFS: rush/1.8+dfsg-1 -- New upstream's release.

[Mats Erik Andersson <mats.andersson@gisladisker.se>]

Onsdag den 7:e december 2016, klockan 23:38, skrev Gianfranco Costamagna detta:
> 
> >> please use a text-version of the signing-key and avoid the include-binaries file?
> >
> >Then I need education on the procedure to create a keyring file on the go,
> >since gpgv only handles keyrings, not armoured keyfiles.
> 
> https://wiki.debian.org/debian/watch#Cryptographic_signature_verification
> gpg --keyserver keys.gnupg.net --recv-keys 3602B07F55D0C732
> gpg --armor --export-options export-minimal --export '3602B07F55D0C732' >> debian/upstream/signing-key.asc
> 
> does this work?

There is no problem to fetch the key. The problem is to use it. My present
use case is this

   gpgv --homedir debian/upstream --keyring debian/upstream/signing-key.pgp \
	archive.sig archive

You are requesting me to use 'debian/upstream/signing-key.asc', an armoured key
which gpgv is not able to handle to my knowledge. Observe that upstream's source
archive must be repackaged to fulfill DFSG, so the above use of gpgv is located
in the target 'get-orig-source' for verification of the original archive
before proceeding to eliminate the texinfo source, which violates DFSG.

Best regards,
  Mats E Andersson