You are not logged in.
I'd like to submit an updated package to the AUR, that has (seemingly) been abandoned by its maintainer. It's not a widely used package, so it hasn't been flagged as out of date for too terribly long (few weeks), but it's back at version 0.23, while 1.6 is currently shipping. Not talking days or weeks out of date, but, months, which is a crippling of the package...
The existing package is also broken, in that it requires additional deps to compile, that are not listed as deps in the package manifest.
I'm fairly new to the Arch community, and, would be willing to maintain this package myself going forward, unless the current maintainer wants to keep it (and is willing to keep it up to date). So what's the procedure in situations like this? I didn't see anything in the FAQ, and, when I attempt to upload the package I've created (with fixed deps and bumped version/code), it says I can't overwrite an existing package (which, is understandable).
What say you, Arch folk?
Last edited by phaseburn (2013-11-21 00:35:35)
Offline
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Procedure is outlined in the Wiki:
Offline
Moving to AUR Issues...
Offline
Thanks, I swear I read that and just didn't see it.
I emailed my source package to the maintainer, and hope he/she'll update it. If not, I'll begin the request tree to have it orphaned.
Offline