Re: Permissions conflict with your "setup" package

ellier, France Facebook | Twitter | www.teclib.com - Mail original - De: "Neil Bowers" À: gboug...@cpan.org Cc: modu...@cpan.org, grou...@cpan.org Envoyé: Lundi 24 Juillet 2017 11:05:59 Objet: Re: Permissions conflict with your "setup" package Hi Guillaume,

Re: Permissions conflict with your "setup" package

Hi Guillaume, Thanks for getting back to me so quickly. > this files was used to solve some packaging issues, and yes this was a > mistake. It was introduced in v2.3.29 but it was moved out of bin/ in > v2.3.20. We are even in the process for future major release of > FusionInventory::Agent to

Re: Permissions conflict

It lives on as pure docs. I dropped the one with the inconsistent camel case. Thanks! (I'm shocked and pleased that you're still diligently cleaning these up. It's insanely great that you're doing it. Thank you!) David On Tue, Jan 10, 2017 at 7:09 PM, Neil Bowers wrote: > Hi David, > > You

Re: Permissions conflict between IMS::LOM::LangString and IMS::LOM::Langstring

Hi Chris, > Drop mine. They are exclusively an example. Thanks. I’ve dropped your (and Karen’s, copied) permissions on IMS::LOM::Langstring, resolving the conflict with ROBINS’s use of IMS::LOM::LangString. Cheers, Neil > > -Chris > > > > > > On Wed, Jul 27, 2016 at 6:11 PM -0400, "Neil

Re: Permissions conflict between Dist::Zilla::PluginBundle::BioPerl and Dist::Zilla::PluginBundle::Bioperl

Yes, go ahead! On Wed, Jul 20, 2016 at 3:39 PM Neil Bowers wrote: > Hi Robert, > > 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

Re: Permissions conflict between Dist::Zilla::PluginBundle::BioPerl and Dist::Zilla::PluginBundle::Bioperl

Hi Robert, I asked: > Would you be happy for me to delete the > Dist-Zilla-PluginBundle-Bioperl-0.01.tar.gz > > release from your author directory, and then drop the associated permissions? To which you re

Re: Permissions conflict between Dist::Zilla::PluginBundle::BioPerl and Dist::Zilla::PluginBundle::Bioperl

Hi Robert, > 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 co

Re: Permissions conflict between Dist::Zilla::PluginBundle::BioPerl and Dist::Zilla::PluginBundle::Bioperl

> What happened to Dist::Zilla::PluginBundle::BioPerl in versions 0.21 and > later? The 0.23 release does contain Dist::Zilla::PluginBundle::BioPerl (see > https://metacpan.org/release/Dist-Zilla-PluginBundle-BioPerl > ) -- why is it

Re: Permissions conflict between Dist::Zilla::PluginBundle::BioPerl and Dist::Zilla::PluginBundle::Bioperl

It sounds fine to drop the older lower-cased name from the index and to move the corresponding 0.01 release to backpan. It also sounds like there's an issue with the newer Dist-Zilla-PluginBundle-BioPerl releases -- since the 02packages index has: Dist::Zilla::PluginBundle::BioPerl 0.20 C/CD/CDRA

Re: permissions conflict between INTEGER and integer namespaces

Hi Sherzod, > 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 c

Re: Permissions conflict between MySAXHandler and MySaxHandler

Hi Xerxes, >> 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 no

Re: Permissions conflict between MySAXHandler and MySaxHandler

Hi Xerxes, > 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 co

Re: Permissions conflict between Net::STOMP and Net::Stomp

Neil Bowers writes: > To resolve these conflicts I’d like to drop your permissions on Net::STOMP > and Net::STOMP::Frame. I don’t think this will cause any problems, but > wanted to check — are you happy for me to do this? Hi! This conflict has been spotted a long time ago and I moved my code

Re: Permissions conflict between Net::STOMP and Net::Stomp

Neil Bowers writes: > Am I ok to drop your permissions on all the Net::STOMP::* namespaces then? No! I own and still use everything under (and including) Net::STOMP::Client. Cheers, Lionel

Re: Permissions conflict between Net::STOMP and Net::Stomp

>> Am I ok to drop your permissions on all the Net::STOMP::* namespaces then? > > No! I own and still use everything under (and including) Net::STOMP::Client. Heh. Ok, I’ll leave those alone then :-)

Re: Permissions conflict between Net::STOMP and Net::Stomp

Hi Lionel, > This conflict has been spotted a long time ago and I moved my code from > Net::STOMP to Net::STOMP::Client at that time. I didn't know that I kept > the ownership of Net::STOMP. > > Fine by me to drop ownership of Net::STOMP and Net::STOMP::Frame. Thanks — I’ve dropped your permissi

Re : Permissions conflict caused by Apache::Session::Ipc

Hi Neil, It's OK for me too

Re: Permissions conflict caused by Apache::Session::Ipc

Hi Xavier & Clément, Xavier said: > It's OK for me too Clément said: > it's ok for me. Thank you — I have dropped your permissions for Apache::Session::Ipc, resolving the conflict. Cheers, Neil

Re: Permissions conflict caused by Apache::Session::Ipc

2016-06-07 23:31 GMT+02:00 Neil Bowers : > Hi Xavier and Clément, > > 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 people are owners of namespaces >