Re: call for help

Greg Beaver wrote:

Hi, I've got a pernicious bug in PEAR 1.4.0a1 and cannot find the problem. Basically, the md5_file() call in the "pear package" command stores a different md5 from the md5 retrieved on install, but I can't find any differences between the files. This only happens with packages that have a package.xml version 2, as far as I can tell. What this means is that I have no frickin idea how to fix this and can't release PEAR until I fix it. Any ideas for finding the mother****ing bug and killing it would be appreciated. Greg

Without looking at the code I'm going to take a stab at this one: 1) Create Package 2) call md5_file() 3) stick the md5 in the file 4) Run install 5) call md5_file See the problem? the second md5_file is run after the MD5 has been placed in the package. You have two choice, remove the md5sum before running md5_file again or don't put the md5sum in the file... instead what about this: 1) Create Package 2) Upload Package 3) server does and stores the md5sum 4) Server puts the md5sum in the RPC calls 5) Install calls md5sum and verifies against the one in the RPC call I am just stabbing in the dark, but it could be the problem :) - Davey