On Tue 2016-08-30 06:49:30 -0400, Axel Beckert wrote: > Daniel Kahn Gillmor wrote: >> However, if your next upload of php-crypt-gpg can't be built or run >> against modern versions of GnuPG, then you probably need to state this >> package's dependency on gnupg as gnupg (<= 2.1). > > Shouldn't "gnupg1" be used then nowadays?
that would involve a fix of forcing php-crypt-gpg to use and look for
/usr/bin/gpg1. that would make me sad, because it would mean that the
users of php-crypt-gpg would be unable to benefit from the work
happening on GnuPG's modern branch. and the fixes available in gcrypt
itself.
So yeah, it's possible to do it that way but i really hope it doesn't
come to that.
--dkg
signature.asc
Description: PGP signature
_______________________________________________ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
