[gentoo-project] Easy task to help Treecleaners: finding broken m-needed packages

[gentoo-project] Easy task to help Treecleaners: finding broken m-needed packages

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

Hi,

Since some people were looking for a ways to help Treecleaners
in the past, I'd like to suggest an easy talk that could help us a bit. 
There is a large number of maintainer-needed packages that are probably
broken, and it would be helpful to do some filtering there.

Basically:

1. Go through the list of m-needed packages not slated for cleaning:

   https://bit.ly/2HnSLQJ

2. Find bugs that indicate that the package does not build and/or is
seriously broken (i.e. useless).

3. If possible, verify the reports (i.e. try building yourself).

4. Check if the package has reverse dependencies.  You can use my quick
ugly script to get them from command-line:

   https://github.com/mgorny/mgorny-scripts/blob/master/rdep

5. If the package is definitely broken and has no revdeps (or all
revdeps are equally broken), CC treecleaner@ on the relevant bug.

6. Providing any extra useful info would be also welcome (i.e. whether
Gentoo version is outdated, last release upst, last commit, whether bug
is fixed upst, etc.)

TIA!

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

Re: [gentoo-project] Easy task to help Treecleaners: finding broken m-needed packages

[Michael Everitt]

[-- Attachment #1.1: Type: text/plain, Size: 1985 bytes --]

On 15/03/19 10:54, Michał Górny wrote:
> Hi,
>
> Since some people were looking for a ways to help Treecleaners
> in the past, I'd like to suggest an easy talk that could help us a bit. 
> There is a large number of maintainer-needed packages that are probably
> broken, and it would be helpful to do some filtering there.
>
> Basically:
>
> 1. Go through the list of m-needed packages not slated for cleaning:
>
>    https://bit.ly/2HnSLQJ
>
> 2. Find bugs that indicate that the package does not build and/or is
> seriously broken (i.e. useless).
>
> 3. If possible, verify the reports (i.e. try building yourself).
>
> 4. Check if the package has reverse dependencies.  You can use my quick
> ugly script to get them from command-line:
>
>    https://github.com/mgorny/mgorny-scripts/blob/master/rdep
>
> 5. If the package is definitely broken and has no revdeps (or all
> revdeps are equally broken), CC treecleaner@ on the relevant bug.
>
> 6. Providing any extra useful info would be also welcome (i.e. whether
> Gentoo version is outdated, last release upst, last commit, whether bug
> is fixed upst, etc.)
>
> TIA!
>
Surely it should be possible to script/automate at least half of this, and
generate a report which a human can then scrutinise .. it could then be run
on a cron job and a report generated for said human to parse ..

1 & 2 are good candidates for pybugz (iirc)
3 is tinderbox/stabilisation/keywording type building anyway
4 .. already a script
6 .. some basic Curl of the HOMEPAGE, SRC_URI to return whether it 404's or
else (even 30x would be instructive)

Then all that's needed is to wrap the results up in some form of eg.
JSON/YAML structure which can then be parsed by some template/etc.

I'm half tempted to throw together a proof-of-concept myself .. but I'm
sure there are better devs out there ..
If nothing better appears by end March .. will hash something together.
Regards,
veremitz/Michael.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]