Your message dated Fri, 26 Dec 2025 09:02:51 +0100
with message-id <[email protected]>
and subject line Re: Bug#1123907: nmu: cdebconf_0.282
has caused the Debian Bug report #1123907,
regarding nmu: cdebconf_0.282
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.)
--
1123907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123907
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:cdebconf
User: [email protected]
Usertags: binnmu
cdebconf has multiarch-desynced. amd64 has +b2 and hurd-i386 has +b4.
I'm not sure we care about hurd being synced given that the libc is not
coinstallable, but fixing amd64 would be nice. I don't think the
following NMU line works as is as I'd expect other archs to go up to
+b1, but I failed to figure out the right invocation.
nmu cdebconf_0.282 . ANY -amd64 . unstable . -m "Sync binNMU"
Helmut
--- End Message ---
--- Begin Message ---
On 20/12/2025 07:43, Helmut Grohne wrote:
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:cdebconf
User: [email protected]
Usertags: binnmu
cdebconf has multiarch-desynced. amd64 has +b2 and hurd-i386 has +b4.
I'm not sure we care about hurd being synced given that the libc is not
coinstallable, but fixing amd64 would be nice. I don't think the
following NMU line works as is as I'd expect other archs to go up to
+b1, but I failed to figure out the right invocation.
`nmu 2 cdebconf . ANY ...`
nmu cdebconf_0.282 . ANY -amd64 . unstable . -m "Sync binNMU"
Scheduled.
Cheers,
Emilio
--- End Message ---
