Processed: xcruise: adding tags

Processing commands for [EMAIL PROTECTED]: > tags 213654 pending Bug#213654: xcruise: cannot steer up and down There were no tags set. Tags added: pending > tags 215865 pending Bug#215865: xcruise: Nothing happens There were no tags set. Tags added: pending > tags 215132 pending Bug#215132: xcru

Bug#243539: libparagui1.0: asc tries to link to libparagui.so. should that be a symlink?

Package: libparagui1.0 Version: 1.0.2-6 Severity: minor I get the following error trying to compile CVS asc (from http://www.asc-hq.org/download_linux.html) g++ -I/usr/include/SDL -D_REENTRANT -I/usr/include/SDLmm -Dkarteneditor -DNEWKEYB -I/usr/include/paragui -I/usr/include/freetype2 -I/usr/in

Bug#243017: marked as done (FTBFS: (unstable/all) build-depends conflict)

Your message dated Tue, 13 Apr 2004 12:32:04 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#243017: fixed in libapache-mod-fastcgi 2.4.0-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

libapache-mod-fastcgi_2.4.0-4_i386.changes ACCEPTED

Accepted: libapache-mod-fastcgi_2.4.0-4.diff.gz to pool/non-free/liba/libapache-mod-fastcgi/libapache-mod-fastcgi_2.4.0-4.diff.gz libapache-mod-fastcgi_2.4.0-4.dsc to pool/non-free/liba/libapache-mod-fastcgi/libapache-mod-fastcgi_2.4.0-4.dsc libapache-mod-fastcgi_2.4.0-4_i386.deb to pool/n

Processing of libapache-mod-fastcgi_2.4.0-4_i386.changes

libapache-mod-fastcgi_2.4.0-4_i386.changes uploaded successfully to localhost along with the files: libapache-mod-fastcgi_2.4.0-4.dsc libapache-mod-fastcgi_2.4.0-4.diff.gz libapache-mod-fastcgi_2.4.0-4_i386.deb Greetings, Your Debian queue daemon

Bug#223157: marked as done (hwtools: FTBFS: Undefined references)

Your message dated Tue, 13 Apr 2004 16:29:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Already fixed in hwtools has caused the attached Bug report 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 responsib

Bug#210899: marked as done (hwtools must depend on debconf)

Your message dated Tue, 13 Apr 2004 16:29:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Already fixed in hwtools has caused the attached Bug report 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 responsib

Bug#200113: marked as done (hwtools: Please switch to gettext-based debconf templates)

Your message dated Tue, 13 Apr 2004 16:29:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Already fixed in hwtools has caused the attached Bug report 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 responsib

Bug#198513: marked as done (debconf abuse)

Your message dated Tue, 13 Apr 2004 16:29:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Already fixed in hwtools has caused the attached Bug report 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 responsib

Bug#126052: marked as done (german template file [hwtools 0.7-1])

Your message dated Tue, 13 Apr 2004 16:29:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Already fixed in hwtools has caused the attached Bug report 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 responsib

Bug#104299: marked as done (Ugly message in debconf)

Your message dated Tue, 13 Apr 2004 16:29:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Already fixed in hwtools has caused the attached Bug report 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 responsib

Bug#101687: marked as done (hwtools: can't build from source; non-pristine source contains binaries)

Your message dated Tue, 13 Apr 2004 16:29:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Already fixed in hwtools has caused the attached Bug report 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 responsib

Bug#137662: marked as done (russian debconf template file for hwtools package)

Your message dated Tue, 13 Apr 2004 16:29:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Already fixed in hwtools has caused the attached Bug report 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 responsib

Bug#175190: marked as done (hwtools: Danish template translation)

Your message dated Tue, 13 Apr 2004 16:29:51 +0200 with message-id <[EMAIL PROTECTED]> and subject line Already fixed in hwtools has caused the attached Bug report 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 responsib

Processed: Syntax error in postinst

Processing commands for [EMAIL PROTECTED]: > tag 243230 patch Bug#243230: x-ttcidfont-conf: Syntax error in postinst Tags were: sid Bug#243223: postinst: test for symlink is -L or -h, not -l Bug#243398: /var/lib/dpkg/info/x-ttcidfont-conf.postinst: line 14: [: -l: unary operator expected Tags add

Processed: your mail

Processing commands for [EMAIL PROTECTED]: > merge 243398 243230 Bug#243230: x-ttcidfont-conf: Syntax error in postinst Bug#243398: /var/lib/dpkg/info/x-ttcidfont-conf.postinst: line 14: [: -l: unary operator expected Bug#243223: postinst: test for symlink is -L or -h, not -l Merged 243223 243230

Bug#243230: Syntax error in postinst

tag 243230 patch quit Hi, I propose "-h" instead of the alternative "-L" as substitution for "-l" since that's what's officially supported by dash. (Otherwise, you could do "#!/bin/bash" instead of "#!/bin/sh", but I wouldn't prefer that.) bye, Roland