On Thu, Oct 16, 2008 at 5:46 PM, Loui <louipc.ist@gmail.com> wrote:
On Thu, Oct 16, 2008 at 11:52:45PM +0200, Ronald van Haren wrote:
On Thu, Oct 16, 2008 at 11:04 PM, Daenyth Blank <daenyth+arch@gmail.com> wrote:
Not much we can do about this in AUR. I wonder why users are not supposed to file bug reports for outdated packages. I think it would actually help people gauge how important certain packages are.
It would: - be globally readable and writable. - allow users to post updated PKGBUILDs. - allow developers to provide comments on why packages are out of date - help ensure that out of date notices don't get lost in the maintainer's mountain of other email, or wherever they go. I am in favor of this. Or maybe instead of having people report it in that manner, have archweb automatically file a bug report when a user marks it out of date.
why? The maintainer gets automatically notified when a package is flagged out of date. If no maintainer is set a message is send to the arch-dev mailing list. IMHO it would be really annoying to clutter the bugtracker with such reports.
Putting them in the bug tracker could help cover the seemingly common occurrance of that message getting lost in a pile of other mail.
They rarely get lost. We also have a list of packages that we see every time we log into the dev backend.
Sure the bug reports can also be pushed aside or ignored, but at least they can be searched, discussed, and tracked in a more centralised and convenient fashion.
I don't think discussion is the issue here. The issue is manpower and desire and real life and all that fun stuff. If instead of people saying "OMG out of date" they would send us successful testing results from their side. Regardless, this is the aur list, and we shouldn't be talking about this. Suffice to say that if a user has a "faster update" to a package, it's a better idea to mail it along to the official maintainer instead of putting it in the AUR