Ubuntu
command-not-found package

autopkg test only fails on armhf

Bug #1849709 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
command-not-found (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

autopkg test only fails on armhf. needs investigation, but currently breaks autopkg tests for many test because the python-apt module is not yet available in the release pocket for python3.8.

Revision history for this message
Iain Lane (laney) wrote :

I bet you that the interesting thing is lxd rather than armhf. Try with a container build like this:

  RELEASE=focal autopkgtest-build-lxd images:ubuntu/eoan/amd64

or if focal images become available before then

  autopkgtest-build-lxd images:ubuntu/focal/amd64

Revision history for this message
Steve Langasek (vorlon) wrote :

The cnf indices were missing on the archive for focal, and this only passed on non-lxd autopkgtest architectures because (presumably) the base cloud image being used by the runners was still built from eoan and upgraded to focal so they had the indices from the prior release. The indices are now published and this bug can be closed.

Changed in command-not-found (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.