Bug#1116621: Should kmscon be removed from unstable?

[Vladimir K]

9.2.1 seems to have these fixed: #1061685, #1091429, #1061691, #1092167. 

#1061686 might require postinst tweak on Debian's side if one still wants to 
autoenable it on install and autodisable properly on removal.

I've built 9.2.1 it with only two patches remaining:
0002-Do-not-use-git-describe-to-generate-version.patch
0003-Use-system-version-of-unifont.hex.patch

Then linked unit to autovt@.service manually. Seems to work fine.

If the new control sequences to release and take back drmMaster are used as 
designed at the right times,
no glitches and broked input in TTYs/compositors are observed.

kmscon is still a WIP project by the look of things, so autoenabling it might 
be a bit premature.

Bug#1116621: Should kmscon be removed from unstable?

[Vladimir K]

Latest upstream 9.1.0 should have fixes for most problems. I'm going to test it.

Bug#1116621: Should kmscon be removed from unstable?

[Helmut Grohne]

Source: kmscon
Severity: important
User: helm...@debian.org
Usertags: sidremove

Dear maintainer,

I suggest removing kmscon from Debian for the following reasons:
 * It accumulated one RC-bug:
   + #1061686: kmscon: The removal of the kmscon package does not bring back 
the classical linux consoles
 Last modified: 1 year, 3 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 helm...@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: kmscon -- RoM; rc-buggy
Control: reassign -1 ftp.debian.org
Control: affects -1 + src:kmscon

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  for assistance.