-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove KDE 4 desktop packages #22977
Conversation
A terse change log: Removed NowRemoved Outright
Already UpdatedRemoved KDE 4 versions.
To Be Removed Dec 2017Update Available
Development Version Available
|
I should add, upstream will stop updating kdelibs4 around Dec 2017. At that time, I will simply remove any package which still depends on it. |
### Removed Outright
- psi
it actually does have an unreleased qt5 version (and maybe it can even
be made independent of KDE)
|
@7c6f434c Thank you for pointing this out! I was operating from information I got through the KDE packagers mailing list, which was apparently incorrect. |
> it actually does have an unreleased qt5 version (and maybe it can even be made independent of KDE)
@7c6f434c Thank you for pointing this out! I was operating from information I got through the KDE packagers mailing list, which was apparently incorrect.
Right now I understand how to build it with Qt5 and QCA2-Qt5, but it
segfaults for some reason…
|
In the "removed outright" section there are various applications with a Frameworks 5 version, at least:
PSI, semnotes are not by KDE. |
I am aware that these are not part of KDE. I was not able to find the Frameworks releases for these packages. I also didn't look hard, because they don't have maintainers in NixOS, anyway. If somebody wants to step forward and take the responsibility to be a maintainer, then I'll gladly put them back in. |
- Already updated to KDE 5 in Nixpkgs
- Already updated to KDE 5 in Nixpkgs
- Already updated to KDE 5 in Nixpkgs
- Already updated to KDE 5 in Nixpkgs
- Already updated to KDE 5 in Nixpkgs
- Already updated to KDE 5 in Nixpkgs
- Already updated to KDE 5 in Nixpkgs
- Already updated to KDE 5 in Nixpkgs
- Already updated to KDE 5 in Nixpkgs
- Already updated to KDE 5 in Nixpkgs - Not useful without the KDE 4 desktop
- Already updated to KDE 5 in Nixpkgs - Not useful without the KDE 4 desktop
- Not useful without the KDE 4 desktop
- Already updated to KDE 5 in Nixpkgs - Not useful without the KDE 4 desktop
- Not useful without the KDE 4 desktop
- Already updated to KDE 5 in Nixpkgs - Not useful without the KDE 4 desktop
- No maintainer in Nixpkgs
- Already updated to KDE 5 in Nixpkgs
- No upstream activity
- No maintainer in Nixpkgs
- Already updated to KDE 5 in Nixpkgs
- No maintainer in Nixpkgs
- No maintainer in Nixpkgs
- No longer used
- Already updated to KDE 5 in Nixpkgs
- No longer used
- No longer used
- No maintainer in Nixpkgs - No upstream activity - Original source unavailable
- No activity upstream - Known vulnerabilities
- No activity upstream
- Not useful without the KDE 4 desktop
This reverts commit c2fcc909cb42d9aaa456d211f9c68cc24f4ef804. - Upstream development is ongoing; we will keep psi for now to preserve continuity.
It was permanently disabled anyway.
Our kdelibs4 package does not come from KDE 4, so per upstream's request I am moving it out of the kde4 set.
To comply with upstream's request, only packages released as part of KDE 4 will be in the kde4 set.
The Travis failure is a spurious build timeout. |
Here I begin to remove the KDE 4 desktop packages.
Discussion period until 25 Feb 2017. To be announced on the mailing list.
The NixOS module for KDE 4 has already been removed. Relevant discussion is at #15866.
I have removed as many core packages as possible at this time. To facilitate this, I have removed third-party applications that depend on KDE 4 if I think they are unlikely to be updated. The remainder should be updated as soon as possible to remove the remaining KDE 4 libraries. The major offenders here are:
In the process of removing core libraries, I discovered that we have not been keeping up-to-date on Nepomuk libraries. This happened because upstream bundles Nepomuk with kdelibs, but our builder was separating them. As a result, we had new kdelibs with old Nepomuk. It is possible there are undisclosed vulnerabilities with our old KDE 4 packages and users should be moved away from them as soon as possible.
ATTN: @grahamc