[pkg-gnupg-maint] ben's "auto-gnupg" transition page

Daniel Kahn Gillmor dkg at fifthhorseman.net
Thu May 12 05:44:37 UTC 2016


Hi debian gnupg folks--

As you know, the gnupg source package in experimental now ships gnupg1
and gpgv1 binary packages, and the gnupg2 source package in experimental
ships the gnupg binary package.

This is an intentional change, and we're hoping to eventually move
debian over to the gnupg 2.1 branch everywhere possible

i just noticed:

  https://release.debian.org/transitions/html/auto-gnupg.html

and i'm a concerned about this bit:

    Affected: .depends ~ /\b(gnupg1|gnupg1\-curl|gpgv1|gnupg|gnupg\-curl|gpgv)\b/
    Good: .depends ~ /\b(gnupg1|gnupg1\-curl|gpgv1)\b/
    Bad: .depends ~ /\b(gnupg|gnupg\-curl|gpgv)\b/

I don't think we want *anything* to depend on gnupg1 or gpgv1 or
gnupg1-curl where we don't need to, so this looks wrong to me.

Mehdi told me that this was machine-generated due to changes in the
source package, and suggested i could ask on #debian-release to remove
the "auto-gnupg" transition.  I've done that but haven't heard back yet.

If anyone has any other thoughts about how to approach such a transition
logistically, please discuss them here.

              --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 948 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20160512/ea361112/attachment.sig>


More information about the pkg-gnupg-maint mailing list