Your message dated Sun, 29 Aug 2021 12:48:47 +0000
with message-id <[email protected]>
and subject line Bug#993216: fixed in dh-cargo 26
has caused the Debian Bug report #993216,
regarding dh-cargo timestamp fix doesn't cover changelogs installed to 
/usr/share/doc
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.)


-- 
993216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993216
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: dh-cargo

Recently a substantial number of upstream cargo packages started using timestamps the ftpmasters consider reject-worthy, I believe this was done in the name of reproducibility.

After it became clear that this was a larger-scale issue and we got sick of working around this in individual packages, sylvestre implemented a workaround in dh_cargo. Unfortunately this fix does not seem to be complete.

Specifically it seems that when an upstream changelog is installed by dh_installchangelogsĀ  to /usr/share/doc it doesn't get the timestamp fixing treatment. Presumablly because dh_installchangelogs pulls it from the source tree while the dh_cargo timestamp fixing happens on the output tree.

I've worked around it for now in crossbeam-deque, but I don't know how many other packages are potentially effected (e.g. have changelogs with dodgy timestamps in their upstream packaging) and whether this is something we need to deal with centrally.
--- End Message ---
--- Begin Message ---
Source: dh-cargo
Source-Version: 26
Done: Sylvestre Ledru <[email protected]>

We believe that the bug you reported is fixed in the latest version of
dh-cargo, 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.
Sylvestre Ledru <[email protected]> (supplier of updated dh-cargo 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: Sun, 29 Aug 2021 11:07:21 +0200
Source: dh-cargo
Architecture: source
Version: 26
Distribution: unstable
Urgency: medium
Maintainer: Rust Maintainers <[email protected]>
Changed-By: Sylvestre Ledru <[email protected]>
Closes: 993216
Changes:
 dh-cargo (26) unstable; urgency=medium
 .
   * Team upload
   * Move the touch step at the pre_building step to make
     sure it is also updating the changelog
     (Closes: #993216)
 .
   [ Debian Janitor ]
   * Bump debhelper dependency to >= 10, since that's what is used in
     debian/compat.
   * Bump debhelper from old 10 to 13.
   * Set debhelper-compat version in Build-Depends.
Checksums-Sha1:
 36833195a6b1c205028fcd793ca512fef9ade0d6 1612 dh-cargo_26.dsc
 c71ad4ab84cd6ccb8ae7a3bb8eae37661a349221 9220 dh-cargo_26.tar.xz
 384bdc43e7b8d760607f7f8502c31207f58ceafe 5841 dh-cargo_26_amd64.buildinfo
Checksums-Sha256:
 37d240f6040a65560a48edcca81d1521c07d6a31fb375c21755d1ff2ae8d8bf4 1612 
dh-cargo_26.dsc
 b03a058971370e1ab4e41352d428fb0ad4d9db38b2ccb7723cb1fa61adc0a71a 9220 
dh-cargo_26.tar.xz
 cfcf67b36eec8103a6d6912669efcf87f48124162acbb995a6842922770a4b63 5841 
dh-cargo_26_amd64.buildinfo
Files:
 98f7ca485c2a55cf2273c6db4cc24edb 1612 devel optional dh-cargo_26.dsc
 bf7f4e20cbba9bbabce90687db7fd08d 9220 devel optional dh-cargo_26.tar.xz
 ac4a685c8171ca2d4fb9a70d8f5ed71b 5841 devel optional 
dh-cargo_26_amd64.buildinfo

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

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmEre/4ACgkQfmUo2nUv
G+GNDg//aLyPkm2MnV7d5Hp79FkAb4NtLgBpLae5wdDbEkko4gciMCxR+U7O0L8S
fTGSRhsNyQR6Sm4TkUuUscu3MosDGJgx0CUdjV7Chv6jzdAUAchjZqLHM7jlYIjV
9ilFyeV3wjj+ca/T/V1TYBDfx5WmeMLhycnrCnx7bn7EmEkKidLDSJxNNM661AJL
yR5x9yx19khbT0WtocN6yP9zaGZk3QVGJ7vioNoDHFQy6wRwDjah0QYA0cHFHVjK
aGpsDTTsIsnWYXV/kaE/vwUeJ2bmHLW+P0PVmQuGDahenlsv8DIl0DHtFLQjev1E
HOhMXsBwzURrucbSMLbuzhU0lVLmM/1SOAblg58PU7kUh3fqOvoF/SjRCS8sjGZD
QQzVVTzsucxHksEz2ysC4oI3T4KokqcixtHHDEMZd7MQfAdIlRyxr/rcZ9nc2rRR
SaagOArWZ832qiX1UVQySSfhDvLbi0pL2KlaKfy8vwKHBppe0XUvnVWihbEWD5Eo
xzgWs3o6DWfLkSr+4An2tJNYQmwx8YiKWcLDi5zR12CCKBK29pweyr9wlOP3nOde
uTXRcYMMq/Y4VMkAd9XGZQutVhgeS2Uz91JiglOOLVA7x3cMyActKTUGhYm+/s/Z
iNGgDrm+Aid/kaH7jk1knU1XlICahes87WkHLwRpsEAYteKqfsY=
=a8Ri
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to