| 1 |
On 6/27/20 2:28 AM, Robin H. Johnson wrote: |
| 2 |
> |
| 3 |
> TL;DR: Please make it easier to search on the QA reports site for |
| 4 |
> issues, and only show things directly relevant to the search. |
| 5 |
> |
| 6 |
> A long time ago, there was blizzy's site that listed packages that were |
| 7 |
> stabilization candidates, and you could filter by developer. It really |
| 8 |
> helped making it easier to detect and progress. |
| 9 |
|
| 10 |
$ pkgcheck --color true scan $(git grep -l robbat2@g.o |
| 11 |
'**/metadata.xml' | cut -d/ -f1-2) -c StableRequestCheck -R |
| 12 |
FormatReporter --format 'stabilize {category}/{package}-{version} # {desc}' |
| 13 |
|
| 14 |
There's also a bug open to integrate some of the pkgchecks to p.g.o, |
| 15 |
https://bugs.gentoo.org/725704 |
| 16 |
|
| 17 |
|
| 18 |
|
| 19 |
> |
| 20 |
> At a bare minimum, having an on-site way that already expands the data |
| 21 |
> and makes it searchable by developer. |
| 22 |
|
| 23 |
You can filter the output.html per-dev/per-project, but it's not as |
| 24 |
verbose as running pkgcheck locally can be. |
| 25 |
|
| 26 |
https://qa-reports.gentoo.org/output/gentoo-ci/output.html;maintainer=robbat2 |
| 27 |
|
| 28 |
https://qa-reports.gentoo.org/output/gentoo-ci/output.verbose.html;maintainer=robbat2 |
| 29 |
|
| 30 |
It doesn't straight out show python2 like this, but with the |
| 31 |
package.deprecated entry for it, it'll flag newly added py2 commits. |
| 32 |
|
| 33 |
-- juippis |
Archives