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#59943 - Include the last update time in https://aur.archlinux.org/requests

Attached to Project: AUR web interface
Opened by Chih-Hsuan Yen (yan12125) - Wednesday, 05 September 2018, 13:52 GMT
Task Type Feature Request
Category Backend
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.7.0
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Many orphan requests are handled within 14 days. Either the request issuer is added as a co-maintainer or the original maintainer updates the package. The last update time helps on finding out such cases.
This task depends upon

2018-09-07: A task closure has been requested. Reason for request: I think Eli is right. This feature brings little benefit and can be closed with WONTFIX.
Comment by Eli Schwartz (eschwartz) - Wednesday, 05 September 2018, 16:29 GMT
I'm not sure how valuable this is, since e.g. I always check the page by hand regardless to read the recent comments. In some cases, just looking at the last update time is not good enough and may lead to incorrectly rejecting a request.

Consider the case where an orphan request is created, due to the maintainer not doing a good job, and then the maintainer updates the package but does not actually fix it.
(In pathological cases, the maintainer is actually using a bot to update, and the bot is itself the problem which breaks the PKGBUILD and which the requester wishes to fix.)

Loading...