1 |
On 15/03/19 10:54, Michał Górny wrote: |
2 |
> Hi, |
3 |
> |
4 |
> Since some people were looking for a ways to help Treecleaners |
5 |
> in the past, I'd like to suggest an easy talk that could help us a bit. |
6 |
> There is a large number of maintainer-needed packages that are probably |
7 |
> broken, and it would be helpful to do some filtering there. |
8 |
> |
9 |
> Basically: |
10 |
> |
11 |
> 1. Go through the list of m-needed packages not slated for cleaning: |
12 |
> |
13 |
> https://bit.ly/2HnSLQJ |
14 |
> |
15 |
> 2. Find bugs that indicate that the package does not build and/or is |
16 |
> seriously broken (i.e. useless). |
17 |
> |
18 |
> 3. If possible, verify the reports (i.e. try building yourself). |
19 |
> |
20 |
> 4. Check if the package has reverse dependencies. You can use my quick |
21 |
> ugly script to get them from command-line: |
22 |
> |
23 |
> https://github.com/mgorny/mgorny-scripts/blob/master/rdep |
24 |
> |
25 |
> 5. If the package is definitely broken and has no revdeps (or all |
26 |
> revdeps are equally broken), CC treecleaner@ on the relevant bug. |
27 |
> |
28 |
> 6. Providing any extra useful info would be also welcome (i.e. whether |
29 |
> Gentoo version is outdated, last release upst, last commit, whether bug |
30 |
> is fixed upst, etc.) |
31 |
> |
32 |
> TIA! |
33 |
> |
34 |
Surely it should be possible to script/automate at least half of this, and |
35 |
generate a report which a human can then scrutinise .. it could then be run |
36 |
on a cron job and a report generated for said human to parse .. |
37 |
|
38 |
1 & 2 are good candidates for pybugz (iirc) |
39 |
3 is tinderbox/stabilisation/keywording type building anyway |
40 |
4 .. already a script |
41 |
6 .. some basic Curl of the HOMEPAGE, SRC_URI to return whether it 404's or |
42 |
else (even 30x would be instructive) |
43 |
|
44 |
Then all that's needed is to wrap the results up in some form of eg. |
45 |
JSON/YAML structure which can then be parsed by some template/etc. |
46 |
|
47 |
I'm half tempted to throw together a proof-of-concept myself .. but I'm |
48 |
sure there are better devs out there .. |
49 |
If nothing better appears by end March .. will hash something together. |
50 |
Regards, |
51 |
veremitz/Michael. |