Re: Module Adoption

Hi Chase, > Digest::Bcrypt is in need of adoption and I wouldn't mind taking over > maintenance of that. My PAUSE id is capoeirab. Have you tried getting in touch with the author, James Aitken (JAITKEN), to ask if you can help? If you don’t get a reply from James, the process for adopting a m

Re: Module Adoption

Hi Chase, > Unfortunately James has passed away and the module is now with ADOPTME. Sorry, I didn’t notice that from the MetaCPAN page. I have transferred ownership of Digest::Bcrypt to you. Thanks for taking this on. Cheers, Neil

Re: Make maintainership

Hi Kevin, > It looks like https://metacpan.org/release/Make > is abandoned at this point, and assuming > that is true, I'm interested in working on it. I'm more interested in getting > https://metacpan.org/pod/PerlPowerTools >

ownership of Time::Hires transferred to P5P

I have just transferred ownership of Time::HiRes from ZEFRAM to P5P, as requested by Rik. Neil

Re: Make maintainership

Hi Kevin, > Is it possible to take over Make::Rule, Make::Rule::Vars, and Make::Target as > well? Sorry, I should have checked the dist and spotted that you need those as well. I’ve now transferred ownership of them to you as well. Neil

Re: Adopting Apache::Htaccess module

Hi Arun, > I noticed the Apache::Htaccess module has no maintainer as of now and I wish > to take over maintaining it. I wish to improve the documentation and improve > some bits as soon as possible. I have transferred ownership of Apache::Htaccess to you. Thanks for taking it on. A small req

Re: Looking for Brent Powers / adoption of Memoize::ExpireLRU

A month ago I wrote: > I’ve tried contacting Brent Powers (BPOWERS) about getting co-maint or > ownership of Memoize::ExpireLRU, but email to him bounces. I think I’ve found > him on LinkedIn, and am waiting to see if he accepts my link request :-) > > In the meantime, this is the first stake in

Re: Failed: PAUSE indexer report POPEFELIX/Mojo-UserAgent-Mockable-1.23.tar.gz

Hi Kit, > As you can see in the attached, the version of this module (1.23) is clearly > higher than the previous version. Is this perhaps because dzil used the > construction "$Mojo::UserAgent::Mockable::VERSION = '1.23';" rather than "our > $VERSION = '1.23'"? Please advise. If you look at t

PAUSE permissions for Config::Hash

Hi Stefan, You have PAUSE permissions for Config::Hash, which previously didn’t clash with CONFIG::Hash, but now that PAUSE treats module names case-insensitively, these permissions clash. You no longer have Config::Hash on CPAN, but MWS does have CONFIG::Hash, so I’m going to drop your permis

Dropped AVATAR's permissions on Config::Ini

Hi Albert, I’m one of the PAUSE admins. In the old days of PAUSE, module names were treated case-sensitively, so you ended up owning Config::Ini, and RJBS ended up owning Config::INI. The latter is still on CPAN, but your module (Config::Ini) isn’t. To remove the ambiguity of ownership of this

Lingua::PT::pln

Hi Alberto, I’m emailing you wearing my PAUSE admin hat. You had PAUSE ownership of both Lingua::PT::PLN and Lingua::PT::pln, which you got when PAUSE considered module names case-sensitively (which it doesn’t do now). To remove the ambiguity, I’ve just dropped your ownership of Lingua::PT::pl

Ownership of module 'O'

Hi Malcolm, I’m one of the PAUSE admins. You previously had the module-list ownership of module ‘O’ in PAUSE. As part of removing the vestiges of the module list from PAUSE we have transferred the ownership of the ‘O’ to P5P, since it’s a core module. This was done in consultation with Rik and

Permissions for DBD::cego and DBD::Cego

Hi Kurt, Your module DBD::Cego is on CPAN, and you have ownership of that namespace. You also had ownership of DBD::cego (note the difference in case). This is leftover from the days when PAUSE treated package names case-sensitively, which it no longer does. To remove the ambiguity, and the po

Re: Perl Module: Exceptions

