** Description changed: + [Impact] + The initrd-boot autopkgtest fails on armhf before the test runs because its debvm dependency cannot be installed: no suitable QEMU package is installable on that architecture. This causes the package’s autopkgtest to report badpkg. + + [Fix] + Exclude armhf from the initrd-boot test in debian/tests/control. The test continues to run on other architectures. + + [Test Plan] + Run the initrd-boot autopkgtest on armhf and confirm it is skipped rather than failing during dependency installation. Run it on a supported architecture and confirm the test still executes. + + [Where problems could occur] + The change only adjusts which architectures run this autopkgtest; it does not change the nbd binaries or runtime behavior. The tradeoff is that initrd-boot is no longer tested on armhf, where its dependencies are currently unavailable. + + [Other Info] + The failure occurs while resolving test dependencies, before initrd-boot starts. The proposed fix is recorded in the package changelog for 1:3.27.1-4ubuntu2. + + + --- + 120s Solving dependencies... 120s Some packages could not be installed. This may mean that you have 120s requested an impossible situation or if you are using the unstable 120s distribution that some required packages have not yet been created 120s or been moved out of Incoming. 120s The following information may help to resolve the situation: - 120s + 120s 120s The following packages have unmet dependencies: 121s satisfy:command-line : Depends: debvm but it is not going to be installed 121s Depends: nbd-server but it is not going to be installed 121s Depends: uidmap but it is not going to be installed 121s E: Unable to satisfy dependencies. Reached two conflicting assignments: 121s 1. debvm:armhf is selected for install because: 121s 1. satisfy:command-line:armhf=1 is selected for install 121s 2. satisfy:command-line:armhf Depends debvm 121s 2. debvm:armhf Depends qemu-system-native | qemu-kvm (> 1:8.0) | qemu-system-any 121s but none of the choices are installable: 121s [no choices] 121s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from tenacious-proposed 122s Reading package lists... 122s Building dependency tree... 122s Reading state information... 122s Solving dependencies... 122s Some packages could not be installed. This may mean that you have 122s requested an impossible situation or if you are using the unstable 122s distribution that some required packages have not yet been created 122s or been moved out of Incoming. 122s The following information may help to resolve the situation: - 122s + 122s 122s The following packages have unmet dependencies: 123s satisfy:command-line : Depends: debvm but it is not going to be installed 123s Depends: nbd-server but it is not going to be installed 123s Depends: uidmap but it is not going to be installed 123s E: Unable to satisfy dependencies. Reached two conflicting assignments: 123s 1. debvm:armhf is selected for install because: 123s 1. satisfy:command-line:armhf=1 is selected for install 123s 2. satisfy:command-line:armhf Depends debvm 123s 2. debvm:armhf Depends qemu-system-native | qemu-kvm (> 1:8.0) | qemu-system-any 123s but none of the choices are installable: 123s [no choices] 123s initrd-boot FAIL badpkg Ref: https://autopkgtest.ubuntu.com/results/autopkgtest- tenacious/tenacious/armhf/n/nbd/20261021_144515_39d5d@/log.gz
** Description changed: [Impact] - The initrd-boot autopkgtest fails on armhf before the test runs because its debvm dependency cannot be installed: no suitable QEMU package is installable on that architecture. This causes the package’s autopkgtest to report badpkg. + + The initrd-boot autopkgtest fails on armhf before the test runs because + its debvm dependency cannot be installed: no suitable QEMU package is + installable on that architecture. This causes the package’s autopkgtest + to report badpkg. [Fix] - Exclude armhf from the initrd-boot test in debian/tests/control. The test continues to run on other architectures. + + Exclude armhf from the initrd-boot test in debian/tests/control. The + test continues to run on other architectures. [Test Plan] - Run the initrd-boot autopkgtest on armhf and confirm it is skipped rather than failing during dependency installation. Run it on a supported architecture and confirm the test still executes. + + Run the initrd-boot autopkgtest on armhf and confirm it is skipped + rather than failing during dependency installation. Run it on a + supported architecture and confirm the test still executes. [Where problems could occur] - The change only adjusts which architectures run this autopkgtest; it does not change the nbd binaries or runtime behavior. The tradeoff is that initrd-boot is no longer tested on armhf, where its dependencies are currently unavailable. + + The change only adjusts which architectures run this autopkgtest; it + does not change the nbd binaries or runtime behavior. The tradeoff is + that initrd-boot is no longer tested on armhf, where its dependencies + are currently unavailable. [Other Info] - The failure occurs while resolving test dependencies, before initrd-boot starts. The proposed fix is recorded in the package changelog for 1:3.27.1-4ubuntu2. + None --- 120s Solving dependencies... 120s Some packages could not be installed. This may mean that you have 120s requested an impossible situation or if you are using the unstable 120s distribution that some required packages have not yet been created 120s or been moved out of Incoming. 120s The following information may help to resolve the situation: 120s 120s The following packages have unmet dependencies: 121s satisfy:command-line : Depends: debvm but it is not going to be installed 121s Depends: nbd-server but it is not going to be installed 121s Depends: uidmap but it is not going to be installed 121s E: Unable to satisfy dependencies. Reached two conflicting assignments: 121s 1. debvm:armhf is selected for install because: 121s 1. satisfy:command-line:armhf=1 is selected for install 121s 2. satisfy:command-line:armhf Depends debvm 121s 2. debvm:armhf Depends qemu-system-native | qemu-kvm (> 1:8.0) | qemu-system-any 121s but none of the choices are installable: 121s [no choices] 121s autopkgtest: WARNING: Test dependencies are unsatisfiable with using apt pinning. Retrying with using all packages from tenacious-proposed 122s Reading package lists... 122s Building dependency tree... 122s Reading state information... 122s Solving dependencies... 122s Some packages could not be installed. This may mean that you have 122s requested an impossible situation or if you are using the unstable 122s distribution that some required packages have not yet been created 122s or been moved out of Incoming. 122s The following information may help to resolve the situation: 122s 122s The following packages have unmet dependencies: 123s satisfy:command-line : Depends: debvm but it is not going to be installed 123s Depends: nbd-server but it is not going to be installed 123s Depends: uidmap but it is not going to be installed 123s E: Unable to satisfy dependencies. Reached two conflicting assignments: 123s 1. debvm:armhf is selected for install because: 123s 1. satisfy:command-line:armhf=1 is selected for install 123s 2. satisfy:command-line:armhf Depends debvm 123s 2. debvm:armhf Depends qemu-system-native | qemu-kvm (> 1:8.0) | qemu-system-any 123s but none of the choices are installable: 123s [no choices] 123s initrd-boot FAIL badpkg Ref: https://autopkgtest.ubuntu.com/results/autopkgtest- tenacious/tenacious/armhf/n/nbd/20261021_144515_39d5d@/log.gz ** Changed in: nbd (Ubuntu Stonking) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2171932 Title: autopkgtest armhf failure due to debvm not being installable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2171932/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
