[arch-general] packager sometimes missing in arch's web interface

[Adam Vogt]

* On Monday, August 11 2008, Jan de Groot wrote:

>Our web frontend works with 2 things when it comes to assigning
>maintainers:
>- the repository it is in
>- the architecture of the package
>
>So when I package glib2, I add two packages, one for i686 and one for
>x86_64. Because of our signoff policy, I will have to do updates to
>testing, creating another set of packages.
>The testing packages are created and deleted everytime they're moved to
>the core or extra repository. It makes no sense to adopt these packages
>everytime. If you flag a testing package, nobody gets notified. Flag the
>extra/core package instead.

Thanks for clearing that up.

In the case of bitlbee, the package in [extra] appears orphaned. If that's 
not the case, wouldn't it be better if the web interface determined 
maintainership from the pkgbuild itself?