Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#32733 closed defect (fixed)

postgresql90 @9.0.6 checksum mismatch

Reported by: jlg@… Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: checksum Cc: jyrkiwahlstedt
Port: postgresql90

Description

While running "port upgrade outdated," postgresql90 was the only one out of maybe 20 ports that threw an error. I ran "port clean postgresql90" and then "port -d upgrade postgresql90" and received the output below (log file is attached as well).

I notice there are similar issues with postgresql90 in recent tickets, which were dismissed with either "it works for me" or "you're probably using opendns." I don't think the NS domain redirection is the problem here, though it could be--so here's my $0.02 on the issue. I realize that NX domain redirection is RFC-ignorant behavior, but given the number of people who are either forced to use it by their ISP, or are choosing to use it (e.g. OpenDNS), I think it would be a Very Good Thing for MacPorts to be able to gracefully handle it. Realistically, the MacPorts community is probably not going to be able to convince Suddenlink, Time Warner, Verizon, etc. etc. to change their DNS server configuration--especially given the fact that much of the MacPorts community doesn't even understand the underlying issue. Reading the other tickets, it seems to be a matter of principle, but I think there are more important battles to fight. NX domain redirection is not a hill worth dying on.

DEBUG: Executing org.macports.main (postgresql90)
DEBUG: archivefetch phase started at Mon Jan  2 08:34:07 CST 2012
--->  Fetching archive for postgresql90
DEBUG: Executing org.macports.archivefetch (postgresql90)
--->  postgresql90-9.0.6_0+universal.darwin_9.ppc-ppc64.tgz doesn't seem to exist in /opt/local/var/macports/software/postgresql90
--->  Attempting to fetch postgresql90-9.0.6_0+universal.darwin_9.ppc-ppc64.tgz from http://packages.macports.org/postgresql90
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
DEBUG: Fetching archive failed:: The requested URL returned error: 404
DEBUG: fetch phase started at Mon Jan  2 08:34:07 CST 2012
--->  Fetching postgresql90
DEBUG: Executing org.macports.fetch (postgresql90)
DEBUG: checksum phase started at Mon Jan  2 08:34:07 CST 2012
--->  Verifying checksum(s) for postgresql90
DEBUG: Executing org.macports.checksum (postgresql90)
--->  Checksumming postgresql-9.0.6.tar.bz2
Error: Checksum (md5) mismatch for postgresql-9.0.6.tar.bz2
Portfile checksum: postgresql-9.0.6.tar.bz2 md5 4ad7e4fc31ef8b8a75a3e4243933963f
Distfile checksum: postgresql-9.0.6.tar.bz2 md5 48afc3dee4f63007ba8631feb8a9386a
Error: Checksum (sha1) mismatch for postgresql-9.0.6.tar.bz2
Portfile checksum: postgresql-9.0.6.tar.bz2 sha1 4a9a7d5579d3683ca1992b2ba116a4356094b3ca
Distfile checksum: postgresql-9.0.6.tar.bz2 sha1 38bc00982eb8de1434d87c03f432fa2066dfb986
Error: Checksum (rmd160) mismatch for postgresql-9.0.6.tar.bz2
Portfile checksum: postgresql-9.0.6.tar.bz2 rmd160 e1794a28e495b861c2f82b325b4e28e71faa58ca
Distfile checksum: postgresql-9.0.6.tar.bz2 rmd160 889b9015ad1c3963b3ff8e3e01ede34da19375fe
The correct checksum line may be:
checksums           md5     48afc3dee4f63007ba8631feb8a9386a \
                    sha1    38bc00982eb8de1434d87c03f432fa2066dfb986 \
                    rmd160  889b9015ad1c3963b3ff8e3e01ede34da19375fe
***
The non-matching file appears to be HTML. See this page for possible reasons
for the checksum mismatch:
<https://trac.macports.org/wiki/MisbehavingServers>
***
Error: Target org.macports.checksum returned: Unable to verify file checksums
DEBUG: Backtrace: Unable to verify file checksums
    while executing
"$procedure $targetname"
Warning: the following items did not execute (for postgresql90): org.macports.install org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build org.macports.destroot
Log for postgresql90 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_postgresql90/postgresql90/main.log
DEBUG: invalid command name "::ui_init"
    while executing
"::ui_init any stdout"
    ("eval" body line 1)
    invoked from within
"eval ::ui_init $priority $prefix $channels($priority) $args"
    ("uplevel" body line 2)
    invoked from within
"uplevel 1 $body"
Error: Unable to upgrade port: 1
To report a bug, see <http://guide.macports.org/#project.tickets>

Attachments (1)

main.log (3.8 KB) - added by jlg@… 8 years ago.

Download all attachments as: .zip

Change History (7)

Changed 8 years ago by jlg@…

