pear-install-phar: checksum mismatch

[mkjasinski+other@…]

--->  Fetching archive for pear-install-phar
--->  Attempting to fetch pear-install-phar-20110901_4.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/pear-install-phar
--->  Attempting to fetch pear-install-phar-20110901_4.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/pear-install-phar
--->  Attempting to fetch pear-install-phar-20110901_4.darwin_13.x86_64.tbz2 from http://packages.macports.org/pear-install-phar
--->  Fetching distfiles for pear-install-phar
--->  Attempting to fetch install-pear-nozlib.phar from http://pear.php.net
--->  Verifying checksums for pear-install-phar
Error: Checksum (rmd160) mismatch for install-pear-nozlib.phar
Error: Checksum (sha256) mismatch for install-pear-nozlib.phar
Error: org.macports.checksum for port pear-install-phar returned: Unable to verify file checksums
Please see the log file for port pear-install-phar for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_php_pear-install-phar/pear-install-phar/main.log
Error: Problem while installing pear-install-phar
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

File: pear-install-phar-20110901_4.darwin_13.x86_64.tbz2 file does not exist.

[ryandesign (Ryan Carsten Schmidt)]

It's not a problem that a package doesn't exist. The problem is that the source code's checksum has changed; this problem is common with ports that use an unversioned distfile.

[mkjasinski+others@…]

ok, now what?

[reed.smith@…]

I'm encountering the same issue here with this port and agree with the sentiment: Now what?

Can we force this particular package to install anyway? It should be safe to do so since PEAR libs are basically a bunch of PHP scripts...right? Some input from Ryan would be nice because I'm working on a production server.

[reed.smith@…]

Replying to reed.smith@…:

I'm encountering the same issue here with this port and agree with the sentiment: Now what?

Can we force this particular package to install anyway? It should be safe to do so since PEAR libs are basically a bunch of PHP scripts...right? Some input from Ryan would be nice because I'm working on a production server.

After running a port selfupdate and a port clean --dist, pear-install-phar appears to install. Looks like the retrieval location changed to something Macports-ish instead of pear.php.net is what corrected the problem.

[pixilla (Bradley Giesbrecht)]

See r116481