[Bug 186993] Review Request: shippy - Space invaders / Galaxians like game with powerups

[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: shippy - Space invaders / Galaxians like game with powerups


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





------- Additional Comments From wart at kobold.org  2006-03-31 02:19 EST -------
(In reply to comment #20)

> One other thing I noticed is when I try to install shippy-common I get:
> # rpm -ivh shippy-common-1.3.3.7-2.x86_64.rpm
> error: Failed dependencies:
>         shippy-engine = 1.3.3.7 is needed by shippy-common-1.3.3.7-2.x86_64


> however, there is no shippy-engine package, just shippy.

shippy-engine is provided by both the base shippy package and shippy-allegro. 
You need to install shippy-common with one of these to get the full game. 
Fortunately, yum will make sure that the dependencies are satisfied.

> APPROVED! [2][3]
> 
> [1] dumb-devel requires allegro-devel must be fixed!  This still fails in mock
> for FC5.

If I'm not mistaken, Hans has (or is in the process of) fixing this in the dumb
package.

> [2] Since this is my first ever official approval perhaps wart or someone might
> want to take a quick 2nd look

Already did.  :)

> [3] Please review that rpmlint error which I couldn't understand,

rpmlint does not like high score files in /var/lib/games being marked as
configuration files.  Perhaps we need to discuss this in the Games SIG.  Should
scoreboard files be marked %config(noreplace) or not?  They aren't really
configuration files, but we also don't want to have them replaced during an upgrade.

> and look into
> why installing shippy-common asks for shippy-engine when the package name is
> just "shippy".

See comment 4 for the explanation of shippy-engine.

-- 
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.