Re: [arch-dev-public] arch-repo-management walkthrough 2022-02-02 19:00 CET (UTC+01:00)
On 2022-01-31 14:23:10 (+0100), David Runge via arch-dev-public wrote: > given recent topics for build automation and work on internal projects I > would like to announce a code walkthrough for arch-repo-management [1]. > > I would like to give an overview of the scope of the project, its > current features and which features I would like to see implemented > (some of which are still in a discussion phase). > I will try to add a few more tickets beforehand to track open features > and to outline them better. This way I hope that it becomes easier for > interested people to follow up on them. Thanks to everyone who attended and participated! We do have a set of meeting notes for anyone who has not been able to attend and wants to read up on things (video link included): https://md.archlinux.org/NIPYO4ZNSkaTneEajF9G1g?view I will send a follow-up mail for the next meeting to the arch-projects mailing list [1] as it is less limited who can interact there. We will try to do bi-weekly meetings now! :) Best, David [1] https://lists.archlinux.org/listinfo/arch-projects -- https://sleepmap.de signature.asc Description: PGP signature
[arch-dev-public] Bi-weekly arch-repo-management meeting
Hi all, as announced on arch-dev-public, we would like to do bi-weekly meetings for arch-repo-management [1]. I misjudged the (current) use-case for the arch-projects mailing list though and therefore am doing the meeting announcement here. I will send another mail to discuss the current/future scope of the arch-projects mailing list. The next meeting takes place on Jitsi on 2022-02-16 at 19:00 CET (UTC+01:00): https://meet.jit.si/20220216-arch-repo-management An ics file for calendar software is attached to this mail. Best, David [1] https://lists.archlinux.org/pipermail/arch-dev-public/2022-February/030711.html -- https://sleepmap.de BEGIN:VCALENDAR VERSION:2.0 PRODID:-//PIMUTILS.ORG//NONSGML khal / icalendar //EN BEGIN:VTIMEZONE TZID:Europe/Berlin BEGIN:STANDARD DTSTART;VALUE=DATE-TIME:20211031T02 TZNAME:CET TZOFFSETFROM:+0200 TZOFFSETTO:+0100 END:STANDARD BEGIN:DAYLIGHT DTSTART;VALUE=DATE-TIME:20220327T03 TZNAME:CEST TZOFFSETFROM:+0100 TZOFFSETTO:+0200 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT SUMMARY:Arch-repo-management meeting DTSTART;TZID=Europe/Berlin;VALUE=DATE-TIME:20220216T19 DTEND;TZID=Europe/Berlin;VALUE=DATE-TIME:20220216T21 DTSTAMP;VALUE=DATE-TIME:20220202T221607Z UID:B11UUSTZG9UGEUJL5PQ8K1DYGY7647P7X6SL SEQUENCE:0 CATEGORIES: LOCATION:https://meet.jit.si/20220216-arch-repo-management END:VEVENT END:VCALENDAR signature.asc Description: PGP signature
[arch-dev-public] Scope of arch-projects mailing list
Hi all, while trying to use the arch-projects mailing list for an announcement I realized, that it is (probably?) not really supposed to be used for that at the moment. It explicitly states to be used for development discussion and providing patches for dbscripts, devtools, mkinitcpio, namcap, netctl, archweb and pyalpm. It seems that apart from netctl none of the above really make much use of this anymore though when it comes to development, as the projects have pivoted towards merge/pull requests on their respective VCS forges. Unless there are any objections, I propose to * add arch-repo-management and arch-release-promotion to it * change arch-projects to *also* become a general discussion list around the above mentioned Arch Linux projects * extend mailing list "about" section with information on how each project prefers to receive patches (e.g. I do not want to use the mailing list for that, but others may) Rationale: We lack a mailing list that revolves around our internal projects and which can also be used by non "elevated users" (such as Trusted Users and Developers) for more general discussion. Given the very low traffic on the arch-projects mailing list I see no issue with it becoming a per-project discussion list as well (as in our case mailing lists seem to be mainly used for discussion and not so much for development anymore these days). Best, David -- https://sleepmap.de signature.asc Description: PGP signature
Re: [arch-dev-public] Scope of arch-projects mailing list
On 3/2/22 21:53, David Runge via arch-dev-public wrote: Unless there are any objections, I propose to * add arch-repo-management and arch-release-promotion to it * change arch-projects to*also* become a general discussion list around the above mentioned Arch Linux projects What do you mean by general discussion? The list already states it can be used for developmental discussion - anything beyond that is probably off-topic on a technical list. Otherwise changes to the list are fine. A
Re: [arch-dev-public] Scope of arch-projects mailing list
On 2022-02-03 22:07:09 (+1000), Allan McRae via arch-dev-public wrote: > On 3/2/22 21:53, David Runge via arch-dev-public wrote: > > Unless there are any objections, I propose to > > > > * add arch-repo-management and arch-release-promotion to it > > * change arch-projects to*also* become a general discussion list around > >the above mentioned Arch Linux projects > > What do you mean by general discussion? The list already states it > can be used for developmental discussion - anything beyond that is > probably off-topic on a technical list. Hm, maybe what I understand as "development discussion" just seemed too narrow to me. I agree, that that point does not have to be altered and will just extend with "and announcements" or so. > Otherwise changes to the list are fine. Thanks for the feedback! Best, David -- https://sleepmap.de signature.asc Description: PGP signature
Re: [arch-dev-public] [RFC] archweb nvchecker integration
On 22-02-02 21:03, Felix Yan via arch-dev-public wrote: > There is a regex plugin and a htmlparser plugin for this. > > The htmlparser plugin accepts XPath, but if you want to process it further > the regex plugin may just work better. > > Examples for your packages: > > [html-xml-utils] > source = "regex" > url = "https://www.w3.org/Tools/HTML-XML-utils/"; > regex = "html-xml-utils-(.*?).tar.gz" > > [oil] > source = "htmlparser" > url = "https://www.oilshell.org/release/latest/"; > xpath = "//h1/text()" > prefix = "Oil " I am guilty of not reading the documentation. Thank you! :) -- George Rawlinson signature.asc Description: PGP signature
Re: [arch-dev-public] [RFC] archweb nvchecker integration
On 31.01.22 21:25, 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-nvchecker Greetings, Jelle van der Waa I got nothing to add to what the others have said but I just wanted to say that this is awesome and thank you for the effort. :) Sven OpenPGP_signature Description: OpenPGP digital signature
Re: [arch-dev-public] Scope of arch-projects mailing list
On 03.02.22 12:53, David Runge via arch-dev-public wrote: Hi all, while trying to use the arch-projects mailing list for an announcement I realized, that it is (probably?) not really supposed to be used for that at the moment. It explicitly states to be used for development discussion and providing patches for dbscripts, devtools, mkinitcpio, namcap, netctl, archweb and pyalpm. It seems that apart from netctl none of the above really make much use of this anymore though when it comes to development, as the projects have pivoted towards merge/pull requests on their respective VCS forges. Unless there are any objections, I propose to * add arch-repo-management and arch-release-promotion to it Sure. * change arch-projects to *also* become a general discussion list around the above mentioned Arch Linux projects Ok. * extend mailing list "about" section with information on how each project prefers to receive patches (e.g. I do not want to use the mailing list for that, but others may) Yeah that's probably good. Rationale: We lack a mailing list that revolves around our internal projects and which can also be used by non "elevated users" (such as Trusted Users and Developers) for more general discussion. Given the very low traffic on the arch-projects mailing list I see no issue with it becoming a per-project discussion list as well (as in our case mailing lists seem to be mainly used for discussion and not so much for development anymore these days). Best, David I think that makes sense. Go for it! Sven OpenPGP_signature Description: OpenPGP digital signature
