On 6/4/24 12:13 PM, Rich Freeman wrote: > I don't want to be too picky as the core language maintainers have A > LOT of work to do, but part of the challenge is that it isn't very > obvious to a package maintainer (or anybody else) what packages > actually have problems. It is obvious if you actually look at a > package, but many maintainers have a large number of packages and some > are co-maintained, and knowing that one of your 100 packages wasn't > updated yet isn't easy. I'm not sure if somebody has a tool for > finding these packages in the tree, but some kind of reporting on that > would help.
It's less grim than you think. https://qa-reports.gentoo.org/ Check out "python reports" -- the list for those missing in testing, not the list for those present in testing but needing a stablereq. > Such reports need to be indexed to maintainers as well, > because getting a list of 1000 package names that need updating > doesn't help a maintainer to notice that they happen to maintain the > one on line 387. And indeed, the list includes the names of the maintainers, so just grep for yourself (or teams you are a member of). -- Eli Schwartz
OpenPGP_0x84818A6819AF4A9B.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
