Bug#695806: marked as done (RM: balazar/0.3.4.ds1-6.1)
Your message dated Wed, 12 Dec 2012 20:58:37 +0000
with message-id <1355345917.13966.30.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#695806: RM: balazar/0.3.4.ds1-6.1
has caused the Debian Bug report #695806,
regarding RM: balazar/0.3.4.ds1-6.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
695806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695806
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: rm
Hi,
please remove balazar from wheezy. It is a game and the RC bug #692753 was not
fixed for a month now. There is also the important bug #630946 that causes
the game to crash unless sound is deactivated. The last upload of the package
by the maintainer was in 2009. The consensus in #692753 was that removal of
the package is the best way to resolve the bug.
Best regards,
Tobias Hansen
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
On Wed, 2012-12-12 at 21:50 +0100, Tobias Hansen wrote:
> please remove balazar from wheezy. It is a game and the RC bug #692753 was not
> fixed for a month now. There is also the important bug #630946 that causes
> the game to crash unless sound is deactivated. The last upload of the package
> by the maintainer was in 2009. The consensus in #692753 was that removal of
> the package is the best way to resolve the bug.
Removal hint added.
Regards,
Adam
--- End Message ---
Reply to: