On 5/15/26 6:23 PM, kpcyrd wrote:
On 5/15/26 3:41 PM, Jelle van der Waa wrote:I've just rolled out a new updated archlinux.org, notable changes are:* Developer reports now contain a link to a list of pkgbases * bumpbuddy out of date data import supportThe bumpbuddy import has now been deployed and is running. See for example aws- vault being flagged by bumpbbuddy. Note that the automatic import doesn't send any email notification like the manual flagging out of date does. [1]In the future the flag out of date button will be disabled in favor of importing bumpbuddy out of date data. Note that we still lack nvchecker integration in packages in this To- Do. [2]Very nice! :)Is there a good way forward with the (old) Gitlab email notifications? I currently receive one email when the package is detected as out-of-date, and then two additional ones when the package is updated (one for the comment, one for the status change to "closed").I guess at this point of the integration I would be fine with just monitoring the developer dashboard on archlinux.org myself, without needing extra emails. That would also solve the problem of stale notifications when a co-maintainer updates the package before I even see the out-of-date email. When a user explicitly flags I'd be fine with receiving one.Thanks for working on this, to everybody involved! cheers, kpcyrd
Hey,Regarding email notifications, here's a quick sum up of how things currently work and future changes on that front:
- Automated "out of date" reports on Archweb from bumpbuddy's data do *not* send an email, so there shouldn't duplicate notifications. GitLab remains the place to manage email notifications for "out of date" reports (which are opt-in and can be controlled from bugbuddy user's settings [1])
- The two additional emails when the package is updated are indeed noisy, this is unfortunately due to limitations of the GitLab API. However, this should be addressed in the next `devtools` release! I've opened a related merge request which is scheduled for the future 1.6.0 devtools release. The change aims to automatically close bumpbuddy "out of date" issues when the matching version is released via `pkgctl release`, by automatically adding the "closes <issue_url>" to the commit message.
This has multiple benefits:- Instant closing of the issue (while it is only closed at the next bumpbuddy run currently) - Issue being closed with linking to the actual commit that pushed the relevant version - No additional notification for the person that closed the issue by releasing the matching version (as you don't get a mail for issues that you closed yourself) - Only a single notification for other assignes (e.g. co-maintainer) like "Person X closed issue Y with commit Z", as a way to know that someone else bumped the package
I think this setup should be much more relevant in terms of notification.- Monitoring the developer dashboard on archlinux.org yourself without opting-in to the notification is indeed a possibility. Alternatively (and also as a reminder for everyone else reading this mail), bumpbuddy data are publicly exposed on a web dashboard [3] and as json [4]. The former allows for a graphical & global monitoring of data with easy filtering (e.g. searching for your nick in the search bar and sort the "Up to date" column) and the later can eventually serve as an endpoint for API calls / custom scripts.
Hopefully this covers your questions? Let me know otherwise :) [1] https://gitlab.archlinux.org/archlinux/bugbuddy/-/work_items/1 [2] https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/338 [3] https://bumpbuddy.archlinux.org [4] https://bumpbuddy.archlinux.org/data.json -- Regards, Robin Candau / Antiz
OpenPGP_0xFDC3040B92ACA748.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
