** Summary changed:
- rust-imago 0.2.2-1: librust-imago-dev uninstallable on armhf (vm-memory is
64-bit only)
+ Please remove rust-imago 0.2.2-1 on armhf
** Changed in: rust-imago (Ubuntu)
Assignee: Nadzeya Hutsko (nadzeya) => (unassigned)
** Changed in: rust-imago (Ubuntu)
Status: Fix Released => New
** Description changed:
+ Please remove rust-imago on armhf as is being done in Debian.
+
+ rust-imago doesn't have any reverse depends yet. (libkrun will probably
+ be the first next cycle but its Build-Depends need to be updated for
+ changes in other rust packages.)
+
+
+ Original Bug Report
+ ===================
+
rust-imago 0.2.2-1 is stuck in stonking-proposed because librust-imago-
dev is uninstallable on armhf:
- librust-imago-dev/armhf has unsatisfiable dependency
- Depends: librust-vm-memory+default-dev (>= 0.16),
librust-vm-memory+default-dev (<< 0.19)
+ librust-imago-dev/armhf has unsatisfiable dependency
+ Depends: librust-vm-memory+default-dev (>= 0.16),
librust-vm-memory+default-dev (<< 0.19)
vm-memory is an optional feature of imago (Cargo.toml: vm-memory =
["dep:vm-memory"]), but the Debian packaging uses collapse_features =
true, so the feature's dependency becomes a hard Depends of librust-
imago-dev.
rust-vm-memory only supports 64-bit hosts: its debcargo.toml build-
depends on architecture-is-64-bit, so it is never built on armhf or
i386, in Debian or Ubuntu. librust-imago-dev is Architecture: any, so it
builds on armhf but cannot be installed there.
Debian has the same problem: rust-imago 0.2.2-1 does not migrate to
testing, with librust-imago-dev/armhf and /i386 reported as having
unsatisfiable dependencies.
Suggested fix, in debcargo-conf src/imago/debian/debcargo.toml, matching
what rust-vm-memory does:
- [source]
- # vm-memory (dependency of the vm-memory feature, collapsed into the
- # main package) only supports 64-bit hosts
- build_depends = ["architecture-is-64-bit"]
+ [source]
+ # vm-memory (dependency of the vm-memory feature, collapsed into the
+ # main package) only supports 64-bit hosts
+ build_depends = ["architecture-is-64-bit"]
Short-term workaround for Ubuntu: nothing in stonking depends or build-
depends on librust-imago-dev, and rust-imago is new (not in the release
pocket), so removing the armhf binaries from stonking-proposed would let
it migrate:
- remove-package -s stonking-proposed -a armhf -b -e 0.2.2-1 librust-
+ remove-package -s stonking-proposed -a armhf -b -e 0.2.2-1 librust-
imago-dev
** Bug watch added: Debian Bug tracker #1149636
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1149636
** Also affects: rust-imago (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1149636
Importance: Unknown
Status: Unknown
** Description changed:
Please remove rust-imago on armhf as is being done in Debian.
rust-imago doesn't have any reverse depends yet. (libkrun will probably
be the first next cycle but its Build-Depends need to be updated for
changes in other rust packages.)
+ https://codesearch.debian.net/search?q=path%3Adebian%2Fcontrol+librust-
+ imago
+
+ https://buildd.debian.org/status/package.php?p=libkrun
+ https://launchpad.net/ubuntu/+source/libkrun/1.19.4-1
Original Bug Report
===================
rust-imago 0.2.2-1 is stuck in stonking-proposed because librust-imago-
dev is uninstallable on armhf:
librust-imago-dev/armhf has unsatisfiable dependency
Depends: librust-vm-memory+default-dev (>= 0.16),
librust-vm-memory+default-dev (<< 0.19)
vm-memory is an optional feature of imago (Cargo.toml: vm-memory =
["dep:vm-memory"]), but the Debian packaging uses collapse_features =
true, so the feature's dependency becomes a hard Depends of librust-
imago-dev.
rust-vm-memory only supports 64-bit hosts: its debcargo.toml build-
depends on architecture-is-64-bit, so it is never built on armhf or
i386, in Debian or Ubuntu. librust-imago-dev is Architecture: any, so it
builds on armhf but cannot be installed there.
Debian has the same problem: rust-imago 0.2.2-1 does not migrate to
testing, with librust-imago-dev/armhf and /i386 reported as having
unsatisfiable dependencies.
Suggested fix, in debcargo-conf src/imago/debian/debcargo.toml, matching
what rust-vm-memory does:
[source]
# vm-memory (dependency of the vm-memory feature, collapsed into the
# main package) only supports 64-bit hosts
build_depends = ["architecture-is-64-bit"]
Short-term workaround for Ubuntu: nothing in stonking depends or build-
depends on librust-imago-dev, and rust-imago is new (not in the release
pocket), so removing the armhf binaries from stonking-proposed would let
it migrate:
remove-package -s stonking-proposed -a armhf -b -e 0.2.2-1 librust-
imago-dev
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2169084
Title:
Please remove rust-imago 0.2.2-1 on armhf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-imago/+bug/2169084/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
