You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@perl.apache.org by Randy Kobes <ra...@theoryx5.uwinnipeg.ca> on 2005/10/26 04:17:04 UTC
PAUSE permissions
I think this has been noticed before, but currently
the CPAN.pm shell doesn't recognize the latest mp2
release, because of permissions problems. I think
what has to happen (which should all be doable
through the PAUSE web page) is for co-ownership of
these packages be granted to PGOLLUCCI, and then
the mp2 2.0.2 package be reindexed.
--
best regards,
randy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: PAUSE permissions
Posted by "Philip M. Gollucci" <pg...@p6m7g8.com>.
Stas Bekman wrote:
>> Status: Permission missing
>> ==========================
>>
>> module: ModPerl::PerlRunPrefork
>> version: 0.01
>> in file:
>> mod_perl-2.0.2/ModPerl-Registry/lib/ModPerl/PerlRunPrefork.pm
>> status: Not indexed because permissions missing. Visit PAUSE and
>> click "View Permissions" to find the legitimate
>> maintainer(s).
>>
>> module: ModPerl::RegistryPrefork
>> version: 0.01
>> in file:
>> mod_perl-2.0.2/ModPerl-Registry/lib/ModPerl/RegistryPrefork.pm
>> status: Not indexed because permissions missing. Visit PAUSE and
>> click "View Permissions" to find the legitimate
>> maintainer(s).
>
>
> Whoever made the released that added these two packages had to figure
> out that those were new packages, go to PAUSE and re-add perms to APML
> (and probably all the co-maintainers). And that's entirely not their
> fault that they didn't do it. Go figure out what are the new files in a
> hundred of existing packages.
>
> This will keep on happening *all the time* until PAUSE will either treat
> perms per all files in the tar-ball and not individually or figure out
> how to automatically re-adjust perms for those newly added packages. At
> the very least the indexer needs to alert the submitter that there were
> new packages added and suggest to check whether others need to get perms
> to it, hopefully provide a one-click link to accomplish the task.
For reference, I believe that was 2.0.0 or RC6.
--
END
------------------------------------------------------------
What doesn't kill us can only make us stronger.
Nothing is impossible.
Philip M. Gollucci (pgollucci@p6m7g8.com) 301.254.5198
Consultant / http://p6m7g8.net/Resume/
Senior Developer / Liquidity Services, Inc.
http://www.liquidityservicesinc.com
http://www.liquidation.com
http://www.uksurplus.com
http://www.govliquidation.com
http://www.gowholesale.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: PAUSE permissions
Posted by Stas Bekman <st...@stason.org>.
Andreas J. Koenig wrote:
[...]
> > Do you think it'd be helpful if I could invest some time in helping with
> > that issue (granted I'm not familiar with pause code)?
>
> I'd start turning my mail into two scripts:
>
> 1. Write a script to find out if there are any packages in the current
> modperl release that are not owned by APML. Write the URLs needed
> to resolve offending packages and send each URL to the respective
> owner.
The problem is that the script requires login/passwd to PAUSE and it'll
have to do screen scraping to get the information. Why doing screen
scraping when someone has an access to the database.
> 2. Before a release make the release manager co-maintainer of all
> APML-owned packages. Do it manually or with a Mech script.
again, this is far from trivial, if you have to do screen scraping. Unless
there is some magical publicly accessible PAUSE API that I'm not aware of.
> > I'd start with a simple suggestion I've suggested in the last
> > email:
>
> > step1: when a package containing new modules is submitted: the indexer
> > needs to alert the submitter that there were new packages added and
> > suggest to check whether others need to get perms to it, hopefully provide
> > a one-click link to accomplish the task."
>
> For my taste, far too complicated and too APML-centric.
I suppose it is if mod_perl is the only project that uses groups. However
a bunch of other Apache- modules and dev communities around those suffer
from the same issue.
since APML is not the only one, writing this script won't help other
projects, since they won't know it even exists.
> > step2: when a package is submitted by another developer, who for some
> > reason doesn't have perms for some of the modules, the indexer could
> > suggest one-click link to fix the problem. It could suggest emailing the
> > person who have added the package in first place and have a list of ready
> > links to click for them to fix the problem. all this can be automated and
> > will save everybody a lot of time.
>
> Ditto
>
> > Does this sound like a lot of work? it doesn't solve the problem, but it
> > suggests to automate all the steps that you've described in this email,
> > and saves your time, Andreas.
>
> I'm not fond of adding any code to PAUSE infrastructure that doesn't
> actually solve problems and must then be maintained. Please consider
> the two scripts I suggest above. They seem pretty trivial to me.
--
_____________________________________________________________
Stas Bekman mailto:stas@stason.org http://stason.org/
MailChannels: Assured Messaging(TM) http://mailchannels.com/
The "Practical mod_perl" book http://modperlbook.org/
http://perl.apache.org/ http://perl.org/ http://logilune.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: PAUSE permissions
Posted by Stas Bekman <st...@stason.org>.
Andreas J. Koenig wrote:
>>>>>>On Wed, 26 Oct 2005 22:32:45 -0700, Stas Bekman <st...@stason.org> said:
>
>
> > Whoever made the released that added these two packages had to figure out
> > that those were new packages, go to PAUSE and re-add perms to APML (and
> > probably all the co-maintainers). And that's entirely not their fault that
> > they didn't do it. Go figure out what are the new files in a hundred of
> > existing packages.
>
> > This will keep on happening *all the time* until PAUSE will either treat
> > perms per all files in the tar-ball and not individually or figure out how
> > to automatically re-adjust perms for those newly added packages. At the
> > very least the indexer needs to alert the submitter that there were new
> > packages added and suggest to check whether others need to get perms to
> > it, hopefully provide a one-click link to accomplish the task.
>
> ****
> I know how much this sucks, its nothing new to me and I will
> fix it but there are still other more urgent and less
> complicated things to fix
> ****
>
> I once again must point out that the sucking factor is not as high as
> it is sometimes believed given these facts:
>
> * Two modules in a hundred not being indexed is not the heaven falling
> down. It does not really hurt anybody.
>
> * The mail from the indexer that Philip was citing is providing
> exactly the information you are looking for.
>
> * You go to PAUSE and ask it about the offending packages like so:
>
> https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_sub=Submit&pause99_peek_perms_query=ModPerl::PerlRunPrefork
>
> Answer is: GOZER
>
> https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_sub=Submit&pause99_peek_perms_query=ModPerl::RegistryPrefork
>
> Answer is: GOZER
>
> This is hardly rocket science.
>
> * GOZER has an interface on PAUSE to pass the ownership to APML with a
> single click. (I just did that for him, it took me 1 minute)
>
> -- Every uploader has a chance to do this step immediately after he
> gets the mail from the indexer, making the sucking factor even
> smaller for the next release.
>
> * You (and maybe others? I do not remember) have an interface on PAUSE
> to make Philip co-maintainer for all APML modules with a single
> click. (I just did that for you, it took me 1 minute)
>
> * Philip has an interface to reindex the file with a single keystroke
> (I just did that for him, it took me less than a minute)
>
> * I repeat: Yes, this sucks. So please keep this email around. It
> sucks less if you know how it currently works.
Andreas, I know the workarounds, but for some reason we keep getting to
that issue every few months (may be because not everybody knows them).
Really, I'm more concerned with your time you've wasted on fixing those
issues. And time of all involved, all combined could have probably fixed
the issue long time ago.
Do you think it'd be helpful if I could invest some time in helping with
that issue (granted I'm not familiar with pause code)? I'd start with a
simple suggestion I've suggested in the last email:
step1: when a package containing new modules is submitted: the indexer
needs to alert the submitter that there were new packages added and
suggest to check whether others need to get perms to it, hopefully provide
a one-click link to accomplish the task."
step2: when a package is submitted by another developer, who for some
reason doesn't have perms for some of the modules, the indexer could
suggest one-click link to fix the problem. It could suggest emailing the
person who have added the package in first place and have a list of ready
links to click for them to fix the problem. all this can be automated and
will save everybody a lot of time.
Does this sound like a lot of work? it doesn't solve the problem, but it
suggests to automate all the steps that you've described in this email,
and saves your time, Andreas.
--
_____________________________________________________________
Stas Bekman mailto:stas@stason.org http://stason.org/
MailChannels: Assured Messaging(TM) http://mailchannels.com/
The "Practical mod_perl" book http://modperlbook.org/
http://perl.apache.org/ http://perl.org/ http://logilune.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: PAUSE permissions
Posted by Stas Bekman <st...@stason.org>.
Philip M. Gollucci wrote:
> Philip M. Gollucci wrote:
>
>> Stas Bekman wrote:
>>
>>> Assuming that you have the APML karma, here is how to do it.
>>>
>>> 1) login into https://pause.perl.org
>>> 2) menu click: Select Mailinglist/Action
>>> 3) choose APML and share_perms and click go
>>> 4) click 3.1 Make somebody else co-maintainer
>>> 5) choose the modules to give the perms to
>>> type the username of the new co-maintainer
>>>
>>> and you are done. (I guess you want to save that somewhere, RELEASE
>>> file?)
>>>
>>> I've done the above for Philip, but it said that he already had these
>>> perms. So if Philip still can't index then you need to contact Andreas.
>>
>>
>> I'll add to RELEASE file as I already made a note to prevent mishaps
>> in the future.
>>
>> I just scheduled a re-index also.
>
> No dice. Or I should say, so close but not quite. Looks like only 2 of
> them failed.
>
> I've cc'ed Andreas.
>
> ---- indexer report ----
>
> The following report has been written by the PAUSE namespace indexer.
> Please contact modules@perl.org if there are any open questions.
> Id: mldistwatch 645 2005-09-19 06:41:20Z k
>
> User: PGOLLUCCI (Philip M. Gollucci)
> Distribution file: mod_perl-2.0.2.tar.gz
> Number of files: 968
> *.pm files: 313
> README: mod_perl-2.0.2/README
> META.yml: mod_perl-2.0.2/META.yml
> Timestamp of file: Fri Oct 21 01:27:23 2005 UTC
> Time of this run: Thu Oct 27 03:58:24 2005 UTC
>
> The following packages (grouped by status) have been found in the distro:
>
> Status: Permission missing
> ==========================
>
> module: ModPerl::PerlRunPrefork
> version: 0.01
> in file: mod_perl-2.0.2/ModPerl-Registry/lib/ModPerl/PerlRunPrefork.pm
> status: Not indexed because permissions missing. Visit PAUSE and
> click "View Permissions" to find the legitimate
> maintainer(s).
>
> module: ModPerl::RegistryPrefork
> version: 0.01
> in file: mod_perl-2.0.2/ModPerl-Registry/lib/ModPerl/RegistryPrefork.pm
> status: Not indexed because permissions missing. Visit PAUSE and
> click "View Permissions" to find the legitimate
> maintainer(s).
Whoever made the released that added these two packages had to figure out
that those were new packages, go to PAUSE and re-add perms to APML (and
probably all the co-maintainers). And that's entirely not their fault that
they didn't do it. Go figure out what are the new files in a hundred of
existing packages.
This will keep on happening *all the time* until PAUSE will either treat
perms per all files in the tar-ball and not individually or figure out how
to automatically re-adjust perms for those newly added packages. At the
very least the indexer needs to alert the submitter that there were new
packages added and suggest to check whether others need to get perms to
it, hopefully provide a one-click link to accomplish the task.
--
_____________________________________________________________
Stas Bekman mailto:stas@stason.org http://stason.org/
MailChannels: Assured Messaging(TM) http://mailchannels.com/
The "Practical mod_perl" book http://modperlbook.org/
http://perl.apache.org/ http://perl.org/ http://logilune.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: PAUSE permissions
Posted by "Philip M. Gollucci" <pg...@p6m7g8.com>.
Philip M. Gollucci wrote:
> Stas Bekman wrote:
>
>> Assuming that you have the APML karma, here is how to do it.
>>
>> 1) login into https://pause.perl.org
>> 2) menu click: Select Mailinglist/Action
>> 3) choose APML and share_perms and click go
>> 4) click 3.1 Make somebody else co-maintainer
>> 5) choose the modules to give the perms to
>> type the username of the new co-maintainer
>>
>> and you are done. (I guess you want to save that somewhere, RELEASE
>> file?)
>>
>> I've done the above for Philip, but it said that he already had these
>> perms. So if Philip still can't index then you need to contact Andreas.
>
> I'll add to RELEASE file as I already made a note to prevent mishaps in
> the future.
>
> I just scheduled a re-index also.
No dice. Or I should say, so close but not quite. Looks like only 2 of them
failed.
I've cc'ed Andreas.
---- indexer report ----
The following report has been written by the PAUSE namespace indexer.
Please contact modules@perl.org if there are any open questions.
Id: mldistwatch 645 2005-09-19 06:41:20Z k
User: PGOLLUCCI (Philip M. Gollucci)
Distribution file: mod_perl-2.0.2.tar.gz
Number of files: 968
*.pm files: 313
README: mod_perl-2.0.2/README
META.yml: mod_perl-2.0.2/META.yml
Timestamp of file: Fri Oct 21 01:27:23 2005 UTC
Time of this run: Thu Oct 27 03:58:24 2005 UTC
The following packages (grouped by status) have been found in the distro:
Status: Permission missing
==========================
module: ModPerl::PerlRunPrefork
version: 0.01
in file: mod_perl-2.0.2/ModPerl-Registry/lib/ModPerl/PerlRunPrefork.pm
status: Not indexed because permissions missing. Visit PAUSE and
click "View Permissions" to find the legitimate
maintainer(s).
module: ModPerl::RegistryPrefork
version: 0.01
in file: mod_perl-2.0.2/ModPerl-Registry/lib/ModPerl/RegistryPrefork.pm
status: Not indexed because permissions missing. Visit PAUSE and
click "View Permissions" to find the legitimate
maintainer(s).
Status: Successfully indexed
============================
module: APR
version: 0.009000
in file: mod_perl-2.0.2/xs/APR/APR/APR.pm
status: indexed
module: APR::Base64
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::Brigade
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::Bucket
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::BucketAlloc
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::BucketType
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::Const
version: 0.009000
in file: mod_perl-2.0.2/xs/APR/Const/Const.pm
status: indexed
module: APR::Date
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::Error
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::Finfo
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::FunctionTable
version: undef
in file: mod_perl-2.0.2/xs/tables/current/APR/FunctionTable.pm
status: indexed
module: APR::IpSubnet
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::OS
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::PerlIO
version: 0.009000
in file: mod_perl-2.0.2/xs/APR/PerlIO/PerlIO.pm
status: indexed
module: APR::Pool
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::SockAddr
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::Socket
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::Status
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::String
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::Table
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::ThreadMutex
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::URI
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::UUID
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::Util
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: APR::XSLoader
version: undef
in file: mod_perl-2.0.2/lib/APR/XSLoader.pm
status: indexed
module: Apache2::Access
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::Build
version: 0.01
in file: mod_perl-2.0.2/lib/Apache2/Build.pm
status: indexed
module: Apache2::CmdParms
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::Command
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::Connection
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::Const
version: undef
in file: mod_perl-2.0.2/xs/Apache2/Const/Const.pm
status: indexed
module: Apache2::ConstantsTable
version: undef
in file: mod_perl-2.0.2/xs/tables/current/Apache2/ConstantsTable.pm
status: indexed
module: Apache2::Directive
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::Filter
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::FilterRec
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::FunctionTable
version: undef
in file: mod_perl-2.0.2/xs/tables/current/Apache2/FunctionTable.pm
status: indexed
module: Apache2::HookRun
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::Log
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::MPM
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::Module
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::ParseSource
version: 0.02
in file: mod_perl-2.0.2/lib/Apache2/ParseSource.pm
status: indexed
module: Apache2::ParseSource::Scan
version: 0.02
in file: mod_perl-2.0.2/lib/Apache2/ParseSource.pm
status: indexed
module: Apache2::PerlSections
version: 2.00
in file: mod_perl-2.0.2/lib/Apache2/PerlSections.pm
status: indexed
module: Apache2::PerlSections::Dump
version: 0.01
in file: mod_perl-2.0.2/lib/Apache2/PerlSections/Dump.pm
status: indexed
module: Apache2::Process
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::Reload
version: 0.09
in file: mod_perl-2.0.2/lib/Apache2/Reload.pm
status: indexed
module: Apache2::RequestIO
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::RequestRec
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::RequestUtil
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::Resource
version: 1.72
in file: mod_perl-2.0.2/lib/Apache2/Resource.pm
status: indexed
module: Apache2::Response
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::ServerRec
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::ServerUtil
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::SizeLimit
version: 0.05
in file: mod_perl-2.0.2/lib/Apache2/SizeLimit.pm
status: indexed
module: Apache2::SourceTables
version: undef
in file: mod_perl-2.0.2/lib/Apache2/SourceTables.pm
status: indexed
module: Apache2::Status
version: 4.00
in file: mod_perl-2.0.2/lib/Apache2/Status.pm
status: indexed
module: Apache2::Status::_version
version: 4.00
in file: mod_perl-2.0.2/lib/Apache2/Status.pm
status: indexed
module: Apache2::StructureTable
version: undef
in file: mod_perl-2.0.2/xs/tables/current/Apache2/StructureTable.pm
status: indexed
module: Apache2::SubProcess
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::SubRequest
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::URI
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::Util
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: Apache2::XSLoader
version: undef
in file: mod_perl-2.0.2/lib/Apache2/XSLoader.pm
status: indexed
module: Apache2::compat
version: undef
in file: mod_perl-2.0.2/lib/Apache2/compat.pm
status: indexed
module: Apache2::porting
version: undef
in file: mod_perl-2.0.2/lib/Apache2/porting.pm
status: indexed
module: Bundle::Apache2
version: 1.00
in file: mod_perl-2.0.2/lib/Bundle/Apache2.pm
status: indexed
module: ModPerl::BuildMM
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/BuildMM.pm
status: indexed
module: ModPerl::BuildOptions
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/BuildOptions.pm
status: indexed
module: ModPerl::CScan
version: 0.75
in file: mod_perl-2.0.2/lib/ModPerl/CScan.pm
status: indexed
module: ModPerl::Code
version: 0.01
in file: mod_perl-2.0.2/lib/ModPerl/Code.pm
status: indexed
module: ModPerl::Config
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/Config.pm
status: indexed
module: ModPerl::Const
version: undef
in file: mod_perl-2.0.2/xs/ModPerl/Const/Const.pm
status: indexed
module: ModPerl::FunctionMap
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/FunctionMap.pm
status: indexed
module: ModPerl::FunctionTable
version: undef
in file: mod_perl-2.0.2/xs/tables/current/ModPerl/FunctionTable.pm
status: indexed
module: ModPerl::Global
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: ModPerl::MM
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/MM.pm
status: indexed
module: ModPerl::Manifest
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/Manifest.pm
status: indexed
module: ModPerl::MapBase
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/MapUtil.pm
status: indexed
module: ModPerl::MapUtil
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/MapUtil.pm
status: indexed
module: ModPerl::MethodLookup
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: ModPerl::ParseSource
version: 0.01
in file: mod_perl-2.0.2/lib/ModPerl/ParseSource.pm
status: indexed
module: ModPerl::PerlRun
version: 1.99
in file: mod_perl-2.0.2/ModPerl-Registry/lib/ModPerl/PerlRun.pm
status: indexed
module: ModPerl::Registry
version: 1.99
in file: mod_perl-2.0.2/ModPerl-Registry/lib/ModPerl/Registry.pm
status: indexed
module: ModPerl::RegistryBB
version: 1.99
in file: mod_perl-2.0.2/ModPerl-Registry/lib/ModPerl/RegistryBB.pm
status: indexed
module: ModPerl::RegistryCooker
version: 1.99
in file: mod_perl-2.0.2/ModPerl-Registry/lib/ModPerl/RegistryCooker.pm
status: indexed
module: ModPerl::RegistryLoader
version: undef
in file: mod_perl-2.0.2/ModPerl-Registry/lib/ModPerl/RegistryLoader.pm
status: indexed
module: ModPerl::StructureMap
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/StructureMap.pm
status: indexed
module: ModPerl::TestConfig
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/TestRun.pm
status: indexed
module: ModPerl::TestReport
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/TestReport.pm
status: indexed
module: ModPerl::TestRun
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/TestRun.pm
status: indexed
module: ModPerl::TypeMap
version: undef
in file: mod_perl-2.0.2/lib/ModPerl/TypeMap.pm
status: indexed
module: ModPerl::Util
version: 0.009
in file: mod_perl-2.0.2/lib/ModPerl/DummyVersions.pm
status: indexed
module: ModPerl::WrapXS
version: 0.01
in file: mod_perl-2.0.2/lib/ModPerl/WrapXS.pm
status: indexed
module: mod_perl2
version: 2.000002
in file: mod_perl-2.0.2/lib/mod_perl2.pm
status: indexed
__END__
--
END
------------------------------------------------------------
What doesn't kill us can only make us stronger.
Nothing is impossible.
Philip M. Gollucci (pgollucci@p6m7g8.com) 301.254.5198
Consultant / http://p6m7g8.net/Resume/
Senior Developer / Liquidity Services, Inc.
http://www.liquidityservicesinc.com
http://www.liquidation.com
http://www.uksurplus.com
http://www.govliquidation.com
http://www.gowholesale.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: PAUSE permissions
Posted by "Philip M. Gollucci" <pg...@p6m7g8.com>.
Stas Bekman wrote:
> Assuming that you have the APML karma, here is how to do it.
>
> 1) login into https://pause.perl.org
> 2) menu click: Select Mailinglist/Action
> 3) choose APML and share_perms and click go
> 4) click 3.1 Make somebody else co-maintainer
> 5) choose the modules to give the perms to
> type the username of the new co-maintainer
>
> and you are done. (I guess you want to save that somewhere, RELEASE file?)
>
> I've done the above for Philip, but it said that he already had these
> perms. So if Philip still can't index then you need to contact Andreas.
I'll add to RELEASE file as I already made a note to prevent mishaps in the future.
I just scheduled a re-index also.
--
END
------------------------------------------------------------
What doesn't kill us can only make us stronger.
Nothing is impossible.
Philip M. Gollucci (pgollucci@p6m7g8.com) 301.254.5198
Consultant / http://p6m7g8.net/Resume/
Senior Developer / Liquidity Services, Inc.
http://www.liquidityservicesinc.com
http://www.liquidation.com
http://www.uksurplus.com
http://www.govliquidation.com
http://www.gowholesale.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: PAUSE permissions
Posted by Stas Bekman <st...@stason.org>.
Randy Kobes wrote:
> On Wed, 26 Oct 2005, Geoffrey Young wrote:
>
>> I went to pause and selected "3.1 Make somebody else co-maintainer"
>> but no
>> mod_perl modules showed up in my list. so I'm not sure there's
>> anything I
>> alone can do...
>
>
> I would assume Andreas could do this, but, for future
> reference, it may be Stas that has that ability?
Assuming that you have the APML karma, here is how to do it.
1) login into https://pause.perl.org
2) menu click: Select Mailinglist/Action
3) choose APML and share_perms and click go
4) click 3.1 Make somebody else co-maintainer
5) choose the modules to give the perms to
type the username of the new co-maintainer
and you are done. (I guess you want to save that somewhere, RELEASE file?)
I've done the above for Philip, but it said that he already had these
perms. So if Philip still can't index then you need to contact Andreas.
--
_____________________________________________________________
Stas Bekman mailto:stas@stason.org http://stason.org/
MailChannels: Assured Messaging(TM) http://mailchannels.com/
The "Practical mod_perl" book http://modperlbook.org/
http://perl.apache.org/ http://perl.org/ http://logilune.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: PAUSE permissions
Posted by Randy Kobes <ra...@theoryx5.uwinnipeg.ca>.
On Wed, 26 Oct 2005, Geoffrey Young wrote:
> I went to pause and selected "3.1 Make somebody else co-maintainer" but no
> mod_perl modules showed up in my list. so I'm not sure there's anything I
> alone can do...
I would assume Andreas could do this, but, for future
reference, it may be Stas that has that ability?
--
best regards,
randy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: PAUSE permissions
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
Randy Kobes wrote:
> I think this has been noticed before, but currently
> the CPAN.pm shell doesn't recognize the latest mp2
> release, because of permissions problems. I think
> what has to happen (which should all be doable
> through the PAUSE web page) is for co-ownership of
> these packages be granted to PGOLLUCCI, and then
> the mp2 2.0.2 package be reindexed.
hmm...
I went to pause and selected "3.1 Make somebody else co-maintainer" but no
mod_perl modules showed up in my list. so I'm not sure there's anything I
alone can do...
does andreas need to fix this himself?
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org
Re: PAUSE permissions
Posted by "Philip M. Gollucci" <pg...@p6m7g8.com>.
Randy Kobes wrote:
> I think this has been noticed before, but currently
> the CPAN.pm shell doesn't recognize the latest mp2
> release, because of permissions problems. I think
> what has to happen (which should all be doable
> through the PAUSE web page) is for co-ownership of
> these packages be granted to PGOLLUCCI, and then
> the mp2 2.0.2 package be reindexed.
I'll schedule the re-indexing as soon as someone does that.
-- Crap, I caught the A-T error which Andreas fixed . I thought the mp2 one
went okay.
--
END
------------------------------------------------------------
What doesn't kill us can only make us stronger.
Nothing is impossible.
Philip M. Gollucci (pgollucci@p6m7g8.com) 301.254.5198
Consultant / http://p6m7g8.net/Resume/
Senior Developer / Liquidity Services, Inc.
http://www.liquidityservicesinc.com
http://www.liquidation.com
http://www.uksurplus.com
http://www.govliquidation.com
http://www.gowholesale.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org