Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#39494 closed defect (fixed)

php: es.php.net is gone

Reported by: funkychicken818@… Owned by: ryandesign (Ryan Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc:
Port: php5

Description (last modified by larryv (Lawrence Velázquez))

i am unable to upgrade to php 5.3.26 i keep seeing the same issue over and over. I have tried doing selfupdate, clean --all php5, upgrade outdated, upgrade php5, nothing has worked its just the same issue over and over again for at least two weeks now.

[Users/sam] > clean --all php5
--->  Cleaning php5
[Users/sam] > upgrade php5                                  
--->  Computing dependencies for php5
--->  Fetching archive for php5
--->  Attempting to fetch php5-5.3.26_0+apache2+fastcgi+pear.darwin_12.x86_64.tbz2 from http://packages.macports.org/php5
--->  Attempting to fetch php5-5.3.26_0+apache2+fastcgi+pear.darwin_12.x86_64.tbz2 from http://lil.fr.packages.macports.org/php5
--->  Attempting to fetch php5-5.3.26_0+apache2+fastcgi+pear.darwin_12.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/php5
--->  Fetching distfiles for php5
--->  Attempting to fetch php-5.3.26.tar.bz2 from http://es.php.net/get/php-5.3.26.tar.bz2/from/this/mirror?dummy=
--->  Verifying checksum(s) for php5
Error: Checksum (rmd160) mismatch for php-5.3.26.tar.bz2
Error: Checksum (sha256) mismatch for php-5.3.26.tar.bz2
***
The non-matching file appears to be HTML. See this page for possible reasons
for the checksum mismatch:
<https://trac.macports.org/wiki/MisbehavingServers>
***
The file has been moved to: /opt/local/var/macports/distfiles/php5/php-5.3.26.tar.bz2.html
Error: org.macports.checksum for port php5 returned: Unable to verify file checksums
Please see the log file for port php5 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_php5/php5/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

Change History (7)

comment:1 Changed 6 years ago by larryv (Lawrence Velázquez)

Description: modified (diff)
Keywords: php php5 php5.3.26 removed
Owner: changed from macports-tickets@… to ryandesign@…
Port: php5 added

Thanks for the ticket. In the future, please Cc relevant port maintainers.

http://es.php.net/ doesn’t resolve anymore.

comment:2 Changed 6 years ago by larryv (Lawrence Velázquez)

Priority: HighNormal

And please don’t set the Priority field; it’s reserved for MacPorts team members.

comment:3 Changed 6 years ago by funkychicken818@…

Well this has been an issue for at least two weeks now and i need to install php5-apc and i can't do so because of this bug. I would say this is an important bug that should be fixed right away, and i bet i am not the only one with this issue.

comment:4 Changed 6 years ago by ryandesign (Ryan Schmidt)

Resolution: fixed
Status: newclosed
Summary: php5 - unable to upgrade to php5.3.26php: es.php.net is gone

I don't believe this issue has existed for two weeks; I last verified the list of PHP mirrors ten days ago; see #39414.

I've updated the list again in r107212. es is out, fr is in.

Wait 30 minutes, then "sudo port clean --all php5" and "sudo port selfupdate" and then try again.

Also, please consider switching to the new php53-* ports instead of the old php5-* ports. And consider upgrading to php54-* or php55-*.

comment:5 Changed 6 years ago by funkychicken818@…

i have been running "sudo port clean --all php5" and "sudo port selfupdate" for the last two weeks every day almost.

comment:6 Changed 6 years ago by ryandesign (Ryan Schmidt)

Ok, well if you wait another 18 minutes and do so again, it should work, since I've taken the now-nonexistent es.php.net server out of the list. If you find such problems again in the future, please don't hesitate to report them. Thanks.

comment:7 in reply to:  3 Changed 6 years ago by larryv (Lawrence Velázquez)

Replying to funkychicken818@…:

I would say this is an important bug that should be fixed right away, and i bet i am not the only one with this issue.

We generally only use High priority for issues that have security implications.

Note: See TracTickets for help on using tickets.