base-files, glibc lockstep migration blocking bug

Bug #2054719 reported by Julian Andres Klode
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
base-files (Ubuntu)
Fix Released
Undecided
Unassigned
glibc (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

With the new changes I'm uploading, taken from Helmut's patches on Debian bug tracker, base-files will own the /lib64 symlink, and /lib64 in libc6 will move to /usr/lib64.

Special care has been taken to not break upgrades: You can upgrade the two in any order.

However, debootstrap requires both packages to be at a matching version:

1. If base-files migrates first, the old libc6 would fail to unpack
2. If glibc migrates first, and is bootstrapped before base-files, we do not end up with the /lib64 symlink at all because debootstrap only *moves* an existing /lib64 (which now is no longer present).

Since upgrades are fine due to having the symlink already, we do not want to solve this by introducing dependencies: We could have added mutual Depends or Breaks, but they would have required temporarily deconfiguring one of the packages to unpack the other on upgrades.

Hence we'll mark this bug as block-proposed and remove the tag once both are ready to land.

tags: added: block-proposed
Revision history for this message
Julian Andres Klode (juliank) wrote :

apt and bzip2 have migrated, so we are ready to land them in the next britney run.

tags: removed: block-proposed
Changed in base-files (Ubuntu):
status: New → Fix Released
Changed in glibc (Ubuntu):
status: New → 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.