Hi,

On 10/13/17 at 10:35am, Sebastian Lau via arch-general wrote:
> On 13.10.2017 09:01, Leonidas Spyropoulos via arch-general wrote:
> > On 13/10/17, Ralf Mardorf wrote:
> >> On Fri, 13 Oct 2017 01:02:54 +0200, Rob Til Freedmen wrote:
> >>> ... for these long outdated packages?
> >>>
> >>> https://www.archlinux.org/packages/?sort=-last_update&q=&maintainer=schiv&flagged=Flagged
> >>>
> >>> https://www.archlinux.org/packages/?sort=-last_update&q=&maintainer=speps&flagged=Flagged
> > Hello,

As a Dev/TU I refrain from updating these outdated flagged packages, since I
have no idea how to test and check if it works. The packages are a quite
specific nice.

> > I can adopt few if they drop to AUR (of if I get sponsor to apply for a
> > TU).

It would be nice, if someone with audio packaging experience and real life user
would join the team.

<snip>
> I would do the same for a few of that listed packages under the same
> circumstances (a drop to AUR or finding a sponsor to apply for a TU). My
> current packages in AUR are listed here:
> https://aur.archlinux.org/packages/?O=0&SeB=m&K=nullptr_t&outdated=&SB=n&SO=a&PP=50&do_Search=Go
> .
> 
> If I would get a sponsor for applying as a TU, I would like to migrate
> plymouth (no AUR dependencies) to [community] or [extra], when current
> issues are patched. It is widely used and got a recent update from
> upstream (even if I think, the next update from upstream will take a
> while, most of my releases address community issues).

A Tu can't access [extra] btw.

> Also, I'd like to have an audio mailing list (wether official or not)
> for discussion on that audio packages.

You're free to setup one or extend the wiki :-)

I would advice you both to find a TU to sponsor you!

-- 
Jelle van der Waa

Attachment: signature.asc
Description: PGP signature

Reply via email to