[Bug 183969] Review Request: worminator - Sidescrolling platform and shoot'em up action-game

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: worminator - Sidescrolling platform and shoot'em up action-game


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=183969





------- Additional Comments From j.w.r.degoede at hhs.nl  2006-03-05 02:52 EST -------
MUSTFIX
=======
* Data should be a noarch package.  Use:
BuildArch: noarch
This will also clean up the rpmlint error on the -data package.

Fixed, new spec file at:
http://home.zonnet.nl/jwrdegoede/worminator-data.spec

* desktop file category incorrect. It should be:
Category: Application;Game;ArcadeGame;

Fixed, new srpm at the same url as the previous one (I didn't bump release): 
http://home.zonnet.nl/jwrdegoede/worminator-3.0R2.1-1.src.rpm

* Segfaults on FC4-x86_64.  strace shows that the game hangs after the segfault,
leaving a lingering worminator process.

Hmm, I really believe this is because of the old (ancient) allegro in FC-4, 
concedering that FC-5 is almost released and since I don't have any FC-4
installs I won't fix this.

* Started up on FC5-i386, but locked up during the tutorial.
Looking at your strace this seems buried deep in alsalib, thus not a worminator
problem, most likely a problem with alsa and vmware, also is your rawhide fully
up2date? I've tried to reproduce this as you described, but it works for me.

I've extensivly tested this on FC-5 x86_64 and Fc-5 i386 and I've seen no
(unfixed) hangs or crashes. I've also had this tested on PPC to make sure me
endian dixes where correct and there it worked too. Also the Cru packager has
been playing it without any problems.

I have to ask you to believe me here that worminator is not an unstable pile of
XXXX, but that you just have 2 unlucky configurations.


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.