Bug#339992: marked as done (sysvinit: shutdown ignores "-a" option)

Your message dated Sun, 20 Nov 2005 01:29:15 -0500 (EST) with message-id <[EMAIL PROTECTED]> and subject line 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 responsibility to reopen th

Bug#339991: marked as done (quodlibet: Fails to start with ValueError: invalid literal for float(): 1.0)

Your message dated Sat, 19 Nov 2005 23:42:52 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#339991: quodlibet: Fails to start with ValueError: invalid literal for float(): 1.0 has caused the attached Bug report to be marked as done. This means that you claim that the problem has b

Bug#339932: marked as done (gnucash: Impossible to install)

Your message dated Sat, 19 Nov 2005 21:06:42 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339932: gnucash: Impossible to install 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

Bug#338753: marked as done (asterisk_1:1.2.0-rc1.dfsg-1(sparc/experimental): FTBFS: invalid option 'arch=sparc')

Your message dated Sat, 19 Nov 2005 20:17:06 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#338753: fixed in asterisk 1:1.2.0.dfsg-3 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 i

Bug#312945: marked as done (gnupg-doc: installs mini-howto in multiple languages)

Your message dated Sun, 20 Nov 2005 04:17:24 + with message-id <[EMAIL PROTECTED]> and subject line gnupg-doc: installs mini-howto in multiple languages 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 c

Bug#339766: marked as done (asterisk - FTBFS: build-depends against not longer built package)

Your message dated Sun, 20 Nov 2005 05:02:52 +0100 with message-id <[EMAIL PROTECTED]> and subject line fixed in 1.2.0.dfsg-2 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 responsibili

Bug#335033: marked as done ([CAN-2005-3120] buffer overflow in nntp schema handling)

Your message dated Sun, 20 Nov 2005 03:40:19 + with message-id <[EMAIL PROTECTED]> and subject line [CAN-2005-3120] buffer overflow in nntp schema handling 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 th

Bug#329341: marked as done (sbackup: Clicking Test (for a remote location) fails with error to console)

Your message dated Sat, 19 Nov 2005 19:17:06 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#329341: fixed in sbackup 0.9-1 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

Bug#339853: marked as done (/usr/sbin/chronyd is missing)

Your message dated Sat, 19 Nov 2005 19:02:04 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339853: fixed in chrony 1.21-2 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

Bug#339764: marked as done (chrony - FTBFS: #error "I don't know the values of the _IOC_* constants for your architecture")

Your message dated Sat, 19 Nov 2005 19:02:04 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339764: fixed in chrony 1.21-2 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

Bug#336602: marked as done (gksu: fails when wheel group trusted in /etc/pam.d/su)

Your message dated Sun, 20 Nov 2005 00:42:29 -0200 with message-id <[EMAIL PROTECTED]> and subject line was fixed in libgksu1.2 1.3.6 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 resp

Bug#339739: marked as done (dbskkd-cdb cannot work correctly on 64bit system)

Your message dated Sat, 19 Nov 2005 18:32:06 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339739: fixed in dbskkd-cdb 1:1.01-14 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 n

Bug#339977: marked as done (gftp: Segfault while trying to get any file (2))

Your message dated Sat, 19 Nov 2005 18:17:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339977: fixed in gftp 2.0.18-11 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 you

Bug#339962: marked as done (gftp-common has circular Depends on gftp-gtk|gtk-text)

Your message dated Sat, 19 Nov 2005 18:17:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339962: fixed in gftp 2.0.18-11 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 you

Bug#326782: marked as done (gftp: Typo in 'New Item' dialog in edit bookmarks window)

Your message dated Sat, 19 Nov 2005 18:17:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#326782: fixed in gftp 2.0.18-11 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 you

Bug#336112: marked as done ([mips/mipsel] FTBFS due to missing arch-specific implementation)

Your message dated Sat, 19 Nov 2005 17:32:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#338442: fixed in libatomic-ops 1.1-1 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 no

Bug#338442: marked as done (libatomic-ops_1.0-3_mipsel: FTBFS: syntax error before 'AO_locks')

Your message dated Sat, 19 Nov 2005 17:32:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#338442: fixed in libatomic-ops 1.1-1 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 no

Bug#338442: marked as done (libatomic-ops_1.0-3_mipsel: FTBFS: syntax error before 'AO_locks')

Your message dated Sat, 19 Nov 2005 17:32:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#336112: fixed in libatomic-ops 1.1-1 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 no

Bug#336112: marked as done ([mips/mipsel] FTBFS due to missing arch-specific implementation)

Your message dated Sat, 19 Nov 2005 17:32:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#336112: fixed in libatomic-ops 1.1-1 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 no

Bug#332488: marked as done (john: sometimes leaves temporary file in postinst)

Your message dated Sat, 19 Nov 2005 17:02:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#332488: fixed in john 1.6-38 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 r

Bug#334883: marked as done (john: [INTL:sv] Swedish debconf templates translation)

Your message dated Sat, 19 Nov 2005 17:02:09 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#334883: fixed in john 1.6-38 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 r

Bug#334588: marked as done (perlmagick: hangs and uses all cpu time)

Your message dated Sun, 20 Nov 2005 02:14:12 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#334588: no bug 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 responsibility

Bug#338434: marked as done (sylpheed: Buffer overflow in LDIF import)

Your message dated Sat, 19 Nov 2005 16:02:22 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#338434: fixed in sylpheed-gtk1 1.0.6-1 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

Bug#324667: marked as done (sylpheed-claws-gtk2: can't display messages with attachments)

Your message dated Sat, 19 Nov 2005 16:02:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#324667: fixed in sylpheed-claws-gtk2 1.9.100-1 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

Bug#329196: marked as done (sylpheed-claws-gtk2: IMAP + TLS problem: connection breaks, possible mail loss)

Your message dated Sat, 19 Nov 2005 16:02:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#329196: fixed in sylpheed-claws-gtk2 1.9.100-1 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

Bug#336163: marked as done (sylpheed-claws-gtk2 should depend on metamail)

Your message dated Sat, 19 Nov 2005 16:02:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#336163: fixed in sylpheed-claws-gtk2 1.9.100-1 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

Bug#329040: marked as done (sylpheed-claws-gtk2: Segfault when I use LC_ALL=pt_BR and I try to click on view option menu.)

Your message dated Sat, 19 Nov 2005 16:02:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#329040: fixed in sylpheed-claws-gtk2 1.9.100-1 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

Bug#325082: marked as done (sylpheed-claws-gtk2: Seg fault while reading IMAP folder)

Your message dated Sat, 19 Nov 2005 16:02:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#325082: fixed in sylpheed-claws-gtk2 1.9.100-1 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

Bug#339054: marked as done (ant-phone: [INTL:sv] Swedish PO-template translation)

Your message dated Sat, 19 Nov 2005 15:32:24 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339054: fixed in ant-phone 0.1.11-1 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

Bug#298369: marked as done (O: styx -- combined parser/scanner generator)

Your message dated Sat, 19 Nov 2005 15:32:30 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#298369: fixed in styx 1.7-1 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 re

Bug#209033: marked as done (Feature request: "native" put-popups-into-tabs feature)

Your message dated Sat, 19 Nov 2005 15:25:59 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#209033: Fixed in Experimental version (RC1 of new Firefox) 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

Bug#339767: marked as done (rox - FTBFS: missing build dependency)

Your message dated Sat, 19 Nov 2005 14:02:55 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339767: fixed in rox 2.3-2 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 res

Bug#339889: marked as done (sng: FTBFS: png api change)

Your message dated Sat, 19 Nov 2005 14:02:59 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339889: fixed in sng 1.0.2-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 case it is now your r

Bug#332385: marked as done (esmtp: [INTL:sv] Swedish debconf templates translation)

Your message dated Sat, 19 Nov 2005 14:02:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#332385: fixed in esmtp 0.5.1-3 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

Bug#333893: marked as done (fails with multiple .sng files on the command line)

Your message dated Sat, 19 Nov 2005 14:02:59 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#333893: fixed in sng 1.0.2-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 case it is now your r

Bug#323946: marked as done (INTL:vi Vietnamese translation for esmtp)

Your message dated Sat, 19 Nov 2005 14:02:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#323946: fixed in esmtp 0.5.1-3 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

Bug#323947: marked as done (esmtp)

Your message dated Sat, 19 Nov 2005 14:02:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#323947: fixed in esmtp 0.5.1-3 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

Bug#320675: marked as done (esmtp: Some man page typo corrections)

Your message dated Sat, 19 Nov 2005 14:02:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#320675: fixed in esmtp 0.5.1-3 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

Bug#319939: marked as done ([l10n] Czech translation for esmtp)

Your message dated Sat, 19 Nov 2005 14:02:23 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#319939: fixed in esmtp 0.5.1-3 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

Bug#329686: marked as done (libkrb53: linker error on powerpc makes depending packages FTBFS)

Your message dated Sat, 19 Nov 2005 13:21:12 -0800 with message-id <[EMAIL PROTECTED]> and subject line libkrb53 is working fine now 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 respo

