On Mon, Mar 21, 2011 at 22:13:23 +0200, Andrei Popescu wrote:
> On Lu, 21 mar 11, 14:27:11, Mark Goldshtein wrote:
> > >
> > > xorg-server (2:1.7.7-12) unstable; urgency=low
> > > [...]
> > > * Add 22-stop-searching-for-xf86config-files, cherry-picking the
> > > upstream commit below (which we can't do directly since it depends on
> > > a patch kept in the quilt series: 08-config-xorg-conf-d.diff), so
> > > that
> > > XF86Config-4 is no longer considered (Closes: #610453). Thanks,
> > > Bernhard R. Link!
> > > - Stop searching for XF86Config files
> > >
> > > This change is briefly mentioned in the 6.0.1 news release.
> >
> > >From a point of view of an average user, I think it may be useful to
> > warn about such critical changes right after # apt-get dist-upgrade
> > command output, as it shows a list of packages marked to change,
> > before yes/no confirmation.
>
> The "critical change" you refer to happened with the release of etch,
> when XFree86 was replaced with Xorg ;) but maybe this warrants a mention
> in the squeeze release notes.
>
> Dear Release Notes editors,
> If this is worth including I can try to come up with a patch.
>
Maybe xserver-xorg-core's NEWS.Debian would be more appropriate, if
anything?
I was bitten by the fact that X in 6.0.0 *did* look at XF86Config
because I moved xorg.conf away after the upgrade, and the old XF86Config
leftover from sarge days made X fail to restart. I didn't expect that
people still willfully used XF86Config.
Cheers,
Julien
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110321203211.gk3...@radis.liafa.jussieu.fr
