The requests queue is getting pretty filled with requests for packages that quite clearly have been abandoned with no chance of them ever becoming useful. It can be pretty exhausting to keep up with that queue!
In particular, there's a lot of "low-hanging fruit" packages that can be pruned from the AUR: Orphaned, 0 votes, last updated years ago packages are hardly worth keeping around, are they?
Has such a conversation popped up before? I didn't find anything in the archives past the patch by Lukas enabling automatic orphaning of an OOD package after 180 days. [1]
If automatically deleting packages on a schedule isn't welcome, would it make sense to at least explore a patch wherein a deletion request for e.g. an orphaned package/<10 votes/last updated >=2 years ago is automatically accepted?
I can recall many times NetSysFire talking about how hard maintaining wiki pages could be when there isn't a deletion request for an AUR package in #archlinux-aur. I'm not sure how they can handle this automatic deletion of packages without a request for it, maybe a list of automatically deleted packages suffice? Best Regards, Amin Vakil
The requests queue is getting pretty filled with requests for packages that quite clearly have been abandoned with no chance of them ever becoming useful. It can be pretty exhausting to keep up with that queue!
In particular, there's a lot of "low-hanging fruit" packages that can be pruned from the AUR: Orphaned, 0 votes, last updated years ago packages are hardly worth keeping around, are they?
Has such a conversation popped up before? I didn't find anything in the archives past the patch by Lukas enabling automatic orphaning of an OOD package after 180 days. [1]
If automatically deleting packages on a schedule isn't welcome, would it make sense to at least explore a patch wherein a deletion request for e.g. an orphaned package/<10 votes/last updated >=2 years ago is automatically accepted?
I can recall many times NetSysFire talking about how hard maintaining wiki pages could be when there isn't a deletion request for an AUR package in #archlinux-aur. I'm not sure how they can handle this automatic deletion of packages without a request for it, maybe a list of automatically deleted packages suffice? Best Regards, Amin Vakil --- Oops, my previous message had wrong subject.
On Sat, Dec 11, 2021 at 03:42:17PM +0330, Amin Vakil via aur-dev wrote:
I can recall many times NetSysFire talking about how hard maintaining wiki pages could be when there isn't a deletion request for an AUR package in #archlinux-aur.
I'm not sure how they can handle this automatic deletion of packages without a request for it, maybe a list of automatically deleted packages suffice?
Best Regards, Amin Vakil
:) Thanks for keeping a look out. Indeed, this is already changed in the "next-gen" aurweb. When released, __all__ package deletions (and merges) will either accept and close pending requests about them or autogenerate a request and send an accepted closure notification to the aur-requests ML. We'll keep with this flow when deleting packages permanently (hopefully). In addition, they are also logged out to the ASGI server now, so even without requests, we have better tracking of what's going on. -- Kevin Morris Software Developer Identities: - kevr @ Libera
On 2021-12-11 12:33 -0800 Kevin Morris via aur-dev wrote:
On Sat, Dec 11, 2021 at 03:42:17PM +0330, Amin Vakil via aur-dev wrote:
I can recall many times NetSysFire talking about how hard maintaining wiki pages could be when there isn't a deletion request for an AUR package in #archlinux-aur.
I'm not sure how they can handle this automatic deletion of packages without a request for it, maybe a list of automatically deleted packages suffice?
Best Regards, Amin Vakil
:) Thanks for keeping a look out. Indeed, this is already changed in the "next-gen" aurweb. When released, __all__ package deletions (and merges) will either accept and close pending requests about them or autogenerate a request and send an accepted closure notification to the aur-requests ML. We'll keep with this flow when deleting packages permanently (hopefully).
In addition, they are also logged out to the ASGI server now, so even without requests, we have better tracking of what's going on.
-- Kevin Morris Software Developer
For wiki maintenance, would it be possible to include hooks that flag pages that link to the deleted packages? If the deletions are listed via an API, then a timer on the wiki server could periodically scan for affected pages and notify the wiki maintainers. Just a thought. Regards, Xyne
On Sun, Dec 12, 2021 at 12:28:02AM +0100, Xyne via aur-dev wrote:
For wiki maintenance, would it be possible to include hooks that flag pages that link to the deleted packages? If the deletions are listed via an API, then a timer on the wiki server could periodically scan for affected pages and notify the wiki maintainers.
This sounds like a great idea. However, I think we should split this off into it's own kind of feature task. As a heads up, for any features that you guys think of, it would best be tracked if you could produce a Feature issue for them on https://gitlab.archlinux.org/archlinux/aurweb. This way, it's a lot simpler to organize these threads into tasks over time. -- Kevin Morris Software Developer Identities: - kevr @ Libera
On 2021-12-12 11:59, Kevin Morris via aur-dev wrote:
On Sun, Dec 12, 2021 at 12:28:02AM +0100, Xyne via aur-dev wrote:
For wiki maintenance, would it be possible to include hooks that flag pages that link to the deleted packages? If the deletions are listed via an API, then a timer on the wiki server could periodically scan for affected pages and notify the wiki maintainers.
This sounds like a great idea. However, I think we should split this off into it's own kind of feature task.
As a heads up, for any features that you guys think of, it would best be tracked if you could produce a Feature issue for them on https://gitlab.archlinux.org/archlinux/aurweb. This way, it's a lot simpler to organize these threads into tasks over time.
Indeed. My purpose on bringing this up on the ML was to first determine what would even be desirable before opening tickets. I've created a discovery ticket over here: https://gitlab.archlinux.org/archlinux/aurweb/-/issues/211
participants (4)
-
Amin Vakil
-
Brett Cornwall
-
Kevin Morris
-
Xyne