action #128087
Updated by jbaier_cz 7 months ago
## Motivation See #127883 ## Acceptance Criteria * ** **AC1:** Projects in devel:openQA:* are in a known, clean state * **AC2:** For each package (link) in in devel:openQA:Leap:* we can understand why we have it there and what needs to be done to not need to maintain that package link anymore * **AC3**: We are notified if there's a package with a link without a reason ## Suggestions * Use the comment feature to add information to every linked package why we need it, which version we need and possibly a related ticket. * For example `Reason for linking: We use it for organizing our repos. Not in Leap yet` like in https://build.opensuse.org/package/show/devel:openQA:Leap:15.4/git-subrepo * Drop links which we don't have a reason to keep * Drop links considered obsolete * Automatically scan packages for comments to check that we're not missing any, e.g. * Check out https://api.opensuse.org/apidocs/index#/Comments/get_comments_package__project_name___package_name_ * curl on the API to list all packages in each Leap:* repo, for each grep comments for "Reason for linking", fail if not found * We could use osc or read-only API, first script solution: `for pkg in $(osc list devel:openQA:Leap:15.5); do osc comment list package devel:openQA:Leap:15.4 $pkg | grep -q 'Reason for linking' && continue; echo "package $pkg is missing reason for linking" && false; done` * `osc api /source/devel:openQA:Leap:15.5/perl-Perl-Tidy/_meta` * `osc api /source/devel:openQA:Leap:15.5/` * Ask in #help-obs