On 06/23/2011 08:53 PM, Kevin A. McGrail wrote:
I was going to fix the Mail::SpamAssassin unauthorized release issue
this morning, but looking at the CPAN Search page, it looks like it
isn't a problem anymore.
If you have other namespaces where you need permissions, just give us
the list and who the primary maintainer is.
Thanks brian. We were able to track down the various people who had the
permissions.
There is a so-called "mailing list" feature that does something like
allowing multiple people to maintain a particular set of modules
(==permissions). It basically is a separate virtual user that a set of
real users can "sudo" to, if I remember correctly. That still requires
new uploaders to check for any new namespaces and assign maintenance to
the mailing list user *once*. Others may be able to explain this better,
but for some reason, this isn't a solution that's preferred by the
admins, I think. I keep forgetting why :(
This recent pause indexer unauthorized module fiasco was quite a hoop to
jump through. Assume it was added recently?
No, it's been that way "forever".
On a related note, is it possible CPAN can lock Mail::SpamAssassin::* to
the SA Project and treat it based on permissions for Mail::SpamAssassin
rather than each individual module?
No, that's not possible. Our tools can't do that. (The PAUSE code is
public, though.)
Cheers,
Steffen
