Your message dated Tue, 07 Jan 2020 15:38:15 -0500 with message-id <8f5ae32a7a131d834b3ad8a7a44005ef25393dd0.camel@debian.org> and subject line Bug#915151: No longer affect gnulib >= 20180305 has caused the Debian Bug report #915151, regarding lbzip2 FTBFS with glibc 2.28 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 915151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915151 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: gzip FTBFS: ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib."
- From: Helmut Grohne <helmut@subdivi.de>
- Date: Sat, 1 Dec 2018 08:07:24 +0100
- Message-id: <20181201070723.GA8531@alf.mars>
Source: gzip Version: 1.9-2.1 Severity: serious Tags: ftbfs User: helmutg@debian.org Usertags: rebootstrap Control: clone -1 -2 Control: reassign -2 gnulib Control: found -2 gnulib/20140202+stable-3 Control: retitle -2 gnulib does not work with glibc/2.28 Control: affects -2 + src:lbzip2 gzip fails to build from source in unstable (since the glibc upgrade to 2.28): | CC fseeko.o | ../../lib/fseeko.c: In function 'rpl_fseeko': | ../../lib/fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib." | #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib." | ^~~~~ | make[4]: *** [Makefile:1775: fseeko.o] Error 1 | make[4]: Leaving directory '/<<PKGBUILDDIR>>/builddir/lib' | make[3]: *** [Makefile:1580: all] Error 2 | make[3]: Leaving directory '/<<PKGBUILDDIR>>/builddir/lib' | make[2]: *** [Makefile:1746: all-recursive] Error 1 | make[2]: Leaving directory '/<<PKGBUILDDIR>>/builddir' | make[1]: *** [Makefile:1527: all] Error 2 | make[1]: Leaving directory '/<<PKGBUILDDIR>>/builddir' | make: *** [debian/rules:96: build-stamp] Error 2 | dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 gnulib likes to use this construct to detect glibc: | #if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */ Unfortunately, _IO_ftrylockfile got removed from glibc/2.28 and __GNU_LIBRARY__ is 6, so glibc is not a GNU libc. gnulib has a history of breaking packages frequently. What makes matters worse is that gnulib gets embedded rather than used like any other component. So fixing this bug in gnulib does not fix gzip. I therefore cloned a separate instance as it still breaks e.g. lbzip2. Helmut
--- End Message ---
--- Begin Message ---
- To: 915151-done@bugs.debian.org
- Subject: Bug#915151: No longer affect gnulib >= 20180305
- From: Boyuan Yang <byang@debian.org>
- Date: Tue, 07 Jan 2020 15:38:15 -0500
- Message-id: <8f5ae32a7a131d834b3ad8a7a44005ef25393dd0.camel@debian.org>
Version: 20180621~6979c25-1 I believe this bug is really fixed with http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4af4a4a71827c0bc5e0ec67af23edef4f15cee8e . -- Best, Boyuan YangAttachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---