i tried to upgrade to newer truecrypt. after manual fetch of http://www.truecrypt.org/download/truecrypt-6.3a-linux-x86.tar.gz and rename the tarball emerge fails. from the message Refetching... File renamed to '/usr/portage/distfiles/truecrypt-6.3a.tar.gz._checksum_failure_.dCjZRa' Reproducible: Always Steps to Reproduce:
Why did you make a manual fetching? What happens if you actually do emerge truecrypt?
>Why did you make a manual fetching because emerge claims to have fetch restrictions
Following the forum thread I came to this bug by [0], it looks like theu ser is downloading the 'latest version' (currently 7.0a) tarball and trying to use it with the 6.3a ebuild. This is then failing because of the checksum not matching. Browsing truecrypt's website, I can't see where to download a from source tarball for older versions, so the correct tarball may no longer actually be available. In any case, it seems like there should be a more verbose fetch restriction message for this package to instruct the user exactly what options to select where to get the correct file. [0] http://forums.gentoo.org/viewtopic-p-6424354.html
or bump 7.0 of course. sabayon already has it.
+ 13 Oct 2010; Dane Smith <c1pher@gentoo.org> truecrypt-6.3a.ebuild: + Updated the fetch link wrt bug 335854. + Fixed the download link provided. I hope to have truecrypt-7.0a in portage tonight as well.
