PEAR Bug Search Results

pearweb: Feature/Change Request 29031 [Open] pear.php.net needs to support account deletion (removal/remove/delete account)

2025-02-27T08:02:19+00:00

pearweb Feature/Change Request
Reported by janmoesen
2025-02-27T08:02:19+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
I want to permanently remove my account. I know PEAR is incredibly outdated, but deleting all of my data should be made possible, if only for GDPR compliance.

pearweb: Bug 21064 [Open] How to change my username?

mick at deafzone dot ch — 2016-05-16T03:39:50+00:00

pearweb Bug
Reported by michael_heuberger
2016-05-16T03:39:50+00:00
PHP: Irrelevant OS: Irrelevant Package Version: Unknown

Description:
------------
Hello there

How can I change the username of my profile or even delete it if changing username is not possible?

Thanks
Michael H

pearweb: Feature/Change Request 21017 [Open] missing IPv6 support for pear.php.net

ports at toco-domains dot de — 2016-01-08T10:59:00+00:00

pearweb Feature/Change Request
Reported by thorny
2016-01-08T10:56:48+00:00
PHP: Irrelevant OS:  Package Version: Unknown

Description:
------------
Hello,

i had done some research about the impact of missing IPv6 support at the FreeBSD ports-tree, which is the list of supported software for FreeBSD.

There are more than 100 programs which are not fetchable because pecl.php.net does not support IPv6 (https://wiki.freebsd.org/IPv6PortsTODO). There is also no AAAA DNS entry for them:

$ host pear.php.net
pear.php.net is an alias for euk3.php.net.
euk3.php.net has address 109.203.101.62

Please at IPv6 support to your servers and enable IPv6 only users to use the packages :)

pearweb: Bug 20325 [Open] Fatal error getLastActivity()

cweiske at php dot net — 2014-06-28T21:28:34+00:00

pearweb Bug
Reported by cweiske
2014-06-28T21:15:41+00:00
PHP: Irrelevant OS:  Package Version: 1.26.0

Description:
------------
The error log on the server shows multiple instances of the same error:

PHP Fatal error:  Call to a member function getLastActivity() on a non-object in /var/www/html/pearweb/pear.php.net/includ
e/services/HoneyPot.php on line 119

Maybe this is also the reason we don't get mails about new bug reports to pear-bugs@

pearweb: Documentation Problem 19830 [Open] Install docs wrong

2013-02-25T10:29:03+00:00

pearweb Documentation Problem
Reported by michael_inet
2013-02-22T22:16:26+00:00
PHP: 5.3.3 OS: CentOS 6.3 Package Version: 

Description:
------------
File_MARC does not install with instructions given on page, http://pear.php.net/package/File_MARC.

Please update "Easy Install" section to install File_MARC given beta status.  (Of if stable, up-rev to 1.0 / stable release.)

Expected result:
----------------
File_MARC to install by following the instructions given

Actual result:
--------------
[root@localhost ~]# pear install File_MARC
Failed to download pear/File_MARC within preferred state "stable", latest release is version 0.7.1, stability "beta", use "channel://pear.php.net/File_MARC-0.7.1" to install
install failed
[root@localhost ~]# pear version
PEAR Version: 1.9.4
PHP Version: 5.3.3
Zend Engine Version: 2.3.0
Running on: Linux localhost.localdomain 2.6.32-279.1.1.el6.x86_64 #1 SMP Tue Jul 10 13:47:21 UTC 2012 x86_64

pearweb: Bug 19828 [Open] Adding packages.zendframework.com to channel list fails

cweiske at php dot net — 2013-02-21T15:14:37+00:00

pearweb Bug
Reported by cweiske
2013-02-21T15:14:37+00:00
PHP: Irrelevant OS:  Package Version: Unknown

Description:
------------
When trying to add https://packages.zendframework.com/ to the channe list via http://pear.php.net/channels/add.php, I get an SSL error.

Actual result:
--------------
Unable to connect to ssl://packages.zendframework.com:443. Error: stream_socket_client() [function.stream-socket-client]: unable to connect to ssl://packages.zendframework.com:443 (Unknown error) stream_socket_client() [function.stream-socket-client]: Failed to enable crypto stream_socket_client() [function.stream-socket-client]: SSL operation failed with code 1. OpenSSL Error messages: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

pearweb: Bug 19567 [Open] Spam

hm2k at php dot net — 2013-01-21T04:46:18+00:00

pearweb Bug
Reported by hm2k
2012-08-16T17:17:56+00:00
PHP: Irrelevant OS:  Package Version: Unknown

Description:
------------
I've received hundreds of these emails from what appears to be 
the pear website.

Test script:
---------------
                                                                                                                                                                                                                                                               
Delivered-To: xxx@gmail.com
Received: by 10.229.149.8 with SMTP id r8csp393835qcv;
        Tue, 14 Aug 2012 12:42:38 -0700 (PDT)
Received: by 10.66.83.129 with SMTP id q1mr22207648pay.4.1344973357748;
        Tue, 14 Aug 2012 12:42:37 -0700 (PDT)
Return-Path: 
Received: from mail6.zoneedit.com (mail6.zoneedit.com. [66.240.226.247])
        by mx.google.com with ESMTP id gk6si5132845pbc.95.2012.08.14.12.42.37;
        Tue, 14 Aug 2012 12:42:37 -0700 (PDT)
Received-SPF: neutral (google.com: 66.240.226.247 is neither permitted nor denied by domain of bounce-no-user@php.net) client-ip=66.240.226.247;
Authentication-Results: mx.google.com; spf=neutral (google.com: 66.240.226.247 is neither permitted nor denied by domain of bounce-no-user@php.net) smtp.mail=bounce-no-user@php.net
Received: from osu1php.osuosl.org (osu1php.osuosl.org [140.211.15.143])
	by mail6.zoneedit.com (Postfix) with ESMTP id 2C3FCD5146
	for ; Tue, 14 Aug 2012 12:42:37 -0700 (PDT)
Authentication-Results: osu1php.osuosl.org header.from=sample@email.tst; sender-id=neutral
Authentication-Results: osu1php.osuosl.org smtp.mail=bounce-no-user@php.net; spf=neutral; sender-id=neutral
Received-SPF: neutral (osu1php.osuosl.org: 140.211.166.137 is neither permitted nor denied by domain of php.net)
Received: from [140.211.166.137] ([140.211.166.137:45724] helo=fraxinus.osuosl.org)
	by osu1php.osuosl.org (envelope-from )
	(ecelerity 3.3.2.44647 r(44647)) with ESMTP
	id BA/30-29436-B2AAA205; Tue, 14 Aug 2012 19:42:35 +0000
Received: from localhost (localhost [127.0.0.1])
	by fraxinus.osuosl.org (Postfix) with ESMTP id D6ABE101EC1
	for ; Tue, 14 Aug 2012 19:42:34 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
Received: from fraxinus.osuosl.org ([127.0.0.1])
	by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id BYVNuQd6OBlz for ;
	Tue, 14 Aug 2012 19:42:14 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6
Received: from euk1.php.net (unknown [78.129.214.25])
	by fraxinus.osuosl.org (Postfix) with ESMTP id 231AC101A10
	for ; Tue, 14 Aug 2012 19:40:51 +0000 (UTC)
Received: by euk1.php.net (Postfix, from userid 48)
	id 14A5B19402E; Tue, 14 Aug 2012 01:41:04 +0100 (BST)
To: hm2k@php.net
Subject: 1
From: "rvqhvaau" 
Message-Id: <20120814004104.14A5B19402E@euk1.php.net>
Date: Tue, 14 Aug 2012 01:41:04 +0100 (BST)

[This message has been brought to you via pear.php.net.]

../..//../..//../..//../..//../..//../..//../..//../..//etc/passwd

Expected result:
----------------
It looks like someone is either trying to spam or exploit the site 
or both.

Actual result:
--------------
I don't expect to be spammed by pear.php.net so I can only 
assume there's a bug in pearweb somewhere.

pearweb: Bug 19534 [Open] wrong bug title in alt/title changelog

melissa at meldraweb dot com — 2014-10-04T02:42:10+00:00

pearweb Bug
Reported by elky
2012-07-30T15:26:12+00:00
PHP: Irrelevant OS: irrelevant Package Version: Unknown

Description:
------------
Affects, for example:
http://pear.php.net/package/Image_Canvas/download/
http://pear.php.net/package/Image_Tools/download/
http://pear.php.net/package/Image_Graph/download/
http://pear.php.net/package/Numbers_Words/download/0.16.
3
http://pear.php.net/package/HTML_Template_IT/download/

But does not affect:
http://pear.php.net/package/PEAR/download/
http://pear.php.net/package/Archive_Tar/download/
http://pear.php.net/package/pearweb/download/1.24.3
etc

Does not seem to be any release-date correlation at all, 
either, so probably not linked to any particular 
version of pearweb.

pearweb: Bug 19288 [Open] go-pear.phar corrupted?

giovannirinaldi_002 at fastwebnet dot it — 2012-02-12T21:32:45+00:00

pearweb Bug
Reported by rinaldi
2012-02-12T21:32:45+00:00
PHP: 5.2.17 OS: linux Package Version: 

Description:
------------
from line 1236 to 1243 and line 99202

Furtermore, why line 3179 "?>" and line 3180 "

pearweb: Bug 19093 [Open] Automatic updates busted

daniel dot oconnor at gmail dot com — 2011-11-30T19:03:33+00:00

pearweb Bug
Reported by doconnor
2011-11-30T19:02:16+00:00
PHP: 5.3.7 OS:  Package Version: SVN

Description:
------------
WARNING: channel "pear.php.net" has updated its protocols, 
use "pear channel-update pear.php.net" to update
Failed to download pear/Services_ProjectHoneyPot within 
preferred state "stable", latest release is version 0.6.0, stability 
"beta", use "channel://pear.php.net/Services_ProjectHoneyPot-
0.6.0" to install
WARNING: "pear/DB" is deprecated in favor of "pear/MDB2"
Package "pear.php.net/pearweb" dependency 
"pear.php.net/Horde_Text_Diff" has no releases
WARNING: "pear/HTML_QuickForm" is deprecated in favor of 
"pear/HTML_QuickForm2"
Failed to download pear/HTML_QuickForm2 within preferred 
state "stable", latest release is version 0.6.1, stability "beta", 
use "channel://pear.php.net/HTML_QuickForm2-0.6.1" to install
WARNING: "pear/DB" is deprecated in favor of "pear/MDB2"
pear/pearweb requires package 
"pear/Services_ProjectHoneyPot" (version >= 0.6.0), installed 
version is 0.5.3
pear/pearweb requires package "pear/Horde_Text_Diff"
pear/DB_DataObject can optionally use package "pear/Validate" 
(version >= 0.1.1)
PHP Warning:  mkdir(): File exists in /local/lib/php/System.php 
on line 285
PHP Warning:  mkdir(): Not a directory in 
/local/lib/php/System.php on line 285
PHP Fatal error:  Call to a member function outputData() on a 
non-object in /local/lib/php/PEAR/Command/Install.php on line 
715

pearweb: Bug 18479 [Open] Regression: show map button, account editing

daniel dot oconnor at gmail dot com — 2011-04-26T14:03:53+00:00

pearweb Bug
Reported by doconnor
2011-04-26T14:03:53+00:00
PHP: Irrelevant OS:  Package Version: 1.24.3

Description:
------------
This feature used to be a link which simply loaded the map. 
Since moving to QF2, it's a button element without a label; 
which submits the form.

