After downloading cedega 4.0.1 and point2play 1.3.1, running emerge -u cedega or emerge -u point2play fails with: # emerge -u point2play; emerge -u cedega Calculating dependencies ...done! >>> emerge (1 of 1) app-emulation/point2play-1.3.1 to / !!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: 010f033c1a80165959939e9d2f1dd5f5 >>> your file's digest: ca6bbb5ba019a4715d6d5ffbab698cc4 !!! File does not exist: /usr/portage/distfiles//point2play-small-1.3.1.tgz Calculating dependencies ...done! >>> emerge (1 of 1) app-emulation/cedega-4.0.1 to / !!! File is corrupt or incomplete. (Digests do not match) >>> our recorded digest: 30b245977dfa50e7d1adadd9ad4822d2 >>> your file's digest: 47d40f6e35aa7e6c5a5f60c6d3fd6922 !!! File does not exist: /usr/portage/distfiles//cedega_4.0.1-1.i386.tgz Reproducible: Always Steps to Reproduce: 1.Download the new transgaming files 2.Try to emerge them 3.Watch the fireworks Actual Results: md5sums differ; emerge fails. Expected Results: md5sums same; emerge succeeds.
Found additional information on the situation: http://transgaming.org/forum/viewtopic.php?t=660 games.slashdot.org/article.pl?sid=04/08/15/2034208
Hmm. I'm not up on my ebuild-foo, but it seems like it'd be somewhat straightforward to change the signature to a Known signature (the bit locations are known), and *then* compare md5s. Is this possible within the current ebuild/portage system, or would this require a rewrite of ebuild/emerge/portage?
Quote from transgaming forum: "Bytes 0x10 through 0x23 in the tgz are the signature." Solution is simple: Just zero the signature. For instance with: dd if=tgz of=tmp1 count=16 bs=1 dd if=/dev/zero of=tmp2 count=19 bs=1 dd if=tgz of=tmp3 skip=35 bs=1 cat tmp1 tmp2 tmp3 > tgz Now you can compute a md5sum without the signature.
Indeedy. Do the md5sums in portage assume 0-set bytes?
Mail from transgaming: This problem was due to TransGaming's prototype watermarking scheme. Due to the errors it is causing with the Gentoo package management system we have now disabled the watermarking scheme and the error should be resolved. -- Lucas Smithen Quality Assurance and Technical Support TransGaming Technologies lucas@transgaming.com
since users pay for this service, I'd say it's critical to get it to work. Thanks.
cedega-4.0.1 doesn't work for me, either. original package: >>> our recorded digest: 1bdadc6811f24bcaf54f393dcebebe59 >>> your file's digest: acd6fdea8534bf828e6d186ea6343c24 after the treatment suggested by Clemens: >>> our recorded digest: 1bdadc6811f24bcaf54f393dcebebe59 >>> your file's digest: b7ff4d43047b0f3b4cd55b2593c17274
A simple workaround is changing the md5sum in: /usr/portage/app-emulation/cedega/files/digest-cedega-4.0.1 to what your md5sum happens to be for the new cedega download. Do the same for whatever else you want to jump around md5sum checking on. Emerge works great for me
From a link provided in the latest trasgaming newsletter (http://www.transgaming.com/gavstates.php) <blockquote>Recently, TransGaming began a pilot project to watermark some of our online binary downloads to track a software pirate who has been posting Cedega releases to peer to peer networks in violation of the Cedega software license. That project was successful, but it caused some unanticipated problems for our Gentoo customers; as a result, we decided to suspend the effort for the moment.</blockquote> Looks like this bug is [for now, at least] moot. This may need to be re-marked in the future, however.
