The copy of 06perms.txt that I had on my machine (pulled last night) only
had LDS listed for Bio::Graphics::DrawTransmembrane, but after pulling a
fresh copy of the file, you are listed. Did you just have LDS give you
permissions in the last day? If so, metacpan could have also been working
with a similarly out-of-date file.

The version number issue appears to be totally separate -- you need to
either have the older distributions deleted on PAUSE (LDS needs to do
this), and then have PAUSE re-index your distribution at pause.perl.org, or
you need to do a new release where the versions are higher than in the
previous release.


On Thu, Dec 15, 2016 at 9:43 PM, Fields, Christopher J <
cjfie...@illinois.edu> wrote:

> Hi Karen,
>
> That’s odd, I’m logged into PAUSE and when I checked those using ‘View
> Permissions' I see myself listed as co-maint.  For instance, 
> Bio::Graphics::DrawTransmembrane
> lists LDS as owner but me as co-maint (see below, apologies for HTML table
> paste).
>
> *module* *userid* *type* *owner*
> Bio::Graphics::DrawTransmembrane
> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Bio::Graphics::DrawTransmembrane&pause99_peek_perms_sub=1>
> CJFIELDS
> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=a&pause99_peek_perms_query=CJFIELDS&pause99_peek_perms_sub=1>
> co-maint LDS
> Bio::Graphics::DrawTransmembrane
> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Bio::Graphics::DrawTransmembrane&pause99_peek_perms_sub=1>
> LDS
> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=a&pause99_peek_perms_query=LDS&pause99_peek_perms_sub=1>
> first-come LDS
> Bio::Graphics::DrawTransmembrane
> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Bio::Graphics::DrawTransmembrane&pause99_peek_perms_sub=1>
> SENDU
> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=a&pause99_peek_perms_query=SENDU&pause99_peek_perms_sub=1>
> co-maint LDS
> Bio::Graphics::DrawTransmembrane
> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Bio::Graphics::DrawTransmembrane&pause99_peek_perms_sub=1>
> STAJICH
> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=a&pause99_peek_perms_query=STAJICH&pause99_peek_perms_sub=1>
> co-maint LDS
>
> I can forward the PAUSE email directly to you if that works.
>
> chris
>
>
> From: <ka...@froods.org> on behalf of Karen Etheridge <p...@froods.org>
> Date: Thursday, December 15, 2016 at 11:36 PM
> To: Chris Fields <cjfie...@illinois.edu>
> Cc: Perl Module Authors List <module-authors@perl.org>
> Subject: Re: Bio-Graphics issues
>
> It would help to see the mail from PAUSE that lists the errors. But the
> modules listed as "unauthorized" on the metacpanm page are indeed modules
> for which you do not have comaint permissions in the PAUSE database (I did
> not check them all, but all of those I did were modules where only LDS had
> permissions).
>
> On Thu, Dec 15, 2016 at 9:26 PM, Fields, Christopher J <
> cjfie...@illinois.edu> wrote:
>
>> I have co-maint on the Bio-Graphics distribution with Lincoln Stein
>> (LDS).  I just tried releasing a simple point update to Bio-Graphics for
>> dependency issues, but the distribution has several modules that appear to
>> be unauthorized (even though I am listed as a co-maintainer of those).  Any
>> idea why?
>>
>> https://metacpan.org/release/CJFIELDS/Bio-Graphics-2.40
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__metacpan.org_release_CJFIELDS_Bio-2DGraphics-2D2.40&d=DQMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=fbHa8Njtvh9VmSnzJxiEUTW9NWDwMMwQAzhgZDO41GQ&m=B5bZSVWgl2U5nhWl8DjMaALOMXOKQCCx4RgnsxJMbtM&s=rOjjnjLfLUPUX7pU0FwijKUhY8tZM-xeGQzMZ9GZnpc&e=>
>>
>> I did get an email about failed indexing of some of the modules but these
>> seem to be primarily from modules having no versions (the dist as currently
>> set up gets the version from the Bio::Graphics module).  But there isn’t
>> any congruence with the failed modules and those showing as unauthorized in
>> the above link.
>>
>> Thanks,
>>
>> chris
>>
>
>

Reply via email to