Re: PAUSE permissions conflict on Main package

2016-07-28 Thread Flavio S. Glock
Thanks for looking into this. I'm adding a "no_index" entry for "Main" in v6.pm 2016-07-28 14:08 GMT+02:00 Neil Bowers : > I’ve just made the following changes: > > Scheduled old releases in PARDUS’s author directory for deletion. They’ll > disappear in 3 days. > Dropped FGLOCK’s ownership of the

Re: PAUSE permissions conflict on Main package

2016-07-28 Thread Jaap Karssenberg
Hi Neil, Feel free to do whatever clean up is needed to resolve this conflict. Happy to help, but I can't locate a "Main.pm" in any of the current Zoidberg packages on CPAN, maybe I'm overlooking it? I think this was a mistake on my side in the first place to place "Main" outside of my "Zoidberg"

Re: PAUSE permissions conflict on Main package

2016-07-28 Thread Jaap Karssenberg
Great, thanks! On Thu, Jul 28, 2016 at 12:45 PM Neil Bowers wrote: > Hi Jaap, > > Feel free to do whatever clean up is needed to resolve this conflict. > > > Thanks — I’ll do that later today, and confirm when it’s done. > > Happy to help, but I can't locate a "Main.pm" in any of the current > Z

Re: PAUSE permissions conflict on Main package

2016-07-28 Thread Neil Bowers
I’ve just made the following changes: Scheduled old releases in PARDUS’s author directory for deletion. They’ll disappear in 3 days. Dropped FGLOCK’s ownership of the Main namespace Dropped PARDUS’s co-maint permissions on Main Cheers, Neil

Re: PAUSE permissions conflict on Main package

2016-07-28 Thread Neil Bowers
Hi Jaap, > Feel free to do whatever clean up is needed to resolve this conflict. Thanks — I’ll do that later today, and confirm when it’s done. > Happy to help, but I can't locate a "Main.pm" in any of the current Zoidberg > packages on CPAN, maybe I'm overlooking it? It’s not a separate modu

PAUSE permissions conflict on Main package

2016-07-27 Thread Neil Bowers
Hi Jaap & Flávio, I’m one of the PAUSE admins. I’m still working on resolving conflicts caused by PAUSE now considering CPAN package names case insensitively. This has left us with some situations where people are owners of namespaces previously considered distinct, and now considered the same.