How to correctly use Upstream release monitoring functionality?
- First Post
- Replies
- Stats
-
Go to
- ----- 2024 -----
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2007 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2006 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2005 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2004 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2003 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2002 -----
- December
- November
- October
- September
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...
https://release-monitoring.org/project/66765/
https://src.fedoraproject.org/rpms/cpr
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASS...
V Tue, Jun 27, 2023 at 02:03:36AM -0000, 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...
https://release-monitoring.org/project/66765/
https://src.fedoraproject.org/rpms/cpr
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASS...
Did you enable the notifications first in Fedora
<https://src.fedoraproject.org/rpms/cpr> and then in Anitya
<https://release-monitoring.org/project/66765/>? 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 <https://pagure.io/fedora-infrastructure/issues> or to
<https://github.com/fedora-infra/the-new-hotness/issues> to start an
investigation. You can also check an archive of the notification
<https://apps.fedoraproject.org/datagrepper/raw?category=hotness&delta...;.
-- Petr
V Tue, Jun 27, 2023 at 08:34:50AM +0200, Petr Pisar napsal(a):
You can also check an archive of the notification
<https://apps.fedoraproject.org/datagrepper/raw?category=hotness&delta...;.
There is
<https://apps.fedoraproject.org/datagrepper/raw?category=hotness&packa...;:
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
326
days inactive
326
days old
2 comments
2 participants
tags (0)
participants (2)
-
Felix Wang -
Petr Pisar