On 11/15/21 14:48, Fabio Valentini wrote:
I don't really have a solution here, but I'd be interested in looking at this problem. For example, most* [1] packages in the Rust stack will have (and should! have) the same versions across all supported Fedora branches. For any Rust packages that I push updates for, I update them right away across all branches, and that works very well to prevent me from forgetting things. However, any "newcomers" (or contributors who are more easily distracted than me) will often mess that up, making it hard for me (main Rust stack maintainer right now) to keep things aligned when I update other packages.
I'm glad to know I am not alone! I started down a path of writing a script that does something like this:
1) Scrape pagure's API to get all of my RPM repositories 2) Request the bodhi update versions for the package 3) Remove the ".fc##" from the version numbers4) Examine the latest available versions for each release and highlight differences
Step #1 takes 1 API request per 100 packages (which is 3 API requests for me), but #2 requires one API request per package. I feel like someone's going to be upset with me eventually for running so many API calls. 😠
I thought Koschei might be able to help with this but I couldn't figure out a way to get that information from there.
-- Major Hayden
Attachment:
OpenPGP_0x737051E0C1011FB1.asc
Description: OpenPGP public key
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
