Bug#249352: marked as done (xchat: cannot connect with SSL enabled)

Your message dated Tue, 19 Jul 2005 12:45:43 +0800 with message-id <[EMAIL PROTECTED]> and subject line debian xchat bug 249352 "cannot connect with SSL enabled" is not a bug has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#282999: marked as done (animate: cine-DICOM does not work due to JPEG processing problem)

Your message dated Mon, 18 Jul 2005 23:47:11 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#282999: fixed in imagemagick 6:6.2.3.4-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#272121: marked as done (Could add .ico rule to /usr/lib/mime/packages/imagemagick)

Your message dated Mon, 18 Jul 2005 23:47:11 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#272121: fixed in imagemagick 6:6.2.3.4-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#263475: marked as done (ImageMagick.1.gz: -ping not documented well)

Your message dated Mon, 18 Jul 2005 23:47:11 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#263475: fixed in imagemagick 6:6.2.3.4-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#296753: marked as done (splay does not interpret the options correctly any more)

Your message dated Mon, 18 Jul 2005 23:47:12 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#296753: fixed in imagemagick 6:6.2.3.4-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#316473: marked as done (convert: -trim -monochrome used together made empty image)

Your message dated Mon, 18 Jul 2005 23:47:12 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#316473: fixed in imagemagick 6:6.2.3.4-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#226385: marked as done (procps doesn't handle Kernel 2.4.24 properly)

Your message dated Tue, 19 Jul 2005 12:31:10 +1000 with message-id <[EMAIL PROTECTED]> and subject line Fixed in procps 3.1.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 your responsibil

Bug#111585: marked as done (skill mis-parses command-line arguments)

Your message dated Tue, 19 Jul 2005 12:41:14 +1000 with message-id <[EMAIL PROTECTED]> and subject line Fixed in procps 3.0.3-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 responsibi

Bug#309352: marked as done (Unknown HZ value! printed output from uptime)

Your message dated Tue, 19 Jul 2005 12:32:42 +1000 with message-id <[EMAIL PROTECTED]> and subject line 3.x procps fixes this 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#279407: marked as done (Conflicting versions: kernel-image 2.6.8-1, procps 2.0.7-8.woody1)

Your message dated Tue, 19 Jul 2005 12:24:55 +1000 with message-id <[EMAIL PROTECTED]> and subject line Fixed in procps 3.2.0 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#200659: marked as done (ps error messages)

Your message dated Tue, 19 Jul 2005 12:28:44 +1000 with message-id <[EMAIL PROTECTED]> and subject line Closing bug, solution is worse than problem 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#298379: marked as done (lprng: memory leak back)

Your message dated Tue, 19 Jul 2005 12:14:15 +1000 with message-id <[EMAIL PROTECTED]> and subject line Bug#298379: lprng: memory leak back 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#218177: marked as done (small documentation error in uptime program.)

Your message dated Tue, 19 Jul 2005 12:20:27 +1000 with message-id <[EMAIL PROTECTED]> and subject line Fixed in procps 3.0.0-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 responsibi

Bug#142361: marked as done (messages are not removed from print queue)

Your message dated Tue, 19 Jul 2005 12:01:08 +1000 with message-id <[EMAIL PROTECTED]> and subject line Fixed in lprng 3.8.20-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 responsibi

Bug#136012: marked as done (lprng: /etc/cron.daily/lprng should run silently)

Your message dated Tue, 19 Jul 2005 12:01:08 +1000 with message-id <[EMAIL PROTECTED]> and subject line Fixed in lprng 3.8.20-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 responsibi

Bug#318767: marked as done (O: lockvc -- Screensaver to lock your Linux console(s))

Your message dated Mon, 18 Jul 2005 22:02:38 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318767: fixed in lockvc 4.0.5-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 you

Bug#210673: marked as done (procps utils cannot determine HZ value)

Your message dated Tue, 19 Jul 2005 12:11:00 +1000 with message-id <[EMAIL PROTECTED]> and subject line Version 3 of procps fixes this 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

Bug#317738: marked as done (libccscript: FTBFS: missing b-dep on doxygen)

Your message dated Mon, 18 Jul 2005 22:02:11 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#317738: fixed in libccscript 2.5.7-5 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#317874: marked as done (libccscript: FTBFS with gcc-3.4/gcc-4.0: ost::ScriptCommand::chkHasArgs is protected)

Your message dated Mon, 18 Jul 2005 22:02:12 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#317874: fixed in libccscript 2.5.7-5 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#168158: marked as done ([lprng] serious queueing problem)

