[arch-dev-public] [RFC] archweb nvchecker integration

Levente Polyak anthraxx at archlinux.org
Sun Feb 6 17:25:21 UTC 2022


On 2/6/22 14:25, David Runge via arch-dev-public wrote:
> On 2022-01-31 21:25:41 (+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.
> 
> One thing that I have been wondering about is the following:
> How do you plan to integrate this with existing packager workflows?
> When I look at my own:
> I periodically (at least daily) check for updates to upstreams using
> nvchecker in a multi-repository (i.e. multiple nvchecker config files)
> setup and am usually aware of changes quite fast.
> 
> If this is integrated into the website, are people supposed to only rely
> on the website, or would there be a way to query the status of a
> packager's packages via some CLI tooling (as that is what I am relying
> on currently and which is easily accessible from multiple locations)?
> 


We have a lot of info exposed in archweb API that some cli scripts can 
pull and display. This would certainly make a lot of sense to expose as 
well :)

cheers,
Levente
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-dev-public/attachments/20220206/7bf26af9/attachment.sig>


More information about the arch-dev-public mailing list