Hi Paul,
On 17/04/25 4:20 pm, Paul Gevers wrote:
Source: kitty
Version: 0.39.1-1
Severity: serious
Control: close -1 0.40.0-1
Tags: sid trixie
User: release.debian.org@packages.debian.org
Usertags: out-of-sync
X-Debbugs-CC: debian-s390@lists.debian.org
User: debian-s390@lists.debian.org
Usertag: s390x
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:kitty has been trying to migrate for 31
days [2], hence this bug report. The current output of the migration
software for this package is copied to the bottom of this report and
should list the reason why the package is blocked.
This migration is stalled due to build (rather build-time test) failures on s390x.
Upstream has explicitly denied to provide any support for s390x see[1].
And I don't think I have the interest, time and energy to support a port this for big endian arch myself.
Given that soft freeze has now started, is it a sensible time to ask for removal
of this package from s390x and specify only rest of the release architectures in d/control?
Or do you think I should just go ahead w disabling tests for this arch for now?
Or to play it safe, do you think we can go ahead with 0.39.1-1 only for trixie? In this case
this bug needs to adjust versions so a removal is not triggered.
This is my least preferred option as there's a CVE reported in #1103691
that I'd very much like to fixup.
I'd appreciate any advice.
[1]
https://github.com/kovidgoyal/kitty/issues/8548
Best,
Nilesh
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)