Bug#775483: hexen: verify that the demo works in some packaged engine, and re-enable

2015-06-24 Thread Alexandre Detiste
Alright. I have filed a bug against chocolate-doom with g-d-p in CC that will get closed when the next chocolate-doom release is uploaded. So you will get informed that the Hexen demo is now supported. Thanks, I guess that calls for a new GDP release. I noticed doomsday-compat doesn't check

Bug#775483: hexen: verify that the demo works in some packaged engine, and re-enable

2015-05-31 Thread Fabian Greffrath
Am Samstag, den 30.05.2015, 15:23 +0200 schrieb Alexandre Detiste: I guess removing this from hexen.yaml is enough: # The other provider of hexen-engine, chocolate-doom, # can play the full game but not the demo. engine: doomsday Then the hexen-demo-wad package generated from

Bug#775483: hexen: verify that the demo works in some packaged engine, and re-enable

2015-05-30 Thread Alexandre Detiste
Hi, I guess removing this from hexen.yaml is enough: # The other provider of hexen-engine, chocolate-doom, # can play the full game but not the demo. engine: doomsday Then the hexen-demo-wad package generated from now on will use the default engine: chocolate-hexen | hexen-engine

Bug#775483: hexen: verify that the demo works in some packaged engine, and re-enable

2015-05-28 Thread Fabian Greffrath
Hi there, Am Dienstag, den 31.03.2015, 06:27 +0200 schrieb Fabian Greffrath: The next release of Chocolate Doom, ne Hexen, will have support for the 4-Level Demo Version. \o/ the next release of chocolate-doom is due shortly. Do I have to add anything to the packaging to indicate that the

Bug#775483: hexen: verify that the demo works in some packaged engine, and re-enable

2015-03-31 Thread Alexandre Detiste
The next release of Chocolate Doom, ne Hexen, will have support for the 4-Level Demo Version. \o/ Cool I'd be happy to swap it back to chocolate-doom (= x.y) | hexen-engine Shouldn't heretic-engine hexen-engine be added to the official list of virtual packages too ?

Bug#775483: hexen: verify that the demo works in some packaged engine, and re-enable

2015-03-31 Thread Simon McVittie
On 31/03/15 09:43, Alexandre Detiste wrote: Shouldn't heretic-engine hexen-engine be added to the official list of virtual packages too ? https://www.debian.org/doc/packaging-manuals/virtual-package-names-list.txt Policy says: They should not use virtual package names (except privately,

Bug#775483: hexen: verify that the demo works in some packaged engine, and re-enable

2015-03-30 Thread Fabian Greffrath
Am Montag, den 02.02.2015, 08:58 +0100 schrieb Fabian Greffrath: We are working on it: https://github.com/chocolate-doom/chocolate-doom/commits/hexndemo Merged: https://github.com/chocolate-doom/chocolate-doom/issues/504 The next release of Chocolate Doom, ne Hexen, will have support for

Bug#775483: hexen: verify that the demo works in some packaged engine, and re-enable

2015-02-02 Thread Simon McVittie
On 02/02/15 07:58, Fabian Greffrath wrote: Am Freitag, den 16.01.2015, 09:46 + schrieb Simon McVittie: The Hexen demo (shareware version? incomplete version, anyway) is currently commented out because it crashes chocolate-doom We are working on it:

Bug#775483: hexen: verify that the demo works in some packaged engine, and re-enable

2015-02-02 Thread Fabian Greffrath
Am Freitag, den 16.01.2015, 09:46 + schrieb Simon McVittie: The Hexen demo (shareware version? incomplete version, anyway) is currently commented out because it crashes chocolate-doom, but all the necessary bits are present in data/hexen.yaml. Maybe it works in doomsday or something. We

Bug#775483: hexen: verify that the demo works in some packaged engine, and re-enable

2015-01-16 Thread Simon McVittie
Package: game-data-packager Version: 39 Severity: wishlist The Hexen demo (shareware version? incomplete version, anyway) is currently commented out because it crashes chocolate-doom, but all the necessary bits are present in data/hexen.yaml. Maybe it works in doomsday or something. It seems a