Your message dated Mon, 19 Aug 2024 19:21:20 +0200
with message-id <zsn_eemvkof_y...@ramacher.at>
and subject line Re: Bug#1079038: nmu: dracut_103-1
has caused the Debian Bug report #1079038,
regarding nmu: dracut_103-1
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.)
--
1079038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: dra...@packages.debian.org
Control: affects -1 + src:dracut
User: release.debian....@packages.debian.org
Usertags: binnmu
nmu dracut_103-1 . ANY . bookworm . -m "Rebuild against the latest libkmod"
Upstream broke backward compatibility and it looks like my latest kmod
upload is a bit more toxic than I tought, and systems will not boot.
I think that the easiest solution is to NMU dracut-install.
--
ciao,
Marco
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On 2024-08-19 12:29:24 +0200, Marco d'Itri wrote:
> On Aug 19, Sebastian Ramacher <sramac...@debian.org> wrote:
>
> > Reserve dependencies failing with unresolved symbols is a sign that
> > libkmod is missing a SONAME bump. Why hasn't that been done?
> To make a long story short, upstream did not believe that anything
> actually used the symbol, and I do not want to have a critical library
> diverge from upstream.
Then an option is to revert to the previous version or to reintroduce
the symbol until upstream performs a SONAME bump. Rebuilding the
reverse dependencies is just papering over the issue.
Closing.
Cheers
--
Sebastian Ramacher
--- End Message ---
