Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helper to file stablereqs? #113

Closed
thesamesam opened this issue Jan 5, 2023 · 1 comment · Fixed by #114
Closed

Helper to file stablereqs? #113

thesamesam opened this issue Jan 5, 2023 · 1 comment · Fixed by #114

Comments

@thesamesam
Copy link
Member

We are nearly there wrt the stablereq/archtesting toolset, but not quite:

  • Testing packages: app-portage/pkg-testing-tools or app-portage/tatt
  • Getting list of work from Bugzilla, updating Bugzilla: app-portage/nattka
  • Processing said work automatically: https://github.com/arthurzam/tattoo
  • Finding stablereqs to file (or kwreqs): pkgcheck scan -k StableRequest or pkgcheck scan -k DroppedKeywords

But we have nothing to help file stablereqs. slyfox pointed this out a while ago at https://trofi.github.io/posts/214-filing-STABLEREQ-for-lazies.html (https://bugs.gentoo.org/708912). I think this would be a good fit for pkgdev.

@arthurzam
Copy link
Member

So, funny enough, I was planing working on it this weekend. While I'm unsure about the name (I was thinking about pkgdev bugs - bad name, right...), I did have a plan for it:

  • accepts list of atoms (=cat/pkg-ver)
  • finds all extra missing packages (similar to nattka make-package-list)
  • build a directed graph - based on hard dependency (AKA blocks field in bug)
  • all packages that are in circular dependency in this graph would be collected into one "super node" (which translates into one bug with multiple packages in package list)
  • enable the user to stop and get the .dot file showing the graph
  • finally, for each new node, create automatically the bug, dependencies, maintainers
  • have a flag to automatically add CC-ARCHES keyword.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants