[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#816697: jessie-pu: package fonts-sil-andika/1.004-2+deb8u1



Control: tags -1 + pending

On Fri, 2016-03-04 at 18:45 +0000, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Fri, 2016-03-04 at 07:36 +0100, Petter Reinholdtsen wrote:
> > When the font-sil-andika package is installed in Jessie, the fontconfig
> > library print out these warnings for all X programs using fontconfig:
> > 
> > Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 16: Having multiple values in <test> isn't supported and may not work as expected
> > Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not work as expected
> > Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not work as expected
> > Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not work as expected
> > Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not work as expected
> > Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not work as expected
> > Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not work as expected
> > Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not work as expected
> > Fontconfig warning: "/etc/fonts/conf.d/65-andika.conf", line 35: Having multiple <family> in <alias> isn't supported and may not work as expected
> > 
> > The package is a reverse dependency of tuxtype and
> > task-hungarian-desktop, and installed by default on Debian Edu.
> > 
> > The cause is an incorrect removal of a obsolete conffile in version
> > 1.004-2.  The fix was uploaded to unstable in version 5.000-1, and I
> > propose to include it in stable too.  The attached patch show the
> > changes. Is this OK to upload to stable?
> 
> Please go ahead.

Uploaded and flagged for acceptance.

Regards,

Adam


Reply to: