Bug#1071663: RFP: minetest-mod-voxelibre -- voxelibre mod for minetest
Matthias Geiger writes: > […] > > Since this is an RFP I suggest you file a different one for Mineclonia. > If someone decides to package either they can draw their own conclusions. Thanks, maybe I will. I am not against packaging VoxeLibre, I just want people to know what they are in for: An upstream that breaks things and is not particularly receptive to approaches that don't break stuff (and arguably that was a big reason for the Mineclonia fork event initially). signature.asc Description: PGP signature
Bug#741029: ITP: redo -- a top-down software build system
I have now written man pages for each redo executable and fixed a few bugs in them. The archive with the binaries and man pages is here: <http://news.dieweltistgarnichtso.net/bin/archives/redo-sh.tar.gz> Extracting the files in the archive to /usr/local yields working redo utilities and man pages on my Debian system. I have successfully created a Debian package using equivs-build(1). Where should I upload my package and the build instructions for it? -- Nils Dagsson Moskopp // erlehmann <http://dieweltistgarnichtso.net>
Bug#741029: equivs control file for redo(1) implementation
I created a file that can be used with the files linked at <http://news.dieweltistgarnichtso.net/bin/redo-sh.html> and the equivs-build(1) command to build a Debian package for redo. I have attached it to this email and also made it available on my web site <http://news.dieweltistgarnichtso.net/bin/redo-sh.ctl>. I have several questions regarding the equivs-build approach: • Is it allowed by Debian policy to package a program this way? My implementation of redo(1) only consists of Bourne Shell scripts and can be packaged as-is without invoking a compiler or similar program. • How do I find the version of coreutils my program depends on? It needs cut(1), md5sum(1), mv(1), rm(1), sh(1) and stat(1). Is it possible to do a binary search on all past Debian packages to find out which one lacked any of these binaries? • Should I explain why my program suggests coreutils in the description? The answer is that it has more functionality on systems with shuf(1). • How can I specify that the program is licensed AGPL-3 or later? • Do I need to write a man page for every redo utility? • Should redo utilities that should only be invoked from redo build scripts (“dofiles”) reside in “/usr/lib/redo”, not in “/usr/bin”? • What is good or bad about the current description of the package? -- Nils Dagsson Moskopp // erlehmann <http://dieweltistgarnichtso.net> pgpIjwZiVYYAS.pgp Description: PGP signature ### Commented entries have reasonable defaults. ### Uncomment to edit them. # Source: Section: devel Priority: optional Homepage: http://news.dieweltistgarnichtso.net/bin/redo-sh.html Standards-Version: 3.9.2 Package: redo-sh Version: 2016-03-02 Maintainer: Nils Dagsson Moskopp <nils+r...@dieweltistgarnichtso.net> # Pre-Depends: Depends: coreutils | busybox | busybox-static # Recommends: Suggests: coreutils Provides: redo # Replaces: Architecture: all # Multi-Arch: # Copyright: AGPL-3 # Changelog: # Readme: # Extra-Files: Files: redo /usr/bin redo-always /usr/bin redo-dot /usr/bin redo-ifchange /usr/bin redo-ifcreate /usr/bin redo-ood /usr/bin redo-targets /usr/bin redo-sources /usr/bin redo-stamp /usr/bin Description: Top-down software build system, Bourne Shell implementation redo is a utility which controls the generation of target files from source files. It determines automatically which targets need to be (re)created and issues commands to (re)create them. In contrast to the widely-used make program, redo records dependencies during the build. redo build scripts (“dofiles”) are shell scripts by default, but can be written in other languages. . For the design, see “Rebuilding target files when source files have changed” from Daniel J. Bernstein (DJB) <http://cr.yp.to/redo.html>. . This package contains an implementation of redo in Bourne Shell. For an overview of other redo implementations, see “Introduction to redo” <http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/introduction-to-redo.html>.
Bug#794470: ITP: openxcom -- Open-source clone of the original X-Com game
Alexandre Detiste alexandre.deti...@gmail.com writes: Package: wnpp Severity: wishlist Owner: Alexandre Detiste alexandre.deti...@gmail.com * Package name: openxcom Version : 1.1 (not yet released) Upstream Author : SupSuper @ GitHub, OpenXcom Developers * URL : http://openxcom.org/ * License : GPL 3 Programming Lang: C Maintainer : Debian Games Team Description : Open-source clone of the original X-Com game As this needs the original game data, as currently still sold on Steam, this game would go in contrib. I think it should be noted that this game data is not only available on Steam, though. Did other games (OpenTTD before free content) note the availability of game data on abandonware sites in their README? Upcoming game-data-packager can automacialy create a .deb for local consumption with these data. For future reference: “Since OpenXcom depends on the original game data, it also suffers from bugs present in that data like map glitches and problems. To fix these you need to apply a data patch.”. Source: http://openxcom.org/downloads-extras/ A draft package is available here: http://anonscm.debian.org/cgit/pkg-games/openxcom.git/ The current draft package is built upon a recent git snapshot, because the commercial data layout has evolved since v1.0 to allow room for 'Terror from the deep' sequel. There is a regression in libyaml-cpp0.5 0.5.2; one needs to downgrade to 0.5.1-1 before building this draft package. This will be solved in next libyaml-cpp release: https://github.com/jbeder/yaml-cpp/commit/b426fafff6238dda8d86fa668f585cba732dd272 -- To UNSUBSCRIBE, email to debian-devel-games-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150803120222.27135.23545.reportbug@antec -- Nils Dagsson Moskopp // erlehmann http://dieweltistgarnichtso.net pgprB7UCT2VM5.pgp Description: PGP signature
Bug#548031: status of ASCIIpOrtal packaging
ASCIIpOrtal is a terminal game where you have a gun that shoots doors. I recently installed ASCIIpOrtal on my N900 running Maemo. Since I like the game, I would like to have access to it in Debian. It seems Peter Pentchev tried to package it once, but gave up in September 2010. Upstream seems to be offline: http://cymonsgames.com/asciiportal Upstream source copy: https://github.com/cymonsgames/ASCIIpOrtal This repository of the Debian games team looks abandoned: http://anonscm.debian.org/cgit/pkg-games/asciiportal.git/ There seems to exist no package named “asciiportal” or “asciip0rtal”: https://packages.debian.org/search?keywords=asciiportal https://packages.debian.org/search?keywords=asciip0rtal In 2009, Peter Pentchev r...@ringlet.net wrote in bug #548031: I actually have an almost-ready package for ASCIIpOrtal in the Debian Games Team's Git repository; just a couple of copyright issues remain to be clarified with the upstream developers. Sorry for the delay! Can anyone tell me what the copyright issues were? I am willing to work on the issues with upstream and create replacement assets if necessary. -- Nils Dagsson Moskopp // erlehmann http://dieweltistgarnichtso.net pgpfaut9cFEPY.pgp Description: PGP signature
Bug#741640: packaging vcmi
Johannes Schauer j.scha...@email.de writes: The colored rectangle version could be the basis of a free graphics pack. Creating such a replacement is surely a multi-year effort True for a beautiful replacement – so i started drawing an ugly one: git clone http://daten.dieweltistgarnichtso.net/src/vcmi-data-libre.git Is CC BY-SA 3.0+ free enough for Debian? -- Nils Dagsson Moskopp // erlehmann http://dieweltistgarnichtso.net -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87pplikp9u@dieweltistgarnichtso.net
Bug#741640: packaging vcmi
Boris Pek tehn...@debian.org writes: Is CC BY-SA 3.0+ free enough for Debian? Yes, if source files for these data files are available. Source is SVG drawings. -- Nils Dagsson Moskopp // erlehmann http://dieweltistgarnichtso.net -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/874n2tyczz@dieweltistgarnichtso.net
Bug#741029: ITP: redo -- a top-down software build system
Package: wnpp Severity: wishlist Owner: Nils Dagsson Moskopp nils+debian-report...@dieweltistgarnichtso.net * Package name: redo Version : 0.0.1 Upstream Author : Nils Dagsson Moskopp n...@dieweltistgarnichtso.net * URL : http://news.dieweltistgarnichtso.net/bin/ * License : AGPLv3+ Programming Lang: Bourne shell Description : a top-down software build system redo is a software build system envisioned by Daniel J. Bernstein, which is simultaneously smaller, faster, more powerful and less complex than make. Build scripts are shell scripts, but can be written in almost any language. http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/introduction-to-redo.html This implementation of redo is simpler and faster than the redo implementation by Avery Pennarun. While Pennarun's version of redo is written in Python, this version of redo depends only on the Bourne shell and standard utilities provided by the GNU coreutils or Busybox packages. Caveat: This version of redo is missing the redo-ifcreate command, which creates dependencies on files not yet existing. Adding it should be simple. As I am the upstream author, I maintain this version of redo. I expert maintenance effort to be low, as the software is essentially finished. I probably need a sponsor for uploading the package. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140307170442.5277.84308.reportbug@lustschutzbunker
