Dear maintainer,

I suggest removing xpra from Debian for the following reasons:
 * It accumulated one RC-bug:
   + #1067627: FTBFS: error: comparison of integer expressions of different signedness: ‘long unsigned int’ and ‘long int’
     Last modified: 1 year, 4 months

 * It is not part of trixie or forky and is not a key package.

This bug serves as a pre-removal warning. After one month, the bug will be
reassigned to ftp.debian.org to actually request removal of the package.

In case the package should be kept in unstable, please evaluate each of the
RC-bugs listed above.
 * If the bug is meant to permanently prevent the package from entering testing
   or a stable release, but this package should stay part of unstable, please
   add a usertag:

       user helmutg@debian.org
       usertags NNN + sidremove-ignore

 * If the bug no longer applies, please close it. If it is closed, check
   whether the fixed version is correct and adjust if necessary.

 * Is the bug really release-critical? If not, please downgrade.

 * If the bug still applies, please send a status update at least once a year.

Once all of the mentioned RC bugs have been acted upon in one way or another,
please close this bug.

In case the package should be removed from unstable, you may reassign this
bug report:

    Control: severity -1 normal
    Control: retitle -1 RM: xpra -- RoM; rc-buggy
    Control: reassign -1 ftp.debian.org
    Control: affects -1 + src:xpra

Alternatively, you may wait a month and have it reassigned.

In case you disagree with the above, please add a wontfix tag to this bug.

    Control: tags -1 + wontfix

Doing so will also prevent automatic reassignment.

Kind regards

A tool for automatically removing packages from unstable

This bug report has been automatically filed with little human intervention.
If the filing is unclear or in error, don't hesitate to contact
Helmut Grohne <helmut@subdivi.de> for assistance.

Helmut Grohne <helmut@subdivi.de> writes:

For what it is worth, I depend on xpra for my work. I have one VM
running bookworm that is crucial in the teaching of one course. I will
be sad if xpra goes away, but it sounds like I should already be sad
since it is not in stable.

d

Maybe you want to ITS it. Upstream seems to be quite active. So it
looks like we "just" need someone doing the Debian work.

Chris

No, Xpra should not be removed. We are going to fix it in "unstable".

---

The worst thing that can happen to a socialist is to have his country ruled
by socialists who are not his friends.
 -- Ludwig von Mises

[Dmitry Smirnov 2025-09-03]

Very good.  Any idea about the time frame for this fixing?

That is still unclear as I am still unwell. Might have a chance to work on
it this month (or next).

Was it necessary to remind? Lately, number of packages were needlessly
removed from "unstabble"... I don't want to ping such bug reports to
prevent removal of packages that need little attention.

---

When enough people understand reality, tyrants can literally be ignored
out of existence. They can't ever be voted out of existence.
 -- Larken Rose

[Dmitry Smirnov]

I guess you know more than me how useful a reminder is/was.  I found it
useful to know more about the expected time frame, to get more
information regarding its likelihood of making it into the next stable
release.

The xpra package was removed from testing 2024-04-24, was last included
in a release in oldstable / bookworm, and any BTS update do not affect
much, as can be seen on <URL: https://tracker.debian.org/pkg/xpra >.