AUR web interface

**This is the bug tracker for the AUR web interface.**

Use this tracker to report bugs or make feature requests regarding the behaviour or implementation of the AUR software.
Please read the Reporting Bug Guidelines before filing a new task.
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

- Please report bugs related to Arch Linux official packages here: http://bugs.archlinux.org/index.php?project=1
- Please report bugs for [community] packages here: http://bugs.archlinux.org/index.php?project=5
- For any packages in the AUR contact the maintainer or leave a comment on the package's detail page.

Source Code:
https://projects.archlinux.org/aurweb.git/
Tasklist

FS#16831 - Add 'Flag for deletion' functionality

Attached to Project: AUR web interface
Opened by xduugu (xduugu) - Sunday, 25 October 2009, 00:03 GMT
Last edited by Lukas Fleischer (lfleischer) - Tuesday, 01 July 2014, 20:02 GMT
Task Type Feature Request
Category Backend
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Medium
Priority Normal
Reported Version 1.5.6.4
Due in Version 3.2.0
Due Date Undecided
Percent Complete 100%
Votes 45
Private No

Details

Currently, there are many obsolet and/or broken packages in the AUR, and when a package should get removed, you have to write a mail to aur-general. This procedure works, but is in my opinion too cumbersome, and therefore, only few request package deletions.

It would be nice if it were possible to flag a package for deletion on its web page. I have another button in mind and when you click it, you have to enter a short statement (> 15 characters or so) explaining why do you think this package should get removed. After this, either a mail is send to the mailing list, e.g.

--------------
xy[1] requests the deletion of the package PKGNAME[2] for the following reasons:
'Cause it stinks

[1] URL to user page
[2] URL to package page
-------------

or it is only stored in the database and accessable for TUs.
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Tuesday, 01 July 2014, 20:02 GMT
Reason for closing:  Implemented
Additional comments about closing:  Implemented in 3.2.0.
Comment by Gavin Bisesi (Daenyth) - Friday, 13 November 2009, 19:24 GMT
I like this. Would cut down on a lot of hassle. There are tons of outdated packages that can be removed, but that aren't watched by anyone.
Comment by Anish Bhatt (anish) - Tuesday, 17 November 2009, 23:44 GMT
agreed
Comment by Laszlo Papp (djszapi) - Saturday, 19 December 2009, 18:53 GMT
* The original maintainer of the package could follow it with a notification.
* Some Maintainer/Contributor doesn't know about mailing list, and no need to know anymore with this implementation, he/she can focus only for AUR site.
* It would be similar situation like on bug tracker 'Closure Request'
* It's easier to click and write a short message in place
* It could just auto-send mail to the mailing list, the list isn't so high-traffic that that would be a problem
* It could be an identifying message in the mail subject e.g., and the subscribed users could filter the automated notices into a folder, if they would like to do it.
Comment by Alexsandr Pavlov (kidoz) - Saturday, 19 December 2009, 19:31 GMT
Agree. But it can also add a button to pick up a package? Also with an explanation.
Comment by Andrea Scarpino (BaSh) - Sunday, 20 December 2009, 14:44 GMT
This morning I worked on this, but I don't like the idea to add a second page that asks for the motivation...I am thinking about another implementation of this cause we need to know the motivation.

@ kidoz
In my implementation that button exists, but only TUs and DEVs can ignore the deletion request.
Comment by vnoel (kaouete) - Sunday, 17 October 2010, 13:15 GMT
Hi, any news on that? :)
Comment by Marcel Korpel (Marcel-) - Monday, 24 December 2012, 16:27 GMT
@BaSh: What about an extra dialog popping up with a text box (using JavaScript, with a fallback to a second page if JavaScript is disabled)?

Also, I think a message should be (B)CC'ed to the maintainer, in case (s)he doesn't follow the mailing list.
Comment by (Det) - Monday, 08 April 2013, 23:02 GMT
The dialog is good. Also, the thread could be linked to the package page as well, so you don't need to actually start looking for it.
Comment by Lukas Fleischer (lfleischer) - Wednesday, 18 June 2014, 22:33 GMT
I am going to implement this as follows:

* Users will be able to flag a package using the package actions box. They can enter a description on a second page (I don't think it is a bad idea to implement it like that).
* Filing a requests automatically results in an email to aur-general and to the maintainer.
* TUs will be able to view a list of pending requests.
* Requests will be marked if they are either newer than 14 days or if there is some discussion on aur-general (the AUR will watch the ML for that purpose).
* TUs have the ability to accept (which automatically opens the deletion dialog) or reject a request.

Loading...