checksum error when installing dom4j-1.6.1

[sgendler@…]

I got repeated checksum errors, despite clean --all and other remedies. I compared Portfile to checksum of file retrieved from sourceforge URL in port output and the checksums matched. The checksum for the file downloaded by port, however, was utterly different:

INCORRECT: [96] ...distfiles/dom4j %>openssl md5 dom4j-1.6.1.tar.gz MD5(dom4j-1.6.1.tar.gz)= 520b2f0cbfcabca66786d8da1d033ae5

CORRECT: ~/Downloads %>openssl md5 dom4j-1.6.1.tar.gz MD5(dom4j-1.6.1.tar.gz)= 1e7ef6d20939315714de4a8502f27b2d

Both files were downloaded simultaneously - one via Safari and the other via port. I'd be inclined to blame some sort of caching between my computer and sourceforge, except that it appears to be dependent upon user-agent. I just checked, and got the correct file via mozilla, too.

I'll probably simulate the port user-agent in a browser and sees what happens in a bit, but I need to get back to work for a while, first. I've been battling this problem for well over an hour already. It'd help if someone were to post the user-agent so that I don't have to go sniffing for it on the wire.

[sgendler@…]

That should read:

INCORRECT:

[96] ...distfiles/dom4j %>openssl md5 dom4j-1.6.1.tar.gz

MD5(dom4j-1.6.1.tar.gz)= 520b2f0cbfcabca66786d8da1d033ae5

CORRECT:

~/Downloads %>openssl md5 dom4j-1.6.1.tar.gz

MD5(dom4j-1.6.1.tar.gz)= 1e7ef6d20939315714de4a8502f27b2d

[blb@…]

port is using libcurl to fetch files, and port sets the agent to "MacPorts x.y.z libcurl/r.s.t" (x.y.z being the MacPorts version and r.s.t being the libcurl one). Though I don't see how the user agent setting would affect what was downloaded.

Tried grabbing the file from sourceforge here and it had the correct checksum. When you have the bad file, what does 'file /opt/local/var/macports/distfiles/dom4j/dom4j-1.6.1.tar.gz' say?

[jmroot (Joshua Root)]

Seems OK here. Maybe one of the SF mirrors has a corrupt file?

[(none)]

Milestone Port Bugs deleted

[tobypeterson]

Works for me... if it's still broken after clean --all, reopen and include debugging output...