Re: RFS: dwarf-fortress
On Wed, Feb 22, 2012 at 10:50 AM, Andrey Rahmatullin wrote: > I've tried to build this package but on amd64 it cannot find GL/glew.h and > fails to build. > So I've created an i386 cowbuilder chroot and tried to build for i386. It > couldn't install libncursesw-dev because there is no such package in the > archive. I've added the missing libglew-dev dependency and fixed the libncursesw-dev package. I'm not even sure this ncurse library is actually required (I know ncurses is required, but I don't know the difference between ncurses and ncursesw). A new version has been uploaded to mentors with these fixes (with same debian release number). >> http://mentors.debian.net/package/dwarf-fortress-mod-default > Why did you split this from the original package? Isn't it a part of the > original distribution? This was so the default graphic mod is maintained and packaged the same way as third-party mods, with same tree and so on, and so that new mods can easily be created from it (without having to provide all the binaries with it). I could have put this in the main dwarf-fortress package though... i'll think about it. -- Beren Minor -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caonpvzylufdqqjm5c1pag9bnkj68f-ss7-7ga6btmrw+kfb...@mail.gmail.com
Re: RFS: dwarf-fortress
On Wed, Feb 22, 2012 at 01:15:39AM +0100, Beren Minor wrote: > I've updated the packages on mentors and splitted the original one in > two. There's the main dwarf-fortress with binaries, data files and > scripts for modding support, and the default graphic mod package that > is also required. I've not re-uploaded the other third-party mods for > now but they would be packaged as separate packages as well. Both > should build without Git. > > http://mentors.debian.net/package/dwarf-fortress I've tried to build this package but on amd64 it cannot find GL/glew.h and fails to build. So I've created an i386 cowbuilder chroot and tried to build for i386. It couldn't install libncursesw-dev because there is no such package in the archive. > http://mentors.debian.net/package/dwarf-fortress-mod-default Why did you split this from the original package? Isn't it a part of the original distribution? -- WBR, wRAR signature.asc Description: Digital signature
Re: RFS: dwarf-fortress
I've updated the packages on mentors and splitted the original one in two. There's the main dwarf-fortress with binaries, data files and scripts for modding support, and the default graphic mod package that is also required. I've not re-uploaded the other third-party mods for now but they would be packaged as separate packages as well. Both should build without Git. http://mentors.debian.net/package/dwarf-fortress http://mentors.debian.net/package/dwarf-fortress-mod-default Kind Regards, -- Beren Minor -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caonpvzxgn1y0bf9jjd7i43ofu5euj8f6rwfhd1p8t+ok0vs...@mail.gmail.com
Re: RFS: dwarf-fortress
> Or make use of format 3.0 multi-orig feature. That seems interesting, is it supported by git-buildpackage? #561071 makes me think it is not... -- Beren Minor -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caonpvzyzxunbtb0dkruto3qt1rnxtcohhrnmc8xpxzc-udz...@mail.gmail.com
Re: RFS: dwarf-fortress
On Tue, Feb 21, 2012 at 06:15:00PM +0100, Beren Minor wrote: > > I'm not talking about patches, gbp and gbp-pq. I mean git checkout magic > > in your Makefile. > > > > As with any other standalone Debian package, dget --build for .dsc URL or > > dpkg-source -x and dpkg-buildpackage for downloaded one. You should learn > > these tools before learning git-buildpackage. > > That's what I've just realised, indeed. I'm maintaining the upstream > sources and third party mods on different git branches for clarity > purpose and to keep things clean and separated. I should probably > introduce a new fake upstream branch with all these merged together. > I'll work on it. Or make use of format 3.0 multi-orig feature. -- WBR, wRAR signature.asc Description: Digital signature
Re: RFS: dwarf-fortress
On Tue, Feb 21, 2012 at 6:05 PM, Andrey Rahmatullin wrote: > For the reference: #598909. > Also, glew doesn't seem to be needed. That's what I was talking about. There's no answer to this bug and no willing to add the sdl libraries to ia32-libs, because the ia32-libs is though to be obsolete, replaced with multi-arch that is still not available. Kafka himself would be impressed. > I'm not talking about patches, gbp and gbp-pq. I mean git checkout magic > in your Makefile. > > As with any other standalone Debian package, dget --build for .dsc URL or > dpkg-source -x and dpkg-buildpackage for downloaded one. You should learn > these tools before learning git-buildpackage. That's what I've just realised, indeed. I'm maintaining the upstream sources and third party mods on different git branches for clarity purpose and to keep things clean and separated. I should probably introduce a new fake upstream branch with all these merged together. I'll work on it. -- Beren Minor -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAONPvZy2chiYObSWpCQJxGfwAmW12pmpKbX=awZ_FbiGXb=e...@mail.gmail.com
Re: RFS: dwarf-fortress
On Tue, Feb 21, 2012 at 05:48:50PM +0100, Beren Minor wrote: > The other correct way, as far as I could see, to have an i386 package > available on amd64 is to use ia32-libs package, however this package > does not contain all the required dependencies for dwarf-fortress > (sdl-ttf, sdl-image and glew are missing). For the reference: #598909. Also, glew doesn't seem to be needed. > > You have a build system that uses git magic and branches while an > > unpacked Debian source package is a directory with upstream sources from > > upstream tarball(s) and debian/ directory with build files. Also, as you > > include 3rd-party mods, you should ask about their distribution licenses > > and mention them in debian/copyright. > I'm using git-buildpackage for building, and patch queue maintained > with the same tool. Patches aren't commited to debian branch (maybe > they should), but can be regenerated with "gbp-pq export" command > before running git-buildpackage. I'm not talking about patches, gbp and gbp-pq. I mean git checkout magic in your Makefile. > > There are some more or less minor things such as copyright notices in > > descriptions and old Standards-Version, but they are not important for > > now, as I could not even build the package. > I'm not sure what the procedure is to build the package from the > mentors uploaded files As with any other standalone Debian package, dget --build for .dsc URL or dpkg-source -x and dpkg-buildpackage for downloaded one. You should learn these tools before learning git-buildpackage. -- WBR, wRAR signature.asc Description: Digital signature
Re: RFS: dwarf-fortress
> > I'm not a Debian Maintainer and I'm also looking for advices and > > comment on the way the game has been packaged, as the available > > upstream binaries are 32bits only, and I had to embed 32bit libraries > > with the package in order to have it work. > You should not embed libraries. You also should not set Architecture: any. > If you want to see a i386-only binary packaged for amd64, you may look at > zsnes (though the proper way is multi-arch dpkg but it is not available in > unstable now). Hello, I had a look at your package. I also confirm that it does not build in a chroot, unfortunately. The package should build without being in a git repository (and without internet access). As a maintainer of the zsnes package, I second the suggestion of having a look at it as the requirements are similar. Feel free to ask here if something is unclear :) -- Etienne Millon -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120221165158.GA3516@klow
Re: RFS: dwarf-fortress
Hi and thanks for you interest, On Tue, Feb 21, 2012 at 5:24 PM, Andrey Rahmatullin wrote: > Did you try to contact the previous ITP owner? I did, a year ago and before as well. The answer I got was "it's still work in progress, we are trying to talk with the upstream author to have a more FHS compliant game". No updates since. I haven't asked again, but it has been WIP for almost two years now and without any release. I don't want to hijack the package, but I've got something working for a year already and I took the opportunity of the new upstream release for uploading it to debian mentors. > You should not embed libraries. You also should not set Architecture: any. > If you want to see a i386-only binary packaged for amd64, you may look at > zsnes (though the proper way is multi-arch dpkg but it is not available in > unstable now). I've been already told like half a year ago that the correct way was to use multi-arch package. However as you said, muti-arch isn't available and I couldn't even make it work with experimental dpkg/aptitude, so I gave up [1]. The other correct way, as far as I could see, to have an i386 package available on amd64 is to use ia32-libs package, however this package does not contain all the required dependencies for dwarf-fortress (sdl-ttf, sdl-image and glew are missing). I asked the ia32-libs maintainer if it was possible to add these libraries, but I've been told that ia32-libs should not be used and that I should use multi-arch (cf [1]). Therefore, embed libraries it is. > You have a build system that uses git magic and branches while an > unpacked Debian source package is a directory with upstream sources from > upstream tarball(s) and debian/ directory with build files. Also, as you > include 3rd-party mods, you should ask about their distribution licenses > and mention them in debian/copyright. I'm using git-buildpackage for building, and patch queue maintained with the same tool. Patches aren't commited to debian branch (maybe they should), but can be regenerated with "gbp-pq export" command before running git-buildpackage. Regarding the copyright thing, I understand that and I'll add the copyrights to the corresponding files, and ask/tell/talk upstream authors about it. > There are some more or less minor things such as copyright notices in > descriptions and old Standards-Version, but they are not important for > now, as I could not even build the package. I'm not sure what the procedure is to build the package from the mentors uploaded files, if you can tell me the issues you are facing, I can try to solve them. -- Beren Minor -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caonpvzxfvxpcg98d+a8gjqiyp5tje71xo+q84yjlcwargs3...@mail.gmail.com
Re: RFS: dwarf-fortress
On Tue, Feb 21, 2012 at 04:47:42PM +0100, Beren Minor wrote: > I am looking for a sponsor for my package "dwarf-fortress". That's good news. Unfortunately, the package is not ready yet. > dwarf-fortress-bin - Dwarf Fortress binaries > dwarf-fortress-data - Dwarf Fortress data files > dwarf-fortress-mod-ironhand - Dwarf Fortress graphic mod "Ironhand" > dwarf-fortress-mod-mayday - Dwarf Fortress graphic mod "Mayday" > dwarf-fortress-mod-phoebus - Dwarf Fortress graphic mod "Phoebus" > > To access further information about this package, please visit the > following URL: > > http://mentors.debian.net/package/dwarf-fortress > > Alternatively, one can download the package with dget using this command: > > dget -x > http://mentors.debian.net/debian/pool/non-free/d/dwarf-fortress/dwarf-fortress_0.34.2.0-1.dsc > > I would be glad if someone uploaded this package for me. > -- Please don't include '-- ' in the middle of your emails, it marks the end of the message text. > There's already an ITP for this package in debian but it has been > inactive for a long time and without any. Did you try to contact the previous ITP owner? > I'm not a Debian Maintainer and I'm also looking for advices and > comment on the way the game has been packaged, as the available > upstream binaries are 32bits only, and I had to embed 32bit libraries > with the package in order to have it work. You should not embed libraries. You also should not set Architecture: any. If you want to see a i386-only binary packaged for amd64, you may look at zsnes (though the proper way is multi-arch dpkg but it is not available in unstable now). You have a build system that uses git magic and branches while an unpacked Debian source package is a directory with upstream sources from upstream tarball(s) and debian/ directory with build files. Also, as you include 3rd-party mods, you should ask about their distribution licenses and mention them in debian/copyright. There are some more or less minor things such as copyright notices in descriptions and old Standards-Version, but they are not important for now, as I could not even build the package. -- WBR, wRAR signature.asc Description: Digital signature
