On Fri, Jan 15, 2010 at 02:06:09PM -0600, Matt Domsch wrote:
On Fri, Jan 15, 2010 at 09:01:20PM +0100, Till Maas wrote:
What about the other packages of these maintainers? E.g. in the recordmydesktop case, there were four bugs open with working patches attached for that package. I did not yet check the other packages, but in case a packager does not have the time anymore to maintain one package from this list, why do we assume that he has the time to maintain the others? So before the mass orphaning is done, it would be nice to do it in a way that allows to at least easily spot which maintainers owned the packages before the orphage, so non responsive maintainers can be found easier. Or tell all maintainers in question and orphan all their packages. But the current solution seems to be only half-baked.
I made sure that no one who fixed a package was actually the package owner.
But what about the other packages by these maintainers that do not fail to build but are probably as unmaintained as the packages that fail to build?
perl-SVN-Mirror iburrell (fixed by Till Maas; spot says kill it) perl-SVN-Simple iburrell
There is a minor error: I fixed the -Simple package with a patch submitted in the upstream bugtracker iirc 7 days ago. But I also noticed that the -Mirror package was removed from debian.
But what about the other packages from this maintainer? He maintains around 36 other packages: https://admin.fedoraproject.org/pkgdb/users/packages/iburrell
E.g. the jigdo packages also has 4 bug. I looked at two an both did not receive any comments from the maintainer: https://bugzilla.redhat.com/show_bug.cgi?id=426847 https://bugzilla.redhat.com/show_bug.cgi?id=503833
Therefore the non responsive maintainer procedure, i.e. orphaning all packages from the affected maintainers, seems to me to be more appropriate.
Regards Till