Re: PAUSE permissions clash between URPM and urpm [TVIGNAUD]

Le ven. 26 avr. 2019 à 00:06, Neil Bowers a écrit : > I’m one of the PAUSE admins. I emailed you back in August 2017 about an issue > in PAUSE that we were hoping to resolve, and are looking to complete the > resolution of very soon. > > I’m working through tidying up permissions conflicts that

Re: PAUSE permissions clash between URPM and urpm [TVIGNAUD]

>> Once our proposed change is released, then PAUSE would index whichever of >> URPM and urpm was most recently released. If you’d prefer that URPM is the >> module that’s always indexed, you could just ensure that the “urpm” module >> is never indexed. The easiest way for you to achieve this wo

Re: PAUSE permissions clash between URPM and urpm [TVIGNAUD]

Le mer. 1 mai 2019 à 10:41, Neil Bowers a écrit : > > Hi Thierry, > > >> Do you know how people are likely to install your distributions? Will they > >> do it using a CPAN client, or using a linux package? Even if you believe > >> most people will install from linux packages, we still want the m

Re: PAUSE permissions clash between URPM and urpm [TVIGNAUD]

> Sorry I miswrite: > I wouldn't rename urpm.pm to urpmi.pm (that would break a lot of > existing software), > I only plan to provide a urpmi.pm stub module) Ah, ok. This will still result in the CPAN Index only including whichever of URPM and urpm was most recently released. If you’re not real

Re: PAUSE permissions clash between URPM and urpm [TVIGNAUD]

Hi Thierry, >> Do you know how people are likely to install your distributions? Will they >> do it using a CPAN client, or using a linux package? Even if you believe >> most people will install from linux packages, we still want the most likely >> behaviour to work on CPAN as well. > > They us

Re: PAUSE permissions clash between URPM and urpm [TVIGNAUD]

Le ven. 26 avr. 2019 à 00:06, Neil Bowers a écrit : > > Hi Thierry, > > I’m one of the PAUSE admins. I emailed you back in August 2017 about an issue > in PAUSE that we were hoping to resolve, and are looking to complete the > resolution of very soon. > > I’m working through tidying up permissio

Re: PAUSE permissions clash between URPM and urpm [TVIGNAUD]

Hi Thierry, I’m one of the PAUSE admins. I emailed you back in August 2017 about an issue in PAUSE that we were hoping to resolve, and are looking to complete the resolution of very soon. > I’m working through tidying up permissions conflicts that have been caused by > the fact that PAUSE now

Re: PAUSE permissions clash between Microarray and microarray package names [CJONES]

>> I’m one of the PAUSE admins. PAUSE previously treated package names >> case-insensitively when considering permissions, but we realised this caused >> problems on operating systems with case-insensitive filesystems, such as >> Windows and MacOS (until APFS). So I’m working through the histor

Re: PAUSE permissions clash between URPM and urpm [TVIGNAUD]

On 22 August 2017 at 20:28, Neil Bowers wrote: > I’m one of the PAUSE admins. I’m working through tidying up permissions > conflicts that have been caused by the fact that PAUSE now consider package > names case insensitively (due to case-insensitive filesystems, as on Windows > and MacOS X). PAUS

PAUSE permissions clash between URPM and urpm [TVIGNAUD]

Hi Thierry, I’m one of the PAUSE admins. I’m working through tidying up permissions conflicts that have been caused by the fact that PAUSE now consider package names case insensitively (due to case-insensitive filesystems, as on Windows and MacOS X). PAUSE doesn’t let these situations occur now

PAUSE permissions clash between Microarray and microarray package names [CJONES]

Hi Christopher, I’m one of the PAUSE admins. PAUSE previously treated package names case-insensitively when considering permissions, but we realised this caused problems on operating systems with case-insensitive filesystems, such as Windows and MacOS (until APFS). So I’m working through the hi

Re: PAUSE permissions clash between File::ShareDir::Install and File::Sharedir::Install [GWYN,ETHER]

Hi Philip, >> You have first-come permissions on File::ShareDir::Install (listed in the >> CPAN Index against E/ET/ETHER/File-ShareDir-Install-0.11.tar.gz). >> You also have first-come permissions on File::Sharedir::Install, which isn’t >> indexed. >> Karen (ETHER) has co-maint on both of these.

Re: PAUSE permissions clash between Business::OnlinePayment::CyberSource and Business::OnlinePayment::Cybersource [XENO]

Hi Caleb, > Yes, that's fine. Great — thanks. I’ve just dropped permissions on Business::OnlinePayment::Cybersource Cheers, Neil > I’m one of the PAUSE admins. I’m working through tidying up permissions > conflicts that have been caused by the fact that PAUSE now consider package > names ca

Re: PAUSE permissions clash between Business::OnlinePayment::CyberSource and Business::OnlinePayment::Cybersource [XENO]

