[Bug 2059257] Re: autopkgtest failure on noble/armhf

Mate Kukri 2059257 at bugs.launchpad.net
Wed May 15 07:28:44 UTC 2024


It looks like this is passing now.

** Changed in: ubiquity (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/2059257

Title:
  autopkgtest failure on noble/armhf

Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  200s autopkgtest [18:33:28]: test unit: preparing testbed
  209s Reading package lists...
  210s Building dependency tree...
  210s Reading state information...
  210s Starting pkgProblemResolver with broken count: 2
  210s Starting 2 pkgProblemResolver with broken count: 2
  210s Investigating (0) autopkgtest-satdep:armhf < none -> 0 @un puN Ib >
  210s Broken autopkgtest-satdep:armhf Depends on oem-config-debconf:armhf < none @un H >
  210s   Considering oem-config-debconf:armhf 1 as a solution to autopkgtest-satdep:armhf 9998
  210s Broken autopkgtest-satdep:armhf Depends on oem-config-gtk:armhf < none @un H >
  210s   Considering oem-config-gtk:armhf 1 as a solution to autopkgtest-satdep:armhf 9998
  210s Broken autopkgtest-satdep:armhf Depends on oem-config-kde:armhf < none @un H >
  210s   Considering oem-config-kde:armhf 1 as a solution to autopkgtest-satdep:armhf 9998
  210s Broken autopkgtest-satdep:armhf Depends on ubiquity:armhf < none @un H >
  210s   Considering ubiquity:armhf 1 as a solution to autopkgtest-satdep:armhf 9998
  210s Broken autopkgtest-satdep:armhf Depends on ubiquity-frontend-debconf:armhf < none @un H >
  210s   Considering ubiquity-frontend-debconf:armhf 1 as a solution to autopkgtest-satdep:armhf 9998
  210s Broken autopkgtest-satdep:armhf Depends on ubiquity-frontend-gtk:armhf < none @un H >
  210s   Considering ubiquity-frontend-gtk:armhf 1 as a solution to autopkgtest-satdep:armhf 9998
  210s Broken autopkgtest-satdep:armhf Depends on ubiquity-frontend-kde:armhf < none @un H >
  210s   Considering ubiquity-frontend-kde:armhf 1 as a solution to autopkgtest-satdep:armhf 9998
  210s Investigating (0) oem-config:armhf < none -> 24.04.3 @un puN Ib >
  210s Broken oem-config:armhf Depends on oem-config-frontend-24.04.3:armhf < none @un H >
  210s   Considering oem-config-kde:armhf 1 as a solution to oem-config:armhf -1
  210s   Considering oem-config-debconf:armhf 1 as a solution to oem-config:armhf -1
  210s   Considering oem-config-gtk:armhf 1 as a solution to oem-config:armhf -1
  210s Broken oem-config:armhf Depends on ubiquity:armhf < none @un H > (= 24.04.3)
  210s   Considering ubiquity:armhf 1 as a solution to oem-config:armhf -1
  210s Done
  210s Some packages could not be installed. This may mean that you have
  210s requested an impossible situation or if you are using the unstable
  210s distribution that some required packages have not yet been created
  210s or been moved out of Incoming.
  210s The following information may help to resolve the situation:
  210s 
  210s The following packages have unmet dependencies:
  210s  autopkgtest-satdep : Depends: oem-config-debconf but it is not installable
  210s                       Depends: oem-config-gtk but it is not installable
  210s                       Depends: oem-config-kde but it is not installable
  210s                       Depends: ubiquity but it is not installable
  210s                       Depends: ubiquity-frontend-debconf but it is not installable
  210s                       Depends: ubiquity-frontend-gtk but it is not installable
  210s                       Depends: ubiquity-frontend-kde but it is not installable
  210s  oem-config : Depends: oem-config-frontend-24.04.3
  210s               Depends: ubiquity (= 24.04.3) but it is not installable
  210s E: Unable to correct problems, you have held broken packages.
  210s autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs
  212s Reading package lists...
  212s Building dependency tree...
  212s Reading state information...
  213s Starting pkgProblemResolver with broken count: 1
  213s Starting 2 pkgProblemResolver with broken count: 1
  213s Investigating (0) os-prober:armhf < none -> 1.81ubuntu3 @un puN Ib >
  213s Broken os-prober:armhf Depends on grub-common:armhf < none @un H >
  213s Done
  213s Some packages could not be installed. This may mean that you have
  213s requested an impossible situation or if you are using the unstable
  213s distribution that some required packages have not yet been created
  213s or been moved out of Incoming.
  213s The following information may help to resolve the situation:
  213s 
  213s The following packages have unmet dependencies:
  213s  os-prober : Depends: grub-common but it is not installable
  213s E: Unable to correct problems, you have held broken packages.
  213s unit                 FAIL badpkg
  213s blame: ubiquity
  213s badpkg: Test dependencies are unsatisfiable. A common reason is that your testbed is out of date with respect to the archive, and you need to use a current testbed or run apt-get update or use -U.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2059257/+subscriptions




More information about the foundations-bugs mailing list