[DRE-maint] Bug#852710: closed by Georg Faerber <georg at riseup.net> (Bug#852710: fixed in schleuder 3.2.1-1)

[Daniel Kahn Gillmor]

On Sat 2017-10-28 12:06:05 +0000, Debian Bug Tracking System wrote:
>    * debian/NEWS: Add note about how to rely on the Debian keyserver defaults.
>    * debian/patches:
>      - Add patch to rely on the Debian keyserver defaults in the schleuder
>        config. (Closes: #852710)

Thanks for this fix!

fwiw, this isn't specific to Debian. GnuPG ships with a default
keyserver upstream now.  If you're depending on anything reasonably
recent from the 2.1.x branch (or anything from 2.2.x now that it's
stabilized) schleuder really should not ship with an explicit config
that the admin needs to override.  Let the underlying tool choose
sensible defaults, and allow the local administrator to override them
should they need to (if they need to, they'll know).

This even goes for older versions of GnuPG -- if they don't supply a
default, the local admin still ought to be the one to make the decision.
(or the user should upgrade to a modern version of GnuPG that is getting
significant amounts of upstream attention ;)

I think it's best for schleuder be agnostic about this choice.

     --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20171028/6470a90e/attachment.sig>