Comments for PEAR Blog

Comment on Welcome to new contributors by doconnor

doconnor — Mon, 19 Dec 2011 09:50:57 +0000

At this stage, I would encourage you to use the pear bug tracker for the moment. It has the advantedge of detecting duplicate issues for you.

With newer packages, some authors might opt to use the github issues – I personally have no problem with it

Comment on Welcome to new contributors by nikic

nikic — Sun, 18 Dec 2011 12:47:04 +0000

Should one still use the bug tracker on pear.php.net or should GitHub issues be used now?

Comment on PHP 5.3 Windows and PEAR (go-pear.phar) by tintin98

tintin98 — Wed, 30 Nov 2011 22:11:39 +0000

workaround fixed. Just copy PEAR folder from older version of PHP, then run

php -d phar.require_hash=0 go-pear.phar

all went well.

Comment on PEAR Development on Github by doconnor

doconnor — Sun, 06 Nov 2011 14:58:02 +0000

I’m actually finding the commit emails to be a non issue. Certainly where there are changes happening from external people; the fork/pull request model is actually letting me review better.
IE: https://github.com/pear/Console_Getargs/pull/1 is out there for comment and review.

Comment on PEAR Development on Github by Alan Knowles

Alan Knowles — Sun, 06 Nov 2011 02:17:13 +0000

Probably should go on the mailing list, but I’ve not had time to post this, github currently has a huge problem for PEAR development.

The commit emails do not include the patches… (only a link to them, and a long wait when you review on a mobile device….)

This means commits are missing peer review, and security review.

I’m guessing not a huge problem at present as most of the packages that have been moved are basically ‘the attic’ ones, but until github supports propper commit emails, It would be a good idea to hold off on migrating the remaining core packages until either this is fixed (not sure if github has settings for that) or we find an alternative, (git.php.net or gitorious)

Alan

Comment on PHP 5.3 Windows and PEAR (go-pear.phar) by Matt Pitts

Matt Pitts — Wed, 19 Oct 2011 18:21:34 +0000

When I run this: C:\PHP>php go-pear.phar

Comment on PHP 5.3 Windows and PEAR (go-pear.phar) by amit

amit — Tue, 04 Oct 2011 03:36:52 +0000

i am trying to do
php -d phar.require_hasg=0 PEAR/go-pear.phar
on wamp 2.1 and php version 5.3.5

but i am getting this error please help

c:\wamp\bin\php\php5.3.5>php -d phar.require_hasg=0 PEAR/go-pear.phar
phar “C:\wamp\bin\php\php5.3.5\PEAR\go-pear.phar” does not have a signaturePHP W
arning: require_once(phar://go-pear.phar/index.php): failed to open stream: pha
r error: invalid url or non-existent phar “phar://go-pear.phar/index.php” in C:\
wamp\bin\php\php5.3.5\PEAR\go-pear.phar on line 1236
PHP Stack trace:
PHP 1. {main}() C:\wamp\bin\php\php5.3.5\PEAR\go-pear.phar:0

Warning: require_once(phar://go-pear.phar/index.php): failed to open stream: pha
r error: invalid url or non-existent phar “phar://go-pear.phar/index.php” in C:\
wamp\bin\php\php5.3.5\PEAR\go-pear.phar on line 1236

Call Stack:
0.0207 719288 1. {main}() C:\wamp\bin\php\php5.3.5\PEAR\go-pear.phar:0

c:\wamp\bin\php\php5.3.5>

Comment on The PEAR Project mourns the loss of Bertrand Gugger by Bertrand Gugger: Qu’il Respose En Paix | Robert Peake

Bertrand Gugger: Qu’il Respose En Paix | Robert Peake — Fri, 15 Jul 2011 17:46:15 +0000

[...] was shocked to discover today that French PHP programmer Bertrand Gugger passed away last week due to a heart attack. Bertrand was co-lead on the Net_Monitor project with me, and contributed many valuable additions [...]

Comment on PEAR in August by Olle Jonsson

Olle Jonsson — Fri, 20 Aug 2010 08:07:47 +0000

I have written a completely unscientific counter page for the deprecation bugs:

http://ollehost.dk/media/pear-bugs/

(The number is a little lower than the number of bugs in the list, since I discount a few deprecated packages that appear in that list. Let’s only fix the stuff people use!)

Comment on Ubuntu Karmic Ships with PEAR-Affecting Issues by Kylie

Kylie — Thu, 19 Aug 2010 03:07:17 +0000

Thanks for the workaround, it came in handy for me