On 2013-11-01 12:58:19 +0100, Francesco Poli (wintermute) wrote: > I wonder why nobody thought to report a release-critical bug against > libfontconfig1, in order to prevent its migration until the issue in > xpdf is fixed... > I am doing this right now, in order to at least give apt-listbugs users > an opportunity to be warned about this issue and to pin libfontconfig1, > until a fixed xpdf has migrated into testing.
Users should be aware that remaining with libfontconfig1 2.10.2-2 may block some security fixes, since many new packages are built with libfontconfig1 2.11.x thus depends on this version at least. This is the case with iceweasel (via xulrunner-24.0), which I had to rebuild locally on my machines (since I still want xpdf to be usable). -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
