• Bug#1103595: RM: kitty [s390x] -- RoM; unsupported upstream

    From Nilesh Patra@21:1/5 to Paul Gevers on Sat Apr 26 10:50:01 2025
    Control: reassign -1 ftp.debian.org
    Control: severity -1 normal

    Hello FTP masters,

    Please remove kitty from s390x architecture. Upstream has refused
    the support for the same, see: https://github.com/kovidgoyal/kitty/issues/8548#issuecomment-2816794626

    Thank you.

    [ Replying to previous mail on this thread ]

    On 24/04/25 11:41 am, Paul Gevers wrote:
    That's OK. Pranav is already looking (in bug 1103595) and they are one
    of the 390x porters.

    A removal of this from testing is triggered in 3 weeks and I don't wish to pressurize
    anyone to come up with a patch quickly so I am reassigning this bug to ask FTP master
    for a removal in s390x.

    If at a later point a s390x patch works *and merged upstream*, we can think about cherry-picking it as a targeted fix.

    Given that soft freeze has now started, is it a sensible time to ask
    for removal
    of this package from s390x


    I think that's quite acceptable given the reply from upstream. Removing
    it now doesn't block Pranav from coming up with a fix in the near future
    and that would restore it for s390x in trixie.

    Yes.

    Nilesh, do you expect upstream to take patches despite the reply? I take it as
    similar to your reply: not interested to do the work, but if patches are available that look maintainable, then they are OK.

    Yes, they should accept it.

    You don't need to restrict the archs in d/control, as long as kitty continues to ftbfs on s390x.

    Fully agree. See also [1].

    I've just uploaded a new release, mostly to fix a pending CVE.
    I've added architecture-is-little-endian in git so this
    is picked up the next time.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)