Groups > linux.debian.bugs.dist > #1223681

Bug#1089033: xen: Please package xen version 4.19

From	Sean Whitton <spwhitton@spwhitton.name>
Newsgroups	linux.debian.bugs.dist
Subject	Bug#1089033: xen: Please package xen version 4.19
Date	2024-12-12 04:20 +0100
Message-ID	<JSHU5-gfWV-1@gated-at.bofh.it> (permalink)
References	(5 earlier) <JR1Ng-epZE-13@gated-at.bofh.it> <JRibn-eBay-3@gated-at.bofh.it> <JSisF-fXUl-3@gated-at.bofh.it> <JPYeK-dHyc-7@gated-at.bofh.it> <JSisF-fXUl-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Hello,

On Tue 10 Dec 2024 at 09:05pm -03, Santiago Ruano Rincón wrote:

> Why not, but... xen security support in bullseye last year (exactly on
> 2023-09-30, a little more than two years after the bullseye release):
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053246, and it was
> similar for buster.
> Of course, part of the goal of my initial bug report was to improve the
> xen security support for trixie in that sense. The Xen packaging team
> has stated in #1053246 that they were not in a position to continue
> supporting xen after the upstream EOL. (And one of the next steps is to
> look again for external help). My point is that the lts-team's
> package.yml is probably not the best place to document the xen team'
> needs, because xen is out of our current tooling radar.
>
> Adding it there doesn't harm, but I wonder if that is the best place if
> the goal is to monitor packages where the LTS team could help on
> unstable/testing. Further discussion can be done at the "Explore ways to
> figure out which packages in unstable could use help" issue:
> https://salsa.debian.org/lts-team/lts-extra-tasks/-/issues/71.

I'll drop a note there, thanks.

-- 
Sean Whitton

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Bug#1089033: xen: Please package xen version 4.19 Santiago Ruano Rincón <santiagorr@riseup.net> - 2024-12-04 15:10 +0100
  Bug#1089033: xen: Please package xen version 4.19 Sean Whitton <spwhitton@spwhitton.name> - 2024-12-05 05:10 +0100
  Bug#1089033: xen: Please package xen version 4.19 Hans van Kranenburg <hans@knorrie.org> - 2024-12-07 13:10 +0100
    Bug#1089033: xen: Please package xen version 4.19 Sean Whitton <spwhitton@spwhitton.name> - 2024-12-08 06:40 +0100
      Bug#1089033: xen: Please package xen version 4.19 Maximilian Engelhardt <maxi@daemonizer.de> - 2024-12-08 16:50 +0100
        Bug#1089033: xen: Please package xen version 4.19 Sean Whitton <spwhitton@spwhitton.name> - 2024-12-10 04:10 +0100
          Bug#1089033: xen: Please package xen version 4.19 Hans van Kranenburg <hans@knorrie.org> - 2024-12-19 23:30 +0100
            Bug#1089033: xen: Please package xen version 4.19 Sean Whitton <spwhitton@spwhitton.name> - 2024-12-20 04:10 +0100
              Bug#1089033: xen: Please package xen version 4.19 Hans van Kranenburg <hans@knorrie.org> - 2024-12-20 18:50 +0100
                Bug#1089033: xen: Please package xen version 4.19 Sean Whitton <spwhitton@spwhitton.name> - 2024-12-21 03:10 +0100
      Bug#1089033: xen: Please package xen version 4.19 Santiago Ruano Rincón <santiagorr@riseup.net> - 2024-12-11 01:10 +0100
        Bug#1089033: xen: Please package xen version 4.19 Sean Whitton <spwhitton@spwhitton.name> - 2024-12-12 04:20 +0100

csiph-web