On Fri, 29 Dec 2017 23:28:19 -0600 Doug Newgard via aur-general said:

On Sat, 30 Dec 2017 12:40:29 +0900 Carsten Haitzler wrote:

...

https://aur.archlinux.org/packages/rage-git

Is gone but repo is alive: git clone ssh://aur@aur.archlinux.org/rage-git.git

Works. As does: git clone https://aur.archlinux.org/rage-git.git

And I see no removal request on aur-requests: https://lists.archlinux.org/pipermail/aur-requests/

(downloaded full mbox archive): $ grep rage-git aur-requests.mbox sickrage-git [3]: [3] https://aur.archlinux.org/pkgbase/sickrage-git/

No rage-git.

What happened? It's unmaintained because it doesn't build (since July 20 when I removed the autotools based build upstream and moved to meson as the build system). I put in a comment on the pkg page that the AUR pkg build was broken ages ago and offered to take over maintenance in the package comments but got no reply and now the package page at least has disappeared.

How about restoring it? I can also take over maintenance as I have kept a git clone of rage-git and moved it to meson locally (have not pushed). I also now maintain efl-git and enlightenment-git too (rage-git depends on efl).

A whole lot of orphans with no votes got deleted. When a package is deleted from the AUR, the git repo remains which is what you're seeing.

oh - it was a lack of votes?

As for restoring it, pushing a new commit to the repo would work. It can also be done over ssh, but you're going to need to fix it up anyway.

ok. i assume this is an ok to take over maintenance? -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - raster@rasterman.com

On Sat, 30 Dec 2017 09:36:16 -0600 Doug Newgard said:

On Sat, 30 Dec 2017 14:33:41 +0900 Carsten Haitzler wrote:

...

On Fri, 29 Dec 2017 23:28:19 -0600 Doug Newgard via aur-general said:

...

A whole lot of orphans with no votes got deleted. When a package is deleted from the AUR, the git repo remains which is what you're seeing.

oh - it was a lack of votes?

Lack of votes plus being an orphan and broken. All of which are strong indicators of lack of interest.

well. fixed and builds now. pushed fixes.

...

...

As for restoring it, pushing a new commit to the repo would work. It can also be done over ssh, but you're going to need to fix it up anyway.

ok. i assume this is an ok to take over maintenance?

It appears this had no maintenance since I dropped it. You're definitely safe taking it over.

-- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - raster@rasterman.com