Filesize of http://distfiles.gentoo.org/distfiles/GMT_share.tar.bz2 is 3662062 Bytes but (according to ftp://ftp.soest.hawaii.edu/gmt/) it have to be: - for GMT version 3: 3661321 Bytes - for GMT version 4: 3661351 Bytes Otherwise the installation will fail with: >>> md5 files ;-) files/digest-gmt-4.1 >>> md5 src_uri ;-) GMT4.0_progs.tar.bz2 !!! Digest verification Failed: !!! /usr/portage/distfiles/GMT_share.tar.bz2 !!! Reason: Filesize does not match recorded size
Well, this is completely FUBAR and cannot work at all. How is this stuff supposed to work with different file sizes for various versions using identical tarball names? digest-gmt-3.4.4-r1 MD5 6f7d5721167e037b03c2bed9f4bb8725 GMT_full.tar.bz2 28789894 MD5 63217a3ca2ebcf3b918f085651a91e12 GMT_high.tar.bz2 8641460 MD5 7375498ea9894255e753bd377ef6eafb GMT_share.tar.bz2 3662062 MD5 3361f8dbf09443814c0c68fb9cfda1b5 triangle.tar.bz2 90342 digest-gmt-4.0 MD5 ffef8d3d3308278fe3e7fcd333e8c610 GMT_full.tar.bz2 28792514 MD5 10f16ecac3eb5435373f76074c847363 GMT_high.tar.bz2 8706163 MD5 f5f2b272f8c8b575ef96849cb3add36f GMT_share.tar.bz2 3661351 MD5 1d65b96eca53342c659676eda3591527 triangle.tar.bz2 103116 digest-gmt-4.1 MD5 ffef8d3d3308278fe3e7fcd333e8c610 GMT_full.tar.bz2 28792514 MD5 10f16ecac3eb5435373f76074c847363 GMT_high.tar.bz2 8706163 MD5 f5f2b272f8c8b575ef96849cb3add36f GMT_share.tar.bz2 3661351 MD5 1d65b96eca53342c659676eda3591527 triangle.tar.bz2 103116 The only thing it produces here is a nifty traceback: <snip> Traceback (most recent call last): File "/usr/bin/emerge", line 3339, in ? mydepgraph.merge(pkglist) File "/usr/bin/emerge", line 1981, in merge retval=portage.doebuild(y,"fetch",myroot,self.pkgsettings,edebug,("--pretend" in myopts),fetchonly=1,tree="porttree") File "/usr/lib/portage/pym/portage.py", line 2825, in doebuild if need_distfiles and not fetch(fetchme, mysettings, listonly=listonly, fetchonly=fetchonly): File "/usr/lib/portage/pym/portage.py", line 2035, in fetch writemsg("!!! Got: "+reason[1]+"\n") TypeError: cannot concatenate 'str' and 'long' objects </snip>
There was no particular reason to keep the old version in portage - everyone should have transitioned by now. It seems they silently changed the share tarball on their servers before ours mirrored the files. In future I will have to create versioned tarballs to reflect their apparently unversioned yet changing tarballs. I only recently obtained permission to mirror the files on our infrastructure and the issue with version 3 had not hit home. If anyone has any ideas for a better solution I would be interested, otherwise I will do as I have said above with their next release. Hopefully this has fixed any immediate issues. Please reopen if it has not.
Thanks this works fine. I'm not sure if anyone uses version 3.x of this tool. I used this version once but this was about 7 years ago.
