severity 395159 important
tag 395159 +patch
thanks
I think that this bug is important;
I really recommend that it be solved pre-etch
here is the problem:
in a Sarge install, xfree86-common (at version
4.3.0.dfsg.1-14sarge ) ships those files
# dpkg -L xfree86-common | grep Xsession.d
/etc/X11/Xsession.d/20xfree86-common_process-args
/etc/X11/Xsession.d/30xfree86-common_xresources
/etc/X11/Xsession.d/50xfree86-common_determine-startup
/etc/X11/Xsession.d/90xfree86-common_ssh-agent
/etc/X11/Xsession.d/99xfree86-common_start
when upgrading at Etch, x11-common will add those files
$ dpkg -L x11-common | grep Xsession.d
/etc/X11/Xsession.d/20x11-common_process-args
/etc/X11/Xsession.d/30x11-common_xresources
/etc/X11/Xsession.d/50x11-common_determine-startup
/etc/X11/Xsession.d/90x11-common_ssh-agent
/etc/X11/Xsession.d/99x11-common_start
*but*
the xfree86 files are sourced (by alphabetical order) *after* the new
*x11* files : so whatever the *x11* files will do, the *xfree86* files
will either override (e.g.variable definition) or duplicate (e.g. daemon
launching)
this is not good quality for Etch IMHO
there is an easy workaround , though: in /etc/X11/Xsession, the function
run_parts only considers scripts that match '[[:alnum:]_-]\+$'
so adding this shell snippet to .postinst will do the trick
for i in ${CONFIG_DIR}/Xsession.d/*xfree* ; do
if test -r "$i" ; then
mv "$i" "$i".disabled.old.conffile.from.sarge.time ;
fi ;
done
Of course the above is just an example, that you may adjust to taste ...
for example, it may be worthwhile to send the root user some debconf
note if the above code is triggered , to explain why and what was done.
thanks for you attention
a.
Attachment:
signature.asc
Description: OpenPGP digital signature