Hi Peter, > Happy to hand it over. I'm quite sure I can't log into PAUSE as it's been > decades since I tried so I'll need some help there. I’ll transfer it to Chase. You have 3 options: 1. give Chase co-maint 2. give Chase ownership and retain co-maint yourself (you’ll still get copied on b

Re: Perl Module: Exceptions

> Option 3 it is. > > On Tue, May 3, 2016 at 8:43 AM, Neil Bowers <mailto:neil.bow...@cogendo.com>> wrote: > Hi Peter, > > > Happy to hand it over. I'm quite sure I can't log into PAUSE as it's been > > decades since I tried so I'll n

Re: A question of permissions

Hi Buddy, > After I uploaded my new module Date::Easy a while back, I got a failure > notice from PAUSE: I only just noticed your email. PAUSE-related issues are better raised to modules@perl.org , or you can send to both modules@ and module-authors. >> This distribut

Tidying up some of GARY's CPAN data

I’ve just scheduled the following file for deletion: G/GA/GARY/Crypt-DES-1.0.tar.gz And dropped GARY’s co-maint on the package ‘DES’. This was released in 1996, and has long been superseded: D/DP/DPARIS/Crypt-DES-2.07.tar.gz was released in 2013. But GARY’s release was still being index

The Javascript package in your v6 distribution

Hi Flavio, I’m emailing you wearing my PAUSE admin hat. I’m have a project to work through conflict in package names and permissions. Your “v6” distribution has a package “Javascript”, which appears in the CPAN Index: Javascript undef F/FG/FGLOCK/v6-0.044.tar.gz This conflicts with t

Mobile::WURFL and Mobile::Wurfl

Hi Valerio and Ave, I’m emailing you wearing my PAUSE admin hat. I have a project to work through conflict in package names and permissions. You two both have WURFL modules on CPAN: Mobile::WURFL and Mobile::Wurfl. These days PAUSE wouldn’t let this happen, as it considers package names case i

Re: The Javascript package in your v6 distribution

> Yes, I'll move all top-level packages to the inner namespace. Thanks Flavio!

CPAN modules Nagios::NRPE and Nagios::Nrpe

Hi Sarah and Andreas, I’m one of the PAUSE admins — I’m emailing you about a module naming conflict. You both have CPAN modules which match the name /^nagios::nrpe$/i Sarah has Nagios::Nrpe Andreas has Nagios::NRPE Until recently PAUSE treated these as two distinct modules, but

CPAN naming conflict: Pod::RTF and Pod::Rtf

Hi Peter & Kenneth, I’m one of the PAUSE admins. You two both have pod-to-RTF modules on CPAN with names that match /^pod::rtf$/i — KJALB has Pod::RTF in the PodSimplify distribution PVHP has Pod::Rtf in the Pod2WinHlp distribution Until recently PAUSE treated this as separate

Renaming your QT module

Hi Chris, I’m one of the PAUSE admins, and I’m emailing you about a CPAN module naming conflict. Your Smil distribution contains a module called “QT”, which is the file lib/SMIL/QT.pm, so it almost looks like you meant to call the module SMIL::QT? The conflict comes because German Garand (copi

Dropped your permissions on package 'super'

Hi Dave, You had first-come permissions on the ‘super’ package, which was now conflicting with ‘SUPER’, which chromatic has first-come permissions on. In the past PAUSE treated package names case-sensitively, but that turned out not to be workable, thanks to case-insensitive filesystems. So now

Re: CPAN modules Nagios::NRPE and Nagios::Nrpe

Hi Sarah, > That's fine. I'll rename my module in next 24 hours. Awesome — thanks for doing this! > Sorry for any inconvenience caused. No apologies needed — we changed the rules under you :-) Cheers, Neil

Re: Need admin to fix permissions on cpan::outdated

Hi Olivier, Sorry for the delay — I’ll get to this later, once the kids are abed :-) Neil

Re: Mobile::WURFL and Mobile::Wurfl

Hi Valerio, > thanks for contacting me about this issue. Feel free to remove my module, and > please use WURFL for the one remaining. I’ve just scheduled deletion of your releases of Mobile-WURFL from CPAN, and dropped your permissions. Thanks for your understanding and support on this, Neil

Re: Need admin to fix permissions on cpan::outdated

Hi Olivier, Sorry for the delay on this, resolving the perms on cpan::outdated needed help from a higher power (Andreas :-) > TOKUHIROM has given me (DOLMEN) co-maint permissions on App::cpanoutdated. > Proof: https://twitter.com/omengue/status/724946706912141312 >

ownership of package "cant"

