#28499 closed defect (wontfix)
libiconv: checksum failure because of local proxy blocking facebook
| Reported by: | artem.zavyalov@… | Owned by: | ryandesign (Ryan Carsten Schmidt) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | Cc: | ||
| Port: | libiconv |
Description (last modified by mf2k (Frank Schima))
$ sudo port install macfuse ---> Computing dependencies for macfuse ---> Dependencies to be installed: autoconf help2man gettext libiconv p5-locale-gettext perl5 perl5.8 m4 automake libtool pkgconfig ---> Verifying checksum(s) for libiconv Error: Checksum (md5) mismatch for libiconv-1.13.1.tar.gz Error: Checksum (sha1) mismatch for libiconv-1.13.1.tar.gz Error: Checksum (rmd160) mismatch for libiconv-1.13.1.tar.gz *** The non-matching file appears to be HTML. See this page for possible reasons for the checksum mismatch: <http://trac.macports.org/wiki/MisbehavingServers> *** Error: Target org.macports.checksum returned: Unable to verify file checksums Error: Failed to install libiconv Log for libiconv is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_libiconv/main.log Error: The following dependencies were not installed: autoconf help2man gettext libiconv p5-locale-gettext perl5 perl5.8 m4 automake libtool pkgconfig Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets>
Attachments (1)
Change History (10)
Changed 13 years ago by artem.zavyalov@…
comment:1 Changed 13 years ago by mf2k (Frank Schima)
| Description: | modified (diff) |
|---|---|
| Keywords: | checksum libiconv removed |
| Milestone: | MacPorts 2.0.0 |
| Owner: | changed from macports-tickets@… to ryandesign@… |
comment:2 follow-up: 3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Did you read MisbehavingServers? What is in the file (/opt/local/var/macports/distfiles/libiconv/libiconv-1.13.1.tar.gz)? (Open it in a text editor.)
comment:3 Changed 13 years ago by artem.zavyalov@…
Ohh... mostly it looks like no file for this archive...
cat /opt/local/var/macports/distfiles/libiconv/libiconv-1.13.1.tar.gz <html> <head> <title></title> </head> <body bgcolor="ffffff"> <h2><h2> <p> This URLs or Page has been blocked. </body> </html>
comment:4 Changed 13 years ago by artem.zavyalov@…
actually may be because it's trying to fetch file from
http://mirror.facebook.net/gnu/gnu/libiconv
looks like facebook blocked by proxy...
could I change source repository or manually use other mirror???
comment:5 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Summary: | Checksum mismatch for libiconv-1.13.1.tar.gz → libiconv: checksum failure because of local proxy blocking facebook |
|---|
You cannot pick the distfiles mirror used; MacPorts picks it for you based on lowest ping time. If your company's DNS server has remapped all Facebook hostnames to its own proxy server, that would explain why that server has the lowest ping time for you.
You can manually download distfiles and place them in the right place.
I added the Facebook mirrors to MacPorts last September because they have mirrors for many projects and I assumed they would be fast, but I did not consider that many businesses would block Facebook, and might not be so discriminating about how they do this. Still, this is the first report I've seen about it. Could you ask your proxy administrators to relax their block slightly? I understand the need to block users from accessing www.facebook.com, maybe even *.facebook.com, but there's no need to block users from accessing their mirrors of open-source software at mirror.facebook.net.
In addition, your proxy's administrator should reconfigure the web server that produces their "This URLs or Page has been blocked" message. They are currently returning an HTTP status code (probably "200 OK") which means everything is ok, the request was successfully processed. This is clearly not the case. They should pick another HTTP status code which indicates that some error has occurred; MacPorts would have seen that error code and tried a different mirror. "404 Not Found" or "403 Forbidden" aren't exactly right, but would be better than "200 OK".
comment:6 follow-up: 8 Changed 13 years ago by artem.zavyalov@…
Thank you for your help!!! I just add
"127.0.0.1 facebook.net" to /etc/hosts to prevent downloading something from this site and it's fix problem )))
PS: yes - our router setup to deny any link with *facebook* on it - any such http://who.is/search.php?query=facebook.net&search_type=Whois&submit=Who.is+Search
comment:7 Changed 13 years ago by artem.zavyalov@…
so you can close this ticket! thank you for your help!
comment:8 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Replying to artem.zavyalov@…:
"127.0.0.1 facebook.net" to /etc/hosts to prevent downloading something from this site and it's fix problem )))
I think you mean "127.0.0.1 mirror.facebook.net". That'll work for you... but other users on your network would have the same problem.
PS: yes - our router setup to deny any link with *facebook* on it - any such http://who.is/search.php?query=facebook.net&search_type=Whois&submit=Who.is+Search
I still think that's overly restrictive and should be relaxed. I also still think your "blocked" page needs to be fixed as per my previous message. But these issues are up to you and your network administrators.
The only fix we could make for this in MacPorts right now would be to remove the Facebook mirrors from our list, but since you're the first person I'm aware of this having affected in 5 months, I'm not going to do that for now. But I'll continue to monitor the tickets and we can reconsider later if it proves to be a bigger problem.
comment:9 Changed 13 years ago by artem.zavyalov@…
No - don't delete facebook from list. I't not macports fault and not facebook fault. We'll fix this problem when the guy who manage our network will be back from vacation and fix this problem... so no wares! But btw may be it will be good idea to create configuration file for macports with list of sources (something like /etc/apt/sources.list in debian) in this case everybody can fix this kind of issues with out any tricks )))
and yes, i put "127.0.0.1 *.facebook.net" to /etc/hosts
Very appreciate your help!
installation log