El 16/09/22 a las 09:39, Emilio Pozuelo Monfort escribió:
> Hi Santiago,
>
> On 15/09/2022 09:52, Emilio Pozuelo Monfort wrote:
> > On 14/09/2022 15:42, Santiago R.R. wrote:
> > > El 14/09/22 a las 13:58, Emilio Pozuelo Monfort escribió:
> > > > On 13/09/2022 16:46, Sylvain Beucler wrote:
> > > >
Hi Santiago,
On 15/09/2022 09:52, Emilio Pozuelo Monfort wrote:
On 14/09/2022 15:42, Santiago R.R. wrote:
El 14/09/22 a las 13:58, Emilio Pozuelo Monfort escribió:
On 13/09/2022 16:46, Sylvain Beucler wrote:
Hi,
IIUC this is about fixing 2 non-security bugs, that were introduced
prior to
On 14/09/2022 15:42, Santiago R.R. wrote:
El 14/09/22 a las 13:58, Emilio Pozuelo Monfort escribió:
On 13/09/2022 16:46, Sylvain Beucler wrote:
Hi,
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
El 14/09/22 a las 13:58, Emilio Pozuelo Monfort escribió:
> On 13/09/2022 16:46, Sylvain Beucler wrote:
> > Hi,
> >
> > 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.
> >
On Wed, Sep 14, 2022 at 01:54:40PM +0200, Emilio Pozuelo Monfort wrote:
> Your top-commit looks very similar to the one from Santiago on [1]. 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
On 13/09/2022 16:46, Sylvain Beucler wrote:
Hi,
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.
We've had bugfix updates
Hi Chris,
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
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
I have
Hi,
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.
Cheers!
Sylvain Beucler
Debian LTS Team
On 13/09/2022 15:27, Santiago
Hi,
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.
> > See
On 2020-07-21 16:53:23 [+0200], Santiago Ruano Rincón wrote:
> 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.0 +0200
> +++ bzip2-1.0.6/debian/rules 2020-07-21 10:31:21.0 +0200
> @@ -14,6 +14,9 @@
>
On Wed, 27 May 2020 11:56:07 +0200 "Santiago R.R."
wrote:
> Package: release.debian.org
> Severity: normal
> Tags: buster
> User: release.debian@packages.debian.org
> Usertags: pu
>
> Dear Release Managers,
>
> Since 1.0.6-9, bzip2 was built without the -D_FILE_OFFSET_BITS=64
> CPPFLAG,
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@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
13 matches
Mail list logo
