libisoburn1 and libisofs6 (in main) depend on libjte2 (in universe)

Bug #1981359 reported by Luís Infante da Câmara
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libisoburn (Ubuntu)
Fix Released
Undecided
Unassigned
libisofs (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

When upgrading my Ubuntu 22.10 VM with apt full-upgrade, I received updates for libisoburn1 and libisofs6 (both in main) that introduce a dependency on libjte2 (in universe).

Users of this version of Ubuntu with the universe component disabled will get an error when upgrading the system (if any of the packages is installed, that is most likely the case as they are installed by default) or any of these packages.

The jigit source package (from which libjte2 is built) is undergoing a main inclusion review (MIR): see bug #1978066.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: libisoburn1 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.22.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 11 20:16:24 2022
InstallationDate: Installed on 2022-06-26 (15 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220624)
SourcePackage: libisoburn
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
Luís Infante da Câmara (luis220413) wrote :
summary: - libisoburn1 and libisofs6 (in main) depends on libjte2 (in universe)
+ libisoburn1 and libisofs6 (in main) depend on libjte2 (in universe)
Revision history for this message
Luís Infante da Câmara (luis220413) wrote (last edit ):

I filed this bug because users of Ubuntu Kinetic with the universe component disabled will get an error when upgrading the system or this package, and to alert users of the development release (that may not be familiar with the Ubuntu development process) for this installation issue, discouraging them from filing duplicate bugs. Therefore, I have removed the duplicate marker from this bug.

description: updated
Revision history for this message
Lukas Märdian (slyon) wrote :

This has been rolled back, see LP: #1900972

It should only be upgrading once the MIR is resolved.

Lukas Märdian (slyon)
Changed in libisoburn (Ubuntu):
status: New → In Progress
Changed in libisofs (Ubuntu):
status: New → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libisofs - 1.5.4-1ubuntu1

---------------
libisofs (1.5.4-1ubuntu1) kinetic; urgency=medium

  * d/rules: Do not build against libjte anymore as jigit can't get into main
    (LP: #1981359, MIR LP: 1978066)

 -- Alexandre Ghiti <email address hidden> Fri, 22 Jul 2022 14:04:06 +0200

Changed in libisofs (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libisoburn - 1:1.5.4-2ubuntu3

---------------
libisoburn (1:1.5.4-2ubuntu3) kinetic; urgency=medium

  * d/rules: Do not build against libjte anymore as jigit can't get into main
    (LP: #1981359, MIR LP: 1978066)

 -- Alexandre Ghiti <email address hidden> Mon, 25 Jul 2022 13:55:49 +0200

Changed in libisoburn (Ubuntu):
status: In Progress → Fix Released
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.