RE: [PEAR-DEV] Help needed, weird bug with the PEAR frontends
| From: | Lukas Smith | Date: | Mon, 26 May 2003 16:01:14 +0000 |
| Subject: | RE: [PEAR-DEV] Help needed, weird bug with the PEAR frontends | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-16720@lists.php.net to get a copy of this message | ||
> From: Pierre-Alain Joye [mailto:paj@pearfr.org]
> Sent: Monday, May 26, 2003 3:46 AM
> On Win32, following these steps:
> 1. install PEAR using CLI (go-pear)
> 1.1 Test it, install, list, list-all (here everyting works fine)
> 2. install PEAR Frontend Web || go-pear web
> 3. run it, change anything related to the PEAR conf (i.e
preferred_state
> to alpha
> 4. go back to cli
> 5. run php list => and now we run in troubles, b0rked
>
> For an unknown reason, the registry (serialized data) is now b0rked.
You
> will get Notices like:
> unserialize(): Error at offset 35137 of 42316 bytes in Registry.php on
> line 327
>
> I'm interested about any feedback on different platforms or win32.
Well now you got me confused. I thought you could reproduce the bug with
Rasmus's test script which means all you have is a broken snaps binary?
So with a working snaps binary that includes the latest fix to
unserialize things should theoretically work for you.
For me its even weirder as I cannot reproduce the bug with Rasmus's test
script but I am pretty sure I have the same snaps release installed as
you have (php4-win32-STABLE-200305252030.zip). Either way I am
definitely experience the above issue with the installer which would
point to the fact that the known and fixed unserialize bug is something
different.
Regards,
Lukas