mark long-failing packages broken for 18.09 #46385
Conversation
no successfull build in Hydra history back to 2017-08-21
no successful hydra build since 2018-01-03
No successful hydra build since 2018-02-14. The build fails in the ruby gem json-1.8.3, which we cannot mark directly as broken in nixpkgs, so we mark this as broken.
|
It may be a good idea to cc the maintainers of those programs here for a reaction. Well, for those with a maintainer!
|
|
Argh, CLASP upstream planned to have 0.5 芦soon禄 in the spring (I asked which branch to package), so I am periodically checking if it is there, and it is not there yet. Yes, my bad, should have marked broken in the meantime. |
no successful hydra build since 2017-12-11
|
|
no successful build since 2017-08-19
|
( |
no successful hydra build since 2018-03-16, last upstream release 2009.
|
( |
- no successful build since 2018-04-25 - not used in nixpkgs anymore
|
btw I think we should get rid of qt56 altogether... |
I agree, now that it is no longer used. We kept it for legacy reasons because it was a long-term support release and some packages could not be upgraded. |
|
I'll merge these now so we can get the numbers down 馃槃. Stay tuned for the next round... |
xeji
changed the title
Motivation for this change
While looking at Hydra failures for ZHF #45960, I found some packages that have been failing for a long time. Great opportunity to start a little clean-up for 18.09.
I propose a simple rule:
A package that has not had a successful Hydra build since 2018-03-01 (before 18.03 was branched off) deserves neither immediate investigation nor more Hydra resources, and will be marked broken right away. It would have been fixed by now if there was demand for it.
Of course, whoever is interested can fix and resurrect them later... If that doesn't happen, these packages should be removed for 19.03.
I'll keep adding more packages to this list as I find them, and merge when the list is long enough 馃槃
How you can help
cc @samueldr @vcunat