kxmame package wrongly conflicts with xmame-x

Bug #113699 reported by meldroc on 2007-05-09
10
Affects Status Importance Assigned to Milestone
kxmame (Ubuntu)
Medium
MOTU

Bug Description

Binary package hint: kxmame

If I check the dependencies for kxmame version 2.0~beta0ubuntu2, I notice that it conflicts with the package xmame-x, while requiring xmame-sdl. This is wrong. Kxmame has been designed to work with both X11 and SDL versions of xmame (and xmess while we're at it), so kxmame's dependency behavior should have it depend on either xmame-x or xmame-sdl - at least one of the two is fine, and they can coexist together. The previous version of kxmame (1.91-0ubuntu1 from edgy) does this correctly.

Micah Cowan (micahcowan) wrote :

Confirming due to sufficient information.

Changed in kxmame:
importance: Undecided → Medium
status: Unconfirmed → Confirmed

Hi this also affect me, and its a big problem here because xmame-sdl is dga broken, and some games run really very faster here in dga.
I want to know how to debug xmame to catch the problem (in dga).
I wish kxmame should return to be the best MAME frotend, bye.

Psykotik (linux-ikiru) wrote :

I confirm issues reported here, and would also be able to use xmame-x with kxmame, since xmame-sdl crash my system.

I suppose if you want something done, you have to do it yourself...

Included is a revised debian/control file which will fix this dependency bug. I just removed the Conflicts line and put xmame-x and xmess-x in the Depends line.

I've verified that it works on my system. Could I talk the maintainer into incorporating this fix into the official release?

Lauri Kainulainen (luopio) wrote :

Still present here on ubuntu studio 8.04. Attached is a deb package with the mess-x and mame-x conflicts removed.

Changed in kxmame (Ubuntu):
assignee: nobody → MOTU (motu)
Anders Østerholt (diebels) wrote :

Bug still present in Jaunty. Attaching amd64 package with correct dependencies.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers