User update for ATRIPPS

[Perl Authors Upload Server]

Record update in the PAUSE users database:

 userid: [ATRIPPS]
   fullname: [UTF-8]
  asciiname: []
  email: [CENSORED]
   homepage: []
cpan_mail_alias: [none]


Data were entered by ATRIPPS (UTF-8).
Please check if they are correct.

Thanks,
The Pause

User update for ATRIPPS

[Perl Authors Upload Server]

Record update in the PAUSE users database:

 userid: [ATRIPPS]
   fullname: [UTF-8] was [Arvind Tripathy]
  asciiname: []
  email: [CENSORED]
   homepage: []
cpan_mail_alias: [none]


Data were entered by ATRIPPS (Arvind Tripathy).
Please check if they are correct.

Thanks,
The Pause

Re: PAUSE permissions conflict between Asterisk::Config and Asterisk::config

[Charlie Gonzalez]

Hi Neil,

Thank you for pointing this out ( I also received an error notification
after the upload to PAUSE regarding the  Asterisk::Config namespace ). I
will follow-up with James and discuss how we are going to move forward with
resolving this conflict.

Best,
Charlie

Charlie Gonzalez
(E) itchar...@gmail.com
Github Profile 


On Tue, Aug 9, 2016 at 7:25 AM, Neil Bowers  wrote:

> Hi James & Charlie,
>
> 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.
>
> James has ownership of Asterisk::Config and Charlie has co-maint. This is
> part of the asterisk-perl distribution.
>
> It now conflicts with the Asterisk::config package, owned by PAUSE id
> HOOWA, and on CPAN in the Asterisk-config distribution.
>  These used to be distinct package names, but now they’re not.
>
> I think the easiest way to resolve this would be if you could rename
> Asterisk::Config to Asterisk::Configuration, or similar, and then update
> the modules currently in the Asterisk::Config:: namespace.
>
> PAUSE doesn’t let situations like this occur any more — I’m just working
> through the existing cases. I realise this is a PITA, so sorry for the
> hassle, and thanks in advance for helping tidy up some of the dusty corners
> of CPAN :-)
>
> The steps would be something like this:
>  - You do a release with renamed modules
>  - I can drop permissions on the old package names
>  - In a few days (once your release has made it to all CPAN mirrors), we
> can schedule the old releases for deletion
>(as they have the conflicting module in them).
>
> Cheers,
> Neil
>
>

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

[Audrey Tang]

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 has left us with some situations where two or more people 
> are owners of namespaces previously considered distinct, and now considered 
> the same.
> 
> One such case is the conflict between I18N::String (which BABF owns, and 
> DRTECH has co-maint on) and i18n::string (owned by AUDREYT, and four others 
> have co-maint). To resolve this, one of the package names needs to either be 
> removed from CPAN, or marked for non indexing. The immediately obvious 
> options I can see are:
> 
>   1. The I18N-String distribution doesn’t appear to install on recent 
> versions of Perl,
>  or on many older Perls either. See: 
> http://matrix.cpantesters.org/?dist=I18N-String 
> 
>  So maybe the distribution can be deleted from CPAN and I drop drop the 
> permissions?
>  I notice that the module name has been marked for HANDOFF as well.
> 
>   2. The i18n::string package is a “cuckoo package” defined in i18n.pm, in 
> the i18n distribution.
>  Given the public interface for i18n, I think it would be fine to hide 
> the i18n::string
>  from PAUSE (or you could rename it, of course).
> 
> Audrey, would you be happy to do a release, changing the package lines to:
> 
> package
>   i18n::string;
> 
> package
> i18n::var;
> 
> PAUSE doesn’t let situations like this occur any more — I’m working through 
> the historical cases, resolving conflicts.
> 
> Cheers,
> Neil
> 
> 
> 

User update for GFISH

[Perl Authors Upload Server]

Record update in the PAUSE users database:

 userid: [GFISH]
   fullname: [Gordon Fisher]
  asciiname: []
  email: [CENSORED]
   homepage: []
cpan_mail_alias: [secr] was [none]
ustatus: [unused]


Data were entered by GFISH (Gordon Fisher).
Please check if they are correct.

Thanks,
The Pause

Welcome new user GFISH

[Perl Authors Upload Server]

Welcome Gordon Fisher,

PAUSE, the Perl Authors Upload Server, has a userid for you:

GFISH

Once you've gone through the procedure of password approval (see the
separate mail you should receive about right now), this userid will be
the one that you can use to upload your work or edit your credentials
in the PAUSE database.

This is what we have stored in the database now:

  Name:  Gordon Fisher
  email: CENSORED
  homepage:  
  enteredby: David Golden