Yes, that's fine. On Sun, Feb 12, 2017 at 5:13 AM Neil Bowers wrote: > Hi Caleb, > > I’m one of the PAUSE admins. I’m working through tidying up permissions > conflicts that have been caused by the fact that PAUSE now consider package > names case insensitively (due to case-insensitive filesyste

PAUSE permissions clash between Business::OnlinePayment::CyberSource and Business::OnlinePayment::Cybersource [XENO]

Hi Caleb, I’m one of the PAUSE admins. I’m working through tidying up permissions conflicts that have been caused by the fact that PAUSE now consider package names case insensitively (due to case-insensitive filesystems, as on Windows and MacOS X). PAUSE doesn’t let these situations occur now,

Re: PAUSE permissions clash between Match::Smart and match::smart

Hi Neil, Yes, that is fine. Thanks, - Dan On Fri, Feb 10, 2017, 7:35 AM Neil Bowers wrote: > Hi Dan, > > I’m one of the PAUSE admins. I’m working through tidying up permissions > conflicts that have been caused by the fact that PAUSE now consider package > names case insensitively (due to cas

Re: PAUSE permissions clash between Match::Smart and match::smart

Hi Dan, > Yes, that is fine. Thanks — I’ve just dropped your permissions on Match::Smart Cheers, Neil

PAUSE permissions clash between File::ShareDir::Install and File::Sharedir::Install [GWYN,ETHER]

Hi Philip, I’m one of the PAUSE admins. I’m working through tidying up permissions conflicts that have been caused by the fact that PAUSE now consider package names case insensitively (due to case-insensitive filesystems, as on Windows and MacOS X). PAUSE doesn’t let these situations occur now,

PAUSE permissions clash between Match::Smart and match::smart

Hi Dan, I’m one of the PAUSE admins. I’m working through tidying up permissions conflicts that have been caused by the fact that PAUSE now consider package names case insensitively (due to case-insensitive filesystems, as on Windows and MacOS X). PAUSE doesn’t let these situations occur now, bu

PAUSE permissions clash between URPM and urpm [TVIGNAUD]

Hi Thierry, I’m one of the PAUSE admins. I’m working through tidying up permissions conflicts that have been caused by the fact that PAUSE now consider package names case insensitively (due to case-insensitive filesystems, as on Windows and MacOS X). PAUSE doesn’t let these situations occur now

Re: PAUSE permissions clash with Stash vs stash

Hi Paweł, > Yes, please do this. > > Cheers, > Paweł Thanks. I’ve just dropped the permissions, and am about to schedule deletion of your releases, which you’ll get an email about from PAUSE. Thanks, Neil > > On 11 December 2016 at 11:35, Neil Bowers > wrote

Re: PAUSE permissions clash with Stash vs stash

Hi Neil, Yes, please do this. Cheers, Paweł On 11 December 2016 at 11:35, Neil Bowers wrote: > Hi Paweł, > > Would just deleting the STD distribution solve stuff? It's not developed > or useful anymore. > > > We’ll need to drop your permissions on the packages, and specifically on > “Stash”. >

Re: PAUSE permissions clash with Stash vs stash

Hi Paweł, > Would just deleting the STD distribution solve stuff? It's not developed or > useful anymore. We’ll need to drop your permissions on the packages, and specifically on “Stash”. Given I’m doing some PAUSE gardening anyway, if you give me permission, I’ll do this on your behalf: Dele

Re: PAUSE permissions clash between MCrypt and Mcrypt

Hi Frey, >>> Frey has ownership of MCrypt (last released in 2000), and Theo has >>> ownership of Mcrypt (last released in 2007). These are now considered the >>> same from a permissions perspective, resulting in a conflict, which >>> wouldn’t let anyone release a new version. >>> >>> […] >> >

Re: PAUSE permissions clash between MCrypt and Mcrypt

Hi again Frey, In November I emailed you: > In early September I emailed you: >> I’m one of the PAUSE admins. I’m emailing you because 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 mor

PAUSE permissions clash with Stash vs stash

Hi Paweł & Stefan, I’m one of the PAUSE admins. I’m working on resolving conflicts caused by PAUSE now considering package names case insensitively. This left us with some situations where two or more people are owners of namespaces previously considered distinct, and now considered the same.

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

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 instal

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

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

Re: PAUSE permissions clash between "stash" and "Stash"

Hi Tim, In August I emailed you: > I’m one of the PAUSE admins, and 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 previously considered > distinct, and now cons

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

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 between MCrypt and Mcrypt

Hi Frey, In early September I emailed you: > I’m one of the PAUSE admins. I’m emailing you because 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 p

Re: PAUSE permissions clash between Load and load modules [MPOURASG - Load]

Hi George, > Thanks > > I will try to fix and rewrite everything. > it is good idea to remove the module until then Thank you. I have dropped your permissions on the “Load” and “Delete” namespaces, which resolves the problem conflict. You can delete your old releases while you work on your u

PAUSE permissions clash between Load and load modules [MPOURASG - Load]

Hi George, 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

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

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

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

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

Re: PAUSE permissions clash between Load and load modules

Hi George, In July I emailed you: > 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 consider

Re: PAUSE permissions clash between HTML::Template::DEFAULT and HTML::Template::Default

Hi Sam & Michael, >> [resolving conflict between HTML::Template::DEFAULT and >> HTML::Template::Default] >> That’s fine - there's no upside to indexing these inner classes, they're >> entirely internal and don't have a public API. Thanks! > > Great! I just sent a pull request to Michael’s rep

Re: PAUSE permissions clash between "Qt::Base" and "Q::base" [AWIN/Qt::Base & GGARAND/Qt::base]

Hi Ashley & Germain, I emailed you back in June: > 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 pre

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

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

PAUSE permissions clash between MCrypt and Mcrypt

Hi Frey & Theo, I’m one of the PAUSE admins. I’m emailing you because 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

Re: PAUSE permissions clash between I18N::String and i18n::string

Thanks for the quick response Audrey. This one was my fault - I based the idea on Audrey's code but didn't realise back then that cpan was case-insensitive like this... Btw it's not actually failing, it just doesn't have any tests :( I'm pretty sure BABF is still using the module On Wed, 10 Aug

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

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 immediat

Re: PAUSE permissions clash between I18N::String and i18n::string

Hi Clinton, > This one was my fault Well … I didn’t want to point any fingers … ;-) > - I based the idea on Audrey's code but didn't realise back then that cpan > was case-insensitive like this… When you did that it was probably case-sensitive — it was only a couple of years ago that it was c

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

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 f

Re: PAUSE permissions clash between I18N::String and i18n::string

Hi Audrey, > Certainly. This is done as i18n-0.11. Thanks for your work! Thanks for dealing with this so promptly! I’ve dropped all permissions on i18n::string and i18n::var, removing the conflict. Cheers, Neil

Re: PAUSE permissions clash between I18N::String and i18n::string

Certainly. This is done as i18n-0.11. Thanks for your work! Cheers, Audrey > Neil Bowers 於 2016年8月10日 上午6:10 寫道： > > Hi all, > > I’m one of the PAUSE admins. I’m emailing you because I’m working on > resolving conflicts caused by PAUSE now considering package names case > insensitively. This

Re: PAUSE permissions clash between HTML::Template::DEFAULT and HTML::Template::Default

> That's fine - there's no upside to indexing these inner classes, they're > entirely internal and don't have a public API. Thanks! Great! I just sent a pull request to Michael’s repo for HTML-Template. I also updated the dist.ini to request that releases include a META.json file as well as a

PAUSE permissions clash between I18N::String and i18n::string

Hi all, I’m one of the PAUSE admins. I’m emailing you because 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 cons

Re: PAUSE permissions clash between HTML::Template::DEFAULT and HTML::Template::Default

That's fine - there's no upside to indexing these inner classes, they're entirely internal and don't have a public API. Thanks! Sam On Tue, Aug 9, 2016 at 5:05 PM, Neil Bowers wrote: > Hi Sam and Michael, > > I’m one of the PAUSE admins. I’m emailing you because I’m working on > resolving con

PAUSE permissions clash between HTML::Template::DEFAULT and HTML::Template::Default

Hi Sam and Michael, I’m one of the PAUSE admins. I’m emailing you because 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,

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

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 y

Re: PAUSE permissions clash between test::helper and Test::Helper

Please drop my permission, it doesn't make sense to make it CPAN indexed. Thanks and keep up the good work. On Thu, Aug 4, 2016 at 9:48 PM, Neil Bowers wrote: > Hi Dobrica & Derrik, > > I’m emailing you wearing my PAUSE admin hat: I’m still working on > resolving conflicts caused by PAUSE now c

Re: PAUSE permissions clash between test::helper and Test::Helper

Hi Dobrica, > Please drop my permission, it doesn't make sense to make it CPAN indexed. > > Thanks and keep up the good work. Thank you — I have dropped your permissions on test::helper, resolving the conflict! Cheers, Neil

PAUSE permissions clash between "stash" and "Stash"

Hi Tim, I’m one of the PAUSE admins, and 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 previously considered distinct, and now considered the same. You have owners

PAUSE permissions clash between test::helper and Test::Helper

Hi Dobrica & Derrik, I’m emailing you wearing my PAUSE admin hat: I’m still 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 previously considered distinct, and now consid

Re: PAUSE permissions clash between "debug" and "DEBUG"

Hi Mark, > 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 cons

PAUSE permissions clash between "debug" and "DEBUG"

Hi Mark, 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 t

PAUSE permissions clash between Load and load modules

Hi George, 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

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

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 we

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

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

Re: PAUSE permissions clash between PARENT and parent

Hi Luke, > I don't really care. I wouldn't want to break anybody's code, but I doubt > this package has many users. I haven't done any perl for many years, can't > say I even know what you're talking about. I defer to your judgment. Thanks for this. I’ll give myself co-maint and do a new relea

Re: PAUSE permissions clash between gcc::node and GCC::Node

Hi Mike, > you can delete my version, it is not maintained. I have more stuff on github. > sorry this has been a long term never ending project. Thanks. I’ve scheduled the files for deletion, and have dropped your permissions, which resolves the conflict. Thanks, Neil

Re: PAUSE permissions clash with "Foo" namespace

Hi Elliot, >> To resolve this clash I propose dropping both of your permissions on >> “Foo”. I don’t think this will cause any problems, but wanted to >> check that you’re happy for me to do this? > > No problem for me. I don't know how I got this. Heh — you’re not the first person to say that

Re: PAUSE permissions clash with "Foo" namespace

On 6/28/16 3:50 PM, Neil Bowers wrote: To resolve this clash I propose dropping both of your permissions on “Foo”. I don’t think this will cause any problems, but wanted to check that you’re happy for me to do this? No problem for me. I don't know how I got this.

Re: PAUSE permissions clash between gcc::node and GCC::Node

you can delete my version, it is not maintained. I have more stuff on github. sorry this has been a long term never ending project. On Tue, Jun 28, 2016 at 5:21 PM, Neil Bowers wrote: > Hi James, > > I’m emailing you wearing my PAUSE admin hat: I’m working on resolving > conflicts caused by PAUS

PAUSE permissions clash between gcc::node and GCC::Node

Hi James, 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

PAUSE permissions clash between "Qt::Base" and "Q::base" [AWIN/Qt::Base & GGARAND/Qt::base]

Hi Ashley & Germain, 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

PAUSE permissions clash with "Foo" namespace

Hi Joel & Elliot, 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 con

Re: PAUSE permissions clash between PARENT and parent

I don't really care. I wouldn't want to break anybody's code, but I doubt this package has many users. I haven't done any perl for many years, can't say I even know what you're talking about. I defer to your judgment. Luke On Wed, Jun 22, 2016, 2:44 PM Neil Bowers wrote: > Hi Luke, > > > I’m em

Re: PAUSE permissions clash between PARENT and parent

Hi Luke, > 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 > previously considered distinct, and now considered the s

Re: PAUSE permissions clash between Lab::Instrument::DummySource and Lab::Instrument::Dummysource

Hi Daniel & Andreas, > Thank you for your efforts and sorry for my late response. I was > pleasantly far away from email access in the last two weeks. > > I am fine with all your proposals. Please go ahead. Thank you! Thank you. I have dropped the relevant permissions, and scheduled deletion of

Re: PAUSE permissions clash between Lab::Instrument::DummySource and Lab::Instrument::Dummysource

Hi Neil and Andreas! Thank you for your efforts and sorry for my late response. I was pleasantly far away from email access in the last two weeks. I am fine with all your proposals. Please go ahead. Thank you! Cheers Daniel 2016-06-15 23:01 GMT+02:00 Neil Bowers : > Hi Andreas, > >>> To resolve

Re: PAUSE permissions clash between Lab::Instrument::DummySource and Lab::Instrument::Dummysource

Hi Neil & Daniel, > Daniel (SCHROEER) has ownership of Lab::Instrument::Dummysource, and > Andreas has co-maint. But Andreas has ownership of > Lab::Instrument::DummySource, which is the version of the module indexed > on CPAN (in the A/AK/AKHUETTEL/Lab-Measurement-3.500.tar.gz release). > > To

Re: PAUSE permissions clash between Lab::Instrument::DummySource and Lab::Instrument::Dummysource

Hi Andreas, >> To resolve this conflict, I’d like to drop both of your permissions on >> Lab::Instrument::Dummysource. I don’t think this will cause any problems, >> but I wanted to check with you. > > No problem for me. > > Recent versions of Lab-Measurement are the continued development of ol

PAUSE permissions clash between Lab::Instrument::DummySource and Lab::Instrument::Dummysource

Hi Daniel & Andreas, 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

Re: PAUSE permissions clash

Done and done! > On Jun 11, 2016, at 05:20, Neil Bowers wrote: > > Hi Moritz, > > 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 peopl

PAUSE permissions clash with INTEGER namespace

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 considere

PAUSE permissions clash

Hi Moritz, 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

PAUSE permissions clash between PARENT and parent

Hi Luke, 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 previously considered distinct, and now considered the same. Yo