Hi Rutger,

It’s that time again … :-)

So you know, I have 8 such cases left on my list. If you don’t fix this before 
then, in 7 weeks or so you’ll be the only case left on my list, and I might 
start emailing you more frequently than monthly! ;-)

> On 8 Sep 2016, at 21:38, Neil Bowers <neil.bow...@cogendo.com> wrote:
> Hi Rutger,
> This is your monthly guilt trip from the PAUSE admins :-)
>>> I'll do my best to fix this but I can't get to this immediately. I made an 
>>> issue which I'll resolve once I have a bit more time: 
>>> https://github.com/rvosa/bio-phylo-beagle/issues/1 
>>> <https://github.com/rvosa/bio-phylo-beagle/issues/1>
>> This is just a gentle reminder. I’ll send you one roughly every month, as 
>> I’m working through similar issues in other distributions.
>> Cheers,
>> Neil
>>> On Thu, Jul 7, 2016 at 10:27 PM, Neil Bowers <neil.bow...@cogendo.com 
>>> <mailto:neil.bow...@cogendo.com>> wrote:
>>> Hi Rutger,
>>> 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.
>>> You have ownership of the “beagle” namespace, as a result of your beagle 
>>> module, which is part of your Bio-Phylo-Beagle distribution. This now 
>>> clashes with the Beagle module, owned by SUNNAVY, and part of his Beagle 
>>> distribution. This conflict means that people couldn’t install your 
>>> distribution and Beagle at the same time on case-insensitive filesystems 
>>> (eg Windows and Mac OS X).
>>> The best solution would be for you to rename the “beagle” module to 
>>> something inside the Bio::Phylo::Beagle:: namespace, so that everything in 
>>> the Bio-Phylo-Beagle distribution would then have the expected name.
>>> Would you be happy to make this change? Once you’ve released a new version, 
>>> all old releases could then be deleted from your CPAN author directory, and 
>>> I’d then drop your permissions on “beagle”.
>>> PAUSE doesn’t let situations like this occur any more, so I’m working on 
>>> resolving the existing cases.

Reply via email to