* Nilesh Patra <[email protected]> [250423 20:54]:

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?

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

IMO: Just get the old binaries removed from s390x.

Or do you think I should just go ahead w disabling tests for this arch for now?

Not Paul or RT, but I think it makes sense to keep the tests
failing. I believe very few people will run GUI programs on s390x,
so not having kitty there seems safe.

Chris

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