Re: RFC: ruby-loofah 2.2.3-1+deb10u2

2023-03-13 Thread Anton Gladky
Hi Daniel, congratulations on your first update! Some notes: 1) to be consistent with all other updates please do not add the suffix in the version number 2) t is not quite a team upload. Better use "dch --lts" which converts to "* Non-maintainer upload by the LTS Security Team." 3) Please

RFC: ruby-loofah 2.2.3-1+deb10u2

2023-03-13 Thread Daniel Leidert
Hi there, I prepared my first LTS update. You can find it here: https://salsa.debian.org/lts-team/packages/ruby-loofah When I ran some test cases to see if all the vulnerabilities are fixed, I discovered that there is a slight behavioral change: As part of the fix for CVE-2022-23516, loofah

Re: LTS upload of ruby-loofah

2023-03-13 Thread Daniel Leidert
Hi Chris, Am Montag, dem 13.03.2023 um 16:29 + schrieb Chris Lamb: > Hi Daniel, > > After being unclaimed through inactivity, I took over the claim for > ruby-loofah in data/dla-needed.txt. However, I've just noticed that > you have already authored and prepared some patches in the Git repo,

Accepted redis 5:5.0.14-1+deb10u3 (source amd64 all) into oldstable

2023-03-13 Thread Debian FTP Masters
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 13 Mar 2023 16:39:07 + Source: redis Binary: redis redis-sentinel redis-server redis-tools redis-tools-dbgsym Architecture: source amd64 all Version: 5:5.0.14-1+deb10u3 Distribution: buster-security Urgency: high

LTS upload of ruby-loofah

2023-03-13 Thread Chris Lamb
Hi Daniel, After being unclaimed through inactivity, I took over the claim for ruby-loofah in data/dla-needed.txt. However, I've just noticed that you have already authored and prepared some patches in the Git repo, which clearly took some time and effort. If you had not committed anything, I