Hi Daniel, I’m a PAUSE admin, and I’m working through issues caused by PAUSE now considering packages case-insensitively, where in the past it considered them case-sensitively. You have ownership of the module “cant”, which clashes with ‘Cant’, owned by used PGUEN. PGUEN still has the module o

Re: The "USER" namespace on CPAN

Hi Jörn, >> You have ownership of the “USER” namespace, but don’t have a “USER” module >> on CPAN. >> This conflict’s with TBONE’s “User” module, which *is* on CPAN. > > I wasn't even aware of having any ownership of the USER namespace ;) Heh, you’re not the first person to respond that way! >

Re: The "Util" and "util" namespaces

Hi Steve & Chocolate, > On 20 May 2016, at 08:18, Steve Hay wrote: > Fine with me. Didn't know I even had it! (Maybe it's from a perl distro > upload?) > On 20 May 2016 01:57, "chocolateboy" wrote: > Totally OK with it. Thank you, I have dropped both of your permissions on “util” and “Util”

Re: The Palm::KeyRing package [JV: Palm::KeyRing]

Hi Johan, >> You have ownership of the “Palm::KeyRing” namespace, but don’t have a >> “Palm::KeyRing” module on CPAN. This conflict’s with ANDREW's >> “Palm::Keyring” module, which *is* on CPAN. He hasn’t released it for a >> while, but if he did it wouldn’t be indexed, due to the conflict. >> >>

Re: T2 and t2 packages on CPAN

Hi Yuval & Sam, > On 20 May 2016, at 00:49, Yuval Kogman wrote: > I am not qualified to have any opinion on T2 despite comaint, and I believe > t2 should have never been indexed, so deletion sounds right to me. > On 19 May 2016, at 22:36, s...@vilain.net wrote: > Sure, feel free! I'm not activ

CPAN: The WebApp and webapp package names [JAYWHY: WebApp, SUKRIA: webapp]

Hi Alexis & Jason, 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

The "sun" package on CPAN [LARSLUND: sun]

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

The "stem" package on CPAN

Hi Siddharth, Ted, and Jason, 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 con

Re: CPAN: The WebApp and webapp package names [JAYWHY: WebApp, SUKRIA: webapp]

Hi Jason, > Hmm.. A cgi-app plugin I wrote had some example code that referenced the > WebApp namespace, solely for example purposes. > > Now how that led me to be the owner of it, I have no idea. Maybe you had the example code in a release in a directory where PAUSE saw it, maybe it was a fin

Re: CPAN: The WebApp and webapp package names [JAYWHY: WebApp, SUKRIA: webapp]

Hi Alexis, > it's perfectly fine with me, feel free to take over "webapp" :) Dang, you rumbled me, I just wanted the namespace for my own nefarious purposes. While I thinking of something nefarious I’ve dropped your perms on this namespace, so whoever thinks of something to do with it first can

The "Connection" perl module [BRONSON: Connection]

Hi Scott, 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. Y

Ownership of "future" namespace [SREZIC: future]

Hi Slaven, 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.

The geo::ecef module [MSICKEL: geo::ecef]

Hi Morten, 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 equivalent.

Re: The geo::ecef module [MSICKEL: geo::ecef]

n > > On 2016-05-21 17:24, Neil Bowers wrote: >> Hi Morten, >> 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 peo

Re: The "Connection" perl module [BRONSON: Connection]

> I don't quite understand, why drop the root namespace? The one that I want to drop permissions for is namespace “Connection”, because it is now treated by PAUSE as the same thing as “connection”. In the past they were treated as separate namespaces, so it was ok for you both to own them. CHI

Re: Ownership of "future" namespace [SREZIC: future]

Hi Slaven, > feel free to drop it. I still have an unpublished "future" pragma on my > disk, but I doubt I'll ever release it (and if, I'll choose another > name). Thank you — I’ve dropped your perms on “future”. Cheers, Neil

Re: Anyone here?

To resolve this I’d like to drop one or both of Bundle::Tk and Bundle::TK — everyone ok with that? Cheers, Neil > Neil Bowers writes: > >> I’m trying to track down anyone who knows about the TKML pause ID, which is >> apparently linked to this mailing list

The "autoload" namespace on PAUSE/CPAN

Hi Lincoln, 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.

Ownership of the "profiler" namespace [PFEIFFER: profiler]

Hi Daniel, 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.

Re: Anyone here?

