Re: How to correctly use Upstream release monitoring functionality?

[Petr Pisar]

V Tue, Jun 27, 2023 at 08:34:50AM +0200, Petr Pisar napsal(a):
> You can also check an archive of the notification
> .
> 
There is
:

org.fedoraproject.prod.hotness.update.drop the-new-hotness saw an update
for 'cpr', but release-monitoring.org doesn't know what that project is
called in Fedora land JSON

It looks like a mapping from an upstream project to a Fedora package was not
defined at the time when Anitya detected a new version in the upstream.

Though, I don't fully understand the message. I thought that Anitya notifies
distributions only having set the mapping. Either the message is wrongly
worded, or my idea how it works is wrong.

-- Petr


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: How to correctly use Upstream release monitoring functionality?

[Petr Pisar]

V Tue, Jun 27, 2023 at 02:03:36AM -, Felix Wang napsal(a):
> I see the Fedora documentation about Upstream release monitoring. First, add 
> the project to Anitya and map it to the corresponding Fedora package, and 
> secondly, enable the monitoring in its fedora-src repository. I have set 
> these for cpr package, but I didn't receive the related message about its 
> updating status. Could anyone can help me to explain and use this?
> 
> Ref:
> https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring/
> https://release-monitoring.org/project/66765/
> https://src.fedoraproject.org/rpms/cpr
> https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW_status=ASSIGNED=Fedora=Fedora=Fedora%20EPEL=cpr

Did you enable the notifications first in Fedora
 and then in Anitya
? I guess if you do it in the
other way, a notification from Anitya is discarded by Fedora because
creating bug reports in Fedora's Bugzilla is disabled at the time of arrival
of the notification.

Otherwise, it's some kind of bug in the notification chain. You can file
i ticket to  or to
 to start an
investigation. You can also check an archive of the notification
.

-- Petr


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

How to correctly use Upstream release monitoring functionality?

[Felix Wang]

I see the Fedora documentation about Upstream release monitoring. First, add 
the project to Anitya and map it to the corresponding Fedora package, and 
secondly, enable the monitoring in its fedora-src repository. I have set these 
for cpr package, but I didn't receive the related message about its updating 
status. Could anyone can help me to explain and use this?

Ref:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring/
https://release-monitoring.org/project/66765/
https://src.fedoraproject.org/rpms/cpr
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW_status=ASSIGNED=Fedora=Fedora=Fedora%20EPEL=cpr
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue