Your message dated Tue, 30 Apr 2024 11:53:51 +0000
with message-id <[email protected]>
and subject line Bug#1069902: fixed in groff 1.23.0-4
has caused the Debian Bug report #1069902,
regarding gropdf generates invalid CreationDate and ModDate
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.)


-- 
1069902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069902
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: groff
Version: 1.23.0-2

$ echo "" | groff -T pdf | grep -F -a Date
5 0 obj << /CreationDate (D:20240426202138+01'+00')
/ModDate (D:20240426202138+01'+00')
$ echo "" | groff -T pdf | grep -F -a Date
5 0 obj << /CreationDate (D:20240426202145+01'+00')
/ModDate (D:20240426202145+01'+00')
$ echo "" | groff -T pdf | grep -F -a Date
5 0 obj << /CreationDate (D:20240426202150+02'+00')
/ModDate (D:20240426202150+02'+00')

Note the '+00' instead of '00' at the end of the date string. Also
note that the first two attempts resulted in a timezone offset of
+01:00, but the last one had a timezone offset of +02:00 (the last one
is correct).

A non-Debian groff 1.23 does not exhibit those issues:

~> echo "" | groff -Tpdf | grep -F -a Date
5 0 obj << /CreationDate (D:20240426202132+02'00')
/ModDate (D:20240426202132+02'00')
~> echo "" | groff -Tpdf | grep -F -a Date
5 0 obj << /CreationDate (D:20240426202142+02'00')
/ModDate (D:20240426202142+02'00')
~> echo "" | groff -Tpdf | grep -F -a Date
5 0 obj << /CreationDate (D:20240426202151+02'00')
/ModDate (D:20240426202151+02'00')


see also
https://lists.gnu.org/archive/html/groff/2024-04/msg00026.html for a
possible patch

--- End Message ---
--- Begin Message ---
Source: groff
Source-Version: 1.23.0-4
Done: Colin Watson <[email protected]>

We believe that the bug you reported is fixed in the latest version of
groff, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <[email protected]> (supplier of updated groff package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 30 Apr 2024 12:25:43 +0100
Source: groff
Architecture: source
Version: 1.23.0-4
Distribution: unstable
Urgency: medium
Maintainer: Colin Watson <[email protected]>
Changed-By: Colin Watson <[email protected]>
Closes: 1069902
Changes:
 groff (1.23.0-4) unstable; urgency=medium
 .
   * Build-depend on pkgconf rather than pkg-config.
   * Fix PDF date format (thanks, Christof Meerwald; closes: #1069902).
Checksums-Sha1:
 88b3e7d7b1c435faae612bd4d26b06aa3ecd98d1 2420 groff_1.23.0-4.dsc
 342dac592e3189e2889523aa43e358f07c392489 42500 groff_1.23.0-4.debian.tar.xz
Checksums-Sha256:
 ce5eef082f05422082eafc4690b372205cb2d6b9e1ddcff10749971dac36ae61 2420 
groff_1.23.0-4.dsc
 bf63126c418f72a99b6d071de58bd1bba33cdc683d9030de5c074491ad4c8f3a 42500 
groff_1.23.0-4.debian.tar.xz
Files:
 1ae5270d2221ee32ccfe04734da75272 2420 text important groff_1.23.0-4.dsc
 3c4603b9d16b793f30adb77532544342 42500 text important 
groff_1.23.0-4.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmYw1V8ACgkQOTWH2X2G
UAujXg//SebXCplfENp7mpPwuH+smtwdBqTrsEp+GpPuOD3ljoAeA2k3b1E6ZnSG
UQIm1LjzhWqhiLOd2lEgQWDeGfj9JzRRJi8GI1pAjVnP0JfyOpPnB9Aa8v6elVjN
e0SbeoQ0D7uGdsvYboNkplDdmifXKTRanVLDaS+qiYtsAynT5zuasKyUJSnx9z1J
dfqx0LTF/6/04gJ3WbMrwQu9ahFeZWj4vnpVO2Vnp2qo2lXS6VaTMeBOpUfKjS/6
Z+o5faS/eyaDaMF0Fhz8+ke61B5cchHjZKHBGerv6t2c7SHWYFujvmaTYPFuNmfi
u01XcOg4G/GLMHaEToA028Jx8CixtrW2O8l2ZnJFVF+FePFxc+8Qi3LHMxLvEol+
z0W+5hvmK334yd41iqc1ELXg2QMrt2yDZ5SDP063A0bOkFfFYijMNZdXMJGRJZBW
4t7y+BAcBBrS2U/Y7PI18s5FTmRJLzhYDsNQJ2kiPFwpC0NiVlILgtBILirqCxOK
KfLe9ytyjG8KzzrFfBPtEYUH9/yhDuA8wnNfYS0yZtGBJeLGOjpVm6phHYSARNWn
GUk6zJWaR3f7eek45Cd11lMP3sOmWsffTmPZuzJGPpUnbNoVMseGQrMfKCtIoXA1
SpRwyz+pAWIhu4H8/xklTCahSQFQzV84B7Rz3DIp/7vpFUXkOAc=
=j+f3
-----END PGP SIGNATURE-----

Attachment: pgpMjj0Q21S1H.pgp
Description: PGP signature


--- End Message ---

Reply via email to