python-libmaas has no autopkgtests, went two release cycles completely broken

Bug #2009238 reported by Steve Langasek
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-libmaas (Ubuntu)
Fix Committed
Critical
James Page

Bug Description

Bug #1989118 shows that python-libmaas was not compatible with python 3.10 and thus made it into an LTS release (and a subsequent non-LTS release) completely broken.

An SRU has been prepared to update the package to the latest upstream version in jammy and kinetic so that it works again.

But even in lunar, this package has no autopkgtests, which would have identified to the Ubuntu developers BEFORE the upgrade to python3.10 that the package was incompatible.

This package should be updated to include the standard sorts of autopkgtests to ensure compatibility with future versions of python (even a simple 'import' as seen in that SRU bug's test case would be enough); or, if this package is of so little importance that no one will notice it is broken for 5 months after an LTS release, it should be dropped from the archive.

Steve Langasek (vorlon)
Changed in python-libmaas (Ubuntu):
importance: Undecided → Critical
Revision history for this message
James Page (james-page) wrote :

Bah - missed the bug - I've just uploaded a new package version with autokpkgtests enabled to Lunar; this includes the autodep8 tests for python and full execution of the unit test suite included with libmaas.

Changed in python-libmaas (Ubuntu):
status: New → Fix Committed
assignee: nobody → James Page (james-page)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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