Your message dated Tue, 27 May 2025 18:50:51 +0200
with message-id <[email protected]>
and subject line Re: Bug#1106672: nmu: fragments_3.0.1-8
has caused the Debian Bug report #1106672,
regarding nmu: fragments_3.0.1-8
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.)
--
1106672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106672
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:fragments
User: [email protected]
Usertags: binnmu
nmu fragments_3.0.1-8 . ANY . unstable . -m "Rebuild with
librust-transmission-client-dev 0.1.5-2 (Closes: #1106237)"
Hi!
I uploaded rust-transmission-client-dev yesterday with a cherry-pick from
upstream to make it compatible with recent transmission-daemon versions.
Since fragments statically links the affected/fixed crate, it needs to be
rebuilt to pick up the fix. I've (manually) verified such a rebuilt package
fixes the referenced bug.
Thanks!
Fabian
--- End Message ---
--- Begin Message ---
On 2025-05-27 17:57:06 +0200, Fabian Grünbichler wrote:
> Package: release.debian.org
> Severity: normal
> X-Debbugs-Cc: [email protected], [email protected],
> [email protected]
> Control: affects -1 + src:fragments
> User: [email protected]
> Usertags: binnmu
>
> nmu fragments_3.0.1-8 . ANY . unstable . -m "Rebuild with
> librust-transmission-client-dev 0.1.5-2 (Closes: #1106237)"
Scheduled.
Cheers
--
Sebastian Ramacher
--- End Message ---
