Dear DSA, As is custom for the Release Team, I'm asking you what your plans are with respect to testing upgrading DSA maintained machines to trixie. If my information is correct, in the past you'd first upgrade a non critical machine to see if there's anything broken in trixie that prevents you from maintaining the machines in a decent manner. When things look OK, I understand it's custom to upgrade at least one buildd for every release architecture to see if all architecture buildds remain working as they should on trixie.I'd like to warn you on this front already with my experience from upgrading ci.d.n machines this week (see backlog of #d-devel if you have it). Due to changes in systemd that raise the amount of open file descriptors [1], some builds and tests may timeout or use absurd amount of RAM, e.g. [2]. I had to limit fs.nr_open [3] to the bookworm values to prevent bad behavior taking the service down, even if things are fixed in unstable/trixie.
Paul [1] https://lists.debian.org/debian-devel/2024/06/msg00041.html [2] https://bugs.debian.org/1073046[3] https://salsa.debian.org/ci-team/debian-ci-config/-/commit/632cc1e4ab46edb49b1c4bf3f4e9e6a0d8394442
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature