On Mon, Jul 25, 2022 at 01:54:38PM +0200, Michal Schorm wrote: > Ah, It's a bit more tangled than I thought: > > I've somehow got an impression that the upstream release monitoring is > not related to Fedora, but I expected the BZ bot should be. > So I've looked for a place to report issues other than > https://github.com/fedora-infra/anitya/issues, as I thought it is the > upstream (not Fedora related) part of the project. Only after > following the link I've seen it is a GitHub repo in the "fedora-infra" > namespace. > > I've actually thought that the "monitoring status" option in the > src.fedoraproject.org does something different (pings you when > _anyone_ do a build or scratch-build of your package in KOJI - which > would be useful for watching who touches your pkg and how) > > The Pagure documentation doesn't seem to know about that field: > https://docs.pagure.org/pagure/search.html?q=monitoring > > So the 'Monitoring' value is likely what I am looking for, thanks ! :)
Just to clairfy some: anitya is release-monitoring.org. It's the thing that watches upstream releases and keeps a mapping of upstream name to downstream distro names. It does this for a bunch of distros, not just fedora. It emits messages on the fedora-messaging bus when mappings are made/changed and when updates are seen. It's configured only on it's web interface (release-monitoring.org). the-new-hotness is a seperate, but related application that listens for messages about new upstream releases, checks to see if that package in fedora wants to be notified/have scratch builds done for those. It handles filing bugzilla bugs, and doing scratch builds (if desired). It can be configured as you note on src.fedoraproject.org. If you want to watch activity on a package you want The little 'watch' pulldown under The package description. You can set there if you want to watch bugs, commits, both, etc. If you only wanted to watch koji builds, you would need to set that in FMN ( apps.fedoraproject.org/notifications) kevin -- > > -- > > On Mon, Jul 25, 2022 at 1:46 PM Fabio Valentini <decatho...@gmail.com> wrote: > > This sounds like it's trying to process and create patches for *the > > same version* again and again? > > If that is the case, you might want to file a bug with anitya / > > the-new-hotness, as that's certainly not its intended behaviour. > > Right, will report. > > -- > > Michal Schorm > Software Engineer > Core Services - Databases Team > Red Hat > > -- > > On Mon, Jul 25, 2022 at 1:46 PM Fabio Valentini <decatho...@gmail.com> wrote: > > > > On Mon, Jul 25, 2022 at 1:39 PM Michal Schorm <msch...@redhat.com> wrote: > > > > > > Hello, > > > I don't know where to go, so I'm trying here. > > > > > > Package 'mariadb-connector-c' [1] I maintain has upstream release > > > monitoring enabled [2]. > > > The bot opened a BZ [3] for me to notify about a new upstream release > > > - as expected. > > > > > > It tried to come up with a patch and try to scratch-build the package > > > with the patch. > > > However it failed. > > > And now it tries again and again, failing every time. Littering the BZ > > > ticket with more and more comments with zero value. Spamming people in > > > CC every day or two. > > > > > > I want it to stop. > > > > > > Ideally, I would like the bot to stop trying making patches and doing > > > scratch builds on all my packages at all. It's a wasted effort (and > > > computing time; and KOJI resources). > > > > > > Is that possible? > > > How? > > > > > > -- > > > > > > I logged into the https://release-monitoring.org/ , but there doesn't > > > seem to be any setting regarding that. > > > > release-monitoring.org only has a mapping from upstream projects to > > Fedora package names, but Fedora-specific settings live on > > src.fedoraproject.org. > > So, if you go to > > https://src.fedoraproject.org/rpms/mariadb-connector-c (you actually > > linked that page yourself), and are logged in: > > > > In the left-hand pane, there's a combobox where you can select "No > > monitoring", "Monitoring", and "Scratch builds". > > It's currently set to "Scratch builds", but if you know that those > > won't work, then change the setting to "Monitoring". > > That will at least cut down the number of notifications. > > > > > And now it tries again and again, failing every time. > > > > This sounds like it's trying to process and create patches for *the > > same version* again and again? > > If that is the case, you might want to file a bug with anitya / > > the-new-hotness, as that's certainly not its intended behaviour. > > > > 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 on the list, report it: > > https://pagure.io/fedora-infrastructure > _______________________________________________ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure
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 on the list, report it: https://pagure.io/fedora-infrastructure
