Hi Marco, Quoting Marco d'Itri (2024-08-19 23:48:24) > The quick and easy solution would be to rebuild dracut-install, but the > release team refused to binNMU it (#1079038). > > The stupid solution would be to revert the change, and I will not do it > because I do not want to diverge from upstream. > > The elegant solution would be to keep for a while both symbols in the > library, but I am not good enough with ld(1) and could not actually > manage to do it myself. > > The nuclear solution would be to make a new upload with "Breaks: > dracut-install (<= 103-1)", which at least would make libkmod2 not > installable until somebody will be forced to do a new sourceful upload > of dracut-install. > > So I will wait for a while to see if anybody can help with #3, and if not > then I will proceed with #4.
given that this issue can render our user's systems unbootable, could we have a quick-and-dirty solution now rather than the proper solution in a few days? You could upload kmod with an ugly version like 33+20240816-2~really32+20240611-1 and the contents of the last-working version of kmod and then take all the time you need to implement the correct solution. Thanks! cheers, josch
signature.asc
Description: signature
