Hi! Thanks for reaching out.
On 12/5/24 05:19, Marek Marczykowski-Górecki wrote: > On Thu, Dec 05, 2024 at 12:06:00PM +0800, Sean Whitton wrote: >> Hello, >> >> On Wed 04 Dec 2024 at 10:56am -03, Santiago Ruano Rincón wrote: >> >>> Source: xen >>> Severity: normal >>> User: debian-...@lists.debian.org >>> Usertags: upstream-trixie >>> X-Debbugs-Cc: debian-...@lists.debian.org >>> >>> Dear xen maintainers, >>> >>> Testing (trixie) currently ships xen 4.17, which, according to the >>> upstream support matrix [x], will get security support until 2025-12-12. >>> The latest upstream release (4.19) will get security support until >>> 2027-07-29. I believe it would be easier to provide security updates for >>> trixie users if 4.19 is packaged in testing. >>> >>> If you need or want help packaging this new upstream version, please >>> don't hesitate to speak up. Someone from the LTS team, may be interested >>> in contributing (CC'ing debian-lts). >> >> As I'm familiar with the git-debrebase workflow that Xen uses in Debian, >> I might be well-placed to help; on the other hand, I'm less experienced >> with packages that require special booting arrangements to test they are >> working. > > I'm not sure about the official plans or the current state, but > exploring salsa one can find a WIP branch with 4.19: > https://salsa.debian.org/xen-team/debian-xen/-/commits/myx/wip/experimental/?ref_type=heads Yes, we need some assistance. The situation regarding the packages is: * We have a Xen 4.19 package ready, that has been tested. * ==> We need a sponsor to upload it to experimental as NEW <== * We can then prepare an up-to-date 4.19 for unstable. * And then... we can again continue doing the 4.17 (security-)updates for stable. The current situation regarding the Debian Xen team is: * Currently that's Maximilian and me. (I'm a DM) * We're a dedicated team, we do manage, but we're also not enormously high on excess bandwidth. I mean, we can't do a lot of the 'nice to haves'. * We have established a stable workflow with great checklists in the last few years. * We always try to work together, mainly for quality reasons, to continuously double-check what we're doing before we ship it, but also of course because it's more fun to do things together than on your own. But, there are single points of failure, as can already be spotted in the above. I myself have been less available for personal reasons in the last months (Hans says yes, life says no, for who recognizes such a situation), and we were not really prepared yet for something like that happening. In general, what we could really use for assistance is a bit of a safety net for certain situations. Like, a few (DD) people who we know and who know about us and what we do, and who we can contact if needed, and who can help with various topics, like sponsoring uploads if needed, help with packaging tooling, navigating non-trivial package transitions, complex makefile/build/library-dependency/etc stuff... By the way, big thanks to the Team Security (Cc), especially Moritz and Carnil, who already are more than a great help with the security update workflow! We can further discuss here, or interactively in #debian-xen on OFTC. I'm going for lunch break now and will be on IRC. Thanks, Hans
