Maintainer seems inactive, how to take over? (solved)

ReaphSharc · 2007-11-20 10:59:20

I'm a big fan of atop and when I was still using Gentoo, I notified the devs there when a new version was available so they could update portage (submitted it through the bugtracker). To that end, the guy that writes and maintains atop sends me an email whenever a new version is released.

Now that I've switched to Arch recently, I noticed atop is in AUR, but out of date and has been for months (version 1.19 in AUR, 1.22 released today). When I did notice this a few weeks ago, I added a comment in AUR, telling the maintainer I would love to take over if he'd have no time (or interest) in maintaining it. I also send him an email with the same (polite) request. No response to this date.

I've created a working PKGBUILD file for atop 1.22, but since I'm not the maintainer and the maintainer hasn't orphaned the package, I can't upload it.

What is the correct procedure in AUR to 'take over' maintenance of the package? I want to go through the proper channels, but have not discovered in AUR, the wiki or the forums what those channels are.

Last edited by ReaphSharc (2007-11-20 12:17:40)

hdoria · 2007-11-20 11:29:33

You can email the maintainer and ask him the package. You said that you already did this. How long ago?

If you got no response in a few days, you can ask a TU to orphan the package for you. I could do that. Just let me know if you email the maintainer recently or some days already passed.

ReaphSharc · 2007-11-20 11:33:44

I emailed the maintainer on the 5th of november.

hdoria · 2007-11-20 11:53:44

atop orphaned!

ReaphSharc · 2007-11-20 12:14:06

Adopted and updated. Thanks.

And if anyone would like to test if it will compile and run on 64-bit architecture, feel free to let me know. :-)

[vEX] · 2007-11-20 15:04:34

Builds, installs and seems to work fine for me (only ran atop, didn't set up any deamons or such).

ReaphSharc · 2007-11-20 15:45:49

I'll add 64 bits to the PKGBUILD file tomorrow. If it'll run I assume the rest will too. Thanks for testing it for me!

I'm feeling more and more at home here with the Arch 'family'

nogoma · 2007-11-20 16:11:12

ReaphSharc wrote:

I'll add 64 bits to the PKGBUILD file tomorrow. If it'll run I assume the rest will too. Thanks for testing it for me!
I'm feeling more and more at home here with the Arch 'family'

I just built this for 64-bit, works no problem. Thanks for bringing this nifty tool to the spotlight.

ReaphSharc · 2007-11-20 18:01:12

Anytime. Don't forget to vote for it

[vEX] · 2007-11-20 18:13:34

ReaphSharc wrote:

I'll add 64 bits to the PKGBUILD file tomorrow. If it'll run I assume the rest will too. Thanks for testing it for me!
I'm feeling more and more at home here with the Arch 'family' :cool:

No problem at all! :-)

Arch Linux

#1 2007-11-20 10:59:20

Maintainer seems inactive, how to take over? (solved)

#2 2007-11-20 11:29:33

Re: Maintainer seems inactive, how to take over? (solved)

#3 2007-11-20 11:33:44

Re: Maintainer seems inactive, how to take over? (solved)

#4 2007-11-20 11:53:44

Re: Maintainer seems inactive, how to take over? (solved)

#5 2007-11-20 12:14:06

Re: Maintainer seems inactive, how to take over? (solved)

#6 2007-11-20 15:04:34

Re: Maintainer seems inactive, how to take over? (solved)

#7 2007-11-20 15:45:49

Re: Maintainer seems inactive, how to take over? (solved)

#8 2007-11-20 16:11:12

Re: Maintainer seems inactive, how to take over? (solved)

#9 2007-11-20 18:01:12

Re: Maintainer seems inactive, how to take over? (solved)

#10 2007-11-20 18:13:34

Re: Maintainer seems inactive, how to take over? (solved)

Board footer