Re: Curious how Upstream Release Monitoring works
Dne 14. 12. 22 v 16:41 Fabio Valentini napsal(a): On Wed, Dec 14, 2022 at 4:38 PM Ron Olson wrote: Hey all- I’m curious how Upstream Monitoring works; I got a BZ filed https://bugzilla.redhat.com/show_bug.cgi?id=2153189 Right? that Swift 5.7.2 is available, which I’m building now, but what surprised me was how fast the new version was detected and brought to my attention. Does it use The New Hotness? I set that up awhile ago but I don’t think it files BZ tickets (and I must not have it set up correctly as it hasn’t notified me about any releases for the past year). To be clear this isn’t a complaint, if anything it’s an awesome feature and I’m just curious what the mechanism is that makes it work. There's several components involved to make this work: - anitya, which powers release-monitoring.org: this is where you need to set up the project and set the Fedora package name for it, and which crawls projects for new versions regularly - the-new-hotness: the service which files bugs for new versions detected by anitya, if "Monitoring" is enabled for a package on src.fedoraproject.org I wonder why "(and I must not have it set up correctly as it hasn’t notified me about any releases for the past year)." happened, though. There are also older similar reports looking at: https://bugzilla.redhat.com/buglist.cgi?component=swift-lang_id=13042844=Fedora so it works for some time already it seems. Vít Fabio ___ 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 OpenPGP_signature Description: OpenPGP digital 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: Curious how Upstream Release Monitoring works
There is a plan to automate that when you request a new package in Fedora [0], but it's still work in progress. The notification settings are now explained in the-new-hotness documentation [1] with new coming in upcoming release of src.fedoraproject.org. Michal [0] - https://pagure.io/releng/issue/10110 [1] - https://the-new-hotness.readthedocs.io/en/stable/user-guide.html#notifications-settings On 14. 12. 22 16:44, Sérgio Basto wrote: On Wed, 2022-12-14 at 09:36 -0600, Ron Olson wrote: Hey all- I’m curious how Upstream Monitoring works; I got a BZ filed that Swift 5.7.2 is available, which I’m building now, but what surprised me was how fast the new version was detected and brought to my attention. Does it use The New Hotness? I set that up awhile ago but I don’t think it files BZ tickets (and I must not have it set up correctly as it hasn’t notified me about any releases for the past year). To be clear this isn’t a complaint, if anything it’s an awesome feature and I’m just curious what the mechanism is that makes it work. Hi , what package is concrete ? you need mapping in https://release-monitoring.org/ for example https://release-monitoring.org/project/6221/ and in src.fedoraproject.org you need set scratch builds https://src.fedoraproject.org/rpms/smb4k Ron ___ 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 ___ 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: Curious how Upstream Release Monitoring works
On Wed, 2022-12-14 at 09:36 -0600, Ron Olson wrote: > Hey all- > > I’m curious how Upstream Monitoring works; I got a BZ filed that > Swift 5.7.2 is available, which I’m building now, but what surprised > me was how fast the new version was detected and brought to my > attention. Does it use The New Hotness? I set that up awhile ago but > I don’t think it files BZ tickets (and I must not have it set up > correctly as it hasn’t notified me about any releases for the past > year). > > To be clear this isn’t a complaint, if anything it’s an awesome > feature and I’m just curious what the mechanism is that makes it > work. Hi , what package is concrete ? you need mapping in https://release-monitoring.org/ for example https://release-monitoring.org/project/6221/ and in src.fedoraproject.org you need set scratch builds https://src.fedoraproject.org/rpms/smb4k > Ron > ___ > 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 -- Sérgio M. B. ___ 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: Curious how Upstream Release Monitoring works
On Wed, Dec 14, 2022 at 4:38 PM Ron Olson wrote: > > Hey all- > > I’m curious how Upstream Monitoring works; I got a BZ filed that Swift 5.7.2 > is available, which I’m building now, but what surprised me was how fast the > new version was detected and brought to my attention. Does it use The New > Hotness? I set that up awhile ago but I don’t think it files BZ tickets (and > I must not have it set up correctly as it hasn’t notified me about any > releases for the past year). > > To be clear this isn’t a complaint, if anything it’s an awesome feature and > I’m just curious what the mechanism is that makes it work. There's several components involved to make this work: - anitya, which powers release-monitoring.org: this is where you need to set up the project and set the Fedora package name for it, and which crawls projects for new versions regularly - the-new-hotness: the service which files bugs for new versions detected by anitya, if "Monitoring" is enabled for a package on src.fedoraproject.org I wonder why "(and I must not have it set up correctly as it hasn’t notified me about any releases for the past year)." happened, though. Fabio ___ 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
Curious how Upstream Release Monitoring works
Hey all- I’m curious how Upstream Monitoring works; I got a BZ filed that Swift 5.7.2 is available, which I’m building now, but what surprised me was how fast the new version was detected and brought to my attention. Does it use The New Hotness? I set that up awhile ago but I don’t think it files BZ tickets (and I must not have it set up correctly as it hasn’t notified me about any releases for the past year). To be clear this isn’t a complaint, if anything it’s an awesome feature and I’m just curious what the mechanism is that makes it work. Ron ___ 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
