Le mardi 18 avril 2006 à 11:14 -0700, Steve Langasek a écrit : > > The postinst contains the following: > > if [ -d "/usr/X11R6/bin" ] && [ ! -L /usr/X11R6/bin ]; then > > rmdir "/usr/X11R6/bin" || die "Could not remove /usr/X11R6/bin. Is not > > yet empty. Please remove any items still in the directory. You can move > > them back after the install has completed successfully." > > fi
> This is a duplicate of bug #362885. Unless you can come up with a better > upgrade path than the one that's been implemented, it's also a non-bug. For sure I have a better upgrade path: - keep a compatibility symbolic link in /usr/X11R6/bin/X, and ditto the few other ones that can cause breakage upon upgrade ; - hunt down packages using them ; - release etch with those links ; - entirely remove /usr/X11R6/bin after the release. There are many broken third-party applications that install stuff in /usr/X11R6 instead of /usr/local. Until now, such cases have been handled by overwriting them upon upgrades, not by entirely failing to upgrade. The "upgrade path" (which is actually a non-upgrade path) will break on many systems without any justification. -- .''`. Josselin Mouette /\./\ : :' : [EMAIL PROTECTED] `. `' [EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
signature.asc
Description: Ceci est une partie de message numériquement signée