Your message dated Tue, 19 Jul 2005 12:01:08 +1000 with message-id <[EMAIL PROTECTED]> and subject line Fixed in lprng 3.8.20-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 responsibi

Bug#159632: marked as done (lprng 3.8.15-1 is causing flaky printing)

Your message dated Tue, 19 Jul 2005 11:55:41 +1000 with message-id <[EMAIL PROTECTED]> and subject line Fixed in lprng 3.8.20-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 responsibi

Bug#259256: marked as done (lprng: Control file is not generated any more, but passed to accounting filters)

Your message dated Tue, 19 Jul 2005 09:20:14 +1000 with message-id <[EMAIL PROTECTED]> and subject line Requires new flags 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#314222: marked as done (libequeue-ocaml: Dhelp title)

Your message dated Mon, 18 Jul 2005 19:17:42 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#314222: fixed in equeue 2.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#190251: marked as done (file 'hfA441', age 45.00 hours > 24.00 hours maximum (removing))

Your message dated Tue, 19 Jul 2005 09:08:48 +1000 with message-id <[EMAIL PROTECTED]> and subject line fixed in 3.8.15 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#318059: marked as done (ekg: Insecure tempfile generation)

Your message dated Tue, 19 Jul 2005 01:11:00 +0200 with message-id <[EMAIL PROTECTED]> and subject line fixed in 1:1.5+20050411-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 responsi

Bug#318901: marked as done (aspell-he: doesn't work with the current aspell)

Your message dated Mon, 18 Jul 2005 16:30:31 -0700 with message-id <[EMAIL PROTECTED]> and subject line aspell-he: doesn't work with the current aspell 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

Bug#318937: marked as done (missing libglu1-xorg)

Your message dated Mon, 18 Jul 2005 16:17:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#318937: missing libglu1-xorg 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#243905: marked as done (lprng slow without 'if', 'master-filter' unusable)

Your message dated Tue, 19 Jul 2005 09:12:17 +1000 with message-id <[EMAIL PROTECTED]> and subject line fixed in lprng 3.8.28-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 responsibi

Bug#145514: marked as done (lprng: Removing active job problem)

Your message dated Tue, 19 Jul 2005 09:03:17 +1000 with message-id <[EMAIL PROTECTED]> and subject line fixed in 3.8.15 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#250616: marked as done (lprng 3.8.26-1 (unstable) translate_incoming_format broken)

Your message dated Tue, 19 Jul 2005 09:14:39 +1000 with message-id <[EMAIL PROTECTED]> and subject line Fixed in lprng 3.8.28 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#318788: marked as done (udev: Does not create /dev/pmu)

Your message dated Tue, 19 Jul 2005 00:31:42 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#318788: udev: Does not create /dev/pmu 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#314464: marked as done (shtool: Insecure tempfile generation)

Your message dated Mon, 18 Jul 2005 18:36:25 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#314464: fixed in mysql-ocaml 1.0.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 no

Bug#318644: marked as done (leafnode: fetchnews hangs when there is a out.going message)

Your message dated Mon, 18 Jul 2005 22:12:28 + with message-id <[EMAIL PROTECTED]> and subject line Bug#318644: leafnode: fetchnews hangs when there is a out.going message has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#306990: marked as done (lvm2: Strange error when attempting to install)

Your message dated Tue, 19 Jul 2005 00:08:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line fixed in 1.3.25-23 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#309589: marked as done (postinstall setup assumes upgrade, but it is an incorrect assumption.)

Your message dated Tue, 19 Jul 2005 00:02:50 +0200 with message-id <[EMAIL PROTECTED]> and subject line fixed in 1.3.25-23 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#318212: marked as done (Needs recompile with libenchant1c2)

Your message dated Mon, 18 Jul 2005 12:47:39 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318212: fixed in abiword 2.2.8-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 yo

Bug#194310: marked as done (ethereal segfaults while trying to change "TCP Stream Analysis" mode)

Your message dated Mon, 18 Jul 2005 20:29:52 +0200 with message-id <[EMAIL PROTECTED]> and subject line fixed in 0.9.15 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#318914: marked as done (hotplug: coldplug mechanism breaks systems)

Your message dated Mon, 18 Jul 2005 19:06:50 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#318914: hotplug: coldplug mechanism breaks systems 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#297430: marked as done (xterm: memory corruption and SEGV iff window height == 1)