Please note that your email address is exposed in various listings and
database dumps. You can register with both a public and a secret email
if you want to protect yourself from SPAM. If you want to do this,
please visit
  https://pause.perl.org/pause/authenquery?ACTION=edit_cred
or
  http://pause.perl.org/pause/authenquery?ACTION=edit_cred

If you need any further information, please visit
  $CPAN/modules/04pause.html.
If this doesn't answer your questions, contact modules@perl.org.

Before uploading your first module, we strongly encourage you to discuss
your module idea on PrePAN at http://prepan.org/ to get feedback from
experienced Perl developers.

Thank you for your prospective contributions,
The Pause Team

PAUSE ID request (GFISH; Gordon Fisher)

[Perl Authors Upload Server]

Request to register new user

fullname: Gordon Fisher
  userid: GFISH
mail: CENSORED
homepage: 
 why:

I wish to become more active in development, testing, and bug
reporting/investigating/resolving/etc.


The following links are only valid for PAUSE maintainers:

Registration form with editing capabilities:
  
https://pause.perl.org/pause/authenquery?ACTION=add_user=a911_2a2df692bf0dc36c_pause99_add_user_sub=1
Immediate (one click) registration:
  
https://pause.perl.org/pause/authenquery?ACTION=add_user=a911_2a2df692bf0dc36c_pause99_add_user_Definitely=1

Re: PAUSE permissions conflict between your Text package and the TEXT package

[Neil Bowers]

Hi again Alexey,

> I’m one of the PAUSE admins. 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 “Text” namespace, which is used for the Text 
> package which is defined and used within your 
> Business::OnlinePayment::SurePay module. This now clashes with the TEXT 
> module, which is owned by user SHERZODR.
> 
> To resolve this conflict, the easiest change would be to rename the package 
> from “Text” to Business::OnlinePayment::SurePay::Text, which is the usual way 
> to name internal packages.
> 
> Or there is another option: I noticed that this module doesn’t work on any 
> version of Perl released in roughly the last 15 years:
>   http://matrix.cpantesters.org/?dist=Business-OnlinePayment-SurePay+0.01
> So another option would be to just delete this from CPAN and then drop your 
> permissions on the relevant namespaces.
> 
> Would you be happy to do one of these please? If you’re not interested in 
> maintaining this module any, are you ok for me to do this on your behalf?

Have you had a chance to look at this and think about which approach you’d like 
to take?

In addition to the suggestions above, you could just “hide” the Text package 
from PAUSE, by changing the line:

package Text;

to

package
Text;

Then I could drop your permissions on the Text namespace.

Cheers,
Neil

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

[Neil Bowers]

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

Cheers,
Neil

PAUSE permissions conflict between Settings and settings packages

[Neil Bowers]

Hi Mark,

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 considered the same.

You have ownership of the Settings package, which is defined in some of the 
example modules in the examples/ directory of your Spread-Message distribution. 
The package isn’t defined in the main module, but the documentation shows that 
you can put data in that namespace.

This conflicts with the “settings” package, which is owned by PAUSE user ALEXE.

The easiest way to resolve this would be to change your use of Settings to 
Spread::Message::Settings, so that everything is within your namespace.

Would you be happy to do a new release of Spread-Message with this change?

Cheers,
Neil

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

[Neil Bowers]

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 considered the same.

One such case is the conflict between I18N::String (which BABF owns, and DRTECH 
has co-maint on) and i18n::string (owned by AUDREYT, and four others have 
co-maint). To resolve this, one of the package names needs to either be removed 
from CPAN, or marked for non indexing. The immediately obvious options I can 
see are:

  1. The I18N-String distribution doesn’t appear to install on recent versions 
of Perl,
 or on many older Perls either. See: 
http://matrix.cpantesters.org/?dist=I18N-String
 So maybe the distribution can be deleted from CPAN and I drop drop the 
permissions?
 I notice that the module name has been marked for HANDOFF as well.

  2. The i18n::string package is a “cuckoo package” defined in i18n.pm, in the 
i18n distribution.
 Given the public interface for i18n, I think it would be fine to hide the 
i18n::string
 from PAUSE (or you could rename it, of course).

Audrey, would you be happy to do a release, changing the package lines to:

package
i18n::string;

package
i18n::var;

PAUSE doesn’t let situations like this occur any more — I’m working through the 
historical cases, resolving conflicts.

Cheers,
Neil

Welcome new user GRAVED

[Perl Authors Upload Server]

Welcome Andreas Schröter,

PAUSE, the Perl Authors Upload Server, has a userid for you:

GRAVED

