Processed: Bug#728444: libfontconfig1: xpdf is broken by fontconfig version 2.11.0-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 728444 2.11.0-2
Bug #728444 {Done: Samuel Bronson } [libfontconfig1] 
libfontconfig1: xpdf is broken by fontconfig version 2.11.0-1
Marked as fixed in versions fontconfig/2.11.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
728444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#728444: libfontconfig1: xpdf is broken by fontconfig version 2.11.0-1

[BubuXP]

fixed 728444 2.11.0-2
thanks

On Mon, 9 Dec 2013 20:57:19 +0100, Klaus Ethgen wrote:
> Hi,
> please don't close this bug. The Bug is still there and yes, it breaks
> xpdf and some other software (At least zathura has some minor problems
> too with this bug).
> I could not believe, there is a working and appropriate fix for this bug
> but the bug is solved by breaking xpdf.
> Such a behaviour is absolutely not helpful and negates the confidence in
> debian at all. So please apply the patch from Michael Gilbert as a short
> term solution and AFTER that, work together searching for a long term
> bug fix.

As written in the previous messages, the problem is not Fontconfig, so
this bug should not have been reopened.
Other packages that had problems with Fontconfig's pthreads are fixing
or have already fixed them.
Applying that proposed NMU patch is out of Debian quality standards
and one could only recompile his own packages with it if xpdf is
really needed (like you did in
ftp://ftp.ethgen.ch/pub/debian/pool/unofficial/f/fontconfig ).

The problem lies elsewhere as Pino Toscano said in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730112#68
> Seriously: the current xpdf in Debian is totally broken, and it has been
> for years even before the recent changes in fontconfig and/or poppler;
> those just uncovered even more the nonsense the current xpdf is.
> [...]


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#728444: libfontconfig1: xpdf is broken by fontconfig version 2.11.0-1

[Michael Gilbert]

On Sat, Nov 9, 2013 at 1:27 PM, Michael Gilbert wrote:
> control: tag -1 pending
>
> On Sat, Nov 2, 2013 at 4:30 PM, Michael Gilbert wrote:
>> control: tag -1 patch
>>
>> Hi, this results from upstream enabling pthreads in 2.11.  I've
>> attached a patch to disable pthreads until a more permanent solution
>> is found for xpdf.
>
> Hi, I've uploaded an nmu with the above patch to delayed/5 fixing
> this.  Please let me know if I should delay or cancel if you think
> this isn't the best solution.

Based on the emotional messages seen so far, I've delayed this another
10 days to give it more time for potential review.

Best wishes,
Mike


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#728444: libfontconfig1: xpdf is broken by fontconfig version 2.11.0-1

[Michael Gilbert]

control: tag -1 pending

On Sat, Nov 2, 2013 at 4:30 PM, Michael Gilbert wrote:
> control: tag -1 patch
>
> Hi, this results from upstream enabling pthreads in 2.11.  I've
> attached a patch to disable pthreads until a more permanent solution
> is found for xpdf.

Hi, I've uploaded an nmu with the above patch to delayed/5 fixing
this.  Please let me know if I should delay or cancel if you think
this isn't the best solution.

Best wishes,
Mike


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#728444: libfontconfig1: xpdf is broken by fontconfig version 2.11.0-1

[Rodrigo Campos]

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 debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#728444: libfontconfig1: xpdf is broken by fontconfig version 2.11.0-1

[Francesco Poli]

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.

That's why I really hope this issue may be fixed very soon...


-- 
 http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt
 New GnuPG key, see the transition document!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpUn9DLy8qR9.pgp
Description: PGP signature

Bug#728444: libfontconfig1: xpdf is broken by fontconfig version 2.11.0-1

[Vincent Lefevre]

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  - Web: 
100% accessible validated (X)HTML - 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

Bug#728444: libfontconfig1: xpdf is broken by fontconfig version 2.11.0-1

[Michael Gilbert]

control: tag -1 patch

Hi, this results from upstream enabling pthreads in 2.11.  I've
attached a patch to disable pthreads until a more permanent solution
is found for xpdf.

Thanks for considering this.

Best wishes,
Mike
diff -Nru fontconfig-2.11.0/debian/changelog fontconfig-2.11.0/debian/changelog
--- fontconfig-2.11.0/debian/changelog	2013-10-20 18:07:16.0 +
+++ fontconfig-2.11.0/debian/changelog	2013-11-02 20:35:08.0 +
@@ -1,3 +1,9 @@
+fontconfig (2.11.0-1.1) UNRELEASED; urgency=low
+
+  * Disable pthreads (closes: #728444).
+
+ -- Michael Gilbert   Sat, 02 Nov 2013 20:34:52 +
+
 fontconfig (2.11.0-1) unstable; urgency=low
 
   * New upstream release.
diff -Nru fontconfig-2.11.0/debian/patches/no-pthread.patch fontconfig-2.11.0/debian/patches/no-pthread.patch
--- fontconfig-2.11.0/debian/patches/no-pthread.patch	1970-01-01 00:00:00.0 +
+++ fontconfig-2.11.0/debian/patches/no-pthread.patch	2013-11-02 20:35:39.0 +
@@ -0,0 +1,12 @@
+Description: Disable pthreads
+Author: Michael Gilbert 
+--- fontconfig-2.11.0.orig/configure
 fontconfig-2.11.0/configure
+@@ -15444,6 +15444,7 @@ ac_compiler_gnu=$ac_cv_c_compiler_gnu
+ 
+ 
+ fi
++have_pthread=false
+ if $have_pthread; then
+ 	LIBS="$PTHREAD_LIBS $LIBS"
+ 	CFLAGS="$CFLAGS $PTHREAD_CFLAGS"
diff -Nru fontconfig-2.11.0/debian/patches/series fontconfig-2.11.0/debian/patches/series
--- fontconfig-2.11.0/debian/patches/series	2013-10-20 18:06:47.0 +
+++ fontconfig-2.11.0/debian/patches/series	2013-11-02 20:35:22.0 +
@@ -0,0 +1 @@
+no-pthread.patch

Bug#728444: libfontconfig1: xpdf is broken by fontconfig version 2.11.0-1

[Francesco Poli (wintermute)]

Package: libfontconfig1
Version: 2.11.0-1
Severity: grave
Justification: renders xpdf package unusable
Control: block -1 by 727070

Hello,
there's a bug in xpdf [#727070] which is triggered by the upgrade
of fontconfig to version 2.11.0-1 (from, say, version 2.10.2-2).

[#727070] http://bugs.debian.org/727070

As far as I can see, it seems that the bug is indeed in package xpdf
and should therefore be fixed there. But, as a matter of fact, the issue
shows up when the user upgrades fontconfig to version 2.11.0-1 ...

Unfortunately, fontconfig/2.11.0-1 has already migrated into testing!

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.

I hope this does not annoy you too much.
Please do not downgrade the severity of this bug report below the
release-critical threshold and please do not close it or reassign it,
until an xpdf package that fixes bug #727070 has landed in testing.

Thanks for your understanding.
Bye.


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org