On Fri, 2015-05-29 at 18:38 -0400, Felix Miata wrote:
Dimstar / Dominique Leuenberger composed on 2015-05-29 14:53 (UTC+0200):
* We have kde3 packages failing to build for 3 weeks without any
reaction. If nobody steps up to maintain this, I will file delete requests (notice mails went to the maintainers already).
Though I have KDE3 as only DE on several TW systems, they are used mostly only for testing, and infrequently for fresh installations. Thus, non-building, non-essential packages wouldn't get noticed here, leaving already installed packages untouched at zypper dup times, or would it? Do non-building packages result in zypper wanting to remove the installed older packages? A lot of zypper -v dup messaging asking confirmation scrolls beyond the start of the vtty screen buffer. Typically what's accessible stops among the lib* items to be upgraded.
As long as the deps of the package are in place (mainly lib) it will
remain installed, probably without issues. This can change any day.
Also, if deps are missing, a user performing updates likely sees less
issue than a user trying to newly install the package: the updater has
the deps already installed - the new user simply can't find them.
A package that does not build in the distribution is per definition to
be considered unmaintained, if nobody steps up and attempts to fix it
in a reasonable time - or at least can give reason why this is
breaking at the moment, with an outlook to get a fix.
Hence, the statement stays: if nobody steps up to maintain those KDE3
packages, they are being kicked out of the repositories (and anything
depending on them)
Cheers,
Dominique
--
Dimstar / Dominique Leuenberger