headers
Michael Gauthier | 1 Aug 2011 21:15
Favicon
Gravatar

Re: Crypt_GPG: Retrieving passphrase

Hi Randy,

You can't programmatically retrieve a key's passphrase. Passphrases are 
supposed to be secret and secure, so GnuPG will never reveal it for you.

It sounds like the key you used to encrypt data requires a passphrase to 
decrypt. The docs say the passphrase is optional for addDecryptKey 
because you can have an encryption key without a passphrase.

If you've used a key that requires a passphrase to decrypt, the 
passphrase is required in addDecryptKey.

Hope this helps.

Cheers,
Mike

On 2011-08-01 16:05, Brown, Randy wrote:
> Hi –
>
> I’ve not tracked down a method for retrieving the key’s passphrase. I
> need this in order to be able to dynamically select from a group of keys
> to decrypt a file. The docs say this is an optional param to
> addDecryptKey, but the ‘No passphrase provided for keys’ error is thrown
> without.
>
> Can you help?
>
> Thanks,
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
ivo nascimento | 2 Aug 2011 16:27
Picon
Gravatar

candidate package Console_Color2 to Pear2

Hi,
I develop a package candidate to a new version of Console_Color (
Console_Color2 ) for pear2 system
and like to know how to procced to send a proposal for pear2 or directly
send the package to be validated.
the package was develop to keep the same interface to permit user from
Console_color migrate to Console_Color2
and solve problems created by php 4.* dependency.

--

-- 
Ivo Nascimento - Iann
-------------------------------------------------
   http://about.me/ivonascimento
-------------------------------------------------
Permalink | Reply | 4 comments |
headers
ivo nascimento | 2 Aug 2011 17:26
Picon
Gravatar

Pear Console_Color2

Just to add more information to last maisl about Console_Color2 proposal
here the github code https://github.com/iannsp/Console_Color2/
tks

--

-- 
Ivo Nascimento - Iann
-------------------------------------------------
   http://about.me/ivonascimento
-------------------------------------------------
Permalink | Reply | 0 comments |
headers
Michael Gauthier | 3 Aug 2011 02:36
Favicon
Gravatar

Re: about pear

On Tue, 2011-08-02 at 12:38 -0300, ivo nascimento wrote:
> Hi Mike,
> can you help me with some questions?
> I'm new into PEAR and ask for your help.
> 
Hi Ivo, welcome to PEAR!

> A send patchs have a week and it's not validate yet, so I just need an
> Idea about how much time it normally need to be validade.
>
It's up the the maintainer of a package to accept a patch. How quickly a
patch gets accepted depends on how active the maintainer is, and whether
or not the patch applies cleanly.

> Another question is about pear2 packages,
> I have a proposal here to Console_color2 without the dependecy of php
> version 4.* but I dont know how to send this to evaluation from the
> dev's.
> 
PEAR2 doesn't have an equivalent to PEPR yet. Github is the place to
start development. If the code is on Github and follows the PEAR2
standards, bbieber can add it to the PEAR2 channel/website.

Cheers,
Mike

> thanks in advanced.
> 
> 
> --
(Continue reading)

Permalink | Reply | 0 comments |
headers
Brett Bieber | 5 Aug 2011 05:20
Picon
Gravatar

PEAR Development on Github

Greetings,

I wanted to notify PEAR package developers that you are all welcome to use any of the github org accounts we have. Just send a message to this list or pear-group and we'll set up a repository for you.

Right now we have two accounts, http://github.com/pear and http://github.com/pear2 — each are organizations which can have teams of developers with push access to repositories.

For those developers that would like to migrate an existing package from svn.php.net, the following is for you:

The svn2git tool supports standard svn layouts and preserves tags and branches. I would highly recommend using it if you're interested in moving your packages to git. One caveat, the svn.php.net repository is very large, so to be respectful of the server resources it is best to start from the first committed revision for your package.

When I migrated all the pear2 packages, I found a fork of svn2git which supported starting at a specific revision. That fork is here: https://github.com/svenax/svn2git

First, the steps on getting svn2git installed:
mkdir svn2git
cd svn2git
svn clone https://github.com/svenax/svn2git.git .
gem build svn2git.gemspec
sudo gem install svn2git-2.0.0.gem

Once you have the svn2git tool installed, you're ready to migrate a package.
svn2git uses an authors file in ~/.svn2git/authors (sample attached), so put that in place.

Here's the simple steps I used to migrate PEAR2_Templates_Savant to git, note the starting revision number:

