severity 412159 important quit On Mon, Feb 26, 2007 at 11:15:59AM +0100, Vincent Lefevre wrote:
> > 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 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > This is exactly what I did (I changed the default "no" into "yes" in > the "enable bitmap" question). FYI, the reference message is here: Ok, yes, I can confirm this. I overlooked a comment character on one line in the postinst script: case "$enable_bitmaps" in "true") # # Bitmap fonts will be enabled by default, so there's no need # to use this configuration file. However, the file remains useful if # you want to force bitmaps to be considered even when some application # disables them. # # ln -s $CONFAVAIL/$yes_bitmaps $CONFDIR/$yes_bitmaps So yes, upgrading or reinstalling this package unconditionally removes the /etc/fonts/conf.d/70-yes-bitmaps.conf symlink. That's still not a release-critical bug. This is clearly a symlink managed under the control of the fontconfig-config package. If you want to configure your package in a way that isn't supported by the configuration interface, then go ahead and do so -- create a file of your own under /etc/fonts/conf.d with the settings of your choosing, instead of trying to use a file with the exact name that is going to be managed via debconf. -- 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]
