severity 365967 grave
merge 365967 365988
thanks

Ok, let's go ahead and bump this severity and merge with 365988 et al.,
because the fix for this is the exact same: x11-common should *not* depend
on xfree86-common, *at all*, and there *definitely* shouldn't be any manual
twiddling of /etc/X11/Xsession on upgrade.

The deal is that the earlier error reported in 354146 was a *file* conflict
error, which could only happen in a version of x11-common that did not
Conflicts: xfree86-common.  Since x11-common now Conflicts with
xfree86-common, xfree86-common is correctly removed first, then x11-common
is unpacked and takes over the config file, with conffile prompts only when
necessary.

So I believe the correct action here is to simply revert the xfree86-common
package and related pre-dependency.

There is probably some additional clean-up that could be done here, because
there are still orphaned xfree86-common config files in /etc/X11/Xsession.d
which duplicate the x11-common versions of these config files; however, the
current xfree86-common package doesn't do anything with these anyway because
it has its purge block in the postinst (!), so this shouldn't block getting
this more urgent upgrade problem fixed.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to