Public bug reported:
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.
** Affects: base-files (Ubuntu)
Importance: Undecided
Status: New
** Affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/2054719
Title:
base-files, glibc lockstep migration blocking bug
Status in base-files package in Ubuntu:
New
Status in glibc package in Ubuntu:
New
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054719/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
