> 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) [...] > 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
A third approach: We can `dpkg -L` the package in question, and report the taint only if any of the installed files has a symlink as a non-final component. You might do that either for usrmerge symlinks only, or, as I suggest, for any symlinked path -- as it's the latter that causes most of problems related to usrmerge. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ If you ponder doing what Jesus did, remember than flipping tables ⢿⡄⠘⠷⠚⠋⠀ and chasing people with a whip is a prime choice. ⠈⠳⣄⠀⠀⠀⠀
