[aur-general] Package search for community repo

Roman Kyrylych roman.kyrylych at gmail.com
Thu Jul 23 11:50:23 EDT 2009

On Thu, Jul 23, 2009 at 02:32, Daniel J Griffiths<ghost1227 at archlinux.us> 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)

This is absolutely no-go because this way bugtracker will be flooded
with out-of date messages
that have no useful information.

+1 for complete merging community into main website (with limited
permissions for TUs)
and removing community-related part of AUR
(with a notice that if there was some important info in comments - it should be
reported as bugs or it will be lost)
(if there would be possibility to limit permissions per category then
I would love
to merge Community Packages bugtracker project as well,
but that's not an option at this time).

Roman Kyrylych (Роман Кирилич)

More information about the aur-general mailing list