Bug#326073: marked as done (sylpheed: causes corruption of non-ASCII messages after "edit with external editor")

Your message dated Sat, 19 Nov 2005 21:32:31 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#326073: sylpheed: causes corruption of non-ASCII messages after "edit with external editor" has caused the attached Bug report to be marked as done. This means that you claim that the probl

Bug#339933: marked as done (signing-party: [caff] problem with a mailserver (but Gnus and Mozilla work))

Your message dated Sat, 19 Nov 2005 21:18:12 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#339933: signing-party: [caff] problem with a mailserver (but Gnus and Mozilla work) has caused the attached Bug report to be marked as done. This means that you claim that the problem has b

Processed: Should be marked as fixed in testing/unstable

Processing commands for [EMAIL PROTECTED]: > close 320017 1:6.3-085+1 Bug#320017: vim: Arbitrary code execution in modelines (CAN-2005-2368) 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1:6.3-085+1, send any further explanations to Martin

Bug#337395: marked as done (libgtk-trayicon-ruby: FTBFS: Tries to install outside build directory)

Your message dated Sat, 19 Nov 2005 12:23:37 -0600 with message-id <[EMAIL PROTECTED]> and subject line Not reproducible 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 responsibility to

Bug#337393: marked as done (libgtk-mozembed-ruby: FTBFS: Tries to install outside build directory)

Your message dated Sat, 19 Nov 2005 12:22:18 -0600 with message-id <[EMAIL PROTECTED]> and subject line Not reproducible 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 responsibility to

Bug#332437: marked as done (docbook-to-man: incorrect behaviour in error reporting (does not work with zsh))

Your message dated Sat, 19 Nov 2005 10:02:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#332437: fixed in docbook-to-man 1:2.0.0-20 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

Bug#331878: marked as done (kinput2 depends on debconf without | debconf-2.0 alternate; blocks cdebconf transition)

Your message dated Sat, 19 Nov 2005 10:02:17 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#331878: fixed in kinput2 3.1-6 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

Bug#331544: marked as done (kinput2: [INTL:sv] Swedish debconf templates translation)

Your message dated Sat, 19 Nov 2005 10:02:17 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#331544: fixed in kinput2 3.1-6 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

Bug#318151: marked as done ([l10n] Czech translation for kinput2)

Your message dated Sat, 19 Nov 2005 10:02:17 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#318151: fixed in kinput2 3.1-6 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

Bug#337283: marked as done (upgrade breaks trac access.)

Your message dated Sat, 19 Nov 2005 15:52:12 -0200 with message-id <[EMAIL PROTECTED]> and subject line Isn't a bug but a UPGRADE issue that's documented 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

Bug#339701: marked as done (gqcam: Crashes while trying to save preferences)

Your message dated Sat, 19 Nov 2005 09:32:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339701: fixed in gqcam 0.9.1-2 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

Processed: closing 333334

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.8 > close 34 Bug#34: Thanks for your work :) 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Christoph Berg <[

Bug#339506: marked as done (psnup: Does not use /etc/papersize)

Your message dated Sat, 19 Nov 2005 09:17:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339506: fixed in psutils 1.17-21 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 yo

Bug#337740: marked as done (libwnn6-1: Missing conflicts with libwnn6)

Your message dated Sat, 19 Nov 2005 09:17:12 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#337740: fixed in wnn6-sdk 1.0.0-13 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

Bug#259894: marked as done (wnn6-sdk: FTBFS with gcc-3.4: conflicting types for 'malloc')

Your message dated Sat, 19 Nov 2005 09:17:12 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#259894: fixed in wnn6-sdk 1.0.0-13 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

Bug#339901: marked as done (pachi-data has circular Depends on pachi)

Your message dated Sat, 19 Nov 2005 09:02:13 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339901: fixed in pachi 1:1.0-3 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

Processed: closing 334258

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.8 > # not really a bug > close 334258 Bug#334258: testing: kdelibs4-dev outdated, depends on old kdelibs4 versions, both install *and* downgrade impossible 'close' is deprecated; see htt

Bug#336178: marked as done (bcm5700-source: Compile fails for kernel 2.6.14 (struct pci_dev slot_name))

Your message dated Sat, 19 Nov 2005 08:32:06 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#336178: fixed in bcm5700-source 8.2.18-1 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 i

Bug#312399: marked as done (kdessh should depend on openssh-client rather than ssh)

Your message dated Sat, 19 Nov 2005 17:27:54 +0100 with message-id <[EMAIL PROTECTED]> and subject line kdessh already depends on openssh-client 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 no

Bug#279194: marked as done (kregexpeditor)

