Your message dated Wed, 27 Mar 2024 10:16:53 +0100 with message-id <zgpkby9lvlgdk...@ramacher.at> and subject line Re: Bug#1067769: nmu: libjcat_0.2.0-2+b1 has caused the Debian Bug report #1067769, regarding nmu: libjcat_0.2.0-2+b1 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 ow...@bugs.debian.org immediately.) -- 1067769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: release.debian.org Severity: normal X-Debbugs-Cc: libj...@packages.debian.org Control: affects -1 + src:libjcat User: release.debian....@packages.debian.org Usertags: binnmu nmu libjcat_0.2.0-2 . armel armhf . unstable . -m "rebuild against libgpgme11t64" Possibly not very high impact, but I think this would unblock fwupd. smcv
--- End Message ---
--- Begin Message ---On 2024-03-26 14:11:02 +0000, Simon McVittie wrote: > Package: release.debian.org > Severity: normal > X-Debbugs-Cc: libj...@packages.debian.org > Control: affects -1 + src:libjcat > User: release.debian....@packages.debian.org > Usertags: binnmu > > nmu libjcat_0.2.0-2 . armel armhf . unstable . -m "rebuild against > libgpgme11t64" Scheduled Cheers -- Sebastian Ramacher
--- End Message ---
