Eric Bélanger wrote:
On Wed, Jul 22, 2009 at 7:32 PM, Daniel J
Griffiths<[email protected]> wrote:
Ronuk Raval wrote:
On July 22, 2009 06:58:31 pm Daniel J Griffiths wrote:
Community has a bugtracker, which should (ideally) be used to notify us
if a package is out of date or broken.
Right now the Flyspray for [community] has a rather clear notice that
says:
"Do NOT report bugs when a package is just outdated, or it is in
Unsupported. Use the 'flag out of date' link on the package page, or the
Mailing List.
REPEAT: Do NOT report bugs for outdated packages!".
Shouldn't that notice be updated to reflect current changes. What would be
the recommended way of notifying TU's of an outdated package (mailing list
or bugtracker?).
Personal opinion... Update the bugtracker to reflect the lack of a 'flag out
of date' option for community anymore, use bugtracker for anything related
to community packages. The TUs as a whole need to use the bugtracker more
anyway. (Wonder, back me up here)
The 'flag out of date' option for community still works (unless it was
disabled). Users just need to check the package version in the repo
instead of the version displayed in AUR to know if a package is
out-of-date or not.
It works only the first time as updating does not reset it...
Allan
