[aur-requests] [PRQ#16196] Deletion Request for lib32-mesa-aco-git
yurikoles [1] filed a deletion request for lib32-mesa-aco-git [2]: ACO is merged upstream https://gitlab.freedesktop.org/mesa/mesa/tree/93c8ebfa780ebd1495095e79473188... [1] https://aur.archlinux.org/account/yurikoles/ [2] https://aur.archlinux.org/pkgbase/lib32-mesa-aco-git/
Request #16196 has been accepted by polyzen [1]. [1] https://aur.archlinux.org/account/polyzen/
On 10/6/19 9:28 AM, notify@aur.archlinux.org wrote:
Request #16196 has been accepted by polyzen [1].
As was explained on the package, the first bits of ACO reaching upstream mesa in no way means the ACO development branch is not relevant - much like mesa being released doesn't mean a mesa-git package is irrelevant. This was explained in the package comments, but apparently re-opening deletion requests until accepted is what it takes. What is the right way to re-upload this package? Am I going to get frowny-faces for just reinstating it? :( - Neph
On 10/6/19 1:20 PM, Nephyrin Zey wrote:
On 10/6/19 9:28 AM, notify@aur.archlinux.org wrote:
Request #16196 has been accepted by polyzen [1].
As was explained on the package, the first bits of ACO reaching upstream mesa in no way means the ACO development branch is not relevant - much like mesa being released doesn't mean a mesa-git package is irrelevant. This was explained in the package comments, but apparently re-opening deletion requests until accepted is what it takes.
What is the right way to re-upload this package? Am I going to get frowny-faces for just reinstating it?
It was incorrectly deleted, so just reupload it. I apologize that the comments and votes were lost. :( -- Eli Schwartz Bug Wrangler and Trusted User
participants (3)
-
Eli Schwartz
-
Nephyrin Zey
-
notify＠aur.archlinux.org