http://qa.mandrakesoft.com/show_bug.cgi?id=5178
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |LATER
------- Additional Comments From [EMAIL PROTECTED] 2003-04-09 06:06 -------
Yes, you are right, the path lenghts are broken, I never experimented with these
registry commands.
The problem is that rpm builds the package in, say
/home/jmdault/rpm/tmp/pear-buildroot/usr/share/pear
To make it possible to install in /usr/share/pear, the build script does a
search and replace of the rpm build root.
Doing that, however, breaks the registry. We'll have to find a new way to build
pear as a RPM...
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: RESOLVED
creation_date:
description:
The files in /usr/share/pear/.registry/*.reg are "broken". They contain
serialized data, like s:4:"toto" which means "String" : Size "4" : data "toto".
But they all contains errors in the size of the string example :
s:81:"/usr/toto". Obviously "/usr/toto" isn't 81 characters !
Consequences are that most of the pear commands like "pear list", "pear update
DB", "pear uninstall DB" are broken.
(Maybe the php-pear should require the php-cli, command line php, for the "pear"
command to work immediately.)
