Hi Neil, Thank you for pointing this out ( I also received an error notification after the upload to PAUSE regarding the Asterisk::Config namespace ). I will follow-up with James and discuss how we are going to move forward with resolving this conflict.
Best, Charlie Charlie Gonzalez (E) itchar...@gmail.com Github Profile <https://github.com/itcharlie> On Tue, Aug 9, 2016 at 7:25 AM, Neil Bowers <neil.bow...@cogendo.com> wrote: > Hi James & Charlie, > > I’m emailing you wearing my PAUSE admin hat: I’m working on resolving > conflicts caused by PAUSE now considering package names case insensitively. > This has left us with some situations where two or more people are owners > of namespaces previously considered distinct, and now considered the same. > > James has ownership of Asterisk::Config and Charlie has co-maint. This is > part of the asterisk-perl distribution. > > It now conflicts with the Asterisk::config package, owned by PAUSE id > HOOWA, and on CPAN in the Asterisk-config distribution. > These used to be distinct package names, but now they’re not. > > I think the easiest way to resolve this would be if you could rename > Asterisk::Config to Asterisk::Configuration, or similar, and then update > the modules currently in the Asterisk::Config:: namespace. > > PAUSE doesn’t let situations like this occur any more — I’m just working > through the existing cases. I realise this is a PITA, so sorry for the > hassle, and thanks in advance for helping tidy up some of the dusty corners > of CPAN :-) > > The steps would be something like this: > - You do a release with renamed modules > - I can drop permissions on the old package names > - In a few days (once your release has made it to all CPAN mirrors), we > can schedule the old releases for deletion > (as they have the conflicting module in them). > > Cheers, > Neil > >
