On Sun, May 18, 2025 at 08:13:17PM +0900, K.Ohta wrote: > 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.
To me, this very much looks like a user error. If you delete /usr/libx32, you are very much on your own. > 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. Can you give instructions on how to reproduce a situation where /libx32 exists but /usr/libx32 does not? Ideally, you describe the release and architecture you start from, the packages you install/remove/upgrade and the point where /libx32 exists without /usr/libx32. > After these user decided to this a empty directory by hand or > automatically, upgrading base-files may occur this (or similar) issue. Packages may install empty directories. If you choose to delete those, it is up to you to deal with failing packages. Helmut
