Re: PAUSE permissions clash with your "beagle" module [RVOSA: beagle]

2016-11-30 Thread Rutger Vos
Ok, cool. Sorry to be so tardy about this.

On Sun, Nov 20, 2016 at 4:27 PM, Neil Bowers 
wrote:

> Hi Rutger,
>
> I’ve dropped your permissions on the “beagle” namespace, to resolve the
> conflict with the Beagle module, which is part of the Beagle namespace.
>
> This won’t stop people from installing your Bio-Phylo-Beagle, but the
> “beagle” module may start showing up as unauthorised. In the unlikely
> chance that someone tries to install both Beagle and Bio-Phylo-Beagle on an
> OS with a case-insensitive filesystem, whichever is installed second will
> clobber the first.
>
> When you rename your beagle module and release that version of your dist,
> then the unauthorised flagging will go away.
>
> Cheers,
> Neil
>
>


Re: PAUSE permissions clash with your "beagle" module [RVOSA: beagle]

2016-11-20 Thread Neil Bowers
Hi Rutger,

I’ve dropped your permissions on the “beagle” namespace, to resolve the 
conflict with the Beagle module, which is part of the Beagle namespace.

This won’t stop people from installing your Bio-Phylo-Beagle, but the “beagle” 
module may start showing up as unauthorised. In the unlikely chance that 
someone tries to install both Beagle and Bio-Phylo-Beagle on an OS with a 
case-insensitive filesystem, whichever is installed second will clobber the 
first.

When you rename your beagle module and release that version of your dist, then 
the unauthorised flagging will go away.

Cheers,
Neil



Re: PAUSE permissions clash with your "beagle" module [RVOSA: beagle]

2016-11-11 Thread Neil Bowers
Hi Rutger,

Do you think you’ll be able to rename the “beagle” module in your 
Bio-Phylo-Beagle distribution?

Cheers,
Neil



Re: PAUSE permissions clash with your "beagle" module [RVOSA: beagle]

2016-10-20 Thread Rutger Vos
Yikes! Ok, thanks for the heads up.

On Mon, Oct 17, 2016 at 11:13 PM, Neil Bowers 
wrote:

> 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  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
>
>
> 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 
> 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.
>>
>
>
>


Re: PAUSE permissions clash with your "beagle" module [RVOSA: beagle]

2016-10-17 Thread Neil Bowers
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  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 
>>> 
>> 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 >> > 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.
> 



Re: PAUSE permissions clash with your "beagle" module [RVOSA: beagle]

2016-09-08 Thread Neil Bowers
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 
>> 
> 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 > > 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.




Re: PAUSE permissions clash with your "beagle" module [RVOSA: beagle]

2016-08-12 Thread Rutger Vos
Hi Neil,

very good, sorry this hasn't been fixed yet. First day back at work,
dealing with the email backlog. I'll try to get to this soon as I can.

Cheers,

Rutger

On Tue, Aug 9, 2016 at 12:24 PM, Neil Bowers 
wrote:

> Hi Rutger,
>
> 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
>
>
> 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 
> 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.
>>
>> Cheers,
>> Neil
>>
>
>


Re: PAUSE permissions clash with your "beagle" module [RVOSA: beagle]

2016-08-10 Thread Neil Bowers
Hi Rutger,

> very good, sorry this hasn't been fixed yet. First day back at work, dealing 
> with the email backlog. I'll try to get to this soon as I can.

No big rush — I’m working through a list of these cases, so this was just a 
gentle reminder.
In a month or so I should be down to the last few cases, at which point you’ll 
hear from me again :-)

Cheers,
Neil




Re: PAUSE permissions clash with your "beagle" module [RVOSA: beagle]

2016-08-09 Thread Neil Bowers
Hi Rutger,

> 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 
> 
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  > 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.
> 
> Cheers,
> Neil



Re: PAUSE permissions clash with your "beagle" module [RVOSA: beagle]

2016-07-08 Thread Rutger Vos
Hi Neil,

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

Cheers,

Rutger


On Thu, Jul 7, 2016 at 10:27 PM, Neil Bowers 
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.
>
> Cheers,
> Neil
>
>
>