Your message dated Fri, 17 Jul 2026 19:56:42 +0200
with message-id <[email protected]>
and subject line Re: Bug#1142002: nmu: lazarus_4.8+dfsg-2
has caused the Debian Bug report #1142002,
regarding nmu: lazarus_4.8+dfsg-2
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.)
--
1142002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1142002
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected], [email protected],
[email protected]
Control: affects -1 + src:lazarus
User: [email protected]
Usertags: amd64
User: [email protected]
Usertags: binnmu
nmu lazarus_4.8+dfsg-2 . ANY . unstable . -m "Rebuild with fpc 3.2.2+dfsg-51
(reproducibility fix)"
--- End Message ---
--- Begin Message ---
Hi Peter,
On 17-07-2026 11:40, Peter Blackman wrote:
I was hoping to achieve this without uploading another lazarus version,
as nothing in lazarus itself needs to change in order to fix this.
Right. For arch:$arch that would work, but as already mentioned, the
infrastructure doesn't support binNMU's of arch:all binaries at the moment.
Paul
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
