<div dir="ltr">Package: rust-blosc2-rs<br>Version: 0.4.0-1<br>Severity: serious<br>Tags: patch<br>Justification: uninstallable<br>User: <a href="mailto:ubuntu-devel@lists.ubuntu.com">ubuntu-devel@lists.ubuntu.com</a><br>Usertags: origin-ubuntu stonking ubuntu-patch<br><br>Hi,<br><br>librust-blosc2-rs-dev is uninstallable on all architectures, which is why<br>rust-blosc2-rs never migrated to testing:<br><br>  librust-blosc2-rs-dev Depends: librust-blosc2-sys-0.4+regenerate-bindings-dev<br><br>rust-blosc2-sys 0.4.0+dfsg-1 doesn't provide that: its debian/patches/drop-static<br>removes the "regenerate-bindings" feature (together with "shared" and<br>"static"), so it only provides the +bindgen variant.<br><br>rust-blosc2-rs's own debian/patches/drop-static removes "shared" and "static"<br>but keeps<br><br>  regenerate-bindings = ["blosc2-sys/regenerate-bindings"]<br><br>so debcargo still generates the +regenerate-bindings feature package and the<br>dependency on the blosc2-sys feature that no longer exists.<br><br>The attached change extends rust-blosc2-rs's drop-static patch to also drop<br>the regenerate-bindings feature, matching blosc2-sys. debian/control then needs<br>regenerating with debcargo (the librust-blosc2-rs+regenerate-bindings-dev<br>provides and the librust-blosc2-sys-0.4+regenerate-bindings-dev dependency go<br>away). I checked the updated patch applies cleanly to the 0.4.0 upstream<br>source.<br><br>We hit this in Ubuntu, where the package is stuck in proposed for the same<br>reason.<br><br>Thanks,<br>Sebastien Bacher<br><br></div>