Bugzilla Bug 60014

New ebuild for point2play-1.3.1
Note that 1.3.1 replaces 1.3b, but portage seems that portage thinks that point2play-1.3b is newer than point2play-1.3.1; I don't know how to correct this - masking maybe, or removing the 1.3b ebuild?

Created an attachment (id=37186) [details]
point2play-1.3.1.ebuild

Created an attachment (id=37187) [details]
1.3.1-fix-sound-test.patch

new version of the fix-sound-test patch (updated, because point2play-1.3.1
added alsa support to test_sound.py)

now in portage

I just tried to emerge 1.3.1 and portage complained that the digests did not
match.

I recomputed the digests and then it complained that the sound fix patch didn't
apply.

I guess transgaming changed their tarball.

Weird... transgaming did change their tarball, but diff doesn't show any
differences when unpacked. I guess they got a new version of gzip?

In any case, the patch still works for me after recomputing the digest. I
downloaded point2play-small-1.3.1.tgz on Aug 15 16:18 UTC; size is 822912, and
MD5 is 020a9d779bb48b2fd42d00bd64a5e5ee.

Did you use the ebuild from here or the one in portage?  I used the one in
portage and after doing:

ebuild /usr/portage/app-emulation/point2play/point2play-1.3.1.ebuild digest

Then:

emerge point2play

I get:

Calculating dependencies ...done!
>>> emerge (1 of 1) app-emulation/point2play-1.3.1 to /
>>> md5 src_uri ;-) point2play-small-1.3.1.tgz
>>> Unpacking source...
>>> Unpacking point2play-small-1.3.1.tgz to /usr/portage/tmp/portage/point2play-1.3.1/work
 * Applying 1.3.1-fix-sound-test.patch...

 * Failed Patch: 1.3.1-fix-sound-test.patch!
 * 
 * Include in your bugreport the contents of:
 * 
 *  
/usr/portage/tmp/portage/point2play-1.3.1/temp/1.3.1-fix-sound-test.patch-8059.out


!!! ERROR: app-emulation/point2play-1.3.1 failed.
!!! Function epatch, Line 326, Exitcode 0
!!! Failed Patch: 1.3.1-fix-sound-test.patch!



Looking at the patch file in portage, it starts with:

---
/var/tmp/portage/point2play-1.3.1/work/usr/lib/transgaming_point2play/tests/test_sound.py.orig
     2004-08-14 01:22:11.956853792 -0400
+++
/var/tmp/portage/point2play-1.3.1/work/usr/lib/transgaming_point2play/tests/test_sound.py
  2004-08-14 01:22:20.241594320 -0400


Looks like it needs to lose the /var/tmp/portage/point2play-1.3.1/work part.

Perhaps this should be reopened? The digests don't match for me either; this is
a bug.

Yes, removed "/var/tmp/portage/point2play-1.3.1/work/" from the first 2 lines
of the diff, recreated digests, and it emerged fine.

re MAL: Strange, for me both versions of the patch (the one in portage and the
one here, without "/var/tmp/portage/point2play-1.3.1/work/") work fine. What
version of portage and patch are you using?

re Joel: transgaming changed their digests at least 3 times over the past 5
days. On Aug 10, their MD5 was 853704654af8fd88a832bee12a8ee27e. In the portage
tree, on Aug 14, it was 010f033c1a80165959939e9d2f1dd5f5. On Aug 15 (today), it
is 020a9d779bb48b2fd42d00bd64a5e5ee. I have no idea what they are doing, but
once you unpack, diff shows no differences between the files.

portage-2.0.50-r9

I've mailed TransGaming to kindly ask if they could leave their tarballs alone, or at least mark revisions as such.

no, transgaming has started being stupid and watermarking their downloads

thus md5's will never match

Email 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