Once you've gone through the procedure of password approval (see the
separate mail you should receive about right now), this userid will be
the one that you can use to upload your work or edit your credentials
in the PAUSE database.

This is what we have stored in the database now:

  Name:  Andreas Schröter
  email: CENSORED
  homepage:  
  enteredby: David Golden

Please note that your email address is exposed in various listings and
database dumps. You can register with both a public and a secret email
if you want to protect yourself from SPAM. If you want to do this,
please visit
  https://pause.perl.org/pause/authenquery?ACTION=edit_cred
or
  http://pause.perl.org/pause/authenquery?ACTION=edit_cred

If you need any further information, please visit
  $CPAN/modules/04pause.html.
If this doesn't answer your questions, contact modules@perl.org.

Before uploading your first module, we strongly encourage you to discuss
your module idea on PrePAN at http://prepan.org/ to get feedback from
experienced Perl developers.

Thank you for your prospective contributions,
The Pause Team

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

[Sam Tregar]

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 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.
>
> The HTML::Template module defines a number of inner classes, including
> HTML::Template::DEFAULT. These aren’t currently being indexed, because
> Michael (WONKO), who’s done the recent releases, doesn’t have permission
> for them. So HTML::Template::DEFAULT is still indexed against the last
> release SAMTREGAR did, 2.9.
>
> This now conflicts with HTML::Template::Default, which is owned by
> LEOCHARRE, and included in his HTML-Template-Default.
>
> Given these are inner classes, the easiest way to resolve this is to tell
> PAUSE not to index any of the inner classes. Then I’ll be able to drop
> SAMTREGAR’s ownership of HTML::Template::DEFAULT.
>
> The easiest way to do this is to add the following to dist.ini
>
> [MetaNoIndex]
> package = HTML::Template::COND
> package = HTML::Template::DEFAULT
> package = HTML::Template::ESCAPE
> package = HTML::Template::JSESCAPE
> package = HTML::Template::LOOP
> package = HTML::Template::NOOP
> package = HTML::Template::PRINTSCALAR
> package = HTML::Template::URLESCAPE
> package = HTML::Template::VAR
>
> I could then drop permissions on HTML::Template::DEFAULT, once there’s a
> new release on CPAN, we can schedule deletion of the old releases.
>
> Are you ok to do this?
>
> PAUSE doesn’t let situations like this occur any more — I’m working
> through the existing cases resolving them.
>
> Cheers,
> Neil
>
>

Re: PAUSE permissions conflict between your "config" package and core "Config"

[Neil Bowers]

Hi Hakan,

> I’m one of the PAUSE admins. 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 “config” namespace, and have a “config” module in 
> your DBIx-HTMLView-LATEST distribution. This conflicts with permissions for 
> the Config module, which is part of the core Perl distribution.
> 
> To resolve this, the best solution would probably be a new release, with the 
> config module renamed to DBIx::HTMLView::Config, or similar. Once you’ve done 
> that we can drop the permissions on “config”.
> 
> Or another option: I noticed that it hasn’t been released since 2001, and 
> doesn’t have any passing CPAN Testers results. So would it just be easiest to 
> delete this from CPAN entirely? If you want to go this way, I can do it for 
> you, and then will drop all the relevant permissions.
> 
> Which approach would you like to take?

Have you had a chance to have a look at this and think about the best way 
forward?

If I haven’t heard anything by the end of this week, I’ll go ahead and drop 
your permissions on the “config” namespace, to resolve the conflict with the 
core “Config” module.

Cheers,
Neil

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

[Neil Bowers]

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, and now considered the same.

The HTML::Template module defines a number of inner classes, including 
HTML::Template::DEFAULT. These aren’t currently being indexed, because Michael 
(WONKO), who’s done the recent releases, doesn’t have permission for them. So 
HTML::Template::DEFAULT is still indexed against the last release SAMTREGAR 
did, 2.9.

This now conflicts with HTML::Template::Default, which is owned by LEOCHARRE, 
and included in his HTML-Template-Default.

Given these are inner classes, the easiest way to resolve this is to tell PAUSE 
not to index any of the inner classes. Then I’ll be able to drop SAMTREGAR’s 
ownership of HTML::Template::DEFAULT.

The easiest way to do this is to add the following to dist.ini

[MetaNoIndex]
package = HTML::Template::COND
package = HTML::Template::DEFAULT
package = HTML::Template::ESCAPE
package = HTML::Template::JSESCAPE
package = HTML::Template::LOOP
package = HTML::Template::NOOP
package = HTML::Template::PRINTSCALAR
package = HTML::Template::URLESCAPE
package = HTML::Template::VAR

I could then drop permissions on HTML::Template::DEFAULT, once there’s a new 
release on CPAN, we can schedule deletion of the old releases.

