Your message dated Thu, 21 May 2026 09:09:23 +0200
with message-id <[email protected]>
and subject line Re: Bug#1136990: RM: lwt-log/1.1.2-4
has caused the Debian Bug report #1136990,
regarding RM: lwt-log/1.1.2-4
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.)
--
1136990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1136990
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:lwt-log
User: [email protected]
Usertags: rm
Dear Release Team,
lwt-log FTBFS (#1136085) and is not going to be fixed. Instead, all
its reverse-dependencies have been fixed to not use it. A RM bug has
been filed against ftp.debian.org (#1136687).
However, lwt is blocked from migration because of lwt-log. All
packages depending on lwt must migrate at once, and at the same time
lwt-log is removed.
I wonder if Britney handles this case? Maybe it needs to be told
explicitly to remove lwt-log? (maybe a ignore-reverse-remove hint?)
Cheers,
--
Stéphane
--- End Message ---
--- Begin Message ---
Le 18/05/2026 à 09:55, Stéphane Glondu a écrit :
I wonder if Britney handles this case? Maybe it needs to be told
explicitly to remove lwt-log? (maybe a ignore-reverse-remove hint?)
Apparently, it does. Sorry for the noise. Closing.
Cheers,
--
Stéphane
--- End Message ---
