Automatically installed bit not transitioned to t64 libraries

Bug #2064090 reported by Julian Andres Klode
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
In Progress
Undecided
Unassigned
Noble
Fix Committed
Undecided
Unassigned

Bug Description

[Impact]
libraries become marked as manually installed after transitioning to t64 package names as we forgot to transition the automatically installed bit.

Before:
root@m:~# apt-mark showmanual
base-files
bash
bsdutils
cloud-init
dash
diffutils
eatmydata
findutils
grep
gzip
hostname
init
isc-dhcp-client
isc-dhcp-common
libeatmydata1
libwrap0
linux-base
login
ncurses-base
ncurses-bin
ncurses-term
openssh-server
openssh-sftp-server
python-babel-localedata
python3-babel
python3-jinja2
python3-json-pointer
python3-jsonpatch
python3-jsonschema
python3-markupsafe
python3-pyrsistent
python3-serial
python3-tz
ssh-import-id
ubuntu-minimal
ubuntu-server
ubuntu-standard
util-linux

Broken After:
base-files
bash
bsdutils
cloud-init
dash
diffutils
eatmydata
findutils
grep
gzip
hostname
init
isc-dhcp-client
isc-dhcp-common
libapt-pkg6.0t64
libarchive13t64
libatm1t64
libc6
libcurl3t64-gnutls
libcurl4t64
libdb5.3t64
libdw1t64
libeatmydata1
libelf1t64
libevent-core-2.1-7t64
libext2fs2t64
libgdbm-compat4t64
libgdbm6t64
libglib2.0-0t64
libgnutls30t64
libgpgme11t64
libhogweed6t64
libisns0t64
libmagic1t64
libmspack0t64
libnettle8t64
libnpth0t64
libntfs-3g89t64
libnvme1t64
libparted2t64
libpng16-16t64
libpsl5t64
libreadline8t64
libssl3t64
libtirpc3t64
liburcu8t64
libuv1t64
libwrap0
libxmlsec1t64
libxmlsec1t64-openssl
linux-base
login
ncurses-base
ncurses-bin
ncurses-term
openssh-server
openssh-sftp-server
python-babel-localedata
python3-babel
python3-jinja2
python3-json-pointer
python3-jsonpatch
python3-jsonschema
python3-markupsafe
python3-pyrsistent
python3-serial
python3-tz
ssh-import-id
ubuntu-minimal
ubuntu-server
ubuntu-standard
util-linux

[Test plan]
Launch a mantic container
Upgrade to noble
Check that the t64 libraries are automatically installed

[Where problems could occur]
Manual install requests are tried harder, but since we only hint the upgrade solver here, we don't expect this to cause any less successful install requests.

affects: systemd (Ubuntu) → ubuntu-release-upgrader (Ubuntu)
description: updated
Revision history for this message
Julian Andres Klode (juliank) wrote :

Fixed in git

Changed in ubuntu-release-upgrader (Ubuntu Noble):
status: New → Fix Committed
Revision history for this message
Mauricio Faria de Oliveira (mfo) wrote :

Moving from Fix Committed back to In Progress as this isn't in -proposed yet,
and In Progress reflects 'uploaded' better.

(I don't mean to be pedantic, but this avoids confusion; even though the git
repo was mentioned, AFAIK the 'Ubuntu' project in bug tasks means the status
Fix Committed should be interpreted as -proposed/Ubuntu Archive, not others.)

https://wiki.ubuntu.com/Bugs/Bug%20statuses

Changed in ubuntu-release-upgrader (Ubuntu Noble):
status: Fix Committed → In Progress
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Julian, or anyone else affected,

Accepted ubuntu-release-upgrader into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:24.04.17 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in ubuntu-release-upgrader (Ubuntu Noble):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-noble
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (ubuntu-release-upgrader/1:24.04.17)

All autopkgtests for the newly accepted ubuntu-release-upgrader (1:24.04.17) for noble have finished running.
The following regressions have been reported in tests triggered by the package:

ubuntu-release-upgrader/1:24.04.17 (arm64, armhf, ppc64el, s390x)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/noble/update_excuses.html#ubuntu-release-upgrader

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello Julian, or anyone else affected,

Accepted ubuntu-release-upgrader into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:24.04.18 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-noble. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Nick Rosbrook (enr0n) wrote :

I have verified using the upgrader tarball in noble-proposed:

root@m:~# wget http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
--2024-05-16 12:44:06-- http://archive.ubuntu.com/ubuntu/dists/noble-proposed/main/dist-upgrader-all/24.04.18/noble.tar.gz
Resolving archive.ubuntu.com (archive.ubuntu.com)... 91.189.91.81, 185.125.190.39, 91.189.91.83, ...
Connecting to archive.ubuntu.com (archive.ubuntu.com)|91.189.91.81|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1274850 (1.2M) [application/x-gzip]
Saving to: ‘noble.tar.gz’

noble.tar.gz 100%[================================================>] 1.21M 1.51MB/s in 0.8s

2024-05-16 12:44:07 (1.51 MB/s) - ‘noble.tar.gz’ saved [1274850/1274850]

root@m:~# tar xvf noble.tar.gz
root@m:~# apt-mark showmanual > manual.before
root@m:~# ./noble
[ ... upgrading ... ]
root@m:~# apt-mark showmanual > manual.after
root@m:~# diff -u manual.{before,after}
--- manual.before 2024-05-16 12:46:58.802671205 +0000
+++ manual.after 2024-05-16 13:00:59.391160334 +0000
@@ -12,6 +12,7 @@
 init
 isc-dhcp-client
 isc-dhcp-common
+libc6
 libeatmydata1
 libwrap0
 linux-base
root@m:~#

tags: added: verification-done verification-done-noble
removed: verification-needed verification-needed-noble
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.