Re: Fixing glib2.0 CVE-2024-34397 in buster

2024-05-13 Thread Markus Koschany
Am Montag, dem 13.05.2024 um 19:51 +0100 schrieb Simon McVittie: > On Mon, 13 May 2024 at 20:00:16 +0200, Markus Koschany wrote: [...] > > > Do you want to upload the security update to buster-security yourself or do > > you > > want me to take care of it? > > Please upload when you are happy

Re: Fixing glib2.0 CVE-2024-34397 in buster

2024-05-13 Thread Simon McVittie
On Mon, 13 May 2024 at 20:00:16 +0200, Markus Koschany wrote: > Am Freitag, dem 10.05.2024 um 16:02 +0100 schrieb Simon McVittie: > > [...] > > > > I would recommend testing: > > > > * build-time tests > > All tests pass except of > > 165/258 glib:gio / live-g-file FAIL

Re: Fixing glib2.0 CVE-2024-34397 in buster

2024-05-13 Thread Markus Koschany
Hello Simon, thank you very much for preparing this update. Am Freitag, dem 10.05.2024 um 16:02 +0100 schrieb Simon McVittie: > [...] > > I would recommend testing: > > * build-time tests All tests pass except of 165/258 glib:gio / live-g-file FAIL 0.07 s (killed by

Re: Fixing glib2.0 CVE-2024-34397 in buster

2024-05-11 Thread Sylvain Beucler
Hello Simon, Markus (apo) claimed the package yesterday after your message. For clarity I'm CC:ing him here, and I added a note in data/dla-needed.txt. https://salsa.debian.org/security-tracker-team/security-tracker/-/blob/master/data/dla-needed.txt Also, thanks for the testing procedure :)

Fixing glib2.0 CVE-2024-34397 in buster

2024-05-10 Thread Simon McVittie
Please cc either me or the glib2.0 package's address on any replies that are relevant outside the LTS team: I am not subscribed to -lts. Normally I don't attempt to support any packages in the LTS distributions, but for glib2.0 I was the author of the original CVE fix and it turns out that I