Re: How to correctly use Upstream release monitoring functionality?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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=2592000>.
> 
There is
<https://apps.fedoraproject.org/datagrepper/raw?category=hotness&package=cpr&delta=2592000>:

    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

Attachment: signature.asc
Description: PGP 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, report it: https://pagure.io/fedora-infrastructure/new_issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux