Re: should the Release Notes be updated concerning trixie security
Santiago Ruano Rincón <[email protected]> Sun, 13 Jul 2025 01:17:36 +0200
| Newsgroups | gmane.linux.debian.devel.release,gmane.linux.debian.devel.security |
|---|---|
| Message-ID | <aHLtEJRhkUt2pa5m@voleno> |
--9j+Z3AACTENl2m0w Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello! (CCing the actual security team address - [email protected]) El 12/07/25 a las 22:04, Paul Gevers escribi=F3: > Dear security team, >=20 > I sent you a similar request at the end of the bookworm release. Are you > aware of issues that are worth mentioning in the release notes from your > point of view? >=20 > The text about golang and rustc and chromium is still from the bookworm > notes. I'm not aware that anything changed (although I recall Santiago > started a conversation about it). The LTS team would like to help to improve the situation of statically-linked ecosystems, it is in our plans, but nothing has changed so far for trixie. > Can we just use the same text or should it > be updated? >=20 > Paul >=20 > Current version jumping straight to the security section: > https://www.debian.org/releases/trixie/release-notes/issues.en.html#limit= ations-in-security-support > or the source: > https://salsa.debian.org/ddp-team/release-notes/ Do you want to mention anything about isc-dhcp? Cheers, -- S --9j+Z3AACTENl2m0w Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQR+lHTq7mkJOyB6t2Un3j1FEEiG7wUCaHLtDQAKCRAn3j1FEEiG 7w0KAP4h35TYTiZmoTY2J7lxcZbbtnaNJjEEc192qQ2Shu2rjAEAxKLkJPIAZVIG Qbi3vpzIuQyuCKuUh2xdRqZ1Hrd8sQE= =spf3 -----END PGP SIGNATURE----- --9j+Z3AACTENl2m0w--