Bug#461659: Fwd: Re: warsow: Clarification for the Warsow Content License
Here's the response I received from the Warsow project founder. There should be no problem with getting the Warsow content using the new license into Debian, as far as I know. -- Forwarded Message -- Subject: Re: warsow: Clarification for the Warsow Content License Date: Thursday 28 February 2008 From: [EMAIL PROTECTED] [EMAIL PROTECTED] To: Andres Mejia [EMAIL PROTECTED] hello Andres, sorry for the late answer. Anyway, since warsow 0.42 is out, the answer is yes, yes and yes =) best regards, Fabrice Demurger 2008/2/18, Andres Mejia [EMAIL PROTECTED]: Hello, I have some more questions for the chasseur de bots team. The Warsow Content License states that the warsow archive can be re-compressed into any format (including .deb). Can anyone take the documentation from the warsow archive and place it in a separate package? Also, can the files in the warsow archive be rearranged into different directories, have files added into the package, and have files excluded from the package before re-compressing the archive? On Monday 28 January 2008 8:15:19 am you wrote: Hello Andres, I'm warsow founder. Thanks for your extended mail, I forwarded it to the team. We are currently making any changes needed, the reference to warsow Team will disappear in 041's license. Last, you can consider this answer is position both from chasseur de bots and warsow team. Best regards and have a nice day, Solomonk / Fabrice Demurger 2008/1/25, Andres Mejia [EMAIL PROTECTED]: Dear Warsow Team, I wasn't sure who exactly to contact about this so I've decided to contact everybody whose email address was posted in the contact.txt file of the Warsow archive/installer. I and other Debian users would like to create and distribute a package for the new version of Warsow (0.4). Before I get started on the new packages, we have some concerns about the Warsow Content License that we'll need clarification for. The license states Assets that are property of Chasseur de bots, use the following Warsow Content License. Then there are these two clauses. 3. You may not copy, modify, publish, transmit, sell, participate in the transfer or sale or reproduce, create Derivative Works from, distribute, perform, display or in any way exploit any of the Material released under this License unless expressly permitted by the Warsow Team. 4. You may freely distribute the Warsow archive/installer unmodified on any media. You may re-compress using different archival formats suitable for your OS (i.e. zip/tgz/rpm/deb/dmg), any changes beyond that require explicit permission of the Chasseur de bots association. In clause 3 when it's stated, unless expressly permitted by the Warsow Team, did you really mean to say the Warsow Team or Chasseur de bots? I ask this since it's stated that the license applies to Assets that are property of Chasseur de bots. If you did mean to say the Warsow Team, can it be assumed that the members of the Warsow Team are those listed in the Warsow team page http://www.warsow.net/?page=team or is there a different list? In regards to clause 4, a Debian package includes a tarball (orig tarball) that would contain the original source (a tarball named package-name_version.orig.tar.gz). The Warsow archive/installer can be delivered unmodified in the orig tarball, but this would be a problem for the deb package. The deb package contains the files in a manner that is compliant with the Filesystem Hierarchy Standard. So the Warsow content would need to reside in /usr/share/games/warsow-data/. Documentation would be placed in /usr/share/doc/warsow-data/. A Debian package also would add in other documentation that are related with the Debian package or are for Debian users. The changelog.txt file from the Warsow archive/installer is renamed to upstream_changelog.txt so as not to confuse it with changelog.Debian.gz, which is the changelog for the Debian packaging. Also, the changelog files are always compressed using gzip, regardless of its size. Also, the binaries from the Warsow archive/installer are included in a separate package that has the binaries built from the SDK. So the binaries from the Warsow archive/installer are not included in the deb package with the Warsow content. The scripts from the Warsow archive/installer are also not used. Even if they were used, they would need to be modified for use in a Debian system and included in the package with the binaries. Also, in the package with the binaries, some of the documentation from the Warsow archive/installer is included in the package's diff.gz file that contains the makefile script and other files necessary to build a Debian package. This way, the documentation from the Warsow archive/installer can be delivered in both packages
Bug#467386: funguloids: 2
On Sunday 24 February 2008 9:45:50 pm Jerry Quinn wrote: Package: funguloids Version: 1.06-5 Severity: grave Justification: causes non-serious data loss I installed and tried to run this game, which immediately gave me a blank screen, and the machine was unresponsive to keystrokes. I had to reboot the box, causing potential data loss in other programs I had open. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages funguloids depends on: ii libalut01.1.0-1 OpenAL Utility Toolkit ii libc6 2.7-6GNU C Library: Shared libraries ii libgcc1 1:4.3-20080202-1 GCC support library ii liblua5.1-0 5.1.3-1 Simple, extensible, embeddable pro ii libmad0 0.15.1b-2.1 MPEG audio decoder library ii libogg0 1.1.3-3 Ogg Bitstream Library ii libogre14 1.4.3-1+b1 Object-oriented Graphics Rendering ii libois1 0.99+1.0rc1-1+b1 Object Oriented Input System libra ii libopenal0a 1:0.0.8-7OpenAL is a portable library for 3 ii libstdc++6 4.3-20080202-1 The GNU Standard C++ Library v3 ii libvorbis0a 1.2.0.dfsg-3 The Vorbis General Audio Compressi ii libvorbisenc2 1.2.0.dfsg-3 The Vorbis General Audio Compressi ii libvorbisfile3 1.2.0.dfsg-3 The Vorbis General Audio Compressi ii ogre-plugins-cgprogramm 1.4.5-1 Ogre plugin: CgProgramManager funguloids recommends no packages. -- no debconf information ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel What I'm seeing wrong here is that ogre-plugins-cgprogrammanager 1.4.5 is installed along with libogre14 1.4.3. I didn't notice this until now. Ogre versions 1.4.x do have ABI breakage in between versions. This will be fixed with the new ogre libraries uploaded to the archive (version 1.4.6.dfsg1). The libraries are built with a release soname scheme and the library packages are named accordingly (libogremain-1.4.6). A binNMU should then be done for funguloids, causing funguloids (and ogre-plugins-cgprogrammanager) to depend on the correct version of ogre. -- Regards, Andres ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#461659: warsow: Clarification for the Warsow Content License
Hello, I have some more questions for the chasseur de bots team. The Warsow Content License states that the warsow archive can be re-compressed into any format (including .deb). Can anyone take the documentation from the warsow archive and place it in a separate package? Also, can the files in the warsow archive be rearranged into different directories, have files added into the package, and have files excluded from the package before re-compressing the archive? On Monday 28 January 2008 8:15:19 am you wrote: Hello Andres, I'm warsow founder. Thanks for your extended mail, I forwarded it to the team. We are currently making any changes needed, the reference to warsow Team will disappear in 041's license. Last, you can consider this answer is position both from chasseur de bots and warsow team. Best regards and have a nice day, Solomonk / Fabrice Demurger 2008/1/25, Andres Mejia [EMAIL PROTECTED]: Dear Warsow Team, I wasn't sure who exactly to contact about this so I've decided to contact everybody whose email address was posted in the contact.txt file of the Warsow archive/installer. I and other Debian users would like to create and distribute a package for the new version of Warsow (0.4). Before I get started on the new packages, we have some concerns about the Warsow Content License that we'll need clarification for. The license states Assets that are property of Chasseur de bots, use the following Warsow Content License. Then there are these two clauses. 3. You may not copy, modify, publish, transmit, sell, participate in the transfer or sale or reproduce, create Derivative Works from, distribute, perform, display or in any way exploit any of the Material released under this License unless expressly permitted by the Warsow Team. 4. You may freely distribute the Warsow archive/installer unmodified on any media. You may re-compress using different archival formats suitable for your OS (i.e. zip/tgz/rpm/deb/dmg), any changes beyond that require explicit permission of the Chasseur de bots association. In clause 3 when it's stated, unless expressly permitted by the Warsow Team, did you really mean to say the Warsow Team or Chasseur de bots? I ask this since it's stated that the license applies to Assets that are property of Chasseur de bots. If you did mean to say the Warsow Team, can it be assumed that the members of the Warsow Team are those listed in the Warsow team page http://www.warsow.net/?page=team or is there a different list? In regards to clause 4, a Debian package includes a tarball (orig tarball) that would contain the original source (a tarball named package-name_version.orig.tar.gz). The Warsow archive/installer can be delivered unmodified in the orig tarball, but this would be a problem for the deb package. The deb package contains the files in a manner that is compliant with the Filesystem Hierarchy Standard. So the Warsow content would need to reside in /usr/share/games/warsow-data/. Documentation would be placed in /usr/share/doc/warsow-data/. A Debian package also would add in other documentation that are related with the Debian package or are for Debian users. The changelog.txt file from the Warsow archive/installer is renamed to upstream_changelog.txt so as not to confuse it with changelog.Debian.gz, which is the changelog for the Debian packaging. Also, the changelog files are always compressed using gzip, regardless of its size. Also, the binaries from the Warsow archive/installer are included in a separate package that has the binaries built from the SDK. So the binaries from the Warsow archive/installer are not included in the deb package with the Warsow content. The scripts from the Warsow archive/installer are also not used. Even if they were used, they would need to be modified for use in a Debian system and included in the package with the binaries. Also, in the package with the binaries, some of the documentation from the Warsow archive/installer is included in the package's diff.gz file that contains the makefile script and other files necessary to build a Debian package. This way, the documentation from the Warsow archive/installer can be delivered in both packages. With all this said, there are things that are added to, modified, and deleted from the Warsow archive/installer in order to create packages for Debian. Most of the modifications I've listed are meant as a way to create and deliver a Debian package. Some others are for purposes of complying with Debian policy. What I'm generally asking in regards to this is, can it be acceptable to build and deliver Debian packages without having to leave the Warsow archive/installer unmodified? There is also some other things I want clarification for. I'm assuming that the Warsow archive/installer is the warsow_0.4_unified.zip file. Am I correct? Also, I'm
Bug#461659: Fwd: warsow: Clarification for the Warsow Content License
I've received this in response to the question of the Warsow Content License I've sent earlier to some members of the Warsow Team. Perhaps it's best to wait for a new release of Warsow with their edited license. -- Forwarded message -- From: slk zombie [EMAIL PROTECTED] Date: Jan 28, 2008 8:15 AM Subject: Re: warsow: Clarification for the Warsow Content License To: Andres Mejia [EMAIL PROTECTED] Hello Andres, I'm warsow founder. Thanks for your extended mail, I forwarded it to the team. We are currently making any changes needed, the reference to warsow Team will disappear in 041's license. Last, you can consider this answer is position both from chasseur de bots and warsow team. Best regards and have a nice day, Solomonk / Fabrice Demurger 2008/1/25, Andres Mejia [EMAIL PROTECTED]: Dear Warsow Team, I wasn't sure who exactly to contact about this so I've decided to contact everybody whose email address was posted in the contact.txt file of the Warsow archive/installer. I and other Debian users would like to create and distribute a package for the new version of Warsow (0.4). Before I get started on the new packages, we have some concerns about the Warsow Content License that we'll need clarification for. The license states Assets that are property of Chasseur de bots, use the following Warsow Content License. Then there are these two clauses. 3. You may not copy, modify, publish, transmit, sell, participate in the transfer or sale or reproduce, create Derivative Works from, distribute, perform, display or in any way exploit any of the Material released under this License unless expressly permitted by the Warsow Team. 4. You may freely distribute the Warsow archive/installer unmodified on any media. You may re-compress using different archival formats suitable for your OS (i.e. zip/tgz/rpm/deb/dmg), any changes beyond that require explicit permission of the Chasseur de bots association. In clause 3 when it's stated, unless expressly permitted by the Warsow Team, did you really mean to say the Warsow Team or Chasseur de bots? I ask this since it's stated that the license applies to Assets that are property of Chasseur de bots. If you did mean to say the Warsow Team, can it be assumed that the members of the Warsow Team are those listed in the Warsow team page http://www.warsow.net/?page=team or is there a different list? In regards to clause 4, a Debian package includes a tarball (orig tarball) that would contain the original source (a tarball named package-name_version.orig.tar.gz). The Warsow archive/installer can be delivered unmodified in the orig tarball, but this would be a problem for the deb package. The deb package contains the files in a manner that is compliant with the Filesystem Hierarchy Standard. So the Warsow content would need to reside in /usr/share/games/warsow-data/. Documentation would be placed in /usr/share/doc/warsow-data/. A Debian package also would add in other documentation that are related with the Debian package or are for Debian users. The changelog.txt file from the Warsow archive/installer is renamed to upstream_changelog.txt so as not to confuse it with changelog.Debian.gz, which is the changelog for the Debian packaging. Also, the changelog files are always compressed using gzip, regardless of its size. Also, the binaries from the Warsow archive/installer are included in a separate package that has the binaries built from the SDK. So the binaries from the Warsow archive/installer are not included in the deb package with the Warsow content. The scripts from the Warsow archive/installer are also not used. Even if they were used, they would need to be modified for use in a Debian system and included in the package with the binaries. Also, in the package with the binaries, some of the documentation from the Warsow archive/installer is included in the package's diff.gz file that contains the makefile script and other files necessary to build a Debian package. This way, the documentation from the Warsow archive/installer can be delivered in both packages. With all this said, there are things that are added to, modified, and deleted from the Warsow archive/installer in order to create packages for Debian. Most of the modifications I've listed are meant as a way to create and deliver a Debian package. Some others are for purposes of complying with Debian policy. What I'm generally asking in regards to this is, can it be acceptable to build and deliver Debian packages without having to leave the Warsow archive/installer unmodified? There is also some other things I want clarification for. I'm assuming that the Warsow archive/installer is the warsow_0.4_unified.zip file. Am I correct? Also, I'm assuming that when it's stated that the Warsow Content License is applied to all art/models/music/texts/names/setting/... present in the game, that this means art/models/music/texts
Bug#461659: warsow: Clarification for the Warsow Content License
Dear Warsow Team, I wasn't sure who exactly to contact about this so I've decided to contact everybody whose email address was posted in the contact.txt file of the Warsow archive/installer. I and other Debian users would like to create and distribute a package for the new version of Warsow (0.4). Before I get started on the new packages, we have some concerns about the Warsow Content License that we'll need clarification for. The license states Assets that are property of Chasseur de bots, use the following Warsow Content License. Then there are these two clauses. 3. You may not copy, modify, publish, transmit, sell, participate in the transfer or sale or reproduce, create Derivative Works from, distribute, perform, display or in any way exploit any of the Material released under this License unless expressly permitted by the Warsow Team. 4. You may freely distribute the Warsow archive/installer unmodified on any media. You may re-compress using different archival formats suitable for your OS (i.e. zip/tgz/rpm/deb/dmg), any changes beyond that require explicit permission of the Chasseur de bots association. In clause 3 when it's stated, unless expressly permitted by the Warsow Team, did you really mean to say the Warsow Team or Chasseur de bots? I ask this since it's stated that the license applies to Assets that are property of Chasseur de bots. If you did mean to say the Warsow Team, can it be assumed that the members of the Warsow Team are those listed in the Warsow team page http://www.warsow.net/?page=team or is there a different list? In regards to clause 4, a Debian package includes a tarball (orig tarball) that would contain the original source (a tarball named package-name_version.orig.tar.gz). The Warsow archive/installer can be delivered unmodified in the orig tarball, but this would be a problem for the deb package. The deb package contains the files in a manner that is compliant with the Filesystem Hierarchy Standard. So the Warsow content would need to reside in /usr/share/games/warsow-data/. Documentation would be placed in /usr/share/doc/warsow-data/. A Debian package also would add in other documentation that are related with the Debian package or are for Debian users. The changelog.txt file from the Warsow archive/installer is renamed to upstream_changelog.txt so as not to confuse it with changelog.Debian.gz, which is the changelog for the Debian packaging. Also, the changelog files are always compressed using gzip, regardless of its size. Also, the binaries from the Warsow archive/installer are included in a separate package that has the binaries built from the SDK. So the binaries from the Warsow archive/installer are not included in the deb package with the Warsow content. The scripts from the Warsow archive/installer are also not used. Even if they were used, they would need to be modified for use in a Debian system and included in the package with the binaries. Also, in the package with the binaries, some of the documentation from the Warsow archive/installer is included in the package's diff.gz file that contains the makefile script and other files necessary to build a Debian package. This way, the documentation from the Warsow archive/installer can be delivered in both packages. With all this said, there are things that are added to, modified, and deleted from the Warsow archive/installer in order to create packages for Debian. Most of the modifications I've listed are meant as a way to create and deliver a Debian package. Some others are for purposes of complying with Debian policy. What I'm generally asking in regards to this is, can it be acceptable to build and deliver Debian packages without having to leave the Warsow archive/installer unmodified? There is also some other things I want clarification for. I'm assuming that the Warsow archive/installer is the warsow_0.4_unified.zip file. Am I correct? Also, I'm assuming that when it's stated that the Warsow Content License is applied to all art/models/music/texts/names/setting/... present in the game, that this means art/models/music/texts/names/setting/... that would appear only while playing the game. Am I correct? If you respond, please email the Debian Games Developers' list at [EMAIL PROTECTED] and also the Bug Tracking System for Bug #461659 at [EMAIL PROTECTED] In your response, please also clarify if the response is the position of Chasseur de bots and/or the Warsow Team. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#461659: warsow: New version of warsow possibly non-distributable.
On Jan 22, 2008 8:29 AM, Ivan Vucica [EMAIL PROTECTED] wrote: Sure, they don't have to give reason to anyone, but that will reduce the number of their players. Which is something they probably care about. I think, after reading your other posts, that with current license they might not only lose Debian as their distributor, but also other distributions. Bringing the issue to them presented like that will probably shake some souls on their team. Everyone, both commercial and for-free developers, want more users. On the other hand, they look like a pretty rude bunch, so perhaps they deserve removal from Debian. But not contacting them due to one guy's post (who is only a team member and not a team leader) and silently removing them should probably not be done. (n.b. I haven't tried the game.) Ivan Vucica Well, I'm not suggesting that warsow be removed from Debian. The old warsow-data is at least distributable, so it can exist in non-free and there can be a playable game with the old warsow. I'm sure the old warsow can still be distributed through Debian since it's licensed under the old terms. I'll have to contact debian-legal to make sure. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#461659: warsow: New version of warsow possibly non-distributable.
Hello, Please CC myself and [EMAIL PROTECTED] when replying to this email. There's an issue with the new upstream version of warsow that I think will make it undistributable, even in the non-free category of Debian. I've attached the entire license file for the new version of warsow. I want to know if it will still be possible to distribute the old version of warsow. The old license states, Warsow license information: The game engine is based on the QFusion engine and licensed under the GNU General Public license. A copy of the GPL license should come with this package, in file named gnu.txt, if not look at http://www.gnu.org/licenses/gpl.txt Game data files are copyrighted by their respective authors. You may only redistribute the game data in unmodified form unless you have written permission from the copyright owner. -- Regards, Andres Mejia Brief Explanation of the licenses Read this paragraph if you want to have a quick overview of the licensing used by Warsow. For players: The first goal of our team is to make a free game for players. This means you will not have to pay for the game, nor pay a monthly cost. You can install our software on many PC as you like, play it as much as you want. You cannot sell the client/server or gain any profit from it. For developers: Code is under GPL license, this means you can get all our source code, study it and reuse it as soon as you keep it open and give back to us your changes. All artwork, musics, dialogues, stories, names, 3d models, etc... are under a proprietary license. This means you cannot reuse those in any way. If you plan to create another game based on our source code, remember you will have to redo all art,music,models,stories,etc... A detailed explanation of the licenses follows. Background and Purpose In the Warsow Project we have two different licenses: 1. The first one is GPL. This license is applied to all our source files. You learn more about that license here. 2. The second one is Warsow Content License. This license is applied to all artwork and texts in this web site and is applied to all art/models/music/texts/names/setting/... present in the game. It is very important that new developers and the community understand why we have decided to split our efforts among these two licenses, so we encourage you to read it all. If you just want to have a brief explanation jump here. Chasseur de bots is the name of the Non-Profit Association that holds all copyrights of Warsow assets and is used to run the development team. Warsow Purpose The commercial industry does not care too much about Open Source because in most cases the projects are not organized and strong enough to reach their goal and to compete with them. The only way for any of these small OSS projects to succeed is to sacrifice a little of their pride and to join a large and well-organized team. In this way, all talented people can bring their ideas and skills into one project. These talented people will be less responsible for overall project progress, but they can concentrate more on what they really want to do, have more fun and have a much greater chance of success. Our vision is to convince talented and dedicated people that this is the right path to follow, by focusing on two key objectives: gathering and keeping resources, and maximizing chances of success. Objective 1: Gathering resources under a single common project is very important to build a strong team. We should try to avoid our project forking into other similar projects, because that means splitting resources and thus, lowering our chances of success. Those other forked projects will repeat efforts already spent on discussion of rules, building new races, writing new code and we will end up again with a lot of resources wasted and no goal reached. Objective 2: Ensuring success is another key point of our organization. We are trying to preserve the work done by our members as much as we possibly can, with licenses and by adding only talented members to our team. For the project to be successful, it needs to be unique in architecture, rules, music and ideas; it must attract good players and RPG ers and create a fun, stimulating, friendly community. Most importantly, it must be playable and complete. Why Warsow Is Licensed the Way It Is To try best to achieve these two goals we have made some tough decisions about licenses. However, in order to explain our conclusion, first it is necessary to examine the alternatives: Option 1: Release absolutely everything under the GPL license. This option sounds great in theory but in practice has the following problems: * Anyone can get all of the code and art, music and setting information and start building a similar game with a part of our team. This is sub-optimal because the forked project will split our forces and will lower our chance of success, which is contrary to Objective 1. We need
Bug#461659: warsow: New version of warsow possibly non-distributable.
Hello, I'm sorry, I forgot to ask about other concerns that myself and another member of the Debian Games team had. I'll repeat what Vincent (the other member) was concerned about. On Jan 21, 2008 10:26 PM, Andres Mejia [EMAIL PROTECTED] wrote: 3. You may not copy, modify, publish, transmit, sell, participate in the transfer or sale or reproduce, create Derivative Works from, distribute, perform, display or in any way exploit any of the Material released under this License unless expressly permitted by the Warsow Team. 4. You may freely distribute the Warsow archive/installer unmodified on any media. You may re-compress using different archival formats suitable for your OS (i.e. zip/tgz/rpm/deb/dmg), any changes beyond that require explicit permission of the Chasseur de bots association. This two points are contradictory: 3 says no one can distribute, 4 says it's fine to distribute if you don't touch anything. Moreover, there are two different groups mentioned in here: the 'Chasseurs de bots association' and the 'Warsow Team'. We'd better take this to debian-legal. To me, it looks like a very badly-written license with ambiguous clauses. That was his concern. My concern was that this license stated Assets that are property of Chasseur de bots, use the following Warsow Content License. However, the last part of clause 3 mentions that exceptions can be made by the Warsow Team. Would this be a problem if we are to distribute warsow in Debian? Below is the previous question I asked earlier. There's an issue with the new upstream version of warsow that I think will make it undistributable, even in the non-free category of Debian. I've attached the entire license file for the new version of warsow. I want to know if it will still be possible to distribute the old version of warsow. The old license states, Warsow license information: The game engine is based on the QFusion engine and licensed under the GNU General Public license. A copy of the GPL license should come with this package, in file named gnu.txt, if not look at http://www.gnu.org/licenses/gpl.txt Game data files are copyrighted by their respective authors. You may only redistribute the game data in unmodified form unless you have written permission from the copyright owner. Please CC myself and [EMAIL PROTECTED] when replying to this email. -- Regards, Andres Mejia Brief Explanation of the licenses Read this paragraph if you want to have a quick overview of the licensing used by Warsow. For players: The first goal of our team is to make a free game for players. This means you will not have to pay for the game, nor pay a monthly cost. You can install our software on many PC as you like, play it as much as you want. You cannot sell the client/server or gain any profit from it. For developers: Code is under GPL license, this means you can get all our source code, study it and reuse it as soon as you keep it open and give back to us your changes. All artwork, musics, dialogues, stories, names, 3d models, etc... are under a proprietary license. This means you cannot reuse those in any way. If you plan to create another game based on our source code, remember you will have to redo all art,music,models,stories,etc... A detailed explanation of the licenses follows. Background and Purpose In the Warsow Project we have two different licenses: 1. The first one is GPL. This license is applied to all our source files. You learn more about that license here. 2. The second one is Warsow Content License. This license is applied to all artwork and texts in this web site and is applied to all art/models/music/texts/names/setting/... present in the game. It is very important that new developers and the community understand why we have decided to split our efforts among these two licenses, so we encourage you to read it all. If you just want to have a brief explanation jump here. Chasseur de bots is the name of the Non-Profit Association that holds all copyrights of Warsow assets and is used to run the development team. Warsow Purpose The commercial industry does not care too much about Open Source because in most cases the projects are not organized and strong enough to reach their goal and to compete with them. The only way for any of these small OSS projects to succeed is to sacrifice a little of their pride and to join a large and well-organized team. In this way, all talented people can bring their ideas and skills into one project. These talented people will be less responsible for overall project progress, but they can concentrate more on what they really want to do, have more fun and have a much greater chance of success. Our vision is to convince talented and dedicated people that this is the right path to follow, by focusing on two key objectives: gathering and keeping resources, and maximizing chances of success. Objective 1: Gathering resources under a single common project is very
Bug#461659: warsow: New version of warsow possibly non-distributable.
It appears that the new license for the data of warsow is even more restrictive than the previous license. The new license reads. Warsow Content License Assets that are property of Chasseur de bots, use the following Warsow Content License. TERMS AND CONDITIONS FOR USAGE, COPYING, DISTRIBUTION AND MODIFICATION 1. This License applies to any material or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this Warsow Content License. 2. Terms defined in this Article, and parenthetically elsewhere, shall throughout this License have the meanings here and there provided. Defined terms may be used in the singular or plural. Definitions: � The Material, below, refers to any such material or work, and a work based on the Material means either the Material or any Derivative Work under copyright law. � Derivative Work shall mean a work containing the Material or a portion of it, such as a revision, modification, enhancement, adaptation, translation (including compilation or recompilation by computer), abridgement, condensation, expansion, or any other form in which such preexisting works may be recast, transformed, or adapted, and that, if prepared without authorization of the owner of the copyright in such preexisting work, would constitute a copyright infringement. � Each licensee is addressed as you. 3. You may not copy, modify, publish, transmit, sell, participate in the transfer or sale or reproduce, create Derivative Works from, distribute, perform, display or in any way exploit any of the Material released under this License unless expressly permitted by the Warsow Team. 4. You may freely distribute the Warsow archive/installer unmodified on any media. You may re-compress using different archival formats suitable for your OS (i.e. zip/tgz/rpm/deb/dmg), any changes beyond that require explicit permission of the Chasseur de bots association. 5. THERE IS NO WARRANTY FOR THE MATERIAL PROVIDED, TO THE EXTENT PERMITTED BY APPLICABLE LAW. THE MATERIAL IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE MATERIAL IS WITH YOU. 6. IN NO EVENT SHALL Chasseur de bots BE LIABLE FOR ANY DAMAGES WHATSOEVER, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE MATERIAL. END OF TERMS AND CONDITIONS Clause 3 of this license goes against clauses 1, 2, 3, 7, and 8 of the Open Source Definition (and thus the DFSG). This to me most likely makes the new version of warsow unsuitable for distribution through Debian. If anyone wants to dispute this, please reply to the Debian Games Developer's mailing list and this bug. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#461659: warsow: New version of warsow possibly non-distributable.
On Jan 21, 2008 8:13 PM, Ivan Vucica [EMAIL PROTECTED] wrote: On Monday 21 January 2008, Andres Mejia wrote: It appears that the new license for the data of warsow is even more restrictive than the previous license. The new license reads. Warsow Content License Assets that are property of Chasseur de bots, use the following Warsow Content License. Cheers, looks like this refers to the data files. Since the binaries are already in contrib and data files are already in non-free, I think this is already resolved. Which bug are you referring to? 441435? Because that bug doesn't seem to apply. -- Ivan Vucica Indeed. The game engine is based on the QFusion engine and licensed under the GNU General Public license. This does refer to warsow's data files. The previous license for the data files read: Game data files are copyrighted by their respective authors. You may only redistribute the game data in unmodified form unless you have written permission from the copyright owner. This was fine at least for non-free. The new license now brings up a completely different issue, not related to any prior issue. It places even more restrictions on what can be done with the data files. The new restrictions looks as though it will be illegal for Debian to do anything with the data files. I don't think we could even write a script that could download the data files as clause 3 of their new license also contains or in any way exploit any of the Material. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#461659: warsow: New version of warsow possibly non-distributable.
On Jan 21, 2008 5:16 PM, Hans de Goede [EMAIL PROTECTED] wrote: Vincent Fourmond wrote: Hello, Andres Mejia wrote: 2. Terms defined in this Article, and parenthetically elsewhere, shall throughout this License have the meanings here and there provided. Defined terms may be used in the singular or plural. Definitions: � The Material, below, refers to any such material or work, and a work based on the Material means either the Material or any Derivative Work under copyright law. � Derivative Work shall mean a work containing the Material or a portion of it, such as a revision, modification, enhancement, adaptation, translation (including compilation or recompilation by computer), abridgement, condensation, expansion, or any other form in which such preexisting works may be recast, transformed, or adapted, and that, if prepared without authorization of the owner of the copyright in such preexisting work, would constitute a copyright infringement. � Each licensee is addressed as you. 3. You may not copy, modify, publish, transmit, sell, participate in the transfer or sale or reproduce, create Derivative Works from, distribute, perform, display or in any way exploit any of the Material released under this License unless expressly permitted by the Warsow Team. 4. You may freely distribute the Warsow archive/installer unmodified on any media. You may re-compress using different archival formats suitable for your OS (i.e. zip/tgz/rpm/deb/dmg), any changes beyond that require explicit permission of the Chasseur de bots association. Clause 3 of this license goes against clauses 1, 2, 3, 7, and 8 of the Open Source Definition (and thus the DFSG). This to me most likely makes the new version of warsow unsuitable for distribution through Debian. Completely agree. That also excludes distributing in non-free, because 'modification' includes compilation according to clause 2. So its either a binary repackaged blurb or nothing. Better it be nothing. You probably should tag the new upstream version bug as wontfix. 1) This is the content license only, the engine is GPL 2) Even then I agree the new license is bad, has anyone actually tried contacting upstream and kindly asking them to change the license back, or otherwise improve their licensing scheme? Regards, Hans Yes, this only refers to the content license. I was thinking of contacting upstream about this issue, but somehow I think upstream is not going to entertain any discussion about the new license anytime soon, especially since they recently changed their license because of an issue with one artist's maps (related to bug #441435). Reading the license.txt file for the new warsow also made me feel as though I would be wasting my time trying to contact upstream about this. I did a search on the keyword license in their forums and after reading http://www.warsow.net/forum/viewtopic.php?id=15145 , I've decided not to contact upstream about this. If anyone else wishes to contact upstream, feel free. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#461659: warsow: New version available (warsow-0.4)
Source: warsow Severity: wishlist Tags: confirmed A new version of warsow is out (warsow-0.4). I'll start working on it soon. Some links for the record. http://www.warsow.net/release/warsow_0.4_unified.zip http://www.warsow.net/release/warsow_0.4_sdk.zip -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#454156:
I recall the script was only meant to fix bug #435468, more specifically, this error. ERROR: R_Upload32_3D: texture is too large (resizing is not supported) Error: Error during initialization ERROR: Received signal 11 Recursive Sys_Error: Received signal 11 Perhaps the direct rendering check should be left out. ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#446515: Could not reproduce
severity 446515 important tags 446515 unreproducible thanks I could not reproduce this bug. It's possible that you are experiencing this problem because of a limitation in your opengl hardware. ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#451669: ogre FTBFS on kfreebsd-*: make[4]: *** No rule to make target `all'. Stop.
Source: ogre Tags: help ogre fails to build from any kfreebsd system. I don't have a means to fix this so I'm requesting help. Here is a snippet of the build log where it's failing. Making all in CEGUIRenderer make[4]: Entering directory `/build/buildd/ogre-1.4.5/Samples/Common/CEGUIRenderer' make[4]: *** No rule to make target `all'. Stop. ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#327423:
tags 327423 wontfix thanks The demos are not distributed primarily because of the content in its Media directory being non-redistributable. It won't be for the foreseeable future. It was easier to just provide a script that downloads the upstream source and compile the demos alone. This script is found under /usr/share/doc/libogre-dev/examples/compileall.sh after installing libogre-dev. ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#449475:
This just tells me that it's dual-licensed. Shouldn't this be asked at debian-legal? ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#441435: Author still allowing redistribution
The author (acid) is still allowing redistribution of his work, under the condition that it not be modified. It is explained more at http://www.warsow.net/?page=blogid=24comments=1 Here's further clarification on this. added by: [EMAIL PROTECTED]/09/2007 @ 15:15 Oh and to clarify: We can release the maps in their current state in our packages (or the maps wouldn't be in 0.32; acid left before that). For 0.4 we are working on some renderupdates which demand texture/mapmodifications which we aren't allowed to do, hence we have no choice but to drop the maps. And here's a comment by the author. added by: [EMAIL PROTECTED]/09/2007 @ 10:39 The team is still allowed to add the current wdm2 state to every following release and even if it will not, then community members may still add the map as a custom map to their basewsw folder. So wdm2 is everything else than lost. Same for wdm11 and wctf2. In the case of Debian, this means these files can still be redistributed but without modifications. The copyright file of warsow-data already says this. This is true for version 0.32 of warsow as well, which is the current release. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#439868: libogre14: cannot be installed, depends on libzzip-0-12
A new version of ogre was released recently so I'll be working on that. It might be a while until the new packages get accepted into the archives, and thus this bug gets fixed. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#437699: vegastrike-data: Broken manpage symlinks
fixed 437699 0.4.3-4 fixed 419146 0.4.3-4 thanks This is fixed in the yet to be uploaded vegatrike-data_0.4.3-4. vegastrike-data won't contain manpages. Only vegastrike will. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#343411:
reassign 343411 vegastrike-data 0.4.3-3 thanks This bug needs to be fixed from vegastrike-data. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#435468:
I would like to make another suggestion and use xmessage or Xdialog instead of zenity. Both require less dependencies of their own. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#433671:
On 8/4/07, Victor Luchits [EMAIL PROTECTED] wrote: Filenames for game modules need the arch suffix so that they can be distinguished at load time. All game modules for all archs are packed into a single .pk3 file which is used for pure servers. Clients that connect to pure servers are forced to download, unpack this .pk3 and load the game modules of their arch. A typical modules.pk3 file (which is essentially a .zip file) looks something like this: game_x86.dll game_x64.dll game_x86.so game_x86_x64.so ... Why would it be preferable to force the download of these modules, pure or not? Why can't the binaries that ship with the client just be used? Also, the Debian packages contain some bug fixes already, and I'm sure there will be more to come. From what you've said, this means that clients connecting to these pure servers are still going to have a problem anyways. Also, Michel has a point. This is a problem when cross compiling. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#433671:
reopen 433671 reassign 433671 warsow 0.31.dfsg-4 severity serious thanks Reopening this as changing from using dpkg-architecture to uname in .so naming scheme makes this package require using ppc for powerpc packages. Some other architectures require different naming scheme as well. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#433590: warsow: FTBFS (ia64) snd_qf/snd_mix.c asm errors
Package: warsow
Version: 0.31.dfsg-2
warsow FTBFS on ia64. Here's the error.
Compiling snd_qf/snd_mix.c
/tmp/ccnsyQEk.s: Assembler messages:
/tmp/ccnsyQEk.s:27: Error: Unknown opcode `pushl %edi'
/tmp/ccnsyQEk.s:28: Error: Unknown opcode `pushl %ebx'
/tmp/ccnsyQEk.s:29: Error: bad expression
/tmp/ccnsyQEk.s:29: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:30: Error: bad expression
/tmp/ccnsyQEk.s:30: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:31: Error: bad expression
/tmp/ccnsyQEk.s:31: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:33: Error: Illegal operand separator `('
/tmp/ccnsyQEk.s:34: Error: Unknown opcode `sarl $8,%eax'
/tmp/ccnsyQEk.s:35: Error: Unknown opcode `cmpl $0x7FFF,%eax'
/tmp/ccnsyQEk.s:36: Error: Unknown opcode `jg LClampHigh'
/tmp/ccnsyQEk.s:37: Error: Unknown opcode `cmpl $0x8000,%eax'
/tmp/ccnsyQEk.s:38: Error: Unknown opcode `jnl LClampDone'
/tmp/ccnsyQEk.s:39: Error: bad expression
/tmp/ccnsyQEk.s:39: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:40: Error: Unknown opcode `jmp LClampDone'
/tmp/ccnsyQEk.s:42: Error: bad expression
/tmp/ccnsyQEk.s:42: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:44: Error: Illegal operand separator `('
/tmp/ccnsyQEk.s:45: Error: Unknown opcode `sarl $8,%edx'
/tmp/ccnsyQEk.s:46: Error: Unknown opcode `cmpl $0x7FFF,%edx'
/tmp/ccnsyQEk.s:47: Error: Unknown opcode `jg LClampHigh2'
/tmp/ccnsyQEk.s:48: Error: Unknown opcode `cmpl $0x8000,%edx'
/tmp/ccnsyQEk.s:49: Error: Unknown opcode `jnl LClampDone2'
/tmp/ccnsyQEk.s:50: Error: bad expression
/tmp/ccnsyQEk.s:50: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:51: Error: Unknown opcode `jmp LClampDone2'
/tmp/ccnsyQEk.s:53: Error: bad expression
/tmp/ccnsyQEk.s:53: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:55: Error: Unknown opcode `shll $16,%edx'
/tmp/ccnsyQEk.s:56: Error: Unknown opcode `andl $0x,%eax'
/tmp/ccnsyQEk.s:57: Error: Unknown opcode `orl %eax,%edx'
/tmp/ccnsyQEk.s:58: Error: bad expression
/tmp/ccnsyQEk.s:58: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:59: Error: Unknown opcode `subl $2,%ecx'
/tmp/ccnsyQEk.s:60: Error: Unknown opcode `jnz LWLBLoopTop'
/tmp/ccnsyQEk.s:61: Error: Unknown opcode `popl %ebx'
/tmp/ccnsyQEk.s:62: Error: Unknown opcode `popl %edi'
/tmp/ccnsyQEk.s:89: Error: Unknown opcode `pushl %edi'
/tmp/ccnsyQEk.s:90: Error: Unknown opcode `pushl %ebx'
/tmp/ccnsyQEk.s:91: Error: bad expression
/tmp/ccnsyQEk.s:91: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:92: Error: bad expression
/tmp/ccnsyQEk.s:92: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:93: Error: bad expression
/tmp/ccnsyQEk.s:93: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:95: Error: Illegal operand separator `('
/tmp/ccnsyQEk.s:96: Error: Unknown opcode `sarl $8,%eax'
/tmp/ccnsyQEk.s:97: Error: Unknown opcode `cmpl $0x7FFF,%eax'
/tmp/ccnsyQEk.s:98: Error: Unknown opcode `jg LClampHighS'
/tmp/ccnsyQEk.s:99: Error: Unknown opcode `cmpl $0x8000,%eax'
/tmp/ccnsyQEk.s:100: Error: Unknown opcode `jnl LClampDoneS'
/tmp/ccnsyQEk.s:101: Error: bad expression
/tmp/ccnsyQEk.s:101: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:102: Error: Unknown opcode `jmp LClampDoneS'
/tmp/ccnsyQEk.s:104: Error: bad expression
/tmp/ccnsyQEk.s:104: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:106: Error: Illegal operand separator `('
/tmp/ccnsyQEk.s:107: Error: Unknown opcode `sarl $8,%edx'
/tmp/ccnsyQEk.s:108: Error: Unknown opcode `cmpl $0x7FFF,%edx'
/tmp/ccnsyQEk.s:109: Error: Unknown opcode `jg LClampHigh2S'
/tmp/ccnsyQEk.s:110: Error: Unknown opcode `cmpl $0x8000,%edx'
/tmp/ccnsyQEk.s:111: Error: Unknown opcode `jnl LClampDone2S'
/tmp/ccnsyQEk.s:112: Error: bad expression
/tmp/ccnsyQEk.s:112: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:113: Error: Unknown opcode `jmp LClampDone2S'
/tmp/ccnsyQEk.s:115: Error: bad expression
/tmp/ccnsyQEk.s:115: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:117: Error: Unknown opcode `shll $16,%edx'
/tmp/ccnsyQEk.s:118: Error: Unknown opcode `andl $0x,%eax'
/tmp/ccnsyQEk.s:119: Error: Unknown opcode `orl %eax,%edx'
/tmp/ccnsyQEk.s:120: Error: bad expression
/tmp/ccnsyQEk.s:120: Error: Illegal operand separator `e'
/tmp/ccnsyQEk.s:121: Error: Unknown opcode `subl $2,%ecx'
/tmp/ccnsyQEk.s:122: Error: Unknown opcode `jnz LWLBLoopTopS'
/tmp/ccnsyQEk.s:123: Error: Unknown opcode `popl %ebx'
/tmp/ccnsyQEk.s:124: Error: Unknown opcode `popl %edi'
make[1]: *** [build/qf/snd_mix.o] Error 1
make[1]: Leaving directory `/build/buildd/warsow-0.31.dfsg/warsow_0.31/source'
make: *** [build-stamp] Error 2
The attached patch should fix this.
--
Regards,
Andres Mejia
Index: Fixes FTBFS for ia64.
===
--- ./warsow_0.31/source/game/q_shared.h.bak 2007-07-18 00:52:28.0 -0400
+++ ./warsow_0.31/source/game/q_shared.h 2007-07-18 00:53:10.0 -0400
@@ -285,7 +285,7 @@
# endif
#endif
-#if (defined(_M_IX86
Bug#433590:
severity 433590 serious tags 433590 patch help thanks Also with this bug, I haven't tested a build with this patch, although I'm sure it won't affect an i386 machine anyways. Plus I don't have access to an ia64 machine, much less one with Debian on it. I would normally make some commits in SVN, but I've been short on time recently. If anyone want's to test and/or upload warsow with this patch, that would be great. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#327423:
tags 327423 wontfix thanks These files are not distributable, which is why they are not included with ogre. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#281598:
reopen 281598 severity 281598 minor thanks I need to properly test this and then close, so I'm reopening this bug. Also setting the severity to minor. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#307992:
reopen 307992 thanks Need to properly test bug and then close, so I'm reopening it. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#343411:
tags 343411 confirmed thanks Vegastrike does have an obscene value for max_texture_dimension in its vegastrike.config file which would cause this kind of memory issue. It is being changed from 65536 to 512. -- Regards, Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#360149:
So can we close this bug? Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Bug#426872:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 libboost-python-dev now uses either -lboost_python-st or -lboost_python-mt. See http://bugs.debian.org/424038 boost_python-st was intended to be the default so modifications were made to the disable_internal_boost and rebootstrap patches and commited in SVN. Now a different problem occurs. g++ -pipe -O2 -ffast-math -falign-loops=2 -falign-jumps=2 -falign-functions=2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -pthread -pipe -L/usr/X11R6/lib -L/usr/X11R6/lib -o vegastrike vsfilesystem.o posh.o stardate.o star_system_xml.o star_system_generic.o universe_generic.o universe_util_generic.o galaxy.o galaxy_xml.o galaxy_gen.o faction_generic.o hashtable.o configxml.o easydom.o xml_serializer.o xml_support.o lin_time.o endianness.o faction_util_generic.o load_mission.o savegame.o pk3.o vs_globals.o debug_vs.o gfxlib_struct.o in_joystick.o force_feedback.o faction_util.o in_kb.o in_sdl.o in_mouse.o in_main.o in_handler.o main_loop.o physics.o star_system_jump.o star_system.o universe.o universe_util.o config_xml.o macosx_math.o cg_global.o main.o networking/netserver_devices.o networking/libnetclient.a networking/lowlevel/libnetlowlevel.a cmd/script/script_call_briefing.o cmd/script/libscript.a cmd/script/c_alike/libc_alike.a python/briefing_wrapper.o cmd/libcmd.a cmd/base_init.o python/libpython.a gfx/libgfx.a gldrv/libgldrv.a cmd/ai/libai.a gui/libgui.a networking/libnet.a cmd/collide/libcollide.a gfx/nav/libnav.a aldrv/libaldrv.a -lboost_python-st -lz -lvorbisfile -lvorbis -logg -lutil -L/usr/lib -lSDL -lGL -lGLU -lglut -lXi -lXmu -lexpat -lpng -ljpeg -lopenal -lalut -lvorbisfile -lvorbis -logg -lpython2.4 -Xlinker -export-dynamic -pthread /usr/lib/libboost_python-st.so: undefined reference to `PyErr_WarnEx' collect2: ld returned 1 exit status make[4]: *** [vegastrike] Error 1 make[4]: Leaving directory `/tmp/buildd/vegastrike-0.4.3.debian/src' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/tmp/buildd/vegastrike-0.4.3.debian/src' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/buildd/vegastrike-0.4.3.debian' make[1]: *** [all] Error 2 make[1]: Leaving directory `/tmp/buildd/vegastrike-0.4.3.debian' make: *** [build-stamp] Error 2 pbuilder: Failed autobuilding of package - Aborting with an error - unmounting dev/pts filesystem - unmounting proc filesystem - cleaning the build env - removing directory /var/cache/pbuilder/sid/build//2619 and its subdirectories -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: http://firegpg.tuxfamily.org iD8DBQFGZMtRgsFbAuXxMZYRArbLAKCPBgnbdVA7yKnrDMd+0nE58MfidgCgr5Tf rphz0CQnReop0rhrva1//h4= =8RkP -END PGP SIGNATURE- ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
Alien Arena 2007 Packaging
Hello, I did some work to create Debian packages for Alien Arena 2007. I've submitted a bug for this http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424951. The debian packaging files are available in the games SVN, http://svn.icculus.org/alienarena2007/trunk/. How can I get sponsored to get these packages uploaded to Debian? Andres Mejia ___ Pkg-games-devel mailing list Pkg-games-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
