Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Le 07/04/2013 23:52, Boris Pek a écrit : Hi Thibaut, I have updated packages astromenace and astromenace-data. Now all issues should be solved. Links for download: http://mentors.debian.net/debian/pool/contrib/a/astromenace/astromenace_1.3.1+ds-1.dsc http://mentors.debian.net/debian/pool/non-free/a/astromenace-data/astromenace-data_1.3.1+ds-1.dsc Git repos: http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace.git http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace-data.git Please have in mind that `cp AstroMenace AstroMenaceFS2VFS` in debian/rules in package astromenace is temporary. As you can see in SVN repo [1], special separate utility AstroMenaceFS2VFS will be available in next release. But new version of program will be released only at summer. [1] http://sourceforge.net/p/openastromenace/code/261/#diff-8 Best regards, Boris Hi Boris, We are almost there, but not quite. Just thinking aloud: the problem with the current scheme is that the game data file will be present twice in the user system: on real FS and in VFS. That could be avoided only by copying the fonts in astromenace-data source, so I guess we'll have to live with that. I'm wondering whether you could ship the data in a tar.xz archive to at least save some space? At least you could avoid duplicating AstroMenace as AstroMenaceFS2VFS: simply move the postinst/prerm logic in astromenace instead of astromenace-data. Note that as is, AstroMenace indirectly depends on AstroMenaceFS2VFS, so you get the two exact same executables twice on the system. Or you could make AstroMenace a link pointing to AstroMenaceFS2VFS for the time being. Typo in astromenace's control: - you can skip the line This package contains game executable file. If you keep it, you need an article in front of game: the game... - This package contains utility which generates AstroMenace date file.: date - data. Here again, you're missing an article: a utility or the utility. Thanks for you continued efforts. Kind regards, Thibaut. signature.asc Description: OpenPGP digital signature
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi Thibaut, Just thinking aloud: the problem with the current scheme is that the game data file will be present twice in the user system: on real FS and in VFS. That could be avoided only by copying the fonts in astromenace-data source, so I guess we'll have to live with that. I'm wondering whether you could ship the data in a tar.xz archive to at least save some space? Done. At least you could avoid duplicating AstroMenace as AstroMenaceFS2VFS: simply move the postinst/prerm logic in astromenace instead of astromenace-data. Note that as is, AstroMenace indirectly depends on AstroMenaceFS2VFS, so you get the two exact same executables twice on the system. Or you could make AstroMenace a link pointing to AstroMenaceFS2VFS for the time being. Done. Typo in astromenace's control: - you can skip the line This package contains game executable file. If you keep it, you need an article in front of game: the game... - This package contains utility which generates AstroMenace date file.: date - data. Here again, you're missing an article: a utility or the utility. Fixed. Links for download: http://mentors.debian.net/debian/pool/contrib/a/astromenace/astromenace_1.3.1+ds-1.dsc http://mentors.debian.net/debian/pool/non-free/a/astromenace-data/astromenace-data_1.3.1+ds-1.dsc Git repos: http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace.git http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace-data.git Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi Thibaut, I have updated packages astromenace and astromenace-data. Now all issues should be solved. Links for download: http://mentors.debian.net/debian/pool/contrib/a/astromenace/astromenace_1.3.1+ds-1.dsc http://mentors.debian.net/debian/pool/non-free/a/astromenace-data/astromenace-data_1.3.1+ds-1.dsc Git repos: http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace.git http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace-data.git Please have in mind that `cp AstroMenace AstroMenaceFS2VFS` in debian/rules in package astromenace is temporary. As you can see in SVN repo [1], special separate utility AstroMenaceFS2VFS will be available in next release. But new version of program will be released only at summer. [1] http://sourceforge.net/p/openastromenace/code/261/#diff-8 Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi Thibaut, In the rules file for astromenace data, you list fonts in /usr/share/fonts/truetype/ttf-liberation/, but the files there are symlinks to files in /usr/share/fonts/truetype/liberation/. The symlinks are provided by a compatility package which is not listed in your build-dependencies, so building fails in a clean chroot. Can you fix that? Thanks, I will fix it ASAP. There is a more serious problem. You copy font files which end-up (AFAIU) in gamedata.vfs. You therefore need to abide by the redistribution terms of the license of those fonts. The Debian way of insuring that in a generic manner (for DFSG-free material) would be to list the font packages in Built-Using. This ensures that the user can get the source for whatever ended-up in the binary package. The problem here is that astromenace-data is not in main but in non-free. I'm not sure that the Built-Using mechanism is sufficient to ensure that the source package for the fonts remain in the archive. Can you check that on -devel or -legal? Ok, I will ask more opinions from team members and then ask people from other mailing lists if necessary. Else I see two solutions: - copy (part of) the font source packages in astromenace-data (I didn't check: if the ttf files are their own source, you only need to copy them and amend debian/copyright); This is bad solution. I prefer do not do such things. - pack gamedata.vfs on the end-user system to avoid redistribution. This is sane solution. And it is very easy to do. I will do this if other variants fail. Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi Paul, I saw a lot of your messages related to fonts in Debian, also there was one or few posts in your blog (I do not remember precisely). So it looks that your well versed in this matter. Could you comment our discussion about astromenace-data package? Quotation: There is a more serious problem. You copy font files which end-up (AFAIU) in gamedata.vfs. You therefore need to abide by the redistribution terms of the license of those fonts. The Debian way of insuring that in a generic manner (for DFSG-free material) would be to list the font packages in Built-Using. This ensures that the user can get the source for whatever ended-up in the binary package. The problem here is that astromenace-data is not in main but in non-free. I'm not sure that the Built-Using mechanism is sufficient to ensure that the source package for the fonts remain in the archive. Can you check that on -devel or -legal? Have you any thoughts on this issue? Is it good idea to ask pkg-fonts-devel mailing list to clarify this theme? Full log of discussion: http://bugs.debian.org/696385#71 Package can be found here: http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace-data.git http://mentors.debian.net/debian/pool/non-free/a/astromenace-data/astromenace-data_1.3.1+ds-1.dsc Best regards, Boris PS: opinions from team members are also welcome. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
On Thu, Apr 4, 2013 at 7:15 PM, Boris Pek wrote: I saw a lot of your messages related to fonts in Debian, also there was one or few posts in your blog (I do not remember precisely). So it looks that your well versed in this matter. Could you comment our discussion about astromenace-data package? Quotation: I would simply echo what I wrote on the freedesktop wiki (slightly reworded): Render text at runtime (enables i18n) or maybe build time. Use the system fonts. If you choose a specific font then use fontconfig to find it rather than bundling it with your project. If you create your own special font, please distribute it in source form (for example FontForge text format) and ensure that it can be built using free tools. When you enable i18n your chosen font probably won't have all the required characters so your text rendering system should be prepared to fall back on other fonts on the system. http://www.freedesktop.org/wiki/Games/Upstream If you are involved with upstream or can get a patch included, the best way to follow my advice is to use one of the Qt, pango or QuesoGLC libraries (or toolkits/wrappers that use them) to render text at runtime. Any other option is suboptimal. In addition, this being Debian, we have dependencies and should use them to pull in fonts. Here is an example of how to do that: http://sourceforge.net/p/chromium-bsu/code/ci/master/tree/src/TextGLC.cpp http://anonscm.debian.org/viewvc/pkg-games/packages/trunk/chromium-bsu/debian/control?view=markup If you are looking for a simple workaround for upstream not rendering text this way, Built-Using seems like a reasonable compromise. I'm not sure if it works with non-free packages, check with the ftpmasters. http://wiki.debian.org/Teams/FTPMaster Honestly though, if upstream is bundling font files in a binary blob then probably using fontconfig to find the right font files automatically from the system fonts catalog is going to be very easy and fit reasonably well to the current code. Based on the astromenace control file it looks like upstream is using freetype, I'm guessing they use FT_New_Memory_Face to load the fonts. To implement this, you would need to switch to FT_New_Face and use fontconfig to feed the font filename to FT_New_Face. To find out the font filename from the font name using fontconfig check out the chromium-bsu code again: http://www.freetype.org/freetype2/docs/tutorial/step1.html http://sourceforge.net/p/chromium-bsu/code/ci/master/tree/src/TextFTGL.cpp#l91 I'm subscribed to the list, no need to CC. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi Ftp Masters, During packaging astromenace-data package [1][2] I have faced with issue of adding fonts into game data file. Full log of our discussion you can find at [3]. In short: 1) astromenace-data is non-free package because of [4]. 2) When package astromenace-data is built, system fonts are embedded [5] into game data file gamedata.vfs. 3) There is a workaround for such cases in Debian packages from main area: used fonts should be listed in Built-Using field. So the question for you: is the same workaround acceptable in non-free packages in common and in this particular case? (Please have in mind that only few files from this package are distributed under CC-BY-SA, and all other files are DFSG-free.) [1] http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace-data.git [2] http://mentors.debian.net/debian/pool/non-free/a/astromenace-data/astromenace-data_1.3.1+ds-1.dsc [3] http://bugs.debian.org/696385#71 [4] http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace-data.git;a=blob;f=debian/copyright;hb=HEAD#l31 [5] http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace-data.git;a=blob;f=debian/rules;hb=HEAD#l21 Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi Boris, just a comment on the copyright file. You are targeting the data for non-free but actually the game data is licensed under free licenses, namely GPL-3+ and CC-BY-SA-3.0. I assume the precompiled 3D models are the reason why astromenace-data should be in non-free because the sources are missing. IMO this should be documented at the top of debian/copyright like Comment: This data package is non-free because... to make it free you have to do the following... Otherwise nobody will know in a few years why you have made this decision and the package will likely stay in non-free forever. Regarding your font issue, i think you have already done the right thing by contacting the decision makers. :) Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi Markus, Thanks for notes. just a comment on the copyright file. You are targeting the data for non-free but actually the game data is licensed under free licenses, namely GPL-3+ and CC-BY-SA-3.0. I assume the precompiled 3D models are the reason why astromenace-data should be in non-free because the sources are missing. IMO this should be documented at the top of debian/copyright like Comment: This data package is non-free because... to make it free you have to do the following... Such comment is already available in appropriate place in debian/copyright (where related files are listed). And I see no reason to move or copy it into top part of debian/copyright. Otherwise nobody will know in a few years why you have made this decision and the package will likely stay in non-free forever. Personally I do not believe that someone will redraw these files in future. And this is not pessimistic but realistic point of view. =) Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi Boris, In the rules file for astromenace data, you list fonts in /usr/share/fonts/truetype/ttf-liberation/, but the files there are symlinks to files in /usr/share/fonts/truetype/liberation/. The symlinks are provided by a compatility package which is not listed in your build-dependencies, so building fails in a clean chroot. Can you fix that? There is a more serious problem. You copy font files which end-up (AFAIU) in gamedata.vfs. You therefore need to abide by the redistribution terms of the license of those fonts. The Debian way of insuring that in a generic manner (for DFSG-free material) would be to list the font packages in Built-Using. This ensures that the user can get the source for whatever ended-up in the binary package. The problem here is that astromenace-data is not in main but in non-free. I'm not sure that the Built-Using mechanism is sufficient to ensure that the source package for the fonts remain in the archive. Can you check that on -devel or -legal? Else I see two solutions: - copy (part of) the font source packages in astromenace-data (I didn't check: if the ttf files are their own source, you only need to copy them and amend debian/copyright); - pack gamedata.vfs on the end-user system to avoid redistribution. Kind regards, Thibaut. signature.asc Description: OpenPGP digital signature
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi Thibaut, Can you explain why you chose to split the source? This forces you to have astromenace only recommend astromenace-data, which is not good since you can't play the game without the data. I have at least three reasons for this: 1) It is more convenient in maintaining. Data files are changed rarely. There is no need to rebuild and re-upload huge package with them each time. 2) As I wrote earlier [1] package astromenace should recommend astromenace-data only at initial upload (to avoid circular dependencies). In next upload astromenace-data can be moved to dependencies. 3) IIRC buildd does not build packages in non-free area and pre-build binary packages should be uploaded into it manually. In this case binary packages will be available on less number of architectures than it should be possible. [1] http://bugs.debian.org/696385#19 Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Le 27/03/2013 09:21, Boris Pek a écrit : Hi Thibaut, Can you explain why you chose to split the source? This forces you to have astromenace only recommend astromenace-data, which is not good since you can't play the game without the data. I have at least three reasons for this: 1) It is more convenient in maintaining. Data files are changed rarely. There is no need to rebuild and re-upload huge package with them each time. 2) As I wrote earlier [1] package astromenace should recommend astromenace-data only at initial upload (to avoid circular dependencies). In next upload astromenace-data can be moved to dependencies. 3) IIRC buildd does not build packages in non-free area and pre-build binary packages should be uploaded into it manually. In this case binary packages will be available on less number of architectures than it should be possible. [1] http://bugs.debian.org/696385#19 Best regards, Boris Hi Boris, That makes sense. I was also thinking that the root of this was the ability to autobuild the binary. However, I have an alternative proposal which would avoid the problem and should not impose too much hassle on you: ship the entire source in astromenace-data, build the executable there, use it to package the data, but do not ship the built executable. This way, astromenace-data does not need to build-depend on astromenace, which can rightfully Depend on astromenace-data. You don't need to bootstrap by first only Recommending astromenace-data. Kind regards, Thibaut. signature.asc Description: OpenPGP digital signature
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi again, However, I have an alternative proposal which would avoid the problem and should not impose too much hassle on you: ship the entire source in astromenace-data, build the executable there, use it to package the data, but do not ship the built executable. Thank you for the interesting proposal. But I do not think that this is a good solution here. Package astromenace has some debian-specific patches [1]. Proposed solution implies that they should be shipped in both packages. Also debian/rules in astromenace-data will be longer and less clean/transparent than now. [1] http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace.git;a=tree;f=debian/patches This way, astromenace-data does not need to build-depend on astromenace, which can rightfully Depend on astromenace-data. You don't need to bootstrap by first only Recommending astromenace-data. This will be done only at first upload. I do not see the reason to avoid it. Do you have one? Moreover, one idea have just came into my mind. If you have already built astromenace-data, you can upload it as is. And astromenace package can be modified even before first upload, so it will depend on astromenace-data when it is added to archive. Problem with circular dependencies affects only to build system of potential sponsor of the package because: a) astromenace-data is arch-indep package and such packages are not re-built by buildd; b) packages in non-free are not re-built by buildd. Thus I propose such solution: 1) You use current (unmodified) package astromenace to build astromenace-data. 2) I update package astromenace: it will depend on astromenace-data. (But without changing package version.) 3) You upload package astromenace-data and updated package astromenace. If you agree with this tricky/artful solution I will prepare updated package astromenace this evening. Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Le 27/03/2013 13:43, Boris Pek a écrit : If you agree with this tricky/artful solution I will prepare updated package astromenace this evening. Forget it, I will upload as is after a last round of checks and after I manage to setup a local repo for use with pbuilder. Cheers, Thibaut. signature.asc Description: OpenPGP digital signature
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
If you agree with this tricky/artful solution I will prepare updated package astromenace this evening. Forget it, I will upload as is after a last round of checks and after I manage to setup a local repo for use with pbuilder. I have just updated package at m.d.n [1]. Now it includes recent changes done by Dmitry and me. See git log [2] for details. [1] http://mentors.debian.net/debian/pool/contrib/a/astromenace/astromenace_1.3.1+ds-1.dsc [2] http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace.git Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Dear Boris, Sorry for the delay and thanks for the ping. Can you explain why you chose to split the source? This forces you to have astromenace only recommend astromenace-data, which is not good since you can't play the game without the data. Kind regards, Thibaut. signature.asc Description: OpenPGP digital signature
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi Boris, On Thu, Dec 20, 2012 at 1:06 AM, Boris Pek tehnic...@yandex.ru wrote: Package: sponsorship-requests Severity: normal X-Debbugs-Cc: debian-devel-ga...@lists.debian.org Hi, I am looking for a sponsor for my packages astromenace and astromenace-data. Basic information: http://mentors.debian.net/package/astromenace http://mentors.debian.net/package/astromenace-data Direct links for download: http://mentors.debian.net/debian/pool/contrib/a/astromenace/astromenace_1.3.1+ds-1.dsc http://mentors.debian.net/debian/pool/non-free/a/astromenace-data/astromenace-data_1.3.1+ds-1.dsc Git repos: http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace.git http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace-data.git IANADD, but here's a list of things that I encountered while testing out your package. - Since you use xz compression, please consider adding Pre-Depends: dpkg (= 1.15.6) to debian/control (i.e. lintian tag data.tar.xz-member-without-dpkg-pre-depends, which I think has been recently removed). This is more of a pedantic issue than something strictly necessary, but it does help backporters. - Another pedantic issue: there are 2 commas in a row in your build-depends list for astromenace-data (i.e. debhelper (= 9),,fonts-liberation...). - Dmitry Smirnov is listed as an Uploader for astromenace but not for astromenace-data; is this intended? - Please make astromenace depend on astromenace-data, not just recommends (and have astromenace-data recommends/suggests astromenace), as is the norm for packages which depend on a separate -data package. - astromenace-data FTBFS when built twice in a row: dpkg-buildpackage -rfakeroot -D -us -uc -sa dpkg-buildpackage: source package astromenace-data dpkg-buildpackage: source version 1.3.1+ds-1 dpkg-buildpackage: source changed by Boris Pek tehnic...@mail.ru dpkg-source --before-build astromenace-data-1.3.1+ds dpkg-buildpackage: host architecture amd64 dpkg-source: info: using options from astromenace-data-1.3.1+ds/debian/source/options: --compression=xz --extend-diff-ignore=(^|/)RAW_VFS_DATA/FONT/[^/]+\.ttf$ fakeroot debian/rules clean dh clean dh_testdir dh_auto_clean debian/rules override_dh_clean make[1]: Entering directory `/tmp/astromenace-data/astromenace-data-1.3.1+ds' dh_clean gamedata.vfs RAW_VFS_DATA/FONT rm: cannot remove `RAW_VFS_DATA/FONT': Is a directory dh_clean: rm -f -- gamedata.vfs RAW_VFS_DATA/FONT returned exit code 1 make[1]: *** [override_dh_clean] Error 25 make[1]: Leaving directory `/tmp/astromenace-data/astromenace-data-1.3.1+ds' make: *** [clean] Error 2 dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi, IANADD, but here's a list of things that I encountered while testing out your package. Thanks a lot for a review. - Since you use xz compression, please consider adding Pre-Depends: dpkg (= 1.15.6) to debian/control (i.e. lintian tag data.tar.xz-member-without-dpkg-pre-depends, which I think has been recently removed). Yes, I am aware of this lintian note, but I ignore it because: 1) It is useless for new packages. 2) Pre-Depends should be used sparingly, preferably only by packages whose premature upgrade or installation would hamper the ability of the system to continue with any upgrade that might be in progress. You should not specify a Pre-Depends entry for a package before this has been discussed on the debian-devel mailing list and a consensus about doing that has been reached. [1] [1] http://www.debian.org/doc/debian-policy/ch-relationships.html This is more of a pedantic issue than something strictly necessary, but it does help backporters. There is dpkg verison 1.15.8.13 in Debian Squeeze: http://packages.debian.org/squeeze/dpkg Older releases are not supported. - Another pedantic issue: there are 2 commas in a row in your build-depends list for astromenace-data (i.e. debhelper (= 9),,fonts-liberation...). Thanks. I'll fix it ASAP. Hope it will be today, because since tomorrow I will be on vacation during two weeks. - Dmitry Smirnov is listed as an Uploader for astromenace but not for astromenace-data; is this intended? I am not sure that he want to co-maintain it. But he could add or remove himself from uploaders list at any moment. Dmitry, could you comment this? - Please make astromenace depend on astromenace-data, not just recommends This is bad idea because astromenace-data has build dependency from astromenace and it FTBFS if astromenace depends from it. (Circular dependencies.) So it should stay as is, at least for a first iteration. (and have astromenace-data recommends/suggests astromenace), as is the norm for packages which depend on a separate -data package. - astromenace-data FTBFS when built twice in a row: Hmm, I missed this. Thanks. Will be fixed. Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
On Tue, 25 Dec 2012 21:06:54 Boris Pek wrote: - Since you use xz compression, please consider adding Pre-Depends: dpkg (= 1.15.6) to debian/control (i.e. lintian tag data.tar.xz-member-without-dpkg-pre-depends, which I think has been recently removed). Yes, I am aware of this lintian note, but I ignore it because: 1) It is useless for new packages. 2) Pre-Depends should be used sparingly, preferably only by packages whose premature upgrade or installation would hamper the ability of the system to continue with any upgrade that might be in progress. You should not specify a Pre-Depends entry for a package before this has been discussed on the debian-devel mailing list and a consensus about doing that has been reached. [1] [1] http://www.debian.org/doc/debian-policy/ch-relationships.html Perhaps it was me who ignored this lintian warning first. :) This warning doesn't make sense for Debain any more. I completely agree with Boris on this. - Dmitry Smirnov is listed as an Uploader for astromenace but not for astromenace-data; is this intended? I am not sure that he want to co-maintain it. But he could add or remove himself from uploaders list at any moment. Dmitry, could you comment this? Boris picked up the packaging where I left it. In the beginning both packages [astromenace,astromenace-data] were generated from single source. It was good enough as proof of concept. I was not following on development since Boris continued it but I trust Boris and I'm sure he knows what he is doing. :) As the moment I have other priorities so I can't co-maintain astromenace-data yet. I'd probably stay a bit longer as astromenace uploader until I decide whenever remove or add myself as uploader of astromenace-data. Thanks, Boris. Thanks Vincent. Cheers, Dmitry. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Hi, - Another pedantic issue: there are 2 commas in a row in your build-depends list for astromenace-data (i.e. debhelper (= 9),,fonts-liberation...). Fixed. have astromenace-data recommends/suggests astromenace Done. - astromenace-data FTBFS when built twice in a row: Fixed. Thanks again for review. Direct links for download: http://mentors.debian.net/debian/pool/contrib/a/astromenace/astromenace_1.3.1+ds-1.dsc http://mentors.debian.net/debian/pool/non-free/a/astromenace-data/astromenace-data_1.3.1+ds-1.dsc Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#696385: RFS: astromenace/1.3.1+ds-1 [ITP] -- hardcore 3D space shooter with spaceship upgrade possibilities
Package: sponsorship-requests Severity: normal X-Debbugs-Cc: debian-devel-ga...@lists.debian.org Hi, I am looking for a sponsor for my packages astromenace and astromenace-data. Basic information: http://mentors.debian.net/package/astromenace http://mentors.debian.net/package/astromenace-data Direct links for download: http://mentors.debian.net/debian/pool/contrib/a/astromenace/astromenace_1.3.1+ds-1.dsc http://mentors.debian.net/debian/pool/non-free/a/astromenace-data/astromenace-data_1.3.1+ds-1.dsc Git repos: http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace.git http://anonscm.debian.org/gitweb/?p=pkg-games/astromenace-data.git AstroMenace is an astonishing hardcore scroll-shooter where brave space warriors may find a great opportunity to hone their combat skills. Gather money during the battle to spend them on turning your spaceship into an ultimate weapon of mass destruction and give hell to swarms of adversaries. Enjoy the wonderfully crafted 3d graphics and high-quality special effects along with a detailed difficulty adjustment and a handy interface of AstroMenace. Package with data files is separated due to license issues: it includes precompiled 3D models under CC-BY-SA-3.0. More information about the game: http://www.viewizard.com/astromenace/ I would be glad if someone uploaded these packages for me. Best regards, Boris -- http://wiki.debian.org/BorisPek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