Are you ok to do this?

PAUSE doesn’t let situations like this occur any more — I’m working through the 
existing cases resolving them.

Cheers,
Neil

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

[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 conflict with "file"

[Neil Bowers]

Hi Chitresh,

> 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 considered 
> the same.
> 
> You have ownership of the “file” namespace, and have a “file” module in your 
> link_NCBI distribution:
>   https://metacpan.org/release/link_NCBI
> This now conflicts with the “File” namespace, owned by ADAMK.
> 
> The link_NCBI zip file isn’t packaged as a proper CPAN distribution, and so 
> cannot be installed. As a result I’d like to propose that we resolve the 
> conflict by dropping your ownership of the “file” namespace. Furthermore, I’d 
> suggest that the link_NCBI.* files can be deleted from your CPAN author 
> directory as well.

Do you want to rename the modules in your distribution, or are you happy to 
delete it and for me to then drop the associated permissions? I can do all of 
these step for you, if you like?

If I don’t hear anything further, I’ll go ahead and drop your permissions on 
the “file” namespace, to resolve the conflict.

Cheers,
Neil

PAUSE ID request (GRAVED; Andreas Schröter)

[Perl Authors Upload Server]

Request to register new user

fullname: Andreas Schröter
  userid: GRAVED
mail: CENSORED
homepage: 
 why:

i would distribute a new perl::critic::policy


The following links are only valid for PAUSE maintainers:

Registration form with editing capabilities:
  
https://pause.perl.org/pause/authenquery?ACTION=add_user=8911_44ce3bc2ec4e7440_pause99_add_user_sub=1
Immediate (one click) registration:
  
https://pause.perl.org/pause/authenquery?ACTION=add_user=8911_44ce3bc2ec4e7440_pause99_add_user_Definitely=1

PAUSE permissions conflict between Asterisk::Config and Asterisk::config

[Neil Bowers]

Hi James & Charlie,

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.

James has ownership of Asterisk::Config and Charlie has co-maint. This is part 
of the asterisk-perl distribution.

It now conflicts with the Asterisk::config package, owned by PAUSE id HOOWA, 
and on CPAN in the Asterisk-config distribution.
 These used to be distinct package names, but now they’re not.

I think the easiest way to resolve this would be if you could rename 
Asterisk::Config to Asterisk::Configuration, or similar, and then update the 
modules currently in the Asterisk::Config:: namespace.

PAUSE doesn’t let situations like this occur any more — I’m just working 
through the existing cases. I realise this is a PITA, so sorry for the hassle, 
and thanks in advance for helping tidy up some of the dusty corners of CPAN :-)

The steps would be something like this:
 - You do a release with renamed modules
 - I can drop permissions on the old package names
 - In a few days (once your release has made it to all CPAN mirrors), we can 
schedule the old releases for deletion
   (as they have the conflicting module in them).

Cheers,
Neil

Re: PAUSE permissions conflict between your "config" package and core "Config"

[Neil Bowers]

Hi Hakan,

> DBIx-HTMLView is indeed obsolete by now, so please go ahead and delete it.

Thank you! I have scheduled deletion of the releases, and have dropped your 
permissions on the relevant namespaces.

Thanks for helping to tidy up CPAN.

Cheers,
Neil

Re: PAUSE permissions conflict between your "config" package and core "Config"

[Hakan Ardo]

Sorry for being unresponsive. DBIx-HTMLView is indeed obsolete by now, so
please go ahead and delete it.

On Tue, Aug 9, 2016 at 1:46 PM, Neil Bowers  wrote:

> Hi Hakan,
>
> > I’m one of the PAUSE admins. 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 “config” namespace, and have a “config” module
> in your DBIx-HTMLView-LATEST distribution. This conflicts with permissions
> for the Config module, which is part of the core Perl distribution.
> >
> > To resolve this, the best solution would probably be a new release, with
> the config module renamed to DBIx::HTMLView::Config, or similar. Once
> you’ve done that we can drop the permissions on “config”.
> >
> > Or another option: I noticed that it hasn’t been released since 2001,
> and doesn’t have any passing CPAN Testers results. So would it just be
> easiest to delete this from CPAN entirely? If you want to go this way, I
> can do it for you, and then will drop all the relevant permissions.
> >
> > Which approach would you like to take?
>
> Have you had a chance to have a look at this and think about the best way
> forward?
>
> If I haven’t heard anything by the end of this week, I’ll go ahead and
> drop your permissions on the “config” namespace, to resolve the conflict
> with the core “Config” module.
>
> Cheers,
> Neil
>
>


-- 
Håkan Ardö