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

Accepted groff 1.22.3-3 (source) into unstable



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

Format: 1.8
Date: Fri, 06 Nov 2015 13:14:24 +0000
Source: groff
Binary: groff-base groff
Architecture: source
Version: 1.22.3-3
Distribution: unstable
Urgency: medium
Maintainer: Colin Watson <cjwatson@debian.org>
Changed-By: Colin Watson <cjwatson@debian.org>
Description:
 groff      - GNU troff text-formatting system
 groff-base - GNU troff text-formatting system (base system components)
Changes:
 groff (1.22.3-3) unstable; urgency=medium
 .
   * Add SOURCE_DATE_EPOCH support to mdate.sh, and restore upstream code
     there to force the C locale.
   * Use gmtime in mdate.sh.
   * Remove unnecessary randomness from hdtbl example output.
   * Always use UTC times for display.
   * Sort Perl hash keys.
   * Build with LC_ALL=C.UTF-8.  To some extent this is a cop-out as other
     packages using groff may still need to do similarly; I believe the
     remaining important place where groff is character-set-sensitive in a
     way that affects reproducibility of output is in the HTML postprocessor,
     which sometimes inserts spaces in UTF-8 locales but not (for example) in
     ASCII locales.
Checksums-Sha1:
 209289ef6e723d32c3e7cb0568f423fca5f9acb8 2109 groff_1.22.3-3.dsc
 7ddfff74058d3537a8a2bc71809fafd5d876ec31 45032 groff_1.22.3-3.debian.tar.xz
Checksums-Sha256:
 7bf4459b8cc65cb65f04482492c91de62b777b7da724b36da7d9b42274e0e9c5 2109 groff_1.22.3-3.dsc
 a538ce6a8b99013d74fcf25645cf10a619ec5b432b76008d3556e0fefd00dfb7 45032 groff_1.22.3-3.debian.tar.xz
Files:
 1e829af2e51cadcb1f88c48b9bdba4ed 2109 text important groff_1.22.3-3.dsc
 84dfd256b9fa23fe48153df5f5403201 45032 text important groff_1.22.3-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Colin Watson <cjwatson@debian.org> -- Debian developer

iQIVAwUBVjynvTk1h9l9hlALAQjdSQ//bC1db1ErFoDw5OAg+OyLX0FZoEXAFzVO
TJ+e8FU3Xa22nN6466i8UWCfy4ZaUd+SxiamTOhnYFvDI8F+CIn3qB3rn+TSXA14
B2Pt2RA9pVvsiXEBtrG/C59BFajQW/njhQ3jnPTZDT/u5tKZSXhbMXlKZZHRsgYH
jaz6QRciyH6oaBq9B7OS5Wj9vhrzJGTqa/9M90XXcNc/HO5TrxmR6wAcKd7V/7lb
6vdmmxbMqq54MM/rvXI3FAL1mRihh9hqhCxaDQR2RO+hTiOyZAg21+D9r3uPTM2L
ld9vZes3kELeGBHNtNJH8jzPq10j331oqhCAmNeiiarZvei0mHmI8BYuoDmRc7SN
CYKIFXK8uvGI+qmobL3P8y4/L7cBbF4qSPXbnNPBb5GnBqRUodp5JGoqV9Ta2LsP
zRYpaJKyYD27eRFjePfK+Rqqk2d+66aC8E8r28t1LIyHnqNcVPvOHenX0ADmYzGP
HCpFXOhEr5OklTslFhC7Y7ewqBO6GvYZpb17iQe1tyIqQqZZMl0F3bKXrD3Itjlh
2spqwuZS7WsLScRW5YTeBUBY9lrek2YSmVKjOi1kWqsHFj2ULv8fI46RF0m0h/nr
68xDfSqxFEsUUErFboxT4Qsu1hg1kYRNxE7NdAUrMVU/+e61bTQWCZgG9I17Dkhg
S3dmFE0XqZM=
=ra0N
-----END PGP SIGNATURE-----


Reply to: