Hi All,
So one thing I noticed when doing the ppc64le bootstrap is that
there's a bunch of updates that are a bit of a mess and there's a
whole bunch of run and dump in updates. There's everything from
updates with CVEs that are broken for a a long time [2], updates there
for 11+ months with missing deps (build or otherwise) [1], or just
sitting there for ever [3]. I have cleaned up a bunch of stuff in
epel7 around tagging too but not looked at the others.
I know Kevin had a bit of a look at this [4] and I think I've fixed up
a bunch of the issues in the process of the arch bringup which should
settle a little once those updates go stable but I think we could do
better to keep this cleaner with some of the tools we already use in
Fedora.
So some ideas to try and improve this, without a bunch of manual work,
in no particular order:
1) Enable task-o-tron dep checking on updates in bodhi with aim to not
push broken updates (EPEL is suppose to be more stable)
2) Automatic unpushing of updates that haven't gone stable after X
time (I propose 3 months/90 days here). That should be ample time to
know if it's good/bad.
3) Some sort of dep check spam-o-matic (daily branched/rawhide) style
weekly report (might not be needed if we never break stuff)
I was a bit shocked to see the state of EPEL7, I sort of expected it
to be better than Fedora due to the more stable nature but it was,
even this early in the el7 cycle, a bit of a mess!
Anyone else have some thoughts and ideas for improving this?
Peter
[1]
https://bodhi.fedoraproject.org/updates/python-flask-assets-0.10-2.el7
[2]
https://bodhi.fedoraproject.org/updates/dokuwiki-0-0.24.20140929c.el7
[3]
https://bodhi.fedoraproject.org/updates/389-admin-console-1.1.10-1.el7
[4]
https://lists.fedoraproject.org/archives/list/epel-devel%40lists.fedorapr...