That's a weird bug to have open, especially considering the last entry from 2019.
I landed here because dpkg have thrown a message on me Unpacking dpkg (1.21.22) over (1.21.21) ... Setting up dpkg (1.21.22) ... dpkg: warning: This system uses merged-usr-via-aliased-dirs, going behind dpkg's dpkg: warning: back, breaking its core assumptions. This can cause silent file dpkg: warning: overwrites and disappearances, and its general tools misbehavior. dpkg: warning: See <https://wiki.debian.org/Teams/Dpkg/FAQ#broken-usrmerge>. referring me to https://wiki.debian.org/Teams/Dpkg/FAQ#broken-usrmerge which lead to https://wiki.debian.org/Teams/Dpkg/MergedUsr which pointed to a seemingly unfinished thread on ML and this bugreport. It was surprising because I thought that's been over for a long time now. (https://lists.debian.org/debian-devel-announce/2022/09/msg00001.html and https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978636 (closed)) Could anyone insert pointers here about - what's the official layout now - what are the supported layouts - what's with dpkg vs layouts - what's with this open bug now, around 2024? (Disclaimer: arrived from Devuan since, as you might have guessed, I try to keep my system uninfected, but otherwise it should not matter too much where I'm arriving from.) (Except maybe if it's about patches like this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061718 but then it would be neat to keep Debian wiki in sync with reality and close/keep bugs with relevant summary to help the people finding for clues.) Thanks, Peter