Your message dated Wed, 20 May 2026 20:09:53 +0200
with message-id <[email protected]>
and subject line Re: Bug#1136620: finish-install: Binaries fail to reproduce
due to future timestamp in changelog
has caused the Debian Bug report #1136620,
regarding finish-install: Binaries fail to reproduce due to future timestamp in
changelog
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.)
--
1136620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136620
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: finish-install
Version: 2.125
Severity: normal
X-Debbugs-Cc: [email protected]
User: [email protected]
Usertags: timestamps
Dear Maintainer,
Your package current fails to reproduce on https://reproduce.debian.net. My
understanding is that this is due to the timestamp in the debian/changelog
being set to the future with respect to the time of the upload to the Debian
archive. This breaks the automatic clamping of the files in the binary package
and makes the package non-reproducible [1]. Please consider uploading a new
source package with a timestamp not set to the future to allow the binary
package to be reproduced.
Thanks!
Gamer191 (https://github.com/gamer191)
[1] Shamelessly plaguirsed from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136274
--- End Message ---
--- Begin Message ---
Version: 2.126
Am 14. Mai 2026 03:00:06 MESZ schrieb gamer191 <[email protected]>:
>Source: finish-install
>Version: 2.125
>Severity: normal
>X-Debbugs-Cc: [email protected]
>User: [email protected]
>Usertags: timestamps
>
>Dear Maintainer,
>
>Your package current fails to reproduce on https://reproduce.debian.net. My
>understanding is that this is due to the timestamp in the debian/changelog
>being set to the future with respect to the time of the upload to the Debian
>archive. This breaks the automatic clamping of the files in the binary package
>and makes the package non-reproducible [1]. Please consider uploading a new
>source package with a timestamp not set to the future to allow the binary
>package to be reproduced.
>
>Thanks!
>
>Gamer191 (https://github.com/gamer191)
>
>[1] Shamelessly plaguirsed from
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136274
>
--
Sent from /e/ OS on Fairphone3
--- End Message ---
