Listing every conceivable package as a conflict is probably not a good solution. Conflicting explicitly with known 3rd-party packages seems kludgy at best. It would be safer to assume there are unaccounted files in /usr/X11R6/bin, because users are unpredictable and do strange things.
In that case, how about changing the install script to move the contents of the directory, if any, before removing it and symlinking it to ../bin? Or, handling a failed rmdir by asking the user to manually resolve the issue, instead of just bailing? I doubt the results will be perfect, but if I have to choose between a slightly broken system (custom add-ons broken) or a mostly-broken system (half of the packages removed, requiring hours of manual recovery), I'd choose the slight breakage. -- x11-common preinst script fails (was: aborts /usr/X11R6/bin not empty) https://bugs.launchpad.net/bugs/67996 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
