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

2022-01-21 Thread Caleb Maclennan via arch-dev-public
I'll pitch in with: * podofo * rdesktop * leptonica As always I prefer to have at least one co-maintainer so nothing bottlenecks during my periods of unavailability, so if you're interested go for it. I would also do tidy if it dropped to [community], but my use isn't heavy either so if som

[arch-dev-public] Update to asciidoc 10.x

2022-01-17 Thread Caleb Maclennan via arch-dev-public
The update from asciidoc 9.x to 10.x has been a long standing fiasco. The initial release had quite a few bugs that completely blocked our usage and (as is the case for many Python projects) packaging has gotten harder as upstream tooling is less distro friendly. After an upstream minor releas

Re: [arch-dev-public] namcap maintainership

2021-08-28 Thread Caleb Maclennan via arch-dev-public
On 2021-08-21 22:24, Jelle van der Waa via arch-dev-public wrote: I would love to see someone from our team pick up namcap maintainership, [...] Is there any progress on this decision? So far we have 4 of us that are interested in maintaining and/or contributing to the project. But, as I unde

Re: [arch-dev-public] Go 1.17 released - to rebuild or not to rebuild

2021-08-21 Thread Caleb Maclennan via arch-dev-public
On 2021-08-17 21:36, Morten Linderud via arch-dev-public wrote: People do not really see the need to rebuild $goWorld when packages a compiled and nothing inherently breaks unless there is a rebuild. We don't do this for GCC, Rust and so on. However I do think it's nice to group up these ecosys

Re: [arch-dev-public] namcap maintainership

2021-08-21 Thread Caleb Maclennan via arch-dev-public
On 2021-08-21 22:24, Jelle van der Waa via arch-dev-public wrote: I would love to see someone from our team pick up namcap maintainership, take a look at all the pending patches, bugs on the tracker and keep it in shape. Is anyone interested in potentially picking up this task? I may be interes