Third-party non-involved user chiming in, but I do not think any sort of
tenure/seniority requirement as mentioned in the final point below would be
a good idea. Something based on recent activity would be better.
On Wed, Nov 28, 2018 at 1:38 AM Bruno Pagani via aur-general <
Le 27/11/2018 à 16:32, Santiago Torres-Arias via aur-general a écrit :
> On Sun, Nov 11, 2018 at 01:29:31PM -0500, Santiago Torres-Arias via
> aur-general wrote:
>> On TU applications, TU participation and package quality:
>> everythign snipped
> I just wanted to bump this thread.
>
> It appears
On Sun, Nov 11, 2018 at 01:29:31PM -0500, Santiago Torres-Arias via aur-general
wrote:
> On TU applications, TU participation and package quality:
> everythign snipped
I just wanted to bump this thread.
It appears to me that bumping the minimum number of TU sponsors + a
buddy system would be
Am 27.11.18 um 15:10 schrieb Bruno Pagani:
Or do I need to upload a new python2-visitor package and file
merge/delete
request for the actual python-visitor split package?
Yes, exactly.
Regards,
Bruno
Ok, thank you.
Michael
Hi,
Le 27/11/2018 à 15:03, Michael Straube via aur-general a écrit :
> Hi All,
>
> I want to remove the python3 package from the python-visitor split
> package [1],
> since it's already in [community].
>
> Will simply changing the pkgbase/pkgname and pushing be enough?
>
> change:
>
Hi All,
I want to remove the python3 package from the python-visitor split package [1],
since it's already in [community].
Will simply changing the pkgbase/pkgname and pushing be enough?
change:
pkgbase=python-visitor
pkgname=('python2-visitor' 'python-visitor')
to:
pkgname=python2-visitor
