Your message dated Sat, 10 Sep 2022 19:11:45 +0100 with message-id <a19d7f82f65843683d6aaf2a207a663345ecfb52.camel@adam-barratt.org.uk> and subject line Re: Bug#961654: buster-pu: package bzip2/1.0.6-9.2~deb10u1 has caused the Debian Bug report #961654, regarding buster-pu: package bzip2/1.0.6-9.2~deb10u1 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.) -- 961654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961654 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: buster-pu: package bzip2/1.0.6-9.2~deb10u1
- From: "Santiago R.R." <santiagorr@riseup.net>
- Date: Wed, 27 May 2020 11:56:07 +0200
- Message-id: <20200527095607.GA1417103@bartik>
Package: release.debian.org Severity: normal Tags: buster User: release.debian.org@packages.debian.org Usertags: pu Dear Release Managers, Since 1.0.6-9, bzip2 was built without the -D_FILE_OFFSET_BITS=64 CPPFLAG, and so it's not able to handle > 2GB files in 32-bit archs. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944557 I've uploaded a fixed version to unstable yesterday. It would be great to fix it also in buster. Please, consider the attached debdiff. Would it be OK for you to upload it? I've confirmed the issue is solved in an armhf machine running buster. Cheers, -- Santiagodiff -Nru bzip2-1.0.6/debian/changelog bzip2-1.0.6/debian/changelog --- bzip2-1.0.6/debian/changelog 2019-07-10 21:17:52.000000000 +0200 +++ bzip2-1.0.6/debian/changelog 2020-05-27 10:18:11.000000000 +0200 @@ -1,3 +1,10 @@ +bzip2 (1.0.6-9.2~deb10u2) buster; urgency=medium + + * Append -D_FILE_OFFSET_BITS=64 variable to buildflags, to renable handling + big files in 32-bit archs (Closes: #944557) + + -- Santiago Ruano Rincón <santiago@debian.org> Wed, 27 May 2020 10:18:11 +0200 + bzip2 (1.0.6-9.2~deb10u1) buster; urgency=medium * Rebuild for buster diff -Nru bzip2-1.0.6/debian/rules bzip2-1.0.6/debian/rules --- bzip2-1.0.6/debian/rules 2019-06-24 22:16:40.000000000 +0200 +++ bzip2-1.0.6/debian/rules 2020-05-27 09:58:14.000000000 +0200 @@ -14,6 +14,9 @@ DEB_BUILD_MAINT_OPTIONS := hardening=+all DEB_CFLAGS_MAINT_APPEND := -Wall -Winline DEB_CPPFLAGS_MAINT_APPEND := -D_REENTRANT +# This -D_FILE_OFFSET_BITS=64 is needed to make bzip2 able to handle > 2GB-size +# files in 32-bit archs. See #944557 +DEB_CPPFLAGS_MAINT_APPEND += -D_FILE_OFFSET_BITS=64 include /usr/share/dpkg/buildflags.mk include /usr/share/dpkg/pkg-info.mkAttachment: signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
- To: "Santiago R.R." <santiagorr@riseup.net>, 961654-done@bugs.debian.org
- Subject: Re: Bug#961654: buster-pu: package bzip2/1.0.6-9.2~deb10u1
- From: "Adam D. Barratt" <adam@adam-barratt.org.uk>
- Date: Sat, 10 Sep 2022 19:11:45 +0100
- Message-id: <a19d7f82f65843683d6aaf2a207a663345ecfb52.camel@adam-barratt.org.uk>
- In-reply-to: <20200527095607.GA1417103@bartik>
- References: <20200527095607.GA1417103@bartik>
On Wed, 2020-05-27 at 11:56 +0200, Santiago R.R. wrote: > Since 1.0.6-9, bzip2 was built without the -D_FILE_OFFSET_BITS=64 > CPPFLAG, and so it's not able to handle > 2GB files in 32-bit archs. > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944557 > > I've uploaded a fixed version to unstable yesterday. It would be > great > to fix it also in buster. Please, consider the attached debdiff. > Would it be OK for you to upload it? > Apologies for apparently letting this sit unanswered. (FTR there was a reply from a non-SRM member 18 months ago.) The final point release for buster has now happened, so any further updates to packages in buster will need to be handled via LTS. I'm therefore going to close this request now. Regards, Adam
--- End Message ---