Your message dated Sat, 19 Nov 2005 17:20:12 +0100 with message-id <[EMAIL PROTECTED]> and subject line libkregexpeditor not available in stable 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 no

Bug#325079: marked as done (quanta: New upstream version)

Your message dated Sat, 19 Nov 2005 17:05:53 +0100 with message-id <[EMAIL PROTECTED]> and subject line New version 3.4.2 is already in the archive :-) 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 i

Processed: closing 246976

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.8 > # bogus report > close 246976 Bug#246976: broken Package: 'kwalletmanager' 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explan

Bug#326459: marked as done (uninstallable in SID, broken dependency)

Your message dated Sat, 19 Nov 2005 16:56:49 +0100 with message-id <[EMAIL PROTECTED]> and subject line kdewebdev is installable in sid now 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 you

Bug#338842: marked as done ([l10n] Initial Czech translation of ltsp debconf messages)

Your message dated Sat, 19 Nov 2005 07:02:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#338842: fixed in ltsp 0.58debian4 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 y

Bug#337044: marked as done (ltsp: French debconf templates translation)

Your message dated Sat, 19 Nov 2005 07:02:05 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#337044: fixed in ltsp 0.58debian4 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 y

Bug#339891: marked as done (evms: corrupts RAID-5 volumes when running in degraded mode)

Your message dated Sat, 19 Nov 2005 16:04:25 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#339891: evms: corrupts RAID-5 volumes when running in degraded mode has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#339351: marked as done (initscripts: "Usage" error message from checkroot.sh displays during bootup)

Your message dated Sat, 19 Nov 2005 06:32:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339351: fixed in sysvinit 2.86.ds1-6 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 no

Bug#339883: marked as done (dbconfig-common: dbconfig-generate-include with template file gives an error.)

Your message dated Sat, 19 Nov 2005 15:48:03 +0100 with message-id <[EMAIL PROTECTED]> and subject line dbconfig-common: dbconfig-generate-include with template file gives an error. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt

Bug#339856: marked as done (gmodels: FTBFS: there is no package called 'gtools')

Your message dated Sat, 19 Nov 2005 06:47:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339856: fixed in gmodels 2.10.0-2 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 y

Bug#338966: marked as done (initscripts: "Usage" error message from checkroot.sh displays during bootup)

Your message dated Sat, 19 Nov 2005 06:32:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#338966: fixed in sysvinit 2.86.ds1-6 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 no

Bug#338966: marked as done (initscripts: "Usage" error message from checkroot.sh displays during bootup)

Your message dated Sat, 19 Nov 2005 06:32:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339351: fixed in sysvinit 2.86.ds1-6 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 no

Bug#338967: marked as done (Please use new lsb log_action_* functions)

Your message dated Sat, 19 Nov 2005 06:32:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#338967: fixed in sysvinit 2.86.ds1-6 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 no

Bug#339351: marked as done (initscripts: "Usage" error message from checkroot.sh displays during bootup)

Your message dated Sat, 19 Nov 2005 06:32:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#338966: fixed in sysvinit 2.86.ds1-6 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 no

Bug#335049: marked as done (konqueror: crash when typing into the location bar)

Your message dated Sat, 19 Nov 2005 15:45:58 +0100 with message-id <[EMAIL PROTECTED]> and subject line Works after upgrade 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 responsibility

Bug#326678: marked as done (sulogin: Handle locket root account gracefully)

Your message dated Sat, 19 Nov 2005 06:32:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#326678: fixed in sysvinit 2.86.ds1-6 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 no

Bug#145542: marked as done (gtkpool: Floating point exception on Alpha)

Your message dated Sat, 19 Nov 2005 15:20:34 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#145542: gtkpool: Floating point exception on Alpha 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

Bug#325177: marked as done (jwhois: -f option causes segfault)

Your message dated Sat, 19 Nov 2005 04:47:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#325177: fixed in jwhois 3.2.3-3 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 you

Bug#337182: marked as done ('man jwhois' typo: "protocoll")

Your message dated Sat, 19 Nov 2005 04:47:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#337182: fixed in jwhois 3.2.3-3 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 you

Bug#336512: marked as done (AFRINIC: 62.114.0.0/16)

Your message dated Sat, 19 Nov 2005 04:47:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#336512: fixed in jwhois 3.2.3-3 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 you

Bug#339409: marked as done (typo in lib64z1-dev dependency)

Your message dated Sat, 19 Nov 2005 13:02:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#339409: typo in lib64z1-dev dependency 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

Bug#334543: marked as done (ITA: jwhois -- Improved Caching Whois client)

