severity 412159 wishlist
thanks
On Sun, Feb 25, 2007 at 12:19:07PM +0100, Vincent Lefevre wrote:
> On 2007-02-24 21:56:29 -0800, Steve Langasek wrote:
> > > and as said in my bug report, a 'must' has been violated ("local
> > > changes *must* be preserved during a package upgrade").
> > You're citing a requirement of policy that applies to *config files*.
> > Files under /var/cache are *not* config files.
> OK, but that was the cause. Now, files under /etc are configuration files.
> In my case, /etc/fonts/conf.d/70-no-bitmaps.conf was not present before
> the upgrade (I had enabled bitmaps via dpkg-reconfigure fontconfig-config
> a few weeks ago). And after the upgrade, this file
> /etc/fonts/conf.d/70-no-bitmaps.conf reappeared, thus changing my
> local configuration.
Yes, and if you delete all symlinks for a given init script under
/etc/rc*.d and then upgrade the package, they'll be readded, changing your
local configuration.
This is no policy violation. I've reviewed the full text of the
fontconfig-config postinst and config scripts. There's nothing being done
wrong here; the scripts do everything possible to preserve the user's
selection between enabling and disabling of bitmaps.
If you want to keep bitmaps enabled, you can:
- manually create the /etc/fonts/conf.d/70-yes-bitmaps.conf link and delete
the 70-no-bitmaps.conf link, or
- use dpkg-reconfigure fontconfig-config to select one, or
- edit /etc/fonts/conf.avail/70-no-bitmaps.conf to your taste.
--
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/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
