Your message dated Mon, 19 May 2025 18:22:22 +0200
with message-id <[email protected]>
and subject line Re: Bug#701566: gnupg: wrong length of month used for key
expiration date
has caused the Debian Bug report #701566,
regarding gnupg: wrong length of month used for key expiration date
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 [email protected]
immediately.)
--
701566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701566
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnupg
Version: 1.4.12-7
Severity: minor
Dear Maintainer,
today I generated a new key (0xfaaad43b), and I set the expiration
date to 24 months. I had expected this to be the same as two
years, as it is defined in the calendar. In fact, it is ten days
less.
It looks like gpg assumes that one month = 30 days, so a timespan
of one month from today, according to gpg, ends not on March 24th,
but on March 26th. This is obviously wrong.
GnuPG should use the measure month as defined in the calendar.
Alternatively, it could define its own measure, but then it should
be named differently.
Thanks for your efforts!
Michael Below
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (900, 'testing'), (500, 'stable-updates'), (500,
'proposed-updates'), (500, 'stable'), (10, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gnupg depends on:
ii dpkg 1.16.9
ii gpgv 1.4.12-7
ii install-info 4.13a.dfsg.1-10
ii libbz2-1.0 1.0.6-4
ii libc6 2.13-38
ii libreadline6 6.2+dfsg-0.1
ii libusb-0.1-4 2:0.1.12-20+nmu1
ii zlib1g 1:1.2.7.dfsg-13
Versions of packages gnupg recommends:
ii gnupg-curl 1.4.12-7
ii libldap-2.4-2 2.4.31-1
Versions of packages gnupg suggests:
ii eog 3.4.2-1+build1
pn gnupg-doc <none>
ii graphicsmagick-imagemagick-compat [imagemagick] 1.3.16-1.1
ii libpcsclite1 1.8.4-1
ii xloadimage 4.1-19
-- no debconf information
--- End Message ---
--- Begin Message ---
On 2013-02-24 Michael Below <[email protected]> wrote:
> Package: gnupg
> Version: 1.4.12-7
> Severity: minor
> Dear Maintainer,
> today I generated a new key (0xfaaad43b), and I set the expiration
> date to 24 months. I had expected this to be the same as two
> years, as it is defined in the calendar. In fact, it is ten days
> less.
> It looks like gpg assumes that one month = 30 days, so a timespan
> of one month from today, according to gpg, ends not on March 24th,
> but on March 26th. This is obviously wrong.
> GnuPG should use the measure month as defined in the calendar.
> Alternatively, it could define its own measure, but then it should
> be named differently.
Hello,
I had forwarded this upstream, and upstream closed with wontfix:
| The report is correct but it does not make sense to fix it. If you want
| to use a concrete expiration date just enter the IS date at the prompt;
| use ? at the prompt for a short description.
I do not think there is any point in keeping this open on the Debian
side.
cu Andreas
--- End Message ---
