Skip Menu |

This queue is for tickets about the WWW-Facebook-API CPAN distribution.

Report information
The Basics
Id: 48937
Status: resolved
Priority: 0/
Queue: WWW-Facebook-API

People
Owner: Nobody in particular
Requestors: frequency [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.4.15
Fixed in: 0.4.15



Subject: Unauthorized Release?
Hi: The latest version of WWW::Facebook::API is marked as an unauthorized release: http://search.cpan.org/~unobe/WWW-Facebook-API-0.4.15/ We have this package in Debian and have difficulty updating it since it's an unauthorized release. It's probably most appropriate to change the permissions to allow co-maintainership? Cheers, Jonathan
From: frequency [...] cpan.org
On Sat Aug 22 18:21:57 2009, FREQUENCY wrote: Show quoted text
> Hi: > > The latest version of WWW::Facebook::API is marked as an unauthorized > release: http://search.cpan.org/~unobe/WWW-Facebook-API-0.4.15/ > > We have this package in Debian and have difficulty updating it since > it's an unauthorized release. It's probably most appropriate to change > the permissions to allow co-maintainership? > > Cheers, > > Jonathan
Oops, I just noticed on the RT that UNOBE is a designated co-maintainer. So I guess this needs a re-indexing from PAUSE. If you still have issues I'd suggest contacting modules@perl.org about it
Subject: Re: [rt.cpan.org #48937] Unauthorized Release?
Date: Sat, 22 Aug 2009 22:06:59 -0700
To: Jonathan Yu via RT <bug-WWW-Facebook-API [...] rt.cpan.org>
From: David Romano <unobe [...] cpan.org>
Hi Jonathan, Jonathan Yu via RT wrote on Sat, Aug 22, 2009 at 03:21:58PM PDT: Show quoted text
> The latest version of WWW::Facebook::API is marked as an unauthorized > release: http://search.cpan.org/~unobe/WWW-Facebook-API-0.4.15/ > > We have this package in Debian and have difficulty updating it since > it's an unauthorized release. It's probably most appropriate to change > the permissions to allow co-maintainership?
Thanks for the heads-up on this. Under "View Permissions" on my Pause account, I am listed as first-come for WWW::Facebook::API and a handful of other sub-namespaces. When I searched for a module -- exact match -- there are three userid's who show, CLSCOTT, SOCK, and UNOBE (the first two are listed as co-maint, and I'm listed as first-come). I don't know where to go from here. Should I contact the PAUSE administrator? - David
Subject: Re: [rt.cpan.org #48937] Unauthorized Release?
Date: Sat, 22 Aug 2009 22:09:33 -0700
To: Jonathan Yu via RT <bug-WWW-Facebook-API [...] rt.cpan.org>
From: David Romano <unobe [...] cpan.org>
Hello again, I just noticed that Admin, Application, and SMS are the three submodules that are listed as UNAUTHORIZED. Weird. I remember giving co-maint to CLSCOTT and he made a new release with those three submodules, so I'll e-mail him to see if I can get co-main. Blech. - David
Subject: Re: [rt.cpan.org #48937] Unauthorized Release?
Date: Sun, 23 Aug 2009 01:13:26 -0400
To: bug-WWW-Facebook-API [...] rt.cpan.org
From: Jonathan Yu <frequency [...] cpan.org>
I am not an expert but reindexing after fixing permissions will probably do it On 8/23/09, unobe@cpan.org via RT <bug-WWW-Facebook-API@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=48937 > > > Hello again, > > I just noticed that Admin, Application, and SMS are the three submodules > that > are listed as UNAUTHORIZED. Weird. I remember giving co-maint to CLSCOTT and > he made a new release with those three submodules, so I'll e-mail him to > see > if I can get co-main. Blech. > > - David > > >
-- Sent from Gmail for mobile | mobile.google.com
Subject: Re: [rt.cpan.org #48937] Unauthorized Release?
Date: Sat, 22 Aug 2009 22:22:14 -0700
To: Jonathan Yu via RT <bug-WWW-Facebook-API [...] rt.cpan.org>
From: David Romano <unobe [...] cpan.org>
Hi Jonathan, Jonathan Yu via RT wrote on Sat, Aug 22, 2009 at 03:24:22PM PDT: Show quoted text
> Oops, I just noticed on the RT that UNOBE is a designated co-maintainer. > So I guess this needs a re-indexing from PAUSE. If you still have issues > I'd suggest contacting modules@perl.org about it
Thanks. I shot off an e-mail to modules@perl.org. Hopefully it will be fixed soon. - David