return false; and setValue/setText

pearweb: Bug 18351 [Open] Security vulnerability in editing bugs

afshin dot meh at gmail dot com — 2014-10-04T02:06:47+00:00

pearweb Bug
Reported by afshin
2011-03-10T01:00:27+00:00
PHP: Irrelevant OS:  Package Version: 1.24.2

Description:
------------
Every registered user in any level can view and use edit bugs in a developer level just with adding "edit" parameter to URL parameters and set this value to 2.

For example : http://pear.php.net/bugs/bug.php?id=18157&edit=2

pearweb: Bug 18317 [Open] Publishing a stable package version erases reference to beta

sergiosgc at gmail dot com — 2011-02-26T23:48:03+00:00

pearweb Bug
Reported by sergiosgc
2011-02-26T23:48:03+00:00
PHP: Irrelevant OS: Irrelevant Package Version: Unknown

Description:
------------
When a package has both a beta version and a stable, if the package publishing order is 1. publish beta, 2. publish stable, then the package page on pear.php.net will lack the reference to the beta version.

It is common for a package to have a bug-maintenance stable version and a beta version that will become the future stable version of the package. Announcing the existence of the beta version is essential to get good user testing. 

On the other hand, it reasonable to expect the stable version to have a bugfix release after the beta has been published. The fact that it has been published later than the beta does not mean that it is replacing the beta.

You have one such case on XML_RPC2. I've published 1.1.0b3, then 1.0.8. The reference to 1.1.0b3 disappeared from the page. 

Test script:
---------------
1. Publish a beta version of a package (e.g. 1.1.0b1)
2. Publish a stable version, with a version number lower than the beta (e.g 1.0.5)

Expected result:
----------------
A reference to both versions in the package page (e.g. http://pear.php.net/package/xml_rpc2)


Actual result:
--------------
Only a reference to the stable version appears

pearweb: Feature/Change Request 18264 [Open] OpenId support

cweiske at php dot net — 2011-02-11T18:41:09+00:00

pearweb Feature/Change Request
Reported by cweiske
2011-02-11T18:41:09+00:00
PHP: Irrelevant OS:  Package Version: SVN

Description:
------------
Users should be able to login with their openid.
To support that, existing users need to be able to assign an openid to their account. Login needs to support openid.

pearweb: Feature/Change Request 17563 [Open] Bug comment author's name shall be retrieved from user profile

mega-squall at caramail dot com — 2011-07-09T22:32:13+00:00

pearweb Feature/Change Request
Reported by megasquall
2010-07-06T15:34:06+00:00
PHP: irrelevant OS: irrelevant Package Version: 1.24.2

Description:
------------
User real name is displayed next to user login and before the comment text. This information is taken from user profile but as a copy of actual value, which means any modification of user real name will not propagate to any existing bug comment.

It would be nice if this information was taken live from user profile so that every bug comment from the same user would display the same real name.

Test script:
---------------
user profile > set real name to : X
post a bug comment

user profile > set real name to : Y
post a bug comment

Expected result:
----------------
[date] userlogin (Y)
blah ...

[date] userlogin (Y)
blah ...

Actual result:
--------------
[date] userlogin (X)
blah ...

[date] userlogin (Y)
blah ...

pearweb: Bug 17547 [Open] UTF-8 characters from package.xml not correctly transferred to REST xml.

agueijo at gmail dot com — 2010-07-02T18:09:06+00:00

pearweb Bug
Reported by agueijo
2010-07-01T20:44:02+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
I collaborate to solve the bug: 
http://pear.php.net/bugs/bug.php?id=17527

And today was published version 1.3.0 with my name AgustÃn 
Eijo in the changelog, but the acute accent character (Ã) of my 
name AgustÃn makes you throw an error try to install the 
package:

# pear upgrade Net_Sieve
Error getting channel info from pear.php.net: Invalid xml 
downloaded from 
"http://pear.php.net/rest/r/net_sieve/1.3.0.xml": XML Error: 
'Invalid character' on line '17'
Nothing to upgrade

change it for Agustin without acute accent character (Ã)

pearweb: Bug 17543 [Verified] Broken link in Quick fix description

alec at alec dot pl — 2014-10-04T02:18:24+00:00

pearweb Bug
Reported by alec
2010-07-01T15:03:39+00:00
PHP: Irrelevant OS:  Package Version: Unknown

Description:
------------
I'm not sure, but probably "Fixed in release (Closed)" position in bugtracker ticket creates a description: "Thank you for your bug report. This issue has been fixed in the latest released version of the package, which you can download at http://pear.php.net/get/". The link doesn't work.

pearweb: Bug 17492 [Open] Account signup FAIL

pear at allenjb dot me dot uk — 2010-06-14T19:08:02+00:00

pearweb Bug
Reported by allenjb
2010-06-14T19:08:02+00:00
PHP: 5.3.2 OS:  Package Version: 

Description:
------------
PEAR Bugs account signup:
- does not explicitly display the constraints of the various fields, 
- does not repopulate fields on failure 
- imposes stupid unnecessary constraints (like a firstname and 
surname in the name field)

pearweb: Bug 17464 [Open] Package release appears to fail if newer pear verison is installed

daniel dot oconnor at gmail dot com — 2010-06-03T06:12:22+00:00

pearweb Bug
Reported by doconnor
2010-06-03T06:12:22+00:00
PHP: 5.2.12 OS:  Package Version: 1.24.1

Description:
------------
Generate a package, put in the minimum dependency as 1.9.1 for the pear installer.

This causes errors like:
PEAR_PackageFileManager2 Error: Package validation failed:
Error: This package.xml requires PEAR version 1.9.1 to parse properly, we are version 1.9.0

on the command line.

When you upload a package, an uninformative error message is generated - Parsing of package.xml from file "/tmp/pear/temp/pearJZVabs/package.xml" failed

Test script:
---------------
 1. Build a release with a super new sounding pear version that your pearweb install doesn't have.
 2. Try to upload and release it.

Expected result:
----------------
A meaningful error message (ie: pfm2's error) is rendered

Actual result:
--------------
Parsing of package.xml from file "/tmp/pear/temp/pearJZVabs/package.xml" failed

pearweb: Feature/Change Request 17298 [Open] User notes can use spam checking

philip at roshambo dot org — 2010-04-07T04:11:21+00:00

pearweb Feature/Change Request
Reported by philip
2010-04-07T04:11:21+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 

Description:
------------
The user notes system contains hundreds of SPAM notes. Although not 
approved (thus, not online), seeing all of these makes administrating 
them overwhelming. I refer to this:

 - http://pear.php.net/notes/admin/

In this case, how about checking to see if "

pearweb: Feature/Change Request 17203 [Open] graveyard.pear.php.net / package end of life tools

daniel dot oconnor at gmail dot com — 2010-03-16T17:35:36+00:00

pearweb Feature/Change Request
Reported by doconnor
2010-03-08T20:26:06+00:00
PHP: 5.3.1 OS:  Package Version: SVN

Description:
------------
PEAR has a problem: there are many unloved packages with few downloads out there; that no longer have a place in PEAR. IE: SQL_Parser.

It's not nice to simply remove all of the releases, the package entry, and the SVN information, pretending it was never there.

We also need a process to widely advertise the end of life *before* it gets hit on the head.

1) I'd like to see a simple channel server set up somewhere; where we can shift these dead packages.
2) As above, for SVN (or just SVN remove, its why we have svn revert).
3) I'd like to see enhanced tools to advertise this (like the unmaintained flags)

