Bug#923090: reportbug: Please add information about systems tainted due to merged-usr-via-symlinks
control: tag -1 +moreinfo
On Sat, Feb 23, 2019 at 9:03 PM Guillem Jover <guillem@debian.org> wrote:
> The merged-/usr deployment method of using directory symlinks, instead
> of properly moving the files or symlinking the contents of these
> directories is broken by design.
>
> Please see <https://lists.debian.org/debian-devel/2019/02/msg00251.html>.
>
> I'd appreciate if you could add information on filed bugs about such
> tainted systems.
i dont believe this is something *every* bug report should have, as it
looks like it's a very small percentage of hosts could be in this
configuration, and let's be honest, the impact is only limited to a
handful of packages (i understand you're coming from the dpkg POV)
> For dpkg I added the following bug-script:
>
> ,---
> #!/bin/sh
>
> set -e
>
> for d in /bin /sbin /lib /lib32 /libo32 /libx32 /lib64; do
> if [ "$(readlink $d)" = "usr$d" ]; then
> echo "System tainted due to merged-usr-via-symlinks." >&3
> break
> fi
> done
> `---
this indeed looks like a more sensible approach: every package that
actually cares about the merged-/usr status, should add its own bug
script to inspect the system status
--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi
Reply to: