It seems there is no upstream release monitoring settings in Pagure (or I wasn't able to find it). Also there is no mention in the migration doc [1] how to setup/edit it.
I need to add upstream release monitoring to existing project preeny. I created request by:
$ fedrepo-req preeny -m monitoring -t 1479022
But the request [2] has been closed as invalid. What's the correct procedure for it? Could you add support/link to Pagure project pages and update the docs?
thanks & regards
Jaroslav
[1] https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb [2] https://pagure.io/releng/fedora-scm-requests/issue/36
Yes. It was @tibbs' suggestion to store the monitoring info in a side repo. You can find the preeny flag over here: https://pagure.io/releng/fedora-scm-requests/blob/master/f/rpms/preeny
However, the-new-hotness hasn't been re-tooled to use that data yet.
See https://github.com/fedora-infra/the-new-hotness/pull/185
ok, so we need a new hotness release deployed and then documentation right?
Would be good to add to whathappenedtopkgdb and the readme file in the fedora-scm-requests repo and any new package workflow wiki pages.
Metadata Update from @kevin: - Issue tagged with: src.fp.o
The README at https://pagure.io/releng/fedora-scm-requests#anitya has been adjusted
whathappenedtopkgdb remains to do
Wiki adjusted: https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb#How_do_I_change_the_upstream-monitoring.2Fanitya_flag_for_my_packages.3F
Feel free to edit/improve it :)
Metadata Update from @pingou: - Issue close_status updated to: Fixed
Login to comment on this ticket.