Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing
and unstable for more than 60 days as having a Release Critical bug in
testing [1]. Your package src:xwayland has been trying to migrate for 61
days [2]. Hence, I am filing this bug. The migration of your package is
blocked by an unresolved RC bug.

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.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bookworm, 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.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg00005.html
[2] https://qa.debian.org/excuses.php?package=xwayland

Hi, upstream Xwayland developer here.

AFAICT this is about https://bugs.debian.org/1008992 . It's very unlikely that this bug affects all users of xwayland, or there would have been a lot more noise about it. Therefore I don't think this should be RC.

(It's not clear that it's an xwayland bug at all. There was just a handful of small fixes upstream between 22.1.0 and 22.1.1, and there has been no similar report upstream)

Removing xwayland from testing would most certainly be much worse than letting the newer version migrate.

Hi

Great. I always love it when upstream watches Debian bugs.

Than I suggest to discuss that on that bug. If the maintainer of
xwaylang agrees that the bug isn't correctly classified according to
https://www.debian.org/Bugs/Developer#severities the severity can be lower.

Well, the bug could be present in other versions too, if that's the
case, adding "found" information will also unblock the migration (as the
bug is then no longer considered a regression.

xwayland is a key-package (but I didn't check that when I filed this
bug, hence "when appropriate" in my message). It's difficult to remove
and will not be done automatically. One of the key reasons of this class
of bug reports is to trigger somebody to look at the real causes and
take the right actions. Your reply is much appreciated by me.

Paul

Alright, I'll follow up there as well.

Right, though that would mean even the bug reporter didn't hit it with older versions, further suggesting it's not a pervasive bug.