[Pkg-xen-devel] Bug#1089033: xen: Please package xen version 4.19

[Hans van Kranenburg]

Hi Sean,

On 12/10/24 03:58, Sean Whitton wrote:
> 
> Uploaded to NEW.  Please 'dgit fetch' my
> debian/4.19.0+14-g0918434e0f-1_exp1 tag and push it to your repository
> on salsa.  Thanks!

Done.

We'd like to request an additional sponsored upload, since we're again
touching the binary packages list...

https://salsa.debian.org/xen-team/debian-xen/-/commits/experimental

I already tried uploading it, but got a REJECTED back. I couldn't really
find definitive information about when exactly a binary package name
would trigger NEW if it was already in the archive and related to the
same source package, so I gave it a try to find out. So, the dgit tags
etc do already exist. I don't know if this is a problem.

We have a FTBFS on armhf, and while investigating, we found out that
we're not going to be able to fix that. Since the armhf build was
already unusable by default for years, we're now deciding to pull the
plug on the life support of the already comatose patient.

Also see the commits.

And, we're also uncrufting the remainder of the t64 stuff, because for
the libraries involved it already did not make sense to begin with. And
if it had made sense, it could actually have introduced upgrade problems
for our users, since these are the libraries that users would also be
using then rebooting back to the Bookworm Xen 4.17 for any reason after
they upgrade to Trixie. But, in any case, we don't even have 32-bit
archs left currently, so that would only have applied to armhf which no
one is running with Debian Xen packages already. ¯\_(ツ)_/¯

Regards,
Hans