Helmut-San, Thank you for replying.
> I'm glad that the current message was sufficient to let you figure a > workaround. Before jumping to any conclusions, I'd like to better > understand the situation and whether it is a common one. Do you > happen to have backups of the system in questions? > > * Where did /libx32 point before the upgrade? > * Do you have any :x32 or -x32 packages installed before or after > the upgrade? Which packages and versions precisely? 1. /libx32 *WAS* symlink from /usr/libx32 . This existed, but I didn't use x32 architecture a long time, so I removed x32 libs by dpkg/apt. This directory (/usr/libx32 ) was empty (perhaps about a week ago). Then, this may have been a my mistake,I deleted /usr/libx32 and /lib32. 2. I had some x32 architecture libs before upgrading base-files to this version (13.8) , previous version (at I did 1.) was 13.7 . > I attempted a few related upgrades and was unsuccessful reproducing > your failure thus far. In particular, libc6-x32 is the only :amd64 > package that installs below /libx32 and installing/removing it > correctly takes care of /libx32 in bookworm. Once upgraded to trixie, > libc6-x32 installs to /usr/libx32 and base-files handles > presence/absence of /libx32. Hmm... this behavior seems to correct, but, if some user installed libc6-x32 and some x32 libraries (by some reasons) , then remove these due to be unused x32 architecture, empty /libx32 (or /usr/libx32) only remains. After these user decided to this a empty directory by hand or automatically, upgrading base-files may occur this (or similar) issue. > > In theory, we could handle the situation by deleting such a dangling > link, but that comes with a risk of breaking things. Hence, the > current strategy is giving up and letting the user sort it out. > I'll leave that up to you, but I think you should mention it in the README or another document. thanks, Ohta. On Thu, 15 May 2025 10:17:30 +0200 Helmut Grohne <hel...@subdivi.de> wrote: > Hi Santiago, > > On Thu, May 15, 2025 at 09:04:33AM +0200, Santiago Vila wrote: > > Hi. I received this from the BTS. > > > > Not sure if there is anything we can do about it. > > Thank you for forwarding. > > Hello Ohta, > > > While upgrade base-files to this version from 13.7 without x32 > > supporting (uninstall or drop x32 arch supporting), fail to install > > with below message: > > > > --- BEGIN QUOTE --- > > ****************************************************************************** > > * > > * The base-files package cannot be installed because > > * /libx32 is a dangling symbolic link. > > * > > * This is an unexpected situation. Cannot proceed with the upgrade. > > * > > * For more information please read https://wiki.debian.org/UsrMerge. > > * > > ****************************************************************************** > > --- END QUOTE --- > > > > So, I mkdir dummy /usr/libx32 and make symlink as /libx32. > > Then, retry to upgrade base-file to 13.8, it succeeded. > (snip) > > Helmut > >