Your message dated Sat, 19 Nov 2005 04:47:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#334543: fixed in jwhois 3.2.3-3 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 you

Bug#331317: marked as done (KRNIC: 58.140.0.0/14)

Your message dated Sat, 19 Nov 2005 04:47:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#331317: fixed in jwhois 3.2.3-3 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 you

Bug#331316: marked as done (AFRINIC: 80.248.64.0/20)

Your message dated Sat, 19 Nov 2005 04:47:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#331316: fixed in jwhois 3.2.3-3 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 you

Bug#295374: marked as done (ddpo: watch/uscan is not running and/or doesn't show results)

Your message dated Sat, 19 Nov 2005 14:01:54 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#295374: packages.qa.debian.org: watch/uscan is not running and/or doesn't show results has caused the attached Bug report to be marked as done. This means that you claim that the problem ha

Bug#264150: marked as done (ddpo: saving vertical space)

Your message dated Sat, 19 Nov 2005 13:57:50 +0100 with message-id <[EMAIL PROTECTED]> and subject line ddpo: saving vertical space 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 respon

Processed: oops

Processing commands for [EMAIL PROTECTED]: > close 339662 3.0a-1 Bug#339662: loop-aes-source: loop-aes does not build with kernel 2.6.14 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 3.0a-1, send any further explanations to Evgeni Golov <[

Bug#338546: marked as done (dillo: displays many characters in Japanese (or Chinese maybe) with fr_FR.UTF-8 locale)

Your message dated Sat, 19 Nov 2005 04:32:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#338546: fixed in dillo 0.8.5-3 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

Bug#304563: marked as done (dillo: babbles heavily when started from command line)

Your message dated Sat, 19 Nov 2005 04:32:08 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#304563: fixed in dillo 0.8.5-3 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

Bug#298640: marked as done (dillo: Can't read Chinese)

Your message dated Sat, 19 Nov 2005 04:32:07 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#298640: fixed in dillo 0.8.5-3 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

Bug#298639: marked as done (dillo: mention http_proxy default)

Your message dated Sat, 19 Nov 2005 04:32:07 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#298639: fixed in dillo 0.8.5-3 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

Bug#298638: marked as done (dillo: debugging on by default)

Your message dated Sat, 19 Nov 2005 04:32:07 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#298638: fixed in dillo 0.8.5-3 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

Bug#334903: marked as done (dillo: Program is not listed in /etc/alternatives/www-browser)

Your message dated Sat, 19 Nov 2005 04:32:07 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#223586: fixed in dillo 0.8.5-3 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

Bug#223586: marked as done (dillo: should be an alternative)

Your message dated Sat, 19 Nov 2005 04:32:07 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#223586: fixed in dillo 0.8.5-3 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

Bug#195292: marked as done (Package mysql-dfsg is shown as not present in stable/security although.)

Your message dated Sat, 19 Nov 2005 13:27:58 +0100 with message-id <[EMAIL PROTECTED]> and subject line Package mysql-dfsg is shown as not present in stable/security although. has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#227531: marked as done (inn2: please consider adding Colin Watson's po-debconf backporting helper patch)

Your message dated Sat, 19 Nov 2005 13:23:12 +0100 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#227531: inn2: please consider adding Colin Watson's po-debconf backporting helper patch has caused the attached Bug report to be marked as done. This means that you claim that the prob

Bug#326728: marked as done (Please list my current NMU packages as well on my package list)

Your message dated Sat, 19 Nov 2005 12:09:30 +0100 with message-id <[EMAIL PROTECTED]> and subject line qa.debian.org: list sponsored packages in developer.php 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 th

Bug#288241: marked as done (qa.debian.org: allow subscription to a key id)

Your message dated Sat, 19 Nov 2005 12:09:30 +0100 with message-id <[EMAIL PROTECTED]> and subject line qa.debian.org: list sponsored packages in developer.php 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 th

Bug#288239: marked as done (qa.debian.org: list sponsored packages in developer.php)

Your message dated Sat, 19 Nov 2005 12:09:30 +0100 with message-id <[EMAIL PROTECTED]> and subject line qa.debian.org: list sponsored packages in developer.php 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 th

Bug#339779: marked as done (qpsmtpd: 0.31 is incomplete, replaced by 0.31.1)

Your message dated Sat, 19 Nov 2005 02:47:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#339779: fixed in qpsmtpd 0.31.1-1 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 y

Bug#338085: marked as done (postgresql-8.0: Does not start with tcpip when post is not 5432)

Your message dated Sat, 19 Nov 2005 11:47:25 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#338085: postgresql-8.0: Does not start with tcpip when post is not 5432 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wi

  1   2   >