Helmut-San,
Sorry for later a lot.
(snip)
> 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.
*Prereq:
1. I installed Debian GNU/Linux for my PC a long time,
from 2.0 "hamm" or 1.3 "bo".
Of cource, I replaced a PCs a lot, but OS and softwares were
inherited beyond PCs, HDDs and SDDs.
2. I added AMD64 archtecture very early timing (perhaps 2005~2006).
*Instruction (I don't test completely due to my poorly
disk capacity , sorry).
1. Install older Debian GNU/Linux (i.e. 8 "jessie")
both for i386 and amd64 on VM capability to get snapshot.
For example, VirtualBox.
2. Enable suppot for x32 architecture, see
https://wiki.debian.org/X32Port .
At least, you should install libc6-x32:amd64 and libc6-dev-x32 .
Using archive.debian.org is useful.
3. Dist-Upgrade distribution versions step by step.
8.0 -> 9.0 ...
I strongly recommend to get a snapshot of VM
before apt-get dist-upgrade.
4. At version 12.0 "bookworm" , you should get snapshot
this point at least.
5. Remove all x32 related programs and libraries before installed.
Then, get snapshot again.
6. Check whether /usr/libx32 and /lib32 are empty.
Then, also get snapshot.
7. If empty, "sudo rm -fR /usr/lib32 /lib32" and get snapshot.
8. Now, you can dist-upgrade to "sid" .
If reproduce this issue, you can't dist-upgrade to sid.
Note:
As long as the source code of base-files is compared from
12.4-deb12u11 to 13.8, it can be expected that the this
reproducable phenomenon will occur at the time of the dist-upgrade
from Debian 12 "bookworm" to "sid" (or 13 "trixie"),
so I think it is OK to start item 1. with Debian 12 "bookworm".
> Packages may install empty directories. If you choose to delete those,
> it is up to you to deal with failing packages.
>
Sorry...
Ohta.
---
On Sun, 18 May 2025 18:38:59 +0200
Helmut Grohne <hel...@subdivi.de> wrote:
> 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
>
>
