[MIR] libisoburn, libburn, libisofs

Bug #1977959 reported by Alexandre Ghiti
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libburn (Ubuntu)
Fix Released
Undecided
Unassigned
libisoburn (Ubuntu)
Fix Released
Undecided
Unassigned
libisofs (Ubuntu)
Fix Released
Undecided
Unassigned
usb-creator (Ubuntu)
Invalid
Undecided
Alexandre Ghiti

Bug Description

[Availability]
The packages libisoburn, libburn, libisofs are already in Ubuntu universe.
The packages libisoburn, libburn, libisofs build for the architectures they are designed to work on.
They currently build and work for architectures: amd64, arm64, armhf, ppc64el, riscv64, s390x
Link to packages:

 [[https://launchpad.net/ubuntu/+source/libisoburn]]
 [[https://launchpad.net/ubuntu/+source/libburn]]
 [[https://launchpad.net/ubuntu/+source/libisofs]]

[Rationale]
- The package libisoburn is required in Ubuntu main for usb-creator, and libburn and libisofs are dependencies of libisoburn.
- The package libisoburn will generally be useful for a large part of
  our user base as usb-creator is seeded
- Package libisoburn covers the same use case as genisoimage, but is better
  because contrary to genisoimage, it is actively maintained upstream, upstream engages with launchpad issues and
  we have been using xorriso for years now instead of genisoimage in the official Ubuntu image pipeline,
  thereby we want to replace it.
- The package libisoburn is a new runtime dependency of package usb-creator that
  we already support
- It would be great and useful to community/processes to have the
  package libisoburn in Ubuntu main, but there is no definitive deadline.

[Security]
- No CVEs/security issues in this software in the past
- no `suid` or `sgid` binaries
- no executables in `/sbin` and `/usr/sbin`
- Packages does not install services, timers or recurring jobs
- Packages does not open privileged ports (ports < 1024)

[Quality assurance - function/usage]
- The packages work well right after install

[Quality assurance - maintenance]
- The packages are maintained well in Debian/Ubuntu and have not any
  long term critical bugs open

libisoburn:
  - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libisoburn/+bug
  => only 1 bug from 2021 on Focal image on ppc64el which received lots of answers
  - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libisoburn
  => only 4 wishlist items

libburn:
  - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libburn/+bug
  => 0 bug
  - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libburn
  => 0 bug

libisofs:
  - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libisofs/+bug
  => 0 bug
  - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libisofs
  => 0 bug

- The packages do not deal with exotic hardware we cannot support

[Quality assurance - testing]

libisoburn:
        - The package runs *one very simple test* at build time, if it fails it makes the build fail, link to build log (https://launchpadlibrarian.net/564560287/buildlog_ubuntu-jammy-amd64.libisoburn_1.5.4-2_BUILDING.txt.gz).
        - The package does not run an autopkgtest because the official test suite was not enabled.
        - The package can be tested by enabling the "releng" testsuite that is present in the package that we will enable before the promotion: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13673188/+listing-archive-extra

libburn:
        - The package does not run a test at build time because it relies on "releng" testsuite enabled in libisoburn.
        - The package does not run an autopkgtest because it relies on "releng" testsuite enabled in libisoburn.
        - The package will take advantage of the enablement of "releng" testsuite in libisoburn.

libisofs:
        - The package does not run a test at build time because it relies on "releng" testsuite enabled in libisoburn.
        - The package does not run an autopkgtest because it relies on "releng" testsuite enabled in libisoburn.
        - The package will take advantage of the enablement of "releng" testsuite in libisoburn.

[Quality assurance - packaging]
- debian/watch is present and works
- debian/control defines a correct Maintainer field

- Those packages do not yield massive lintian Warnings, Errors:

libisoburn:
        - Please link to a recent build log of the package https://launchpadlibrarian.net/564560287/buildlog_ubuntu-jammy-amd64.libisoburn_1.5.4-2_BUILDING.txt.gz

        P: libisoburn source: maintainer-manual-page debian/local/libisoburn.3
        P: libisoburn source: package-uses-old-debhelper-compat-version 12
        P: libisoburn source: silent-on-rules-requiring-root [debian/control]
        P: libisoburn source: trailing-whitespace debian/control (line 154)

        - Lintian overrides are present (https://salsa.debian.org/optical-media-team/libisoburn/-/blob/master/debian/libisoburn1.lintian-overrides), but ok because there are only 2 spelling overrides (spelling-error-in-binary) that are kept for compatibility with frontends.

libburn:
        - Please link to a recent build log of the package https://launchpadlibrarian.net/564542502/buildlog_ubuntu-jammy-amd64.libburn_1.5.4-1_BUILDING.txt.gz

        P: libburn source: package-uses-old-debhelper-compat-version 12
        P: libburn source: silent-on-rules-requiring-root [debian/control]

        - Lintian overrides are present (https://salsa.debian.org/optical-media-team/libburn/-/blob/master/debian/libburn4.lintian-overrides), but ok it is a exit-in-shared-library which is only an info.

libisofs:
        - Please link to a recent build log of the package https://launchpadlibrarian.net/564542190/buildlog_ubuntu-jammy-amd64.libisofs_1.5.4-1_BUILDING.txt.gz

        W: libisofs source: superfluous-file-pattern libtool.m4 [debian/copyright:143]
        W: libisofs source: superfluous-file-pattern ltoptions.m4 [debian/copyright:147]
        W: libisofs source: superfluous-file-pattern ltsugar.m4 [debian/copyright:17]
        W: libisofs source: superfluous-file-pattern ltversion.m4 [debian/copyright:17]
        W: libisofs source: superfluous-file-pattern lt~obsolete.m4 [debian/copyright:17]
        P: libisofs source: package-uses-old-debhelper-compat-version 12
        P: libisofs source: silent-on-rules-requiring-root [debian/control]

        => the warnings only link to entries in debian/copyright that point to non-existing files in the package.

        - Lintian overrides are not present

- Those packages do not rely on obsolete or about to be demoted packages.
- Those packages have no python2 or GTK2 dependencies

- Those packages will be installed by default, but do not ask debconf
  questions higher than medium

- Packaging and build is easy, link to d/rules

libisoburn: https://salsa.debian.org/optical-media-team/libisoburn/-/blob/master/debian/rules
libburn: https://salsa.debian.org/optical-media-team/libburn/-/blob/master/debian/rules
libisofs: https://salsa.debian.org/optical-media-team/libisofs/-/blob/master/debian/rules

[UI standards]
- libisofs and libburn packages produce a binary package whose application is end-user facing and translation is not present.
- End-user applications without desktop file, not needed because those are very niche applications that most users won't ever use.

[Dependencies]
- There are further dependencies that are not yet in main, MIR for them is at jigit (TODO)
- There are further dependencies that are not yet in main, the MIR
  process for them is handled as part of this bug here since libburn and libisofs are part of the same upstream project.

[Standards compliance]
- Those packages correctly follow FHS and Debian Policy

[Maintenance/Owner]
- Owning Team will be Foundations
- Team is not yet, but will subscribe to the packages before promotion
- They do not use static builds
- They do not use vendored code
- The packages successfully built during the most recent test rebuild

libisoburn: https://launchpad.net/ubuntu/+archive/test-rebuild-20220317-jammy/+packages?field.name_filter=libisoburn&field.status_filter=published&field.series_filter=
libburn: https://launchpad.net/ubuntu/+archive/test-rebuild-20220317-jammy/+packages?field.name_filter=libburn&field.status_filter=published&field.series_filter=
libburn: https://launchpad.net/ubuntu/+archive/test-rebuild-20220317-jammy/+packages?field.name_filter=libisofs&field.status_filter=published&field.series_filter=

[Background information]
The Package descriptions explain the packages well
Upstream Name is libisoburn, libburn and libisofs respectively
Link to upstream project https://dev.lovelyhq.com/libburnia/web/wiki

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

FTR: these packages have been in main in the past, LP: #582189

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libburn (Ubuntu):
status: New → Confirmed
Changed in libisoburn (Ubuntu):
status: New → Confirmed
Changed in libisofs (Ubuntu):
status: New → Confirmed
description: updated
tags: added: update-excuse
Changed in usb-creator (Ubuntu):
assignee: nobody → Alexandre Ghiti (alexghiti)
Changed in libisofs (Ubuntu):
assignee: nobody → Didier Roche (didrocks)
Changed in libisoburn (Ubuntu):
assignee: nobody → Didier Roche (didrocks)
Changed in libburn (Ubuntu):
assignee: nobody → Didier Roche (didrocks)
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :
Download full text (3.6 KiB)

[Summary]
MIR review for libisoburn
MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.
This does not need a security review
List of specific binary packages to be promoted to main: xorriso, libisoburn1, libisoburn-dev, libisoburn-doc

Notes:
Required TODOs:
- In addition of this MIR for the 3 packages, ensure that jigit MIR is also acked (https://bugs.launchpad.net/ubuntu/+source/jigit/+bug/1978066).
- Symbol tracking is not in place for libisoburn. Please add some tracking for the libisoburn symbols.
Recommended TODOs:
- There are quite a lot of warning during build (see section), I think some of them are valid and should be fixed. Mind looking at them? (Warnings are always asking for more warnings and could be overlooked)
- The package should get a team bug subscriber before being promoted

[Duplication]
libisoburn/libisofs/libburn will replace genisoimage usage in main.

[Dependencies]
OK:
- no other Dependencies to MIR due to this than the ones listed in description and jigit which is in another MIR (https://bugs.launchpad.net/ubuntu/+source/jigit/+bug/1978066)
- libisoburn checked with `check-mir`
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring more tests now.

Problems:
- ensure that jigit MIR is acked (https://bugs.launchpad.net/ubuntu/+source/jigit/+bug/1978066)

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have odd Built-Using entries

OK:
- not a go package, no extra constraints to consider in that regard

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats
- does not open a port/socket
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)

[Common blockers]
OK:
- does not FTBFS currently
- does have a test suite that runs at build time
- test suite fails will fail the build upon error.
- does have the releng non-trivial test suite that runs as autopkgtest
- no new python2 dependency

[Packaging red flags]
OK:
- Ubuntu does carry a delta, but it is reasonable and maintenance under
  control
- d/watch is present and looks ok (if needed, e.g. non-native)
- Upstream update history is slow (but acceptable for this kind of project due to the history)
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
- no massive Lintian warnings
- d/rules is rather clean
- It is not on the lto-disabled list

Problems:
- symbol tracking is not in place for libisoburn and only rely on shlibs. Any reason to not have a real symbol tracking?

[Upstream red flags]
OK:
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests) as...

Read more...

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

[Summary]
MIR review for libburn
MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.
This does not need a security review
List of specific binary packages to NOT be promoted to main: cdrskin

Notes:
Required TODOs:
- Symbol tracking is not in place for libburn. Please add some tracking for the libburn symbols.
Recommended TODOs:
- There are quite a lot of warning during build (see section), I think some of them are valid and should be fixed. Mind looking at them? (Warnings are always asking for more warnings and could be overlooked)
- The package should get a team bug subscriber before being promoted

[Duplication]
libisoburn/libisofs/libburn will replace genisoimage usage in main.

[Dependencies]
OK:
- no other Dependencies to MIR due to this.
- libburn checked with `check-mir`
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring more tests now.

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have odd Built-Using entries

OK:
- not a go package, no extra constraints to consider in that regard

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats
- does not open a port/socket
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)

[Common blockers]
OK:
- does not FTBFS currently
- does rely on libisoburn releng non-trivial test suite that runs as autopkgtest for both build test and package test.- no new python2 dependency

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- d/watch is present and looks ok
- Upstream update history is slow (but acceptable for this kind of project due to the history)
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
- no massive Lintian warnings
- d/rules is rather clean
- It is not on the lto-disabled list

Problems:
- symbol tracking is not in place for libburn and only rely on shlibs. Any reason to not have a real symbol tracking?

[Upstream red flags]
OK:
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests).
- no use of user nobody
- use of setuid possible, but ok because in cdrskin which we don’t consider and not by default.
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- UI desktop/translation: no translation present, but the niche usage can justify not having it.

Problems:
- There are a bunch of warnings during builds. Some of them sounds fixable and it’s probably the right time to look at them.

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

[Summary]
MIR review for libisofs
MIR team ACK under the constraint to resolve the below listed
required TODOs and as much as possible having a look at the
recommended TODOs.
This does not need a security review
List of specific binary packages to be promoted to main: libisofs-dev, libisofs-doc, libisofs6

Notes:
Required TODOs:
- Symbol tracking is not in place for libisofs. Please add some tracking for the libburn symbols.
Recommended TODOs:
- This package have more lintian issues than others (and not only pendatic ones). As previously, warnings are always asking for more warnings IMHO and those are really easy to fix (files in debian/copyright that are not present). Can we clean them?
- The package should get a team bug subscriber before being promoted

[Duplication]
libisoburn/libisofs/libburn will replace genisoimage usage in main.

[Dependencies]
OK:
- no other Dependencies to MIR due to this.
- libburn checked with `check-mir`
- no -dev/-debug/-doc packages that need exclusion
- No dependencies in main that are only superficially tested requiring more tests now.

[Embedded sources and static linking]
OK:
- no embedded source present
- no static linking
- does not have odd Built-Using entries

OK:
- not a go package, no extra constraints to consider in that regard

[Security]
OK:
- history of CVEs does not look concerning
- does not run a daemon as root
- does not use webkit1,2
- does not use lib*v8 directly
- does not parse data formats
- does not open a port/socket
- does not process arbitrary web content
- does not use centralized online accounts
- does not integrate arbitrary javascript into the desktop
- does not deal with system authentication (eg, pam), etc)
- does not deal with security attestation (secure boot, tpm, signatures)

[Common blockers]
OK:
- does not FTBFS currently
- does rely on libisoburn releng non-trivial test suite that runs as autopkgtest for both build test and package test.
- no new python2 dependency

[Packaging red flags]
OK:
- Ubuntu does not carry a delta
- d/watch is present and looks ok
- Upstream update history is slow (but acceptable for this kind of project due to the history)
- Debian/Ubuntu update history is good
- the current release is packaged
- promoting this does not seem to cause issues for MOTUs that so far
- d/rules is rather clean
- It is not on the lto-disabled list

Problems:
- Several lintian warnings that ought to be simple to fix. I think we should have a lintian-clean package (excluding pedantic) at least.
- symbol tracking is not in place for libburn and only rely on shlibs. Any reason to not have a real symbol tracking?

[Upstream red flags]
OK:
- no Errors/warnings during the build
- no incautious use of malloc/sprintf (as far as we can check it)
- no use of sudo, gksu, pkexec, or LD_LIBRARY_PATH (usage is OK inside
  tests).
- no use of user nobody
- use of setuid possible, but ok because in cdrskin which we don’t consider and not by default.
- no important open bugs (crashers, etc) in Debian or Ubuntu
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
- no translation present, but not needed.

Changed in libburn (Ubuntu):
assignee: Didier Roche (didrocks) → nobody
Changed in libisoburn (Ubuntu):
assignee: Didier Roche (didrocks) → nobody
Changed in libisofs (Ubuntu):
assignee: Didier Roche (didrocks) → nobody
Changed in libburn (Ubuntu):
status: Confirmed → Incomplete
Changed in libisofs (Ubuntu):
status: Confirmed → Incomplete
Changed in libisoburn (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Alexandre Ghiti (alexghiti) wrote :

* libisoburn:

Required TODOs:
- I completed every required TODOs for the jigit MIR: https://bugs.launchpad.net/ubuntu/+source/jigit/+bug/1978066.
- I added the symbols file and wait for sponsor https://bugs.launchpad.net/ubuntu/+source/libisoburn/+bug/1979530
Recommended TODOs:
- I'll take a look at the warnings in 10 days after my holidays.
- I have just subscribed the Foundations team to all bugs.

* libisofs:
Required TODOs:
- I added the symbols file and wait for sponsor https://bugs.launchpad.net/ubuntu/+source/libisofs/+bug/1979533
Recommended TODOs:
- I'll take a look at the warnings in 10 days after my holidays.
- I have just subscribed the Foundations team to all bugs.

* libburn:

Required TODOs:
- I added the symbols file and wait for sponsor https://bugs.launchpad.net/ubuntu/+source/libburn/+bug/1979531
Recommended TODOs:
- I'll take a look at the warnings in 10 days after my holidays.
- I have just subscribed the Foundations team to all bugs.

Revision history for this message
Alexandre Ghiti (alexghiti) wrote :

Thanks by the way!

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

The .symbols change got sponsored for libisoburn.

For libisofs and libburn, I think we do not necessarily need it, according to MIR rules:
RULE: - If it's a library, does it either have a symbols file or use an empty
RULE: argument to dh_makeshlibs -V? (pass such a patch on to Debian, but
RULE: don't block on it).

The packages make use of `dh_makeshlibs -V` in d/rules – so we should be fine for the MIR. And the patches from LP: #1979533 and LP: #1979531 should rather be forwarded to Debian, to start a discussion, instead of inroducing an Ubuntu delta.

Revision history for this message
Alexandre Ghiti (alexghiti) wrote :
Changed in libburn (Ubuntu):
status: Incomplete → New
Changed in libisoburn (Ubuntu):
status: Incomplete → New
Changed in libisofs (Ubuntu):
status: Incomplete → New
Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

MIR team ACK then. Thanks for working on this!

Changed in libburn (Ubuntu):
status: New → Fix Committed
Changed in libisoburn (Ubuntu):
status: New → Fix Committed
Changed in libisofs (Ubuntu):
status: New → Fix Committed
Revision history for this message
Steve Langasek (vorlon) wrote :

Override component to main
libburn 1.5.4-1 in kinetic: universe/libs -> main
cdrskin 1.5.4-1 in kinetic amd64: universe/otherosfs/optional/100% -> main
cdrskin 1.5.4-1 in kinetic arm64: universe/otherosfs/optional/100% -> main
cdrskin 1.5.4-1 in kinetic armhf: universe/otherosfs/optional/100% -> main
cdrskin 1.5.4-1 in kinetic ppc64el: universe/otherosfs/optional/100% -> main
cdrskin 1.5.4-1 in kinetic riscv64: universe/otherosfs/optional/100% -> main
cdrskin 1.5.4-1 in kinetic s390x: universe/otherosfs/optional/100% -> main
libburn-dev 1.5.4-1 in kinetic amd64: universe/libdevel/optional/100% -> main
libburn-dev 1.5.4-1 in kinetic arm64: universe/libdevel/optional/100% -> main
libburn-dev 1.5.4-1 in kinetic armhf: universe/libdevel/optional/100% -> main
libburn-dev 1.5.4-1 in kinetic ppc64el: universe/libdevel/optional/100% -> main
libburn-dev 1.5.4-1 in kinetic riscv64: universe/libdevel/optional/100% -> main
libburn-dev 1.5.4-1 in kinetic s390x: universe/libdevel/optional/100% -> main
libburn-doc 1.5.4-1 in kinetic amd64: universe/doc/optional/100% -> main
libburn-doc 1.5.4-1 in kinetic arm64: universe/doc/optional/100% -> main
libburn-doc 1.5.4-1 in kinetic armhf: universe/doc/optional/100% -> main
libburn-doc 1.5.4-1 in kinetic i386: universe/doc/optional/100% -> main
libburn-doc 1.5.4-1 in kinetic ppc64el: universe/doc/optional/100% -> main
libburn-doc 1.5.4-1 in kinetic riscv64: universe/doc/optional/100% -> main
libburn-doc 1.5.4-1 in kinetic s390x: universe/doc/optional/100% -> main
libburn4 1.5.4-1 in kinetic amd64: universe/libs/optional/100% -> main
libburn4 1.5.4-1 in kinetic arm64: universe/libs/optional/100% -> main
libburn4 1.5.4-1 in kinetic armhf: universe/libs/optional/100% -> main
libburn4 1.5.4-1 in kinetic ppc64el: universe/libs/optional/100% -> main
libburn4 1.5.4-1 in kinetic riscv64: universe/libs/optional/100% -> main
libburn4 1.5.4-1 in kinetic s390x: universe/libs/optional/100% -> main
26 publications overridden.

Changed in libburn (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :

Override component to main
libisofs 1.5.4-1 in kinetic: universe/libs -> main
libisofs-dev 1.5.4-1 in kinetic amd64: universe/libdevel/optional/100% -> main
libisofs-dev 1.5.4-1 in kinetic arm64: universe/libdevel/optional/100% -> main
libisofs-dev 1.5.4-1 in kinetic armhf: universe/libdevel/optional/100% -> main
libisofs-dev 1.5.4-1 in kinetic ppc64el: universe/libdevel/optional/100% -> main
libisofs-dev 1.5.4-1 in kinetic riscv64: universe/libdevel/optional/100% -> main
libisofs-dev 1.5.4-1 in kinetic s390x: universe/libdevel/optional/100% -> main
libisofs-doc 1.5.4-1 in kinetic amd64: universe/doc/optional/100% -> main
libisofs-doc 1.5.4-1 in kinetic arm64: universe/doc/optional/100% -> main
libisofs-doc 1.5.4-1 in kinetic armhf: universe/doc/optional/100% -> main
libisofs-doc 1.5.4-1 in kinetic i386: universe/doc/optional/100% -> main
libisofs-doc 1.5.4-1 in kinetic ppc64el: universe/doc/optional/100% -> main
libisofs-doc 1.5.4-1 in kinetic riscv64: universe/doc/optional/100% -> main
libisofs-doc 1.5.4-1 in kinetic s390x: universe/doc/optional/100% -> main
libisofs6 1.5.4-1 in kinetic amd64: universe/libs/optional/100% -> main
libisofs6 1.5.4-1 in kinetic arm64: universe/libs/optional/100% -> main
libisofs6 1.5.4-1 in kinetic armhf: universe/libs/optional/100% -> main
libisofs6 1.5.4-1 in kinetic ppc64el: universe/libs/optional/100% -> main
libisofs6 1.5.4-1 in kinetic riscv64: universe/libs/optional/100% -> main
libisofs6 1.5.4-1 in kinetic s390x: universe/libs/optional/100% -> main
20 publications overridden.

Changed in libisofs (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote :
Download full text (3.4 KiB)

libisoburn 1:1.5.4-2ubuntu2 in kinetic: universe/libs -> main
libisoburn-dev 1:1.5.4-2ubuntu2 in kinetic amd64: universe/libdevel/optional/100% -> main
libisoburn-dev 1:1.5.4-2ubuntu2 in kinetic arm64: universe/libdevel/optional/100% -> main
libisoburn-dev 1:1.5.4-2ubuntu2 in kinetic armhf: universe/libdevel/optional/100% -> main
libisoburn-dev 1:1.5.4-2ubuntu2 in kinetic ppc64el: universe/libdevel/optional/100% -> main
libisoburn-dev 1:1.5.4-2ubuntu2 in kinetic riscv64: universe/libdevel/optional/100% -> main
libisoburn-dev 1:1.5.4-2ubuntu2 in kinetic s390x: universe/libdevel/optional/100% -> main
libisoburn-doc 1:1.5.4-2ubuntu2 in kinetic amd64: universe/doc/optional/100% -> main
libisoburn-doc 1:1.5.4-2ubuntu2 in kinetic arm64: universe/doc/optional/100% -> main
libisoburn-doc 1:1.5.4-2ubuntu2 in kinetic armhf: universe/doc/optional/100% -> main
libisoburn-doc 1:1.5.4-2ubuntu2 in kinetic i386: universe/doc/optional/100% -> main
libisoburn-doc 1:1.5.4-2ubuntu2 in kinetic ppc64el: universe/doc/optional/100% -> main
libisoburn-doc 1:1.5.4-2ubuntu2 in kinetic riscv64: universe/doc/optional/100% -> main
libisoburn-doc 1:1.5.4-2ubuntu2 in kinetic s390x: universe/doc/optional/100% -> main
libisoburn1 1:1.5.4-2ubuntu2 in kinetic amd64: universe/libs/optional/100% -> main
libisoburn1 1:1.5.4-2ubuntu2 in kinetic arm64: universe/libs/optional/100% -> main
libisoburn1 1:1.5.4-2ubuntu2 in kinetic armhf: universe/libs/optional/100% -> main
libisoburn1 1:1.5.4-2ubuntu2 in kinetic ppc64el: universe/libs/optional/100% -> main
libisoburn1 1:1.5.4-2ubuntu2 in kinetic riscv64: universe/libs/optional/100% -> main
libisoburn1 1:1.5.4-2ubuntu2 in kinetic s390x: universe/libs/optional/100% -> main
xorriso 1:1.5.4-2ubuntu2 in kinetic amd64: universe/otherosfs/optional/100% -> main
xorriso 1:1.5.4-2ubuntu2 in kinetic arm64: universe/otherosfs/optional/100% -> main
xorriso 1:1.5.4-2ubuntu2 in kinetic armhf: universe/otherosfs/optional/100% -> main
xorriso 1:1.5.4-2ubuntu2 in kinetic ppc64el: universe/otherosfs/optional/100% -> main
xorriso 1:1.5.4-2ubuntu2 in kinetic riscv64: universe/otherosfs/optional/100% -> main
xorriso 1:1.5.4-2ubuntu2 in kinetic s390x: universe/otherosfs/optional/100% -> main
xorriso-dd-target 1:1.5.4-2ubuntu2 in kinetic amd64: universe/utils/optional/100% -> main
xorriso-dd-target 1:1.5.4-2ubuntu2 in kinetic arm64: universe/utils/optional/100% -> main
xorriso-dd-target 1:1.5.4-2ubuntu2 in kinetic armhf: universe/utils/optional/100% -> main
xorriso-dd-target 1:1.5.4-2ubuntu2 in kinetic i386: universe/utils/optional/100% -> main
xorriso-dd-target 1:1.5.4-2ubuntu2 in kinetic ppc64el: universe/utils/optional/100% -> main
xorriso-dd-target 1:1.5.4-2ubuntu2 in kinetic riscv64: universe/utils/optional/100% -> main
xorriso-dd-target 1:1.5.4-2ubuntu2 in kinetic s390x: universe/utils/optional/100% -> main
xorriso-tcltk 1:1.5.4-2ubuntu2 in kinetic amd64: universe/utils/optional/100% -> main
xorriso-tcltk 1:1.5.4-2ubuntu2 in kinetic arm64: universe/utils/optional/100% -> main
xorriso-tcltk 1:1.5.4-2ubuntu2 in kinetic armhf: universe/utils/optional/100% -> main
xorriso-tcltk 1:1.5.4-2ubuntu2 in kinetic i386: universe/ut...

Read more...

Changed in libisoburn (Ubuntu):
status: Fix Committed → Fix Released
Changed in usb-creator (Ubuntu):
status: New → Fix Released
Revision history for this message
Lukas Märdian (slyon) wrote :

src:libisofs is still blocked on the jigit MIR (LP: #1978066)

Changed in libisofs (Ubuntu):
status: Fix Released → In Progress
Revision history for this message
Lukas Märdian (slyon) wrote :

The libisoburn->jigit & libisofs->jigit dependency got dropped to avoid the component mismatch.

https://launchpad.net/ubuntu/+source/libisoburn/1:1.5.4-2ubuntu3
https://launchpad.net/ubuntu/+source/libisofs/1.5.4-1ubuntu1

Changed in libisofs (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Lukas Märdian (slyon) wrote :

Looks like src:libisoburn inroduced another component-mismatch:
"xorriso-tcltk/amd64 in main cannot depend on bwidget in universe"

I wonder if we should demote the xorriso-tcltk binary, AFAIU the GUI is not really needed.

Changed in usb-creator (Ubuntu):
status: Fix Released → New
tags: added: block-proposed
Changed in libisoburn (Ubuntu):
status: Fix Released → In Progress
Lukas Märdian (slyon)
Changed in libisoburn (Ubuntu):
status: In Progress → Fix Released
Lukas Märdian (slyon)
Changed in usb-creator (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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