Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1242432 > unrolled thread

Bug#1103423: src:kitty: fails to migrate to testing for too long: FTBFS on s390x

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1103423: src:kitty: fails to migrate to testing for too long: FTBFS on s390x Paul Gevers <elbrus@debian.org> - 2025-04-17 13:00 +0200
    Bug#1103423: src:kitty: fails to migrate to testing for too long: FTBFS on s390x Nilesh Patra <nilesh@debian.org> - 2025-04-23 21:00 +0200

#1242432 — Bug#1103423: src:kitty: fails to migrate to testing for too long: FTBFS on s390x

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

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.

If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or its 
(reverse-)dependencies. We expect maintainers to fix issues that hamper 
the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.

This bug submission immediately closes the bug with the version in 
unstable, so if that version or a later version migrates, this bug will 
no longer affect testing. This bug is also tagged to only affect sid and 
trixie, so it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.

This bug report has been automatically generated and has only been sent 
manually. If you have any comments with regards to the content or the 
process, please reach out to me.

Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=kitty

Current text from [2]:
Migration status for kitty (0.39.1-1 to 0.40.0-1): BLOCKED: Maybe 
temporary, maybe blocked but Britney is missing information (check below)
Issues preventing migration:
∙ ∙ missing build on s390x
∙ ∙ arch:s390x not built yet, autopkgtest delayed there
Additional info:
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/k/kitty.html
∙ ∙ Ignoring non-reproducibility on amd64 (not a regression) - info ♻ ∙ 
∙ Ignoring non-reproducibility on arm64 (not a regression) - info ♻ ∙ ∙ 
Waiting for reproducibility test results on armhf - info ♻ ∙ ∙ Ignoring 
non-reproducibility on i386 (not a regression) - info ♻ ∙ ∙ 31 days old 
(needed 10 days)

[toc] | [next] | [standalone]

#1243356

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web