OoO La nuit ayant déjà recouvert d'encre ce jour du jeudi 21 août 2003, vers 23:48, [EMAIL PROTECTED] (Debian Bug Tracking System) disait:
> Okay, if your analysis is correct then there MUST exist the following > file: > /etc/X11/XF86Config-4.dpkg-old Yes, it is here. > You still had xserver-xfree86/manage_config_with_debconf answered > "true", so you got migrated, as documented: > In the event that you have customized these configuration files, and ha= > ve > neglected to correct debconf's notion of whether it should manage those > files before upgrading to xfree86 4.2.1-10 or later, backups are made a= > nd > stored in the same directory, with the suffix ".dpkg-old". For example, > if you have answered the "Manage XFree86 4.x server configuration file > with debconf?" question in the affirmative, your /etc/X11/XF86Config-4 > file will be backed up in /etc/X11/XF86Config-4.dpkg-old. Note that th= > is > is only done *once*, on upgrades from xfree86 package versions prior to > 4.2.1-10. If you do not like the new /etc/X11/XF86Config-4 that gets > written, for example, either edit it or rename the .dpkg-old > file to it. I understand, however I think this is still a bug since to avoid that debconf messes with a file, removing debconf marks is one way to do and this worked fine until this release. It would be nice that the transition notices the absence of debconf marks like debconf does (even if this method is now deprecated, there is no clear notice of this, not everybody uses apt-listchanges). However, it is ok for me to let this bug closed, I did not notice this was done on purpose (and documented). -- BOFH excuse #265: The mouse escaped.
