Hi. I added to the repository fedora-misc-package-utilities
https://forge.fedoraproject.org/packaging/fedora-misc-package-utilities three new scripts. They should ease your work rebasing to the new upstream release. * check-release-monitoring - Checks if packages you maintain has Fedora entry at https://release-monitoring.org/ * check-packit-pull-from-upstream - Checks if packages you maintain has Packit config with pull-from-upstream job defined. * create-packit-pull-from-upstream - Create Packit config with pull-from-upstream job using data retrieved from https://release-monitoring.org/ The first two scripts accept the username as an optional parameter. Otherwise, it will use your OS username. The first script - check-release-monitoring checks the existence of an entry inhttps://release-monitoring.org/ Your package can have "Monitoring" enabled in src.fedoraproject.org, but unless there is an entry in https://release-monitoring.org/ you will never receive any notification about a new upstream release. If your package is not listed on release-monitoring.org, you can add it there. If you are a member of many SIGs (and FAS groups), you can run this script with '--ignore-groups` the script will print only packages where you are explicitly listed. The second script checks if your package has a Packit configuration for pull-from-upstream https://packit.dev/docs/configuration/downstream/pull_from_upstream when this job is configured, Packit will create a new pull request automatically every time upstream release new version. Packit-CI will run tests on it, and if you are lucky, then rebase is just a quick review and one click on the merge button. When your package is missing the Packit config and pull-from-upstream job, you can use third script. You should run it in the package's dist-git repository. It will try to utilize the in release-monitoring.org If you already have an existing Packit config, it will amend it and not overwrite it. After you add a new Packit config (and release-monitoring entry), and there is already a new upstream release from the past that is not present in Fedora, you can trigger Packit manualy to create a pull-request for you using: packit pull-from-upstream in dist-git repo. Seehttps://packit.dev/docs/cli/pull-from-upstream for more information. Last but not least, thank you @churchyard for the review of these scripts -- Miroslav Suchy, RHCA Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
-- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
