On Sat, 2014-07-05 at 18:29 +0100, Steven Honeyman wrote: > Does anyone else think there is now just one thing missing from the > "request" feature (or a different link)? I keep thinking "this package > is broken" or "this package needs attention" (for reasons other than > being out of date or abandoned), and there isn't a suitable button! > Yes, the maintainer *should* be watching the comments, but that's very > often not the case. > > Currently, I think my only choices are: > 1. Flag as "to be orphaned" (even though I know the maintainer is still > active) > 2. Flag as "out of date" (even though it isn't) > > Examples might include: VCS packages that no longer build properly; or > PKGBUILDs that do something unintentional (copy a file to the wrong > directory, etc); or packages that don't build anymore because of a > changed dependency. > > Just wondered if those would be considered reasons for flagging as > "out of date", or if anyone agrees this would be useful to have?
How about adding a "needs attention" checkbox when submitting a comment that, when checked, would email the maintainer and raise an "attention requested" flag on the package display page? The maintainer could check an "AR reset" checkbox when submitting his/her own comment, which would clear the flag. Carl > > On 5 July 2014 14:23, Lukas Fleischer <archli...@cryptocrack.de> wrote: > > Hello, > > > > I am pleased to announce that AUR 3.3.0 has just been released. The > > official AUR setup [1] has already been updated. > > > > This release includes several improvements to the package request > > feature and a couple of bug fixes. > > > > For a comprehensive list of changes, please consult the Git log [2]. As > > usual, bugs should be reported to the AUR bug tracker [3]. > > > > [1] https://aur.archlinux.org/ > > [2] https://projects.archlinux.org/aur.git/log/?id=v3.3.0 > > [3] https://bugs.archlinux.org/index.php?project=2