On Mon, Jan 31, 2022 at 09:25:41PM +0100, Jelle van der Waa via arch-dev-public wrote:
We’ve wanted automatic flagging packages out of date for a while and currently every packager has to come up with it’s own solution. Let’s solve this centralized by integrating nvchecker into archweb.
nvchecker is a program which can monitor versions upstreams, github, pypi, haskell, crates.io or custom provided for updates. Various packagers already use nvchecker in some form. [1]
The idea is that every package in svn has a .NVCHECKER file (linux/trunk/.NVCHECKER) which contains the package specific settings i.e.:
[go] source = “github” github = “golang/go” prefix = “go” use_max_tag = true exclude_regex = “.(release|weekly|rc|alpha|beta).”
Archweb will have a systemd service which regularly goes through the pkgbases, check if the file exists, runs nvchecker and if required flags the package out of date automatically.
For Github sources a token is required so we can do 5000 requests per hour, Arch Linux already has a Github account so this is no issue.
Felix already has a script which converts a subset of packages to nvchecker. This could be extended to apply to more packages. [2]
The question is if anyone object to checking these small .NVCHECKER files into our svn repository. If there are no real objections, I'll start implementing this functionality into archweb in two weeks.
[1] https://nvchecker.readthedocs.io/en/latest/usage.html#check-crates-io [2] https://github.com/felixonmars/archlinux-futils/blob/master/arch-to-nvchecke...
Greetings,
Jelle van der Waa
Using nvchecker for a couple of years now not only for Arch packages, but also for a lot of IoT devices, hobby equipment and more. Pretty happy with nvchecker-notify :) An integration into Archweb would be awesome. Do we remove the ability to mark packages out-of-date manually then? It seems to me that a broken nvchecker config in a certain repo is more a bug than an ood package after such an addition. Best regards, Frederik