Bug#740988: vavoom fails to run if rebuilt against unstable

[Olly Betts]

On Fri, Mar 07, 2014 at 09:51:59AM +0100, Fabian Greffrath wrote:
> Am Freitag, den 07.03.2014, 15:07 +1300 schrieb Olly Betts: 
> > If I rebuild vavoom 1.33-4 with current unstable, then install it and
> > run vavoom, it fails to start.  If I reinstall the package of 1.33-4
> > currently in the archive, vavoom starts OK, and seems to work - I played
> > a whole level to check (purely in the interests of debugging).
> 
> thank you very much for that bug report. I have to admit, I have already
> seen this before in the course of preparing an NMU for vavoom but forgot
> to file a bug report. The severity is IMHO appropriate, because the game
> simply fails to start. My attempts to debug the issue were also without
> success.
> 
> This and the fact that Vavoom upstream is actually dead and has its
> homepage removed lead me to the conclusion that it is maybe better to
> entirely remove vavoom from Debian before the next stable release.

http://www.vavoom-engine.com/ seems to work for me, and while it's
not as dead as some upstreams I've seen, the last release was over 3
years ago, and last SVN commit about 2.5 years ago:
http://sourceforge.net/p/vavoom/code/4431/log/?path=

But removal doesn't sound too terrible a plan.  Users should still be
able to play most of these games, as we have other doom engine ports in
Debian (I see at least doomsday and prboom-plus), and I noticed at least
two visual glitches while playing the first level of freedoom with
vavoom.

Cheers,
    Olly