[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Warzone 2100 packaging status report



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Linas Žvirblis wrote:
> Dear colleagues,
> 
> I am back.
> 
> Packaging work for Warzone 2100 is taking way too long, and this is
> mostly my fault. I will try my best to make it happen this time.

Same goes for glest... :-/ (as in *my* fault, not yours), but OTOH, glest's
upstream seems rather split and busy with other things (the CVS didn't had
any commits for quite a few months, time I checked).

> I have prepared updated packages for Warzone 2100 release 2.0.6. The
> packaging files are available at Debian Games Team SVN repository [0],
> and the source tarball on Alioth web space [1]. A tutorial for building
> the packages is available in the wiki [2].
> 
> [0]svn+ssh://svn.debian.org/svn/pkg-games/packages/trunk/warzone2100
> [1]http://pkg-games.alioth.debian.org/tarballs/warzone2100_2.0.6.orig.tar.gz
> [2]http://wiki.debian.org/Games/SVN
> 
> I have purged the changelog, because the data it contained is now
> irrelevant. (Eddy, what is the point of build-depending on dpkg-dev? It
> is build-essential, is it not?)

You use a feature (the variables that allow bin NMUs) which is present only
in dpkg-dev 1.13.19 or later. You have to have a versioned dependency on dpkg-dev.

> The package is set to Architecture: any, but this may not be the best
> option. Warzone 2100 does not officially support 64-bit architectures,
> and insists on being built as 32-bit application.

Maybe we can patch that (I have a 64 bit system ;-)

> I patched it to allow building as 64-bit, but the resulting binary seems
> unstable and segfaults almost immediately after startup (displays splash
> screen for a couple of seconds) on AMD64 for me. I, however, have seen
> people reporting success running 64-bit version of Warzone 2100, so I
> would greatly appreciate some testing here.

Will do.

> P.S. Please post any comments to debian-devel-games@lists.debian.org
> mailing list.

Your reply-to is the proper way to fix this...
- --
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGLK45Y8Chqv3NRNoRAp2tAJkBBNnei5oMqiOgWXHC6qWMc3rm3gCgtKzT
VRQExTr8wegqUtujPbDpG1U=
=TsDm
-----END PGP SIGNATURE-----



Reply to: