Bug#996997: buster-pu: Cleaning up the http-parser ABI breakage in Debian 10 ("buster")

2021-12-06 Thread Hilko Bengen
* Julien Cristau: > Control: tag -1 confirmed > > On Wed, Dec 01, 2021 at 07:38:23PM +0100, Christoph Biedl wrote: >> Christoph Biedl wrote... >> >> > About next steps, I would do the upload in the next days. Let me know if >> > you prefer other things to happen first or instead. >> >> To avoid

Bug#996997: buster-pu: Cleaning up the http-parser ABI breakage in Debian 10 ("buster")

2021-12-06 Thread Julien Cristau
On Mon, Dec 06, 2021 at 02:20:16PM +0100, Hilko Bengen wrote: > * Julien Cristau: > > > Control: tag -1 confirmed > > > > On Wed, Dec 01, 2021 at 07:38:23PM +0100, Christoph Biedl wrote: > >> Christoph Biedl wrote... > >> > >> > About next steps, I would do the upload in the next days. Let me

Bug#996997: buster-pu: Cleaning up the http-parser ABI breakage in Debian 10 ("buster")

2021-12-03 Thread Julien Cristau
Control: tag -1 confirmed On Wed, Dec 01, 2021 at 07:38:23PM +0100, Christoph Biedl wrote: > Christoph Biedl wrote... > > > About next steps, I would do the upload in the next days. Let me know if > > you prefer other things to happen first or instead. > > To avoid this gets lost I've just

Bug#996997: buster-pu: Cleaning up the http-parser ABI breakage in Debian 10 ("buster")

2021-12-01 Thread Christoph Biedl
Christoph Biedl wrote... > About next steps, I would do the upload in the next days. Let me know if > you prefer other things to happen first or instead. To avoid this gets lost I've just uploaded http-parser 2.8.1-1+deb10u2. Updated debiff attached, only editorial changes since the previous

Bug#996997: buster-pu: Cleaning up the http-parser ABI breakage in Debian 10 ("buster")

2021-11-23 Thread Christoph Biedl
Julien Cristau wrote... > Would you mind providing the old/new/proposed versions of http_parser.h? > (this is me being lazy, sorry, if I'm being too much of a pain I can go > and figure them out for myself, just let me know). Not that much on my side, so find the files attached. The name for the

Bug#996997: buster-pu: Cleaning up the http-parser ABI breakage in Debian 10 ("buster")

2021-11-23 Thread Julien Cristau
On Mon, Nov 01, 2021 at 12:01:51AM +0100, Christoph Biedl wrote: > Adam D. Barratt wrote... > > > Do you already have a proposed new upload / debdiff? > > After many more tests and some more discussion with Hilko, find attached > a debdiff that in my opinion is ready for upload. The patch itself

Bug#996997: buster-pu: Cleaning up the http-parser ABI breakage in Debian 10 ("buster")

2021-10-31 Thread Christoph Biedl
Adam D. Barratt wrote... > Do you already have a proposed new upload / debdiff? After many more tests and some more discussion with Hilko, find attached a debdiff that in my opinion is ready for upload. The patch itself is unmodified, I just enhanced the description for posterity. About next

Bug#996997: buster-pu: Cleaning up the http-parser ABI breakage in Debian 10 ("buster")

2021-10-22 Thread Christoph Biedl
Thanks for your swift and kind response. Adam D. Barratt wrote... > On Fri, 2021-10-22 at 09:18 +0200, Christoph Biedl wrote: > > ## Rework the patch > > > > Revert the ABI break by reworking the patch to restore the previous > > struct layout - while maintaining the purpose of the change:

Bug#996997: buster-pu: Cleaning up the http-parser ABI breakage in Debian 10 ("buster")

2021-10-22 Thread Christoph Biedl
Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Folks, perhaps I should start with an outright confession: When doing http-parser version 2.8.1-1+deb10u1 for a buster point release, I messed up things horribly. Nobody noticed in time, it's

Bug#996997: buster-pu: Cleaning up the http-parser ABI breakage in Debian 10 ("buster")

2021-10-22 Thread Adam D. Barratt
On Fri, 2021-10-22 at 09:18 +0200, Christoph Biedl wrote: > As described in #996939: The fix for CVE-2019-15605 changed, among > other things, the layout of "struct http_parser", by increasing the > size of the "flag" field and also its position¹ within the struct. > > The latter ought not to do