Re: [arch-dev-public] On the toolchain current status

2022-02-09 Thread Frederik Schwan via arch-dev-public
On Mon, Feb 07, 2022 at 12:26:54PM -0300, Giancarlo Razzolini via arch-dev-public wrote: > Hi All, > > Most of you are aware that our toolchain is currently outdated. We always had > very few people > working on it through the years and I took over once Barth left, because it > was needed. > >

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

2022-02-06 Thread Frederik Schwan via arch-dev-public
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. > >

Re: [arch-dev-public] Packages seeking Maintainers

2022-01-21 Thread Frederik Schwan via arch-dev-public
On Fri, Jan 21, 2022 at 11:32:59AM +0100, Jelle van der Waa via arch-dev-public wrote: > Hello, > > Noticing that I don't really have time and energy to maintain a part of my > packages. I think it's better to disown them and let others take care of > them, the list is: > > chromium-bsu > guetzl

[arch-dev-public] News draft: Archlinux mailing list id changes

2020-12-29 Thread Frederik Schwan via arch-dev-public
Hey all, below is the news item I would like to post. We had to change some mailing list ids which used to be @archlinux.org to @lists.archlinux.org to mitigate anti spam issues. Sending to @archlinux.org still works as usual though. ``` Due to issues with our anti spam measures, we had to migrat