Your message dated Tue, 19 Jul 2005 00:14:09 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#297430: Is this fixed with the latest version in sid? 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

Bug#318940: marked as done (c-dev is no longer a valid task; causes "Unrecognized tasks" section in aptitude)

Your message dated Mon, 18 Jul 2005 17:47:21 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318940: fixed in leaktracer 2.4-5 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#318655: marked as done (unable upgrade any package, because of error: files list file for package `automake' is missing final newline)

Your message dated Mon, 18 Jul 2005 13:46:30 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318655: unable upgrade any package, because of error: files list file for package `automake' is missing final newline has caused the attached Bug report to be marked as done. This means tha

Bug#259754: marked as done (xlibmesa-dri: [i830] crack-attack segfaults)

Your message dated Mon, 18 Jul 2005 21:49:39 +0200 with message-id <[EMAIL PROTECTED]> and subject line Fixed in 6.8.2.dfsg.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 responsibi

Bug#316224: marked as done (INTL:vi)

Your message dated Mon, 18 Jul 2005 14:47:14 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#316224: fixed in norwegian 2.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 is now y

Bug#316082: marked as done (ethereal: fails to correctly add diameter vendors from the dictionary xml files)

Your message dated Mon, 18 Jul 2005 14:47:05 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#316082: fixed in ethereal 0.10.11-5 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#317705: marked as done ([INTL:bg] New Bulgarian translation)

Your message dated Mon, 18 Jul 2005 15:48:56 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#317705: fixed in localepurge 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 case it is now yo

Bug#318878: marked as done (wxvlc: Please rebuild against libwxgtk2.6-0)

Your message dated Mon, 18 Jul 2005 21:19:39 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#318878: wxvlc: Please rebuild against libwxgtk2.6-0 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#272118: marked as done (Inappropriately uses raw printing with CUPS (by default))

Your message dated Mon, 18 Jul 2005 14:11:47 -0400 (EDT) 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#309998: marked as done (konwert: a)

Your message dated Mon, 18 Jul 2005 23:21:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line bogus report 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 reo

Bug#261712: marked as done (FTBFS on GNU/Hurd (and GNU/k*BSD))

Your message dated Tue, 19 Jul 2005 06:36:39 + with message-id <[EMAIL PROTECTED]@dcemail.com> and subject line Autodesk Architectural Desktop 2006 (3 cds) $55 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 no

Bug#314734: marked as done (AbiWord help should be registered with doc-base)

Your message dated Mon, 18 Jul 2005 12:47:39 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#314734: fixed in abiword 2.2.8-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 yo

Bug#318819: marked as done (Please remove build-dependency on libgimpprint1-dev)

Your message dated Mon, 18 Jul 2005 14:32:37 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318819: fixed in gimp 2.2.8-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#318860: marked as done (since 0.0.20050628 DESKTOP mode of wine is not available)

Your message dated Mon, 18 Jul 2005 13:31:38 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318860: since 0.0.20050628 DESKTOP mode of wine is not available has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#309906: marked as done (heartbeat: LVM resource script does not work with LVM2)

Your message dated Mon, 18 Jul 2005 17:17:10 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#309906: fixed in heartbeat 1.2.3-12 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#318266: marked as done (CONF_D not defined in /etc/ha.d/resources.d/IPaddr2 and /etc/ha.d/resources.d/SendArp)

Your message dated Mon, 18 Jul 2005 17:17:10 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318266: fixed in heartbeat 1.2.3-12 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#318287: marked as done (CAN-2005-2231 temporary file vulnerabilities)

Your message dated Mon, 18 Jul 2005 17:17:10 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318287: fixed in heartbeat 1.2.3-12 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#318899: marked as done (libocc0-dev: still depends on (old) libocc0)

Your message dated Mon, 18 Jul 2005 16:17:58 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318899: fixed in openc++ 2.8-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#317211: marked as done (libjack0.80.0-0 removed from unstable; rebuild required)

Your message dated Mon, 18 Jul 2005 16:47:42 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#317211: fixed in linphone 1.0.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 y

Bug#317933: marked as done (INTL:vi Vietnamese translation for sendpage)

Your message dated Mon, 18 Jul 2005 15:49:46 -0500 (EST) with message-id <[EMAIL PROTECTED]> and subject line closing 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 re

Bug#309086: marked as done (Bug in OpenC++: Preprocessor Parameters Ignored)

Your message dated Mon, 18 Jul 2005 16:17:58 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#309086: fixed in openc++ 2.8-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#209891: marked as done (The package description does not follow Debian policy)

Your message dated Tue, 19 Jul 2005 06:44:35 + with message-id <[EMAIL PROTECTED]> and subject line Cheap software store 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 responsibilit

Bug#305870: marked as done (The way mysql plugin uses to hide password isn't clean)

Your message dated Mon, 18 Jul 2005 16:17:21 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#305870: fixed in backupninja 0.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

Bug#300334: marked as done ('man abiword' typo: "intial")

Your message dated Mon, 18 Jul 2005 12:47:39 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#300334: fixed in abiword 2.2.8-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 yo

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

Your message dated Mon, 18 Jul 2005 14:47:14 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#287539: fixed in norwegian 2.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 is now y

Bug#313756: marked as done (gtkballs: [INTL:de] German PO file corrections)

Your message dated Mon, 18 Jul 2005 16:47:20 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#313756: fixed in gtkballs 3.1.5-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#313802: marked as done (norwegian: [INTL:de] German PO file corrections)

Your message dated Mon, 18 Jul 2005 14:47:14 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#313802: fixed in norwegian 2.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 is now y

Bug#303332: marked as done (/usr/bin/AbiWord-2.2: Spellchecking doesn't work)

Your message dated Mon, 18 Jul 2005 12:47:39 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#303332: fixed in abiword 2.2.8-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 yo

Bug#317356: marked as done (backupninja: backup handler to burn cd or dvd backups)

Your message dated Mon, 18 Jul 2005 16:17:21 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#317356: fixed in backupninja 0.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

Bug#318911: marked as done (ijsgimpprint: depends on wrong replacement)

Your message dated Mon, 18 Jul 2005 14:33:06 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318911: fixed in gutenprint 4.3.99+cvs20050715-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 c

Bug#315950: marked as done ([DPKG-SCANSOURCES] getopt prototype mismatch)

Your message dated Sun, 17 Jul 2005 18:13:51 +0300 with message-id <[EMAIL PROTECTED]> and subject line Bug#315950: Fixed? 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#318945: marked as done (amoeba: rebuilt with wrong libGLU)

Your message dated Mon, 18 Jul 2005 16:32:29 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318945: fixed in amoeba 1.1-16 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#310437: marked as done (backupninja: backup handler for trac environments)

Your message dated Mon, 18 Jul 2005 16:17:21 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#310437: fixed in backupninja 0.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

Bug#318926: marked as done (gettext-base package not renamed for C++ ABI change)

Your message dated Mon, 18 Jul 2005 20:17:26 +0200 (CEST) with message-id <[EMAIL PROTECTED]> and subject line Bug#318926: gettext-base package not renamed for C++ ABI change has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#267688: marked as done ([DPKG-SCANSOURCES] getopt prototype mismatch)

Your message dated Sun, 17 Jul 2005 18:13:51 +0300 with message-id <[EMAIL PROTECTED]> and subject line Bug#315950: Fixed? 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#318909: marked as done (apcupsd: multimon.cgi missing)

Your message dated Mon, 18 Jul 2005 19:11:24 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#318909: apcupsd: multimon.cgi missing 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#250577: marked as done (New version released: 1.5.2)

Your message dated Mon, 18 Jul 2005 13:02:28 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#250577: fixed in mmucl 1.5.2-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#296042: marked as done (xchat: linebreak in the middle of words)

Your message dated Tue, 19 Jul 2005 01:54:23 +0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#296042: debian xchat bug 296042 seems fixed 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

Bug#318817: marked as done (xsltproc: Trys to access network entity when --nonet is specified)

Your message dated Mon, 18 Jul 2005 19:32:18 +0200 with message-id <[EMAIL PROTECTED]> and subject line [xml/sgml-pkgs] Bug#318817: xsltproc: Trys to access network entity when --nonet is specified has caused the attached Bug report to be marked as done. This means that you claim that the problem

Bug#318811: marked as done (mozilla-ctxextensions: Can't be installed because of broken link in extensions.d dir)

Your message dated Mon, 18 Jul 2005 13:32:58 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318811: fixed in ctxextensions 4.0.2005071301-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 ca

Bug#253850: marked as done (popularity-contest: [EMAIL PROTECTED] as target email does not work)

Your message dated Mon, 18 Jul 2005 18:23:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#253850: [EMAIL PROTECTED] as target email does not work 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 no

Bug#310892: marked as done (abiword: clean doesn't clean)

Your message dated Mon, 18 Jul 2005 12:47:39 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#310892: fixed in abiword 2.2.8-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 yo

Bug#314735: marked as done (AbiWord tutorials should be registered with doc-base )

Your message dated Mon, 18 Jul 2005 12:47:39 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#314735: fixed in abiword 2.2.8-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 yo

Bug#315178: marked as done (FTBFS: Build-depends on libnautilus2-dev instead of libgnomeui-dev)

Your message dated Mon, 18 Jul 2005 12:47:39 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#315178: fixed in abiword 2.2.8-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 yo

Bug#309466: marked as done (INTL:vi)

Your message dated Mon, 18 Jul 2005 12:02:29 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#309466: fixed in autolog 0.40-7 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#293603: marked as done ([l10n] Initial Czech translation of autolog debconf messages)

Your message dated Mon, 18 Jul 2005 12:02:29 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#293603: fixed in autolog 0.40-7 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#227806: marked as done (autolog: Japanese po-debconf template translation (ja.po))

Your message dated Mon, 18 Jul 2005 12:02:29 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#227806: fixed in autolog 0.40-7 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#276695: marked as done ([l10n:de] updated German debconf translation)

Your message dated Mon, 18 Jul 2005 12:02:29 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#276695: fixed in autolog 0.40-7 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#276909: marked as done (autolog depends on debhelper)

Your message dated Mon, 18 Jul 2005 12:02:29 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#276909: fixed in autolog 0.40-7 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#287089: marked as done (shermans-aquarium: contains non-free or undistributable images)

Your message dated Mon, 18 Jul 2005 11:48:14 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#287089: fixed in shermans-aquarium 3.0.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

Bug#293359: marked as done (shermans-aquarium: New upstream version - 3.0.0 with "Tons of new features and updates" available)

Your message dated Mon, 18 Jul 2005 11:48:15 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#293359: fixed in shermans-aquarium 3.0.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

Bug#288554: marked as done (mozilla-firefox: Firefox sometimes hangs within futex() calls for a long time.)

Your message dated Mon, 18 Jul 2005 12:09:48 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#288554: mozilla-firefox: Firefox sometimes hangs within futex() calls for a long time. has caused the attached Bug report to be marked as done. This means that you claim that the problem ha

Bug#200109: marked as done (autolog: not killing ssh sessions)

Your message dated Mon, 18 Jul 2005 08:47:34 -0700 (PDT) with message-id <[EMAIL PROTECTED]> and subject line this bug was woody-only 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#310161: marked as done (sendpage : Japanese po-debconf template translation (ja.po))

Your message dated Mon, 18 Jul 2005 11:34:57 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#310161: fixed in sendpage 0.9.14-5 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#317993: marked as done (nvidia-settings: Include desktop entry)

Your message dated Mon, 18 Jul 2005 11:34:57 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#317993: fixed in sendpage 0.9.14-5 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#303697: marked as done (gai: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment)

Your message dated Mon, 18 Jul 2005 11:33:25 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#303697: fixed in gai 0.5.10-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

Processed: john

Processing commands for [EMAIL PROTECTED]: > close 252138 1.6-30 Bug#252138: debconf template mentions "john.cron" instead of "john-cronjob" 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.6-30, send any further explanations to Cedric Cell

Processed: new debbugs rocks!

Processing commands for [EMAIL PROTECTED]: > package john Ignoring bugs not assigned to: john > close 127920 1.6.36-1 Bug#127920: john: Snapshot of devel branch 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.6.36-1, send any further expla

Bug#318891: marked as done (bad C++ transition)

Your message dated Mon, 18 Jul 2005 10:03:02 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#318891: fixed in alsamixergui 0.9.0rc2-1-9 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#318887: marked as done (gettextize can't be run in debian/rules)

Your message dated Mon, 18 Jul 2005 16:32:24 +0200 (CEST) with message-id <[EMAIL PROTECTED]> and subject line Bug#318887: gettextize can't be run in debian/rules 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

Bug#259821: marked as done (sitecopy: FTBFS with gcc-3.4: label at end of compound statement)

Your message dated Mon, 18 Jul 2005 09:36:40 -0500 with message-id and subject line sitecopy: FTBFS with gcc-3.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 responsibility to re

Bug#318478: marked as done (qemu: NIC detection in d-i fails and occasional hangs)

Your message dated Mon, 18 Jul 2005 16:21:19 +0200 with message-id <[EMAIL PROTECTED]> and subject line qemu: NIC detection in d-i fails and occasional hangs 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

  1   2   3   >