pearweb: Bug 16982 [Open] creating new roadmap: bugs in "Importing closed bugs" feature

danielc at analysisandsolutions dot com — 2010-01-09T07:53:51+00:00

pearweb Bug
Reported by danielc
2010-01-09T07:52:35+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
When creating a new Roadmap for a package, there is a checkbox to "Import closed bugs since last release."  (Totally cool feature, thank you.)  Unfortunately, in addition to importing "Closed" bugs, it imports tickets with a status of "Won't Fix" (and perhaps others).  Also, it does not import "feature requests," but it should.

pearweb: Bug 16845 [Open] Bug Change/Comment Notifications Contain Raw HTML

demon dot gene at gmail dot com — 2010-05-10T02:51:50+00:00

pearweb Bug
Reported by ashnazg
2009-11-29T06:28:17+00:00
PHP: Irrelevant OS: Linux Package Version: 1.24.0

Description:
------------
In the bug change/comment notification email, the comment area shows some plain text HTML tags.  It looks like these are the actual HTML styling tags that go around the part of a comment that shows changes in the bug header values.

These HTML tags should be stripped out of these parts of comments when the plain text emails are created.

Expected result:
----------------
------------------------------------------------------------------------

[2009-07-21 17:32:39] ashnazg

-Roadmap Versions:
+Roadmap Versions: 1.4.3

------------------------------------------------------------------------

