On Fri, Jul 19, 2013 at 2:16 PM, Lukas Jirkovsky <l.jirkovsky@gmail.com> wrote:
The problem is that the users don't read. It's happening all the time. I had a package once or twice that couldn't be updated but even though I stated it in the comments people were still marking it out of date. BTW, leaving the package as out of date is a good reminder that the maintainer should check if the problem was fixed every now and then.
It sounds like there are two separate problems here. We need to clarify what the out-of-date marker on the AUR means. Does it mean it is out of date with upstream, or out of date with the newest viable/working version? Perhaps there should be another field added, so we can mark packages as out-of-date-but-cannot-be-upgraded-at-this-time. That way, if a package is marked out-of-date but not cannot-be-upgraded with no activity for a period of time, it should be safe to orphan after sending a warning email. The second problem is that users don't read. Frankly, I don't have a magic solution for this, but could there be a way to limit how many times a user can mark out-of-date or a package can be marked out-of-date until they prove their reading abilities? Actually, a 12 or 24 hour limit between marking and unmarking out of date for everyone except the package owner and TUs on each package seems reasonable, now that I think about it, possibly limited to "hot" packages for which this is a problem.