Hi

On 02-06-2022 10:53, Michel Dänzer wrote:
On 2022-06-01 21:14, Paul Gevers wrote:
Hi, upstream Xwayland developer here.

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

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.

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.

(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)

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.

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.

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

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

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to