Actual result:
--------------
(this was a comment from bug #14159)

------------------------------------------------------------------------

[2009-07-21 17:32:39] ashnazg


-Roadmap Versions:
+Roadmap Versions: 1.4.3


------------------------------------------------------------------------

pearweb: Bug 16844 [Assigned] "Patch Added" Email Is Missing Its Bug Info

demon dot gene at gmail dot com — 2014-10-04T02:29:25+00:00

pearweb Bug
Reported by ashnazg
2009-11-29T06:19:34+00:00
PHP: Irrelevant OS: Linux Package Version: 1.24.0

Description:
------------
The "Patch Added/Updated" email I received for Bug #16586 is completely missing any and all references to the bug itself.  Therefore, it's subject is incomplete, and all its hyperlinks are incomplete.

Expected result:
----------------
subject	[Patch] Patch Added/Updated for bug 16586

	
Dear maintainer,

The following patch has been added/updated for bug #16586:

Bug Package: XML_Serializer
Bug Summary: namespace duplication
Patch Name:  add-firstcall-check-to_createXMLTag
URL:         http://pear.php.net/bugs/patch-display.php?bug_id=16586&patch=add-firstcall-check-to_createXMLTag&revision=1259260750&display=1
Date:        2009-11-26 18:46:15

View bug report at : http://pear.php.net/bugs/bug.php?id=16586

Actual result:
--------------
subject	[Patch] Patch Added/Updated for bug

	
Dear maintainer,

The following patch has been added/updated for bug #:

Bug Package: XML_Serializer
Bug Summary:
Patch Name:  add-firstcall-check-to_createXMLTag
URL:         http://pear.php.net/bugs/patch-display.php?bug_id=&patch=add-firstcall-check-to_createXMLTag&revision=1259260750&display=1
Date:        2009-11-26 18:46:15

View bug report at : http://pear.php.net/bugs/bug.php?id=

pearweb: Bug 16671 [Open] Entire Comments Frame is in Description Box

demon dot gene at gmail dot com — 2009-10-19T07:19:01+00:00

pearweb Bug
Reported by ashnazg
2009-10-02T19:22:35+00:00
PHP: 5.3.0 OS: Linux Package Version: 1.23.2

Description:
------------
On Bug #4197, the entire comments frame (all comments plus the page footer) are included in the Description box.

http://pear.php.net/bugs/bug.php?id=4197

pearweb: Feature/Change Request 16566 [Assigned] Usability: Add a 'reset password' / other actions to bug error messages

muell at bruechner dot de — 2009-09-10T04:19:10+00:00

pearweb Feature/Change Request
Reported by muell
2009-09-02T22:48:43+00:00
PHP: Irrelevant OS: Windows Package Version: Unknown

Description:
------------
ERROR:

    * Email is already in use for an existing account


Test script:
---------------
When I click "Add Comment" to add a comment for a existing bug, and enter my email adress. Or when I try to add a new bug, like this.

Expected result:
----------------
that there is not such a result.

Actual result:
--------------
ERROR:

    * Email is already in use for an existing account

This happend even when I tried to add   T  H  I  S   bug. Argh!!!!

pearweb: Feature/Change Request 16401 [Open] show a count of comments next to proposed packages in pepr.

daniel dot oconnor at gmail dot com — 2009-07-03T09:31:20+00:00

pearweb Feature/Change Request
Reported by doconnor
2009-07-03T09:31:20+00:00
PHP: Irrelevant OS:  Package Version: 1.21.1

Description:
------------
(12:50:14 PM) gauthierm: CloCkWeRX: another pearweb suggestion: show a count of comments next to proposed packages in pepr.
(12:51:53 PM) loopie [coco@host241-150-1-58.bc-centralplus.com] entered the room.
(12:55:00 PM) CloCkWeRX: i can has feature request for that so i don't forget?

pearweb: Bug 16343 [Verified] Latest pear depends on 5.1.6 but only says 4.4.0

darren at dcook dot org — 2009-06-21T00:39:44+00:00

pearweb Bug
Reported by darrencook
2009-06-18T15:42:28+00:00
PHP: 5.1.4 OS: linux Package Version: 

Description:
------------
http://pear.php.net/package/PEAR/download/All

says php 4.4.0 is the requirement, but it won't upgrade with php 5.1.4.
The reason is only hidden in the release notes for 1.8.0alpha1, where it says "PHP 4.4 and 5.1.6 are now the minimum PHP requirements"

That information needs to be in the requirements section for all 1.8.x versions, not just alpha1 !!

pearweb: Bug 16252 [Open] Adding a new bug report with the wrong db driver = error

daniel dot oconnor at gmail dot com — 2009-10-19T07:20:01+00:00

pearweb Bug
Reported by doconnor
2009-05-23T22:02:28+00:00
PHP: 5.2.9 OS:  Package Version: CVS

Description:
------------
Direct calls to mysqli_last_insertid are being done, instead of trusting the DB abstraction layer.

Test script:
---------------
1. Add a dsn of mysql://foo:bar@localhost/pearweb in
2. Add a bug report

            /*
            * Need to move the insert ID determination to DB eventually...
            */
            $cid = mysqli_insert_id($dbh->connection);

Expected result:
----------------
No errors

Actual result:
--------------
Warning: mysqli_insert_id() expects parameter 1 to be mysqli, resource given in /home/clockwerx/pear-cvs/pearweb/public_html/bugs/report.php on line 310

pearweb: Bug 16236 [Open] Unit tests fail: pear_rest

daniel dot oconnor at gmail dot com — 2009-05-18T21:10:26+00:00

pearweb Bug
Reported by doconnor
2009-05-18T21:10:26+00:00
PHP: 5.2.9 OS:  Package Version: CVS

Description:
------------
Failed unit tests everywhere :(

Test script:
---------------
pear run-tests -r tests/pear_rest/

Expected result:
----------------
Tests run, pass

Actual result:
--------------
Most tests fail with:

Warning: Missing argument 2 for pearweb_Channel_REST_Generator::__construct(), called in /home/clockwerx/pear-cvs/pearweb/tests/pear_rest/setup.php.inc on line 13 and defined in /home/clockwerx/pear-cvs/pearweb/include/pear-rest.php on line 9

Notice: Undefined variable: db in /home/clockwerx/pear-cvs/pearweb/include/pear-rest.php on line 14

pearweb: Bug 16088 [Open] wrong open bugs count when unconfirmed or spam report

pear at laurent-laville dot org — 2009-05-24T20:05:09+00:00

pearweb Bug
Reported by farell
2009-04-11T13:38:02+00:00
PHP: Irrelevant OS:  Package Version: Unkown

Description:
------------
Following my chat with Helgi on PEAR webmaster list 
http://news.php.net/php.pear.webmaster/6502

I open this new bug report about user information page and number of open bugs.

When there is an unconfirmed bug report (or as it was in my case) a presumed spam report, we should not see the number of open bugs increased by these pseudo false reports.



Expected result:
----------------
Number open bugs : 1

For report #15674 only

Actual result:
--------------
Number open bugs : 2

#15674 + #16080
Before I declare #16080 as spam

pearweb: Feature/Change Request 15992 [Verified] Header in bug tracker emails should only contain current values

wiesemann at php dot net — 2009-06-07T12:35:16+00:00

pearweb Feature/Change Request
Reported by wiesemann
2009-03-08T15:54:07+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
The header part of the bug tracker emails should only contain the current values of Status/Type/Version/Summary etc. because the differences between old and new values are now listed in the comment section. The current implementation is redundant.

pearweb: Feature/Change Request 15853 [Assigned] Better format for RSS feeds from bug system

daniel dot oconnor at gmail dot com — 2009-06-30T06:06:26+00:00

pearweb Feature/Change Request
Reported by doconnor
2009-02-01T03:00:58+00:00
PHP: 5.2.6 OS:  Package Version: CVS

Description:
------------
If you subscribe to the bug system's rss feeds from a search result, the feed is badly presented in readers (whitespace is ignored, for instance in google reader).

It should be easy to render out html or something else in the feed which fixes this.



Expected result:
----------------
Readable output

Actual result:
--------------
"Description: ------------ It expects $this->_metaHttpEquivResponse to be an instance of HTTP_Request, but it's actually the value of $request->getResponse() Test script: --------------- $yadis = new Services_Yadis('https://me.yahoo.com'); @$yadis->discover(); var_dump($yadis->getUserREsponse()); Expected result: ---------------- [HTML from request] Actual result: -------------- bool(false)"

pearweb: Feature/Change Request 15399 [Open] Add column "Closed since last release" to bug statistics overview

troehr at php dot net — 2009-06-14T11:46:03+00:00

pearweb Feature/Change Request
Reported by troehr
2008-12-26T17:26:30+00:00
PHP: Irrelevant OS:  Package Version: 1.17.1

Description:
------------
Please add a new column to http://pear.php.net/bugs/stats.php to display the tickets that have been closed since the last release. This makes it easy to identify packages that may need a new release because a lot of issues have already been fixed in CVS.

Maybe #15393 should be fixed first.

Thanks,

Torsten

pearweb: Feature/Change Request 14973 [Open] easy api doc acces

cweiske at php dot net — 2009-06-14T11:44:49+00:00

pearweb Feature/Change Request
Reported by cweiske
2008-11-07T13:11:56+00:00
PHP: Irrelevant OS:  Package Version: 1.17.1

Description:
------------
It would be very helpful if one could easily type in api doc urls like
pear.php.net/classname::method
pear.php.net/classname::$var
pear.php.net/Packagename/classname

pearweb: Feature/Change Request 14372 [Open] Better explain "How do I contribute" via pearweb

daniel dot oconnor at gmail dot com — 2011-09-06T01:57:04+00:00

pearweb Feature/Change Request
Reported by doconnor
2008-07-19T12:05:33+00:00
PHP: Irrelevant OS:  Package Version: 1.17.1

Description:
------------
We aren't gaining enough developers quickly.

We should examine how pearweb can help us do that.

From IRC:
(9:31:52 PM) CloCkWeRX: what's the process-flow from pear.php.net?
(9:32:47 PM) CloCkWeRX: ie, i click into 'developers' and i don't have a "How do I contribute" link / also there's no wonderful button in the bug tracker which converts an outside to a pear dev.
(9:32:48 PM) bentob0x left the room (quit: Read error: Connection reset by peer).
(9:33:16 PM) helgi: mm yes how do I contribute would be a good link in developers


Test script:
---------------
Log in to pear.php.net
Try to find out how to become a developer/contributor

Expected result:
----------------
It's easy

Actual result:
--------------
It's not

pearweb: Feature/Change Request 14192 [Open] ability to add a note when drop a release

pear at laurent-laville dot org — 2008-06-19T17:19:19+00:00

pearweb Feature/Change Request
Reported by farell
2008-06-19T17:19:19+00:00
PHP: Irrelevant OS:  Package Version: 1.17.1

Description:
------------
I would like to have ability to add a note (reason) about a release dropped.

For example : yesterday (2008-06-18) I've published/uploaded the version 1.8.0b4 of PHP_CompatInfo.

Just in time, I've realized that I've forgotten two package tasks file replacement and 1 dependency.

So, I've dropped the recent upload release, before to reload it again: but as no reason could be given
All users have seen two announcements about PHP_CompatInfo 1.8.0b4 on the PEAR General Mailing List

pearweb: Feature/Change Request 14018 [Open] Packing Rating with Comments

jeichorn at JoshuaEichorn dot com — 2009-07-24T15:43:37+00:00

pearweb Feature/Change Request
Reported by jeichorn
2008-05-29T21:07:15+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
Add a simple 5star package rating system to the website something like the rating system on cpan
http://search.cpan.org/dist/SVN-Notify/
http://cpanratings.perl.org/dist/SVN-Notify

pearweb: Bug 13985 [Open] Doc bug mails sent out before confirmation

bjori at php dot net — 2008-05-27T16:39:16+00:00

pearweb Bug
Reported by bjori
2008-05-25T12:16:11+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.17.1

Description:
------------
(No idea if the package version is correct, didn't get "don't know" option..)

When filing bug reports user has to confirm his email address before the bug reports is visible online. However; The bug report is sent out to the mailinglists (at least pear-doc@) without any confirmation hence defeating the whole purpose of the spam system.


Test script:
---------------
http://news.php.net/php.pear.doc/
10791
10792
10793
10795
(Intentionally not linking)

Expected result:
----------------
Only confirmed bug reports to be mailed to the mailinglists.

Actual result:
--------------
All bug reports are mailed to mailinglists, before being confirmed.

pearweb: Feature/Change Request 13814 [Open] Mail reminder about open bugs need to be clarify

pear at laurent-laville dot org — 2008-05-01T12:01:33+00:00

pearweb Feature/Change Request
Reported by farell
2008-05-01T08:55:40+00:00
PHP: 5.2.5 OS:  Package Version: 1.17.1

Description:
------------
As I've just received the mail reminder about open bugs, I think that you should clarify/classify open bugs and requests , with a new column info (bug Type)


Bug, Request, Doc


Expected result:
----------------
Perharps content like this


Mail content:

 PEAR Bug Database summary for PEAR_Info - http://pear.php.net/bugs

  ID  Status     Type      Summary

13741 Open     Request  show list if potential config files. 

  Further comments can be seen at http://pear.php.net/bugs/13741
  Edit this bug report at http://pear.php.net/bugs/bug.php?id=13741&edit=1


Actual result:
--------------
Mail subject:
[PEAR-BUG][Reminder] Reminder about open bugs in PEAR_Info

Mail content:

 PEAR Bug Database summary for PEAR_Info - http://pear.php.net/bugs

  ID  Status     Summary

13741 Open      show list if potential config files. 

  Further comments can be seen at http://pear.php.net/bugs/13741
  Edit this bug report at http://pear.php.net/bugs/bug.php?id=13741&edit=1

pearweb: Feature/Change Request 13622 [Open] xml/csv export of bug numbers

cweiske at php dot net — 2009-09-08T13:29:19+00:00

pearweb Feature/Change Request
Reported by cweiske
2008-04-08T12:55:25+00:00
PHP: 5.2.5 OS:  Package Version: 1.17.1

Description:
------------
The bug statistics page should get a csv or xml output, so we can make graphs over time and so.

pearweb: Feature/Change Request 13621 [Open] main pages for packages should link back to their proposals

ken at linux dot ie — 2008-04-08T12:51:36+00:00

pearweb Feature/Change Request
Reported by kguest
2008-04-08T12:51:36+00:00
PHP: 5.2.3 OS:  Package Version: 1.17.1

Description:
------------
It would be very useful if the main page for each package would include a link back to the pepr/proposal for that package.

This would make it easier for [lead] developers to determine if there is anything useful in the proposal comments and votes that need to be considered/revisited when they are working on the package after it has been accepted.

Some may consider these links as clutter so I think it might be a good idea to have the display of these links configurable from the developers profile page as there is no 'preference' page [as yet].

pearweb: Feature/Change Request 13566 [Open] Check projects/peopls homepage urls with DNSBL

helgith at gmail dot com — 2009-04-30T03:16:42+00:00

pearweb Feature/Change Request
Reported by dufuz
2008-04-02T13:54:41+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
Check all urls inputted against DNSBL and reject them, check in peoples homepage, project homepage and all related url fields

pearweb: Feature/Change Request 13463 [Open] Usability: Make the wiki-ish markup more obvious

daniel dot oconnor at gmail dot com — 2008-03-22T10:49:57+00:00

pearweb Feature/Change Request
Reported by doconnor
2008-03-22T09:58:29+00:00
PHP: 5.2.5 OS:  Package Version: 1.17.1

Description:
------------
I've been around pearweb for a little while now, and I only just discovered the magic trick of typing "bug #1234"

I'd previously tried a number of different tricks, but if I'd had a 'bugtracker wiki markup' how-to link; I'd not have gone uneducated for so long.

pearweb: Feature/Change Request 13151 [Assigned] 'Add Site' feature too restrictive - allow directories

pear at jldupont dot com — 2009-02-03T20:05:15+00:00

pearweb Feature/Change Request
Reported by jldupont
2008-02-19T20:23:39+00:00
PHP: Irrelevant OS: irrelevant Package Version: 

Description:
------------
The 'Add Site' functionality located at http://pear.php.net/channels/  does not permit adding channels of the form 'HTTP://host/directory/' .

" add.php " expects to use only the 'host' part of the URI provided by the user whilst it would require the full URI in order to support the aforementioned case.

pearweb: Feature/Change Request 13075 [Open] reopening "No Feedback" bugs by third party

2008-03-08T20:57:41+00:00

pearweb Feature/Change Request
Reported by ddis11
2008-02-06T21:59:37+00:00
PHP: Irrelevant OS:  Package Version: 1.17.1

Description:
------------
Best explained by example: bug #5257 was suspended last March with status "No Feedback".  While I did not submit this bug, I recently encountered it, and produced a test case as requested by dufuz.  Instead of opening a new bug, I posted the test case and a proposed patch on the bug; however, I have no way to reopen the bug, as I am not the assignee or reporter.

From the bug.php and related source it appears that comments on suspended bugs are still emailed to the assignee, which is nice, but that action isn't as sticky as a bug status change.

pearweb: Feature/Change Request 12983 [Open] Be able to delete a user account from the admin panel

arnaud at limbourg dot com — 2008-02-01T20:13:06+00:00

pearweb Feature/Change Request
Reported by arnaud
2008-01-28T06:24:56+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
It would be nice to be able to delete accounts from the admin panel after jumping through the necessary hoops.

pearweb: Feature/Change Request 12891 [Open] Request to add link to MarkMail

jorrit at ncode dot nl — 2008-02-02T00:07:32+00:00

pearweb Feature/Change Request
Reported by jorrit
2008-01-12T11:13:16+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.17.1

Description:
------------
MarkMail (http://markmail.org) has indexed our mailinglist at http://pear.markmail.org/. They ask for a link back. Would that be possible?

I asked them if it were possible to index the PEAR lists, as they already had the PHP lists, and they agreed immediately. It looked to me like an interesting, promising project, so I thought it would be no harm.

pearweb: Bug 12868 [Assigned] Test concering the layout fail

dufuz at php dot net — 2014-10-04T09:49:03+00:00

pearweb Bug
Reported by dufuz
2008-01-09T20:26:49+00:00
PHP: Irrelevant OS: N/A Package Version: CVS

Description:
------------
After the redesign of the page all the tests that test against the layout fail horribly, we have to get them up to standard before the next release.

pearweb: Feature/Change Request 12606 [Open] Package warnings should be free-form text

aharvey at php dot net — 2007-12-04T09:26:30+00:00

pearweb Feature/Change Request
Reported by aharvey
2007-12-04T09:26:30+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.16.3

Description:
------------
We should have an option to set the warning message box on package pages (the one that displays messages that a given package is deprecated or unmaintained) to a free-form text string to cope with situations where the current list of options is insufficient. Two examples of this are:

- HTML_QuickForm, which has been superseded by an alpha package, and would be better described by a message pointing users to the new package if they want to live on the bleeding edge.

- DB, where I'd really like to be able to include a message saying that support will cease in August (as discussed on pear-dev a while back) in addition to the deprecation message.

I'm sure there are others. We did discuss this as part of the QuickForm issue on pear-dev about a month ago, but it doesn't look like anyone actually opened a feature request. (If they did, I haven't found it with a search, and I apologise for the dupe.)

pearweb: Feature/Change Request 12520 [Assigned] Reenable comment deleting for certain types of users

dufuz at php dot net — 2008-03-30T20:50:11+00:00

pearweb Feature/Change Request
Reported by dufuz
2007-11-24T23:38:27+00:00
PHP: Irrelevant OS: NA Package Version: 1.16.3

Description:
------------
At the moment we have all the functionality to delete comments, the site possessed that ability in the past since it's a fork from bugsweb but for some reason it was taken out and now I want to reinstate that because of spam people have been getting.

At the moment only pear.bugs.admin can do it but that's a bit much, I think I might want to allow pear.dev people in general to delete comments even if it's not their own packages.

pearweb: Feature/Change Request 11319 [Assigned] allow time range selection for download stats

cweiske at php dot net — 2008-02-06T22:44:11+00:00

pearweb Feature/Change Request
Reported by cweiske
2007-06-14T20:20:41+00:00
PHP: Irrelevant OS:  Package Version: 1.16.0

Description:
------------
It would be helpful if the package download stats page would allow selecting the timeframe for download counts.

Old packages normally have higher download numbers than new ones, so it is interesting to see which packages have been downloaded most in the last month.


I think it'd be enough to give a hard number of choices:
1 day, 1 week, 1 month, 2 months, 3 months, 6 months, 1 year, 2 years, all time


http://pear.php.net/package-stats.php

pearweb: Feature/Change Request 11304 [Open] The manual should show a "deprecated" warning when the package is

arnaud at limbourg dot com — 2008-01-27T03:46:12+00:00

pearweb Feature/Change Request
Reported by arnaud
2007-06-13T07:23:10+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
When a package is marked as deprecated the corresponding section in the manual should show this.

pearweb: Feature/Change Request 11271 [Open] unit tests for packages.php

greg at chiaraquartet dot net — 2008-02-05T17:05:32+00:00

pearweb Feature/Change Request
Reported by cellog
2007-06-11T04:50:09+00:00
PHP: 5.2.2 OS:  Package Version: 

Description:
------------
packages.php needs unit tests

pearweb: Feature/Change Request 11219 [Assigned] Cleaning out inactive PEPr proposals

mj at php dot net — 2008-04-15T12:45:23+00:00

pearweb Feature/Change Request
Reported by mj
2007-06-04T10:01:58+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
As decided by the PEAR Group in yesterdays meeting, PEPr proposals that have been inactive for more than three months will trigger warnings sent to the proposer.  If proposals are inactive for more than six months, they will be deleted.

pearweb: Feature/Change Request 11218 [Open] Give unmaintained packages more visiblity

arnaud at limbourg dot com — 2008-04-20T15:56:37+00:00

pearweb Feature/Change Request
Reported by arnaud
2007-06-04T07:15:47+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
Currently the list of unmaintained packages is hard to find and has restriction access in place (pear.dev karma).

The list should more visible (and generated regularly as generating it live takes up some resources).

pearweb: Feature/Change Request 11044 [Open] Better suggestions for similar bugs/requests

wiesemann at php dot net — 2007-11-18T13:30:33+00:00

pearweb Feature/Change Request
Reported by wiesemann
2007-05-15T12:50:32+00:00
PHP: 5.2.1 OS:  Package Version: 1.15.2

Description:
------------
The bug tracker suggests possibly similar bugs after submitting the form. The current implementation also shows bugs for e.g. Auth if I report something for e.g. HTML_Table. Even if an error is the same in both packages (e.g. a PHP notice caused by the same coding style), it is very unlikely that one of the bugs should not be reported.

To keep it short: The way the suggestions are generated should be revised. The suggestions could even be restricted to the package, the package and its subpackage (maybe hard to implement, but interesting for e.g. Structures_DataGrid or Validate), or at least to categories.

(To give a real-life example: While submitting this request, a got three hints on pearweb, but also two hints on HTTP_WebDAV_Server and HTTP_Request.)

pearweb: Feature/Change Request 11026 [Assigned] Reminder for pear-group about accounts not being processed

dufuz at php dot net — 2008-02-09T19:03:27+00:00

pearweb Feature/Change Request
Reported by dufuz
2007-05-13T18:41:23+00:00
PHP: Irrelevant OS:  Package Version: 1.15.2

Description:
------------
The idea is to have a cronjob run X many times a week (perhaps only once) and check if there are any accounts or karma requests that haven't been processed, we'd define a stalled age, probably a week and if the request is 1 week or more then pear-group would be emailed about it and thus someone could jump in and resolve it.

This way pear-group doesn't have to assign a certain person to monitor the account approving stage and also if people forget it then we will have these reminders to bug us.

pearweb: Feature/Change Request 10955 [Open] pearweb installation script should remember your alternative DSN

daniel dot oconnor at gmail dot com — 2008-02-01T20:46:33+00:00

pearweb Feature/Change Request
Reported by doconnor
2007-05-06T11:21:37+00:00
PHP: 5.2.1 OS:  Package Version: 1.15.0

Description:
------------
When you first install pearweb, you (sometimes) go through the fooling about of pointing to an alternative DSN.

After you've done that, you get connection failures when you visit the installation in your browser.

the run-script should:
 1. prompt me for my DSN
 2. if it's different to the default, write it out to file (pear-local-configuration.php) along with any other configuration (PEAR_TMPDIR; for instance; on windows systems)
 3. alter the httpd.conf to include your defaults as well
 php_value auto_prepend_file pear-local-configuration.php

pearweb: Feature/Change Request 10860 [Assigned] Roadmap Col on Bug Tracker View

demon dot gene at gmail dot com — 2007-11-18T13:30:59+00:00

pearweb Feature/Change Request
Reported by ashnazg
2007-04-27T13:51:47+00:00
PHP: 5.1.6 OS: irrelevant Package Version: 1.14.0

Description:
------------
Could a "Roadmap" column be added to the already tight Bug Tracker view?  It would help see at-a-glance which bugs were unassigned to maps, even if it showed only a boolean flag rather than the map number.  Perhaps the "Summary" column could squeeze in a little to make room, since it already wraps longs lines in its rows.