Hi Slaven, >> TKML has ownership of the “Plot” namespace. >> You and NI-S have co-maint on this namespace. >> There is no “Plot” module on CPAN, and from checking BackPAN, there >> never has been. >> Your “Plot” permissions conflict with “plot”, which is owned by CJONES. >>

The Chart::GnuPlot namespace

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

The Common::Sense perl module

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

The Env::path namespace on CPAN

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

The "Feature" namespace on CPAN

Hi Peter, 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. Y

The Input namespace on CPAN

Hi Brian, 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. Y

Re: The "Feature" namespace on CPAN

Hi Peter, > I have no recollection of obtaining the Feature name space and have no plans > to use it. I'm completely happy for it to be re-purposed. Thanks — I have dropped your permissions on the “Feature” namespace. Cheers, Neil

Re: The Input namespace on CPAN

Hi Brian, > I'm surprised that I'm still considered the "owner". I renamed it to RawInput > in response to a conversation with the CPAN admin at the time, and was under > the impression that I had essentially "given up" Term::Input at that time. > > Yes - you may take the ownership back. Than

Resolving permissions conflicts in Aspect::Point[Cc]ut*

Hi, 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. You all

Conflicting permissions on the "autoload" namespace

Hi Lincoln, 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.

The "cwd" namespace on CPAN

Hi Vidul, 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. Y

Re: Conflicting permissions on the "autoload" namespace

> Sure will. Thanks for letting me know. Do I transfer, or just relinquish? Just relinquish the ownership. When you do that a co-maint permission will almost certainly appear, so you’ll then need to drop that as well. I can do this for you, if you like? I’m doing it a lot at the moment, so well

The 'AO' namespace on CPAN

Hi Brian, 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. Y

Re: The 'AO' namespace on CPAN

> I’m fine with it. thanks for checking! Thanks. I’ve just noticed that you have a bunch of AO::* package names owned as well. These aren’t in conflict, but I’m given I’m deleting the parent namespace, shall I drop your permissions on the subsidiary namespaces as well?

Re: The 'AO' namespace on CPAN

> Sure. Thanks Brian — I’ve dropped those permissions. Cheers, Neil

Re: Conflicting permissions on the "autoload" namespace

> I've given up ownership of "autoload.” Thank you! > Let me know if I did it correctly. When you gave up ownership you ended up still having co-maint on “autoload”. I just dropped that for you. Cheers, Neil

Cleaning up PAUSE permission conflicts [DCOPPIT]

Hi David, 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. Y

Resolving conflicting PAUSE permissions

Hi Marco, 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. Y

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

Conflict between PAUSE permissions for MT and Mt

Hi Roman, 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. Y

Re: Conflict between PAUSE permissions for MT and Mt

Hi Roman, > You can drop the ownership, no problem Thanks — I’ve dropped your permissions on package “Mt”. Cheers, Neil

Re: Resolving conflicting PAUSE permissions

Hi Marco, > well, I don't understand exactly what is the problem but I assume there are > no problems… Looking at the “csv” example, you had ownership of it. If you looked at PAUSE’s permissions you’d have seen: csv,MMARCO,f Which says that you have “first-come” permissions. Only one

Re: PAUSE permissions on package 'About'

dexed > that way. You’re not the first person to respond this way. As you say, given you can’t remember why you have the ownership, it’s pretty safe to delete it. I’ve dropped your permissions on the “About” namespace. Cheers, Neil > > Thanks, > Robert > > On Tue, May 17, 201

Re: Cleaning up PAUSE permission conflicts [DCOPPIT]

Hi again David, > Yep. Same story as with my previous reply for "Array". These are sub-modules > of DailyUpdate/NewsClipper. Thanks — I’ve dropped your permissions on these. Cheers, Neil > > On Thu, May 26, 2016 at 3:51 PM, Neil Bowers <mailto:neil.bow...@cogend

Re: Carp::Clan co-maint bits needed

Hi Kent, > https://rt.cpan.org/Ticket/Display.html?id=114537 > > Existing maintainer is happy for me to maintain it, but they don't > have first-come bits. > > Only person with First-Come bits has mentioned in-thread they're fine > with whatever happening in repsonse to STBEY's "Can we have a >

Re: Gearman-1.12

Hi Alexei, You should now have co-maint on all the package names needed to be able to have a new release of Gearman be indexed by PAUSE. Cheers, Neil

Re: Gearman-1.12

Hi Alexei, > thank you for permissions update. Unfortunately I still can't upload Gearman > package because permissions for Gearman itself has only DORMANDO. See indexer > report in attachment. Could you give me permissions for Gearman package? Sorry about that. You now have co-maint on the root

Re: Ownership of the "profiler" namespace [PFEIFFER: profiler]

Hi Daniel, > this is ancient. Years ago I have moved it to "package Mpp::profiler;”. Thanks — I’ve dropped your permissions on “profiler”. Cheers, Neil

Common::Sense module

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

The "or" namespace on CPAN

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

Re: Common::Sense module

Hi Adam, > Please, go ahead. > > I thought 'use Common::Sense' would be quite amusing, without realising it > conflicted at the time! Upon realising, I deleted the module. Thanks — I’ve dropped your permissions on Common::Sense. Cheers, Neil

The "Helloworld" namespace on CPAN

Hi Alexandr, 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.

The ICal::Parser namespace on CPAN

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

Re: Problem with indexing

Hi Johan, > I've uploaded a new package, App-Music-ChordPro. It has gone through several > uploads for the last couple of days. The first version was 0.51, the most > recent upload is 0.52.2. > > The packages appears in the CPAN collection (www.cpan.org) a couple > of hours after each upload, but

Re: The "or" namespace on CPAN

Hi Matt, > I'm really struggling with this. I might like to unknowingly squat on the > namespace for another, uh, how long have I had it? > > J/k. I think I came by the namespace accidentally. I hereby relinquish my > claim upon it. And mourn the loss of something I didn't know I I had. I tri

Re: Oops ...

Hi Dave, > I gave up primary on Pg::DatabaseManager when I meant to transfer it to > ADOPTME. I did the following: 1. dropped your co-maint permissions on Pg::DatabaseManager and Pg::DatabaseManager::TestMigrations 2. forced re-indexing on Pg-DatabaseManager. Because no-one had any permissi

Permissions conflict caused by Apache::Session::Ipc

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 previously considered distinct, and now considered

Conflicting permissions for Cache::Memcached::[Ll]ib[Mm]emcached

Hi Maki-san and CODEREPOS, 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 consid

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

Resolving namespace permission conflicts

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

Re: The "Connection" perl module [BRONSON: Connection]

Hi Scott, > No problem at all, thanks for checking! Can I just double-check please: are you ok with me dropping your permissions on the “Connection” namespace? Cheers, Neil

namespace conflict with your "git" module

Hi Olivier, 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.

Your ownership of Image::Exif

Hi Gisle, 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. Y

Resolving permissions conflict between LISP::List and Lisp::List

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

Marc::Field

Hi Frédéric, 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 consider

PAUSE permissions conflict on MyConfig and myconfig

Hi Mizuno-san and Piers, 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

PAUSE permissions conflict between "With" and "with"

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

Re: PAUSE permissions conflict between "With" and "with"

Hi Iain, > "Kill it with fire!" > > Completely agree. Do what you gotta do to remove the blockage. It burned with a subtle purple flame. It has gone now.

Re: PAUSE permissions conflict on MyConfig and myconfig

Hi Piers, > Happy for mine to go. Thanks for that — I have dropped your permissions on MyConfig. Cheers, Neil

Re: Your ownership of Image::Exif

Hi Gisle, > No problem. I can't remember that I had an Image::Exif module. I do have an > EXIF parser in the Image::Info module. Perhaps there was a module in that > package once with Image::Exif as name. Thanks — I’ve dropped your permissions. Cheers, Neil

Re: Resolving permissions conflict between LISP::List and Lisp::List

Hi Doug, > yes, fine w/me, thanks. Thanks — I’ve dropped your permissions on LISP::List. Cheers, Neil

Re: Marc::Field

Hi Frédéric, > Yes, let proceed. You can drop my permission on Marc::Field. Thank you — I have dropped your permissions on this. Cheers, Neil

Re: Types::Datetime

Hi Alex, > I hope you're well although you vanished from the Perl world. > I'd need a fix for Types::Datetime and would take over the module and git > repo from you if you like. I’ve been in touch with Toby, and he said he’s happy for you to have co-maint on Types::DateTime, so I’ve just given

<    1   2   3   4   5   6   7   8   9   10   >