On Tue, Nov 05, 2013 at 12:10:35AM +0100, Francesco Poli wrote: > On Mon, 4 Nov 2013 13:01:22 +0100 Vincent Lefevre wrote: > > > 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. > > Hi Vincent, > that's true, no doubt. > > > 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). > > Users who are not willing to do the same (perhaps because they do not > have the time and/or the required expertise), will have to choose > between an up-to-date system with an unusable xpdf and a system lagging > behind some package upgrades with a usable xpdf. > Unfortunately.
AND not being able to install some packages. If you don't have the package installed and depends on newer fontconfig version you are on your own. Chromium, for example, requires newer version of fontconfig. And probably there is more software that wouldn't be possible to install. Or using snapshot.debian.org or compiling or... Thanks, Rodrigo -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
