On 09/30/2016 03:22 PM, Yassine Imounachen via aur-general wrote:
> OK what I did really mean is how to update it
Let's try that again.
> the rules for submitting a deleted AUR3 package are of course the
> same rules as for submitting a brand-new package.
The old, AUR3 version will give you a
On Fri, Sep 30, 2016 at 9:22 PM, Yassine Imounachen via aur-general
wrote:
> OK what I did really mean is how to update it
>
That is a very unspecific question and in practice the answer may be
two little changes (version numbers) or a total rewrite of the build
and
OK what I did really mean is how to update it
On 30 Sep 2016 6:43 pm, "Yassine Imounachen" wrote:
> Hello,
> What are good practices of re-submitting deleted AUR3 packages? Namely
> 'strongswan-git'.
>
On 09/30/2016 01:43 PM, Yassine Imounachen via aur-general wrote:
> Hello,
> What are good practices of re-submitting deleted AUR3 packages? Namely
> 'strongswan-git'.
>
There are no official good practices, but IMPHO, all packages migrated
from the AUR3 (whether deleted or not) *should* have
On 30.09.2016 19:43, Yassine Imounachen via aur-general wrote:
> Hello,
> What are good practices of re-submitting deleted AUR3 packages? Namely
> 'strongswan-git'.
>
Hello Yassine,
For strongSwan, a git package (even though there existed one once) does
not make sense, because the git master
Hello,
What are good practices of re-submitting deleted AUR3 packages? Namely
'strongswan-git'.
=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 0 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 1 fully signed off package
* 17 packages missing signoffs
* 12 packages older than 14