[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#987838: marked as done (unblock: gnupg2/2.2.27-2)

Your message dated Fri, 7 May 2021 21:46:21 +0200
with message-id <8d110cf3-4736-a40e-047f-61a2d3ef0f40@debian.org>
and subject line Re: Bug#987838: unblock: gnupg2/2.2.27-2
has caused the Debian Bug report #987838,
regarding unblock: gnupg2/2.2.27-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
987838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987838
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pkg-gnupg-maint@lists.alioth.debian.org

Please unblock package gnupg2

Being fully aware about the signifiance of the gnupg2 package and the
advanced progress of the bullseye release, I am asking to unblock
gnupg2/2.2.27-2. As there are no changes to the code, just a
documentation update, there shouldn't be any risk of introducing
regressions.

[ Reason ]
Document the fact the gnupg suite no longer reads a configuration file
at "~/.gnupg/options".

This fixes Debian bug is <https://bugs.debian.org/985158>. Related,
mentioning this in the release notes has been requested in
<https://bugs.debian.org/987440>.

[ Impact ]
Without that information, users have less chance to learn about that
change, and might more likely experience regressions or breakage in
their GnuPG-based workflows.

[ Risks ]
There shouldn't be any risks as no code was changed.

[ Checklist ]
  [x] all changes are documented in the d/changelog
      (did not mention I'd added myself to uploaders, though)
  [X] I reviewed all changes and I approve them
      (TBH, they were done by yours truly)
  [X] attach debdiff against the package in testing

unblock gnupg2/2.2.27-2


diff -Nru gnupg2-2.2.27/debian/changelog gnupg2-2.2.27/debian/changelog
--- gnupg2-2.2.27/debian/changelog	2021-02-08 23:57:00.000000000 +0100
+++ gnupg2-2.2.27/debian/changelog	2021-04-22 20:40:36.000000000 +0200
@@ -1,3 +1,10 @@
+gnupg2 (2.2.27-2) unstable; urgency=medium
+
+  * Add a NEWS entry about the end of support for ~/.gnupg/options.
+    Closes: #985158
+
+ -- Christoph Biedl <debian.axhn@manchmal.in-ulm.de>  Thu, 22 Apr 2021 20:40:36 +0200
+
 gnupg2 (2.2.27-1) unstable; urgency=medium
 
   [ NIIBE Yutaka ]
diff -Nru gnupg2-2.2.27/debian/control gnupg2-2.2.27/debian/control
--- gnupg2-2.2.27/debian/control	2021-02-08 23:56:55.000000000 +0100
+++ gnupg2-2.2.27/debian/control	2021-04-22 20:40:36.000000000 +0200
@@ -5,6 +5,7 @@
 Uploaders:
  Eric Dorland <eric@debian.org>,
  Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
+ Christoph Biedl <debian.axhn@manchmal.in-ulm.de>,
 Standards-Version: 4.5.1
 Build-Depends:
  automake,
diff -Nru gnupg2-2.2.27/debian/NEWS gnupg2-2.2.27/debian/NEWS
--- gnupg2-2.2.27/debian/NEWS	2021-02-08 20:38:26.000000000 +0100
+++ gnupg2-2.2.27/debian/NEWS	2021-04-22 20:40:36.000000000 +0200
@@ -1,3 +1,12 @@
+gnupg2 (2.2.27-2) unstable; urgency=medium
+
+  Starting with version 2.2.27-1, per-user configuration of the GnuPG
+  suite has completely moved to ~/.gnupg/gpg.conf, and ~/.gnupg/options
+  is no longer in use.  Please rename the file if necessary, or move
+  its contents to the new location.
+
+ -- Christoph Biedl <debian.axhn@manchmal.in-ulm.de>  Thu, 22 Apr 2021 20:37:45 +0200
+
 gnupg2 (2.2.17-1) unstable; urgency=medium
 
   Upstream GnuPG now defaults to not accepting third-party certifications

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Hi Christoph,

On 30-04-2021 19:05, Christoph Biedl wrote:
> Please unblock package gnupg2

unblocked.

> As there are no changes to the code, just a
> documentation update, there shouldn't be any risk of introducing
> regressions.

Seems to follow our policy quite nicely:
https://release.debian.org/bullseye/freeze_policy.html#appropriate

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: