Re: [aur-general] pisg-fixed

2017-11-20 Thread Christos Nouskas
On 20 November 2017 at 17:40, Jeremy Audet via aur-general < aur-general@archlinux.org> wrote: > > > > well, i beg your pardon if i made the assumption that TU and the entire > > AUR structure was smart enough to understand a merge request of a > > differently-owned package as an orphan request

Re: [aur-general] pisg-fixed

2017-11-20 Thread Jeremy Audet via aur-general
> > well, i beg your pardon if i made the assumption that TU and the entire > AUR structure was smart enough to understand a merge request of a > differently-owned package as an orphan request for a clearly fixed package. > > i humbly beseech myself towards your graces and fall upon my sword for >

Re: [aur-general] pisg-fixed

2017-11-20 Thread Morten Linderud
On Mon, Nov 20, 2017 at 10:06:13AM -0500, brent s. wrote: > well, i beg your pardon if i made the assumption that TU and the entire > AUR structure was smart enough to understand a merge request of a > differently-owned package as an orphan request for a clearly fixed package. > Yes, we

Re: [aur-general] pisg-fixed

2017-11-20 Thread Eli Schwartz
On 11/20/2017 09:56 AM, Eli Schwartz wrote: > Since merging only merges votes and comments, I cannot fathom in any > way, shape, or form why you thought there was any functional utility in > creating a new pkgbase, then deleting it and merging nonexistent votes > and comments into the original

Re: [aur-general] pisg-fixed

2017-11-20 Thread brent s.
On 11/20/2017 09:56 AM, Eli Schwartz wrote: > On 11/20/2017 09:41 AM, brent s. wrote: >> "Merge requests are for when one package is replacing another one. Users >> still have to resubmit a package under a new name and may request >> merging of the old version's comments and votes. This has

Re: [aur-general] pisg-fixed

2017-11-20 Thread Eli Schwartz
On 11/20/2017 09:41 AM, brent s. wrote: > "Merge requests are for when one package is replacing another one. Users > still have to resubmit a package under a new name and may request > merging of the old version's comments and votes. This has nothing to do > with 'git merge' and is not similar to

Re: [aur-general] pisg-fixed

2017-11-20 Thread brent s.
On 11/20/2017 09:18 AM, Doug Newgard wrote: > On Mon, 20 Nov 2017 07:58:47 -0500 > "brent s." wrote: > >> TU Alad has deleted this package: >> >> """ >> Request #9816 has been rejected by Alad [1]: >> >> File an orphan request, duplicate packages with meaningless "fixed" >>

Re: [aur-general] pisg-fixed

2017-11-20 Thread Doug Newgard
On Mon, 20 Nov 2017 07:58:47 -0500 "brent s." wrote: > TU Alad has deleted this package: > > """ > Request #9816 has been rejected by Alad [1]: > > File an orphan request, duplicate packages with meaningless "fixed" > suffixes are not acceptable. > > [1]

Re: [aur-general] pisg-fixed

2017-11-20 Thread Morten Linderud
On Mon, Nov 20, 2017 at 07:58:47AM -0500, brent s. wrote: > IGNORING the entire reason for creating the package - to merge the fixed > version to the existing package, the request for which was done minutes > after the package was created. > > What the hell? > Yes, creating new packages to

[aur-general] pisg-fixed

2017-11-20 Thread brent s.
TU Alad has deleted this package: """ Request #9816 has been rejected by Alad [1]: File an orphan request, duplicate packages with meaningless "fixed" suffixes are not acceptable. [1] https://aur.archlinux.org/account/Alad/ """ IGNORING the entire reason for creating the package - to merge the