Control: reassign -1 src:rust-if-watch

On Sat, 08 Mar 2025 01:02, Jonas Smedegaard <jo...@jones.dk> wrote:
Control: reassign -1 src:rust-if-addrs
Control: affects -1 src:rust-if-watch

Quoting Matthias Geiger (2025-03-08 00:29:24)
if-watches' deps have been unfulfilled for some time now causing the package to unbuildable. When I updated if-addrs to 0.13 I attempted to patch if-addrs for it but I couldn't compile it because it rnetlink deps are not satisfied.

This issue belongs to src:rust-if-addrs - it is an uncoordinated
upgrade.  Don't do that.  Please revert, or provide the older branch as
a separate package. It is not ok to just change a library package like
that.


I acknownledge that I should've communicated /coordinated my if-addrs update better.
This doesn't change the fact that if-addrs was *already* uninstallable:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
librust-if-watch-dev : Depends: librust-if-addrs-0.10+default-dev but it is not 
installable
                       Depends: librust-netlink-packet-route-0.17-dev but it is 
not installable
                       Depends: librust-rtnetlink-0.13+smol-socket-dev but it 
is not installable
                       Depends: librust-rtnetlink-0.13+tokio-socket-dev but it 
is not installable
Error: Unable to correct problems, you have held broken packages.


The upload of the netlink packages on the 20th of February broke if-watch long before I uploaded if-addrs. This is unfortunate. If if-watch would have had an RC bug this'd caught my attention and reconsider the upload. I verified that if-watch itself does build and test find against the newer if-addrs, thus reassigning, since the RC issue is primarly caused by netlink (and, arguably, worsened by my upload. Sorry.)

I can provide a patch to remedy my mess, but rnetlink is beyond me.

regards,

werdahias

Reply via email to