Attachment: main.log added

comment:1 Changed 8 years ago by jlg@…

Not sure if this helps, but here are the contents of /opt/local/var/macports/distfiles/postgresql90/postgresql-9.0.6.tar.bz2

<html>
        <head>
                <title>  </title>
                <script type="text/javascript">
        function bredir(a,b,c,d,e,ldr){var f,g,h,i,j;var k=false;var l=false;var m=[[300,250,false],[250,250,false],[240,400,false],[336,280,false],[180,150,false],[468,60,false],[234,60,false],[88,31,false],[120,90,false],[120,60,false],[120,240,false],[125,125,false],[728,90,false],[160,600,false],[120,600,false],[300,600,false],[300,125,false],[530,300,false],[190,200,false],[470,250,false],[720,300,true],[500,350,true],[550,480,true]];if(typeof window.innerHeight=="number"){g=window.innerHeight;f=window.innerWidth}else if(typeof document.body.offsetHeight=="number"){g=document.body.offsetHeight;f=document.body.offsetWidth}for(var n=0;n<m.length;n++){j=m[n];h=Math.abs(f-j[0]);i=Math.abs(g-j[1]);if(h<=2&&i<=2){k=true;l=j[2]}}if((a!="www.facebook.com"&&a!="platform.twitter.com")&&(k||f<100&&f!==0||g<100&&g!==0)){if(l&&self==parent){self.close();return}return "/b"+"anner.php?w="+f+"&h="+g+"&d="+a+"&url="+b+"&ref="+c+"&view="+d}else if((a=="www.facebook.com"||a=="platform.twitter.com")&&(f>=250&&g>=60)&&(k||f<100&&f!==0||g<100&&g!==0)){if(l&&self==parent){self.close();return}return e+"&w="+f+"&h="+g+"&ldr="+"b"}else if((a=="www.facebook.com"||a=="platform.twitter.com")&&(f<250||g<60)&&(k||f<100&&f!==0||g<100&&g!==0)){if(l&&self==parent){self.close();return}return "/b"+"anner.php?w="+f+"&h="+g+"&d="+a+"&url="+b+"&ref="+c+"&view="+d}else{return e+"&w="+f+"&h="+g}}
                </script>
        </head>
        <body onLoad="location.replace(bredir('ftp9.us.postgresql.org', 'ftp9.us.postgresql.org%2Fpub%2Fmirrors%2Fpostgresql%2Fsource%2Fv9.0.6%2Fpostgresql-9.0.6.tar.bz2', '', 'error', '/main?url=ftp9.us.postgresql.org%2Fpub%2Fmirrors%2Fpostgresql%2Fsource%2Fv9.0.6%2Fpostgresql-9.0.6.tar.bz2'));" style="margin: 0px;">
                <noscript>
                        <iframe frameborder="0" src="/main?url=ftp9.us.postgresql.org%2Fpub%2Fmirrors%2Fpostgresql%2Fsource%2Fv9.0.6%2Fpostgresql-9.0.6.tar.bz2" width="100%" height="100%"></iframe>
                </noscript>
        </body>
</html>

comment:2 Changed 8 years ago by jlg@…

Maybe that URL should be http://ftp.postgresql.org/pub/source/v9.0.6/postgresql-9.0.6.tar.bz2 instead? Because ftp9.us.postgresql.org appears to be a nonexistent hostname.

comment:3 Changed 8 years ago by ryandesign (Ryan Schmidt)

Cc: jwa@… added
Keywords: postgresql90 removed
Milestone: MacPorts 2.0.4
Owner: changed from macports-tickets@… to mww@…
Port: @9.0.6 removed

comment:4 in reply to:  2 Changed 8 years ago by ryandesign (Ryan Schmidt)

Replying to jlg@…:

Maybe that URL should be http://ftp.postgresql.org/pub/source/v9.0.6/postgresql-9.0.6.tar.bz2 instead? Because ftp9.us.postgresql.org appears to be a nonexistent hostname.

Changed in r88448.

comment:5 in reply to:  description Changed 8 years ago by ryandesign (Ryan Schmidt)

Resolution: fixed
Status: newclosed

Replying to jlg@…:

I realize that NX domain redirection is RFC-ignorant behavior, but given the number of people who are either forced to use it by their ISP, or are choosing to use it (e.g. OpenDNS), I think it would be a Very Good Thing for MacPorts to be able to gracefully handle it.

My original fix for the issue did gracefully handle it. See #25128. But when Joshua committed it he decided to rewrite it in a way that turned it into an error message, rather than transparently try another mirror (which is the behavior we get for users using "proper" DNS servers). I will write a message to the macports-dev list requesting we revisit this topic, because as you say these broken DNS servers are very common and are not going away.

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

See #33930.

Note: See TracTickets for help on using tickets.