mkdir PEAR2_Templates_Savant
cd PEAR2_Templates_Savant
svn2git http://svn.php.net/repository/pear2/Templates_Savant --revision 284750
git remote add origin git <at> github.com:pear2/PEAR2_Templates_Savant.git

git push -u origin master

Just change the directory name, svn.php.net path, revision number, and remote repository url and you should be set.

Once you're comfortable with the source on github, you can either delete the source on svn.php.net or request that commit access to your package be removed by emailing pear-group.

If you have any trouble feel free to email the pear-dev list or ask on efnet #PEAR.

Happy social coding.

--
Brett Bieber
--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 5 comments |
headers
Igor Feghali | 5 Aug 2011 13:56
Picon

Re: PEAR Development on Github

Hello Brett,

> Right now we have two accounts, http://github.com/pear and
> http://github.com/pear2 — each are organizations which can have teams of
> developers with push access to repositories.

can we use those repositories to host proposed codes or only current packages ?

Best,
~IF.

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 4 comments |
headers
Igor Feghali | 5 Aug 2011 14:03
Picon

Re: candidate package Console_Color2 to Pear2

Hello Ivo,

You can still create a PEAR package and make it PHP 5+ compatible
only. If your only concern is dropping PHP 4 compatibility, you don't
really have to make a PEAR2 package. If you decide to propose a PEAR
package, you can follow the guidelines here:

http://pear.php.net/manual/en/newmaint.proposal.php

Best,
~IF.

On Tue, Aug 2, 2011 at 11:27, ivo nascimento <iannsp <at> gmail.com> wrote:
> Hi,
> I develop a package candidate to a new version of Console_Color (
> Console_Color2 ) for pear2 system
> and like to know how to procced to send a proposal for pear2 or directly
> send the package to be validated.
> the package was develop to keep the same interface to permit user from
> Console_color migrate to Console_Color2
> and solve problems created by php 4.* dependency.

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 0 comments |
headers
Brett Bieber | 5 Aug 2011 15:29
Picon
Gravatar

Re: PEAR Development on Github

On Fri, Aug 5, 2011 at 6:56 AM, Igor Feghali <igor.feghali <at> gmail.com> wrote:
> Hello Brett,
>
>> Right now we have two accounts, http://github.com/pear and
>> http://github.com/pear2 — each are organizations which can have teams of
>> developers with push access to repositories.
>
> can we use those repositories to host proposed codes or only current packages ?

I would say, only current PEAR packages can be moved to
github.com/pear. PEAR2 proposals are welcome on github.com/pear2.
Because the proposal process is different for PEAR vs PEAR2, each is
managed differently. There's no pepr process required before creating
or releasing a PEAR2 package. The PEAR2 review process is required
before a package can be released as stable, but not before any code is
accepted.

-- 
Brett Bieber

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 3 comments |
headers
till | 5 Aug 2011 16:18
Picon

Re: candidate package Console_Color2 to Pear2

Hi Ivo,

I can fork your code into github.com/pear2 and when you're ready, we
could give you feedback on the code, etc..

The proposal process for pear2 is pretty simple - generally, you can
start right away. If you want to release a "stable" (aka
PEAR2_Console_Color-1.0.0), you'll have to go through a review.

Till

On Tue, Aug 2, 2011 at 4:27 PM, ivo nascimento <iannsp <at> gmail.com> wrote:
> Hi,
> I develop a package candidate to a new version of Console_Color (
> Console_Color2 ) for pear2 system
> and like to know how to procced to send a proposal for pear2 or directly
> send the package to be validated.
> the package was develop to keep the same interface to permit user from
> Console_color migrate to Console_Color2
> and solve problems created by php 4.* dependency.
>
>
> --
> Ivo Nascimento - Iann
> -------------------------------------------------
>   http://about.me/ivonascimento
> -------------------------------------------------
>

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 2 comments |
headers
Brett Bieber | 5 Aug 2011 16:33
Picon
Gravatar

Re: candidate package Console_Color2 to Pear2

On Fri, Aug 5, 2011 at 9:18 AM, till <till <at> php.net> wrote:
> Hi Ivo,
>
> I can fork your code into github.com/pear2 and when you're ready, we
> could give you feedback on the code, etc..
>
> The proposal process for pear2 is pretty simple - generally, you can
> start right away. If you want to release a "stable" (aka
> PEAR2_Console_Color-1.0.0), you'll have to go through a review.

Shooot. He's there already with his first release.

http://pear2.php.net/PEAR2_Console_Color

Getting your PEAR2 packages out to the public is quick and easy.

-- 
Brett Bieber

--

-- 
PEAR Development Mailing List (http://pear.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Permalink | Reply | 1 comment |

Gmane