autopkgtest failure with new lsb_release implementation
Bug #2007566 reported by
Dave Jones
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| apt-clone (Debian) |
Fix Released
|
Unknown
|
|||
| apt-clone (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
The autopkgtests for apt-clone fail with the version of lsb_release now provided by lsb-release-
The upstream repository has a PR addressing this [1] which we should apply temporarily to permit migration of lsb-release-
Revision history for this message
| Dave Jones (waveform) wrote | #1 |
| tags: | added: patch |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in apt-clone (Ubuntu): | |
| status: | New → Fix Released |
| Changed in apt-clone (Debian): | |
| status: | Unknown → New |
| Changed in apt-clone (Debian): | |
| status: | New → Fix Committed |
| Changed in apt-clone (Debian): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package apt-clone - 0.4.3+nmu1ubuntu1
---------------
apt-clone (0.4.3+nmu1ubuntu1) lunar; urgency=medium
* Apply PR #17 to have apt-clone call lsb_release as a command, instead of
importing the Python module which no longer exists (LP: #2007566)
-- Dave Jones <email address hidden> Thu, 16 Feb 2023 11:38:03 +0000