-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 19 Jan 2015 20:23:20 +0100
Source: xd
Binary: xd
Architecture: source amd64
Version: 3.23.01-1
Distribution: experimental
Urgency: low
Maintainer: Frank B. Brokken f.b.brok...@rug.nl
Changed-By: Frank B. Brokken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 19 Jan 2015 21:37:39 +0100
Source: qmapshack
Binary: qmapshack
Architecture: source amd64
Version: 0.11.0-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project pkg-grass-de...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 19 Jan 2015 20:57:36 +0100
Source: code-saturne
Binary: code-saturne code-saturne-bin code-saturne-data code-saturne-include
code-saturne-doc
Architecture: source all amd64
Version: 3.3.3+svn-1~exp1
Distribution: experimental
On Mon, Jan 19, 2015 at 11:31:20AM +, Wookey wrote:
Am I right that the
only way to expliticly mail the submitter and the maintainer is to
look the submitter's mail up in the initial bugrep and just CC it,
whilst replying to bugnum@b.d.o, which will automatically include the
maintainer?
On Mon, 2015-01-19 at 16:57 -0500, Michael Gilbert wrote:
Isn't the spam vector already wide open for
nn-subscr...@bugs.debian.org, which isn't much (ab)used today?
I fail to see how any of the discussed changes open an abuse vector
that doesn't already exist.
OK, so let me help you
Hi,
Quoting Ben Hutchings (2015-01-19 02:03:52)
On Mon, 2015-01-19 at 08:37 +0800, Paul Wise wrote:
I'd very much appreciate the ability to not be auto-subscribed to
every bug so please do implement the opt-out thing, preferably before
this change is rolled out.
Personally, I think
On Mon, Jan 19, 2015 at 4:30 PM, Johannes Schauer wrote:
how about the other way round then:
- by default everything stays as it is and there is no auto subscription
- by sending an email to the bts I can activate that I'm automatically
subscribed to all bugs I submitted or contributed
Steven,
While being in terrible position to tell you what you should or should
not do, I'd still suggest you to read:
https://www.debian.org/code_of_conduct
https://people.debian.org/~enrico/dcg/
On Fri, Jan 16, 2015 at 5:48 PM, Steven Capper steven.cap...@gmail.com wrote:
Mathieu,
I'm
On Mon, Jan 19, 2015 at 9:25 AM, Mathieu Malaterre ma...@debian.org wrote:
Steven,
While being in terrible position to tell you what you should or should
not do, I'd still suggest you to read:
https://www.debian.org/code_of_conduct
https://people.debian.org/~enrico/dcg/
Just to be clear: I
Package: wnpp
Severity: wishlist
Owner: Christopher Hoskin christopher.hos...@gmail.com
* Package name: libapache-session-memcached-perl
Version : 0.03
Upstream Author : Enrico Sorcinelli en...@cpan.org
* URL : https://metacpan.org/release/Apache-Session-Memcached
*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 20 Jan 2015 12:14:02 +0530
Source: ruby-rails-assets-jquery-idletimer
Binary: ruby-rails-assets-jquery-idletimer libjs-jquery-idletimer
Architecture: source all
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
On 19/01/15 01:14, Paul Wise wrote:
On Mon, Jan 19, 2015 at 5:03 PM, Tomas Pospisek wrote:
But isn't subscribing participants natural? Posting to a bug
report means participation and thus you'd get the follow-ups. Why
would you post to a bug report if you aren't interested in what
On Mon, Jan 19, 2015 at 4:41 AM, Russell Stuart wrote:
But isn't subscribing participants natural?
It may be natural, but IMO you are underestimating the spam vector
problem.
Debian's bug submission mechanism does not try to verify you control the
email address you are submitting from.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 18 Jan 2015 20:40:41 +0100
Source: routes
Binary: python-routes python3-routes
Architecture: source all
Version: 2.1-1
Distribution: experimental
Urgency: medium
Maintainer: Piotr Ożarowski pi...@debian.org
Changed-By: Piotr
Package: wnpp
Severity: wishlist
Owner: Christopher Hoskin christopher.hos...@gmail.com
* Package name: libauthen-htpasswd-perl
Version : 0.171
Upstream Author : Matt S Trout perl-st...@trout.me.uk
* URL : https://metacpan.org/release/Authen-Htpasswd
* License
On 2015-01-19 10:03, Eugene Zhukov wrote:
Through my experience this is not the case - even the maintainer
doesn't get mail about a bug.
For example I'm listed as a maintainer of epubcheck package,
No, you're not:
Maintainer: Debian XML/SGML Group
debian-xml-sgml-p...@lists.alioth.debian.org
+++ Adam D. Barratt [2015-01-19 11:01 +]:
On 2015-01-19 10:47, Mattia Rizzolo wrote:
On Mon, Jan 19, 2015 at 09:26:41AM +, Wookey wrote:
Can someone remind me what the current rules are (or where it's
written down). I know it doesn't work the way I expect it ought
to, but I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 19 Jan 2015 21:17:31 +0900
Source: birdfont
Binary: birdfont
Architecture: source amd64
Version: 2.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Fonts Task Force pkg-fonts-de...@lists.alioth.debian.org
Package: wnpp
Severity: wishlist
Owner: Markus Koschany a...@gambaru.de
* Package name: caveexpress
Version : 2.1
Upstream Author : Martin Gerhardy i...@caveproductions.org
* URL : http://www.caveproductions.org
* License : GPL3+, CC-BY-SA-4.0
Programming
[ CCing debian-release. ]
Hi!
On Sun, 2015-01-18 at 20:12:55 +0200, Niko Tyni wrote:
In order to fix trigger related wheezy-jessie upgrade failures in
xfonts-traditional (#774844, cc'd), I intend to make the main perl
binary packages (perl, perl-base, and perl-modules) Pre-Depend on dpkg
(=
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 19 Jan 2015 12:23:03 +
Source: xemacs21
Binary: xemacs21 xemacs21-mule xemacs21-nomule xemacs21-mule-canna-wnn
xemacs21-bin xemacs21-support xemacs21-supportel
Architecture: source all amd64
Version: 21.4.22-11
Firstly, I should say: I'm sorry that I got the design of this wrong
when I set up the BTS. I hadn't appreciated at the time that bug
reports are actually (amongst other things) ad-hoc mailing lists.
Paul Wise writes (Re: Who gets an email when with bugreports [was: Re:
Unauthorised activity
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 08 Jan 2015 06:39:25 -0400
Source: php-sql-formatter
Binary: php-sql-formatter
Architecture: source all
Version: 1.2.17-1
Distribution: unstable
Urgency: low
Maintainer: Debian PHP PEAR Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 11 Jan 2015 22:02:57 +0300
Source: haskell-decimal
Binary: libghc-decimal-dev libghc-decimal-prof libghc-decimal-doc
Architecture: source all amd64
Version: 0.4.2-1
Distribution: experimental
Urgency: low
Maintainer: Debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 08 Jan 2015 16:58:24 -0400
Source: php-json-patch
Binary: php-json-patch
Architecture: source all
Version: 0.1.0-1
Distribution: unstable
Urgency: low
Maintainer: Debian PHP PEAR Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 15 Dec 2014 13:19:02 +0100
Source: pyusb
Binary: python-usb python3-usb
Architecture: source amd64
Version: 1.0.0~b2-1
Distribution: experimental
Urgency: low
Maintainer: Debian Python Modules Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 14 Jan 2015 12:08:03 +0530
Source: ruby-devise
Binary: ruby-devise
Architecture: source all
Version: 3.4.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Ruby Extras Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 26 Nov 2014 14:28:24 +0200
Source: ruby-mina
Binary: mina
Architecture: source all
Version: 0.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 30 Dec 2014 22:40:33 +0530
Source: ruby-rails-assets-jquery-placeholder
Binary: ruby-rails-assets-jquery-placeholder libjs-jquery-placeholder
Architecture: source all
Version: 2.0.8-1
Distribution: unstable
Urgency: medium
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 31 Dec 2014 12:08:07 +0530
Source: ruby-js-routes
Binary: ruby-js-routes
Architecture: source all
Version: 0.9.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 09 Jan 2015 15:36:52 +0530
Source: ruby-rails-assets-punycode
Binary: ruby-rails-assets-punycode libjs-punycode
Architecture: source all
Version: 1.3.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian Ruby Extras
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 14 Jan 2015 21:47:18 +0100
Source: php-text-languagedetect
Binary: php-text-languagedetect
Architecture: source amd64
Version: 0.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 14 Jan 2015 21:40:04 +0100
Source: php-xml-svg
Binary: php-xml-svg
Architecture: source amd64
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers pkg-php-p...@lists.alioth.debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 14 Jan 2015 21:23:16 +0100
Source: php-crypt-chap
Binary: php-crypt-chap
Architecture: source all
Version: 1.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 08 Jan 2015 14:22:29 +0530
Source: ruby-rails-assets-jquery-idletimer
Binary: ruby-rails-assets-jquery-idletimer libjs-jquery-idletimer
Architecture: source all
Version: 1.0.1-1
Distribution: unstable
Urgency: medium
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 18 Jan 2015 21:47:00 +0100
Source: jzmq
Binary: libzmq-java libzmq-java-doc
Architecture: source amd64 all
Version: 3.1.0-1
Distribution: unstable
Urgency: low
Maintainer: Jan Niehusmann j...@debian.org
Changed-By: Jan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 08 Jan 2015 06:33:54 -0400
Source: php-doctrine-cache-bundle
Binary: php-doctrine-cache-bundle
Architecture: source all
Version: 1.0.1-1
Distribution: unstable
Urgency: low
Maintainer: Debian PHP PEAR Maintainers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 15 Jan 2015 20:47:15 +0300
Source: cl-trivial-utf-8
Binary: cl-trivial-utf-8
Architecture: source all
Version: 20111001-1
Distribution: unstable
Urgency: medium
Maintainer: Dimitri Fontaine d...@tapoueh.org
Changed-By: Dimitri
Package: wnpp
Severity: wishlist
Owner: Paul Novotny p...@paulnovo.us
* Package name: opensurgsim
Version : 0.6.0
Upstream Author : Paul Novotny pnovo...@simquest.com
* URL : http://www.opensurgsim.org/
* License : Apache 2.0
Programming Lang: C++
Guillem Jover writes (Re: new pre-dependency: perl{,-base,-modules} - dpkg
(= 1.17.17)):
On Sun, 2015-01-18 at 20:12:55 +0200, Niko Tyni wrote:
In order to fix trigger related wheezy-jessie upgrade failures in
xfonts-traditional (#774844, cc'd), I intend to make the main perl
binary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 19 Jan 2015 12:45:02 +0100
Source: simple-scan
Binary: simple-scan simple-scan-dbg
Architecture: source amd64
Version: 3.15.4-1
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst deb...@jff-webhosting.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 19 Jan 2015 15:45:16 +0200
Source: frogr
Binary: frogr frogr-data
Architecture: source amd64 all
Version: 0.10-2
Distribution: unstable
Urgency: medium
Maintainer: Alberto Garcia be...@igalia.com
Changed-By: Alberto Garcia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 21 Nov 2014 22:21:54 +0900
Source: dash-el
Binary: dash-el
Architecture: source all
Version: 2.10.0-1
Distribution: unstable
Urgency: low
Maintainer: Hajime Mizuno mizuno...@ubuntu.com
Changed-By: Hajime Mizuno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 19 Jan 2015 15:17:06 +0100
Source: isodate
Binary: python-isodate python3-isodate
Architecture: source all
Version: 0.5.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Python Modules Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 19 Jan 2015 14:35:21 +0100
Source: synaptic
Binary: synaptic
Architecture: source amd64
Version: 0.81.3
Distribution: unstable
Urgency: low
Maintainer: Michael Vogt m...@debian.org
Changed-By: Michael Vogt
On Mon, Jan 19, 2015 at 05:14:18PM +0800, Paul Wise wrote:
People often file bugs for issues they discover in software they don't
use or care about, getting followups to those isn't necessary.
Uh? What's your rationale for this, and in particular for the often
part?
Surely the typical use case
On Mon, January 19, 2015 10:14, Paul Wise wrote:
On Mon, Jan 19, 2015 at 5:03 PM, Tomas Pospisek wrote:
But isn't subscribing participants natural? Posting to a bug report
means participation and thus you'd get the follow-ups. Why would you
post to a bug report if you aren't interested in
+++ Paul Wise [2015-01-19 17:14 +0800]:
On Mon, Jan 19, 2015 at 5:03 PM, Tomas Pospisek wrote:
I can understand your point of view and I think also the why but isn't
that position the exception from the rule? That is shouldn't the process
be optimized for the common case and allow the
On Mon, Jan 19, 2015 at 09:26:41AM +, Wookey wrote:
Can someone remind me what the current rules are (or where it's
written down). I know it doesn't work the way I expect it ought to, but
I forget/never-understood exactly how it does work.
Do maintainers always get the initial mail to a
On Mon, Jan 19, 2015 at 5:03 PM, Tomas Pospisek wrote:
But isn't subscribing participants natural? Posting to a bug report
means participation and thus you'd get the follow-ups. Why would you
post to a bug report if you aren't interested in what happens with it,
how things proceed/evolve?
It
On Mon, 2015-01-19 at 10:03 +0100, Tomas Pospisek wrote:
Am 19.01.2015 um 02:03 schrieb Ben Hutchings:
No, this would turn the BTS into a (worse) spam vector.
But the acknowledgement mail should tell you how to subscribe, if you
aren't already subscribed.
But isn't subscribing
On Mon, Jan 19, 2015 at 11:26 AM, Wookey woo...@wookware.org wrote:
+++ Paul Wise [2015-01-19 17:14 +0800]:
On Mon, Jan 19, 2015 at 5:03 PM, Tomas Pospisek wrote:
I can understand your point of view and I think also the why but isn't
that position the exception from the rule? That is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 19 Jan 2015 10:16:13 +0100
Source: inkscape
Binary: inkscape
Architecture: source amd64
Version: 0.91~pre4-1
Distribution: experimental
Urgency: medium
Maintainer: Wolfram Quester wo...@sigxcpu.org
Changed-By: Matteo F.
On 2015-01-19 11:31, Wookey wrote:
I recall looking at that list for the 'maintainer and submitter'
option, and being disappointed not to find one. Am I right that the
only way to expliticly mail the submitter and the maintainer is to
look the submitter's mail up in the initial bugrep and just
Am 19.01.2015 um 02:03 schrieb Ben Hutchings:
On Mon, 2015-01-19 at 08:37 +0800, Paul Wise wrote:
On Mon, Jan 19, 2015 at 8:06 AM, Don Armstrong wrote:
I'm going to put together a bit more firm of a proposal in the next few
weeks, but I think that basically everything but nnn-done@ and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 19 Jan 2015 09:58:16 +0100
Source: tomcat8
Binary: tomcat8-common tomcat8 tomcat8-user libtomcat8-java libservlet3.1-java
libservlet3.1-java-doc tomcat8-admin tomcat8-examples tomcat8-docs
Architecture: source all
Version:
Hi,
Am Montag, den 19.01.2015, 19:41 +1000 schrieb Russell Stuart:
Debian's bug submission mechanism does not try to verify you control the
email address you are submitting from.
At least trac allows you to put other people’s email address in the CC
header, at least in some configurations.
On 2015-01-19 10:47, Mattia Rizzolo wrote:
On Mon, Jan 19, 2015 at 09:26:41AM +, Wookey wrote:
Can someone remind me what the current rules are (or where it's
written down). I know it doesn't work the way I expect it ought to,
but
I forget/never-understood exactly how it does work.
Do
Tomas Pospisek t...@sourcepole.ch writes:
But isn't subscribing participants natural? Posting to a bug report
means participation and thus you'd get the follow-ups. Why would you
post to a bug report if you aren't interested in what happens with it,
how things proceed/evolve?
Most other bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 20 Jan 2015 00:29:25 +0800
Source: picolisp
Binary: picolisp
Architecture: source amd64
Version: 3.1.9.3-1
Distribution: unstable
Urgency: medium
Maintainer: Kan-Ru Chen (陳侃如) kos...@debian.org
Changed-By: Kan-Ru Chen (陳侃如)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 17 Jan 2015 19:51:55 +0100
Source: lirc
Binary: lirc lirc-x liblircclient-dev liblircclient0
Architecture: source
Version: 0.9.0~pre1-1.2
Distribution: unstable
Urgency: medium
Maintainer: lirc Maintainer Team
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 17 Jan 2015 20:28:43 +0100
Source: xine-ui
Binary: xine-ui xine-console xine-dbg
Architecture: source
Version: 0.99.9-1.2
Distribution: unstable
Urgency: medium
Maintainer: Darren Salt devs...@moreofthesa.me.uk
Changed-By:
Package: wnpp
Severity: wishlist
Owner: Ruben Undheim ruben.undh...@gmail.com
* Package name: pyvisa-py
Version : 0.1~20150106gitd86fb71
Upstream Author : Hernan E. Grecco
* URL : https://github.com/hgrecco/pyvisa-py
* License : MIT
Programming Lang: Python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 19 Jan 2015 19:32:00 +0100
Source: manaplus
Binary: manaplus manaplus-dbg manaplus-data
Architecture: source amd64 all
Version: 1.5.1.17-1
Distribution: unstable
Urgency: low
Maintainer: Andrei Karas aka...@inbox.ru
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 04 Jan 2015 07:28:35 -0600
Source: python-ipcalc
Binary: python-ipcalc
Architecture: source all
Version: 1.1.3-1
Distribution: experimental
Urgency: medium
Maintainer: Florian Pelgrim florian.pelg...@craneworks.de
Changed-By:
On 19 January 2015 at 08:25, Mathieu Malaterre ma...@debian.org wrote:
Steven,
Hi Mathieu,
While being in terrible position to tell you what you should or should
not do, I'd still suggest you to read:
https://www.debian.org/code_of_conduct
https://people.debian.org/~enrico/dcg/
Thanks,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 19 Jan 2015 19:22:59 +0100
Source: geoip
Binary: libgeoip1 libgeoip-dev geoip-bin geoip-dbg
Architecture: source amd64
Version: 1.6.4-1
Distribution: experimental
Urgency: low
Maintainer: Patrick Matthäi pmatth...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 19 Jan 2015 19:14:15 +0100
Source: apt-dater
Binary: apt-dater apt-dater-dbg
Architecture: source amd64
Version: 1.0.1+git20150119-1
Distribution: unstable
Urgency: low
Maintainer: Patrick Matthäi pmatth...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 19 Jan 2015 20:38:08 +0100
Source: doxygen
Binary: doxygen doxygen-latex doxygen-doc doxygen-gui doxygen-dbg
Architecture: source amd64 all
Version: 1.8.9.1-1
Distribution: experimental
Urgency: medium
Maintainer: Matthias
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 19 Jan 2015 21:07:18 +0100
Source: python-astropy
Binary: python-astropy python3-astropy python-astropy-doc
Architecture: source amd64 all
Version: 0.4.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Mon, 19 Jan 2015 18:00:58 -0200
Source: ruby-mini-exiftool
Binary: ruby-mini-exiftool
Architecture: source all
Version: 2.5.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers
On Mon, Jan 19, 2015 at 02:39:47PM +0100, Markus Koschany wrote:
* Package name: caveexpress
* URL : http://www.caveproductions.org
Description : 2D platformer with physic-based gameplay
CaveExpress is a classic 2D platformer with physics-based gameplay and
dozens of
On Mon, 19. Jan 21:24 Adam Borowski kilob...@angband.pl wrote:
You mean, Ugh? :p
Yes, that's the remake of Ugh, a great C-64/Amiga game but adapted to
modern hardware. :-) It also provides a HTML5 flavour, AFAIK the first
one of its kind in Debian.
signature.asc
Description: Digital signature
73 matches
Mail list logo
