Re: Bug#961654: buster-pu: package bzip2/1.0.6-9.2~deb10u1
On 14/09/2022 05:48, Chris Frey wrote:
On the other hand, the fix has been known since 2019 and looks like a
prime problem for an LTS newbie volunteer like me.
I have created the fix based on the Debian/bzip2 repo, the fix is in
the debian/buster branch.
git clone http://digon.foursquare.net/debian-buster-bzip2/.git
Your top-commit looks very similar to the one from Santiago on . I'd rather
use that to give him credit as he proposed the fix first (plus using CPPFLAGS
seems more correct for this flag). In addition to that, the commit misses his
follow-up fix in . I'm going to consider that last debdiff from him for an
upload to buster. Thanks in any case for looking at it (and coming up with a
similar fix) and for testing the update.
I have tested it on a 32bit buster, and it works on +2g files.
I do not have privileges to push this to any server yet, so feel free to
tweak the changelog and claim it as your own, whoever wishes to upload it.
On Tue, Sep 13, 2022 at 04:46:14PM +0200, Sylvain Beucler wrote:
IIUC this is about fixing 2 non-security bugs, that were introduced prior to
buster's initial release.
I personally don't think this fits the LTS project scope.
Maybe other LTS members will have a different opinion.
Debian LTS Team
On 13/09/2022 15:27, Santiago R.R. wrote:
El 10/09/22 a las 19:11, Adam D. Barratt escribió:
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.
I've uploaded a fixed version to unstable yesterday. It would be
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.)
And I am sorry I missed that answer.
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.
I am forwarding this to the LTS folks, so they can decide about this