Bug#331330: marked as done (bzr should install testsweet.py into PYTHONPATH)

Your message dated Mon, 10 Oct 2005 23:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331330: fixed in bzr 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 is now your res

Bug#329950: marked as done (bzr 0.0.9 new upstream version available)

Your message dated Mon, 10 Oct 2005 23:17:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#329950: fixed in bzr 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 is now your res

Bug#267765: marked as done (doesn't properly show VLAN frames)

Your message dated Tue, 11 Oct 2005 08:02:02 +0200 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 reopen t

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

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332143: fixed in webalizer 2.01.10-27 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#306008: marked as done (ITA: scsiadd -- add or remove SCSI devices by rescanning the bus)

Your message dated Mon, 10 Oct 2005 22:32:14 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#306008: fixed in scsiadd 1.95-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#332235: marked as done (ITA: webalizer - Web server log analysis program)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332235: fixed in webalizer 2.01.10-27 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#330766: marked as done (webalizer: [INTL:sv] Swedish debconf templates translation)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#330766: fixed in webalizer 2.01.10-27 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#324088: marked as done (INTL:vi Vietnamese translation for webalizer)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#324088: fixed in webalizer 2.01.10-27 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#314944: marked as done ([l10n] Initial Czech translation of webalizer debconf messages)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#314944: fixed in webalizer 2.01.10-27 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#297928: marked as done (webalizer: [INTL] Bad encoding in pl.po)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#297928: fixed in webalizer 2.01.10-27 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#303616: marked as done (ITA: php4-imagick -- ImageMagick module for php4)

Your message dated Mon, 10 Oct 2005 22:32:12 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#303616: fixed in php4-imagick 0.9.11-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

Bug#308279: marked as done (webalizer: /etc/cron.daily/webalizer - Use AWK for more effective/simpler code)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#308279: fixed in webalizer 2.01.10-27 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#303807: marked as done (webalizer: [intl:fi] Finnish translation)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#303807: fixed in webalizer 2.01.10-27 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#272316: marked as done (webalizer: [INTL:ca] Catalan debconf file rename and minor update)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#275288: fixed in webalizer 2.01.10-27 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#293333: marked as done (webalizer: Incorrect charset in po/ru.po)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#29: fixed in webalizer 2.01.10-27 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#275288: marked as done (: [INTL:ca] Catalan debconf translation should be named ca.po)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#275288: fixed in webalizer 2.01.10-27 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#286094: marked as done (Danish translation of the Debconf-template for webalizer.)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#286094: fixed in webalizer 2.01.10-27 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#272316: marked as done (webalizer: [INTL:ca] Catalan debconf file rename and minor update)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#272316: fixed in webalizer 2.01.10-27 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#272583: marked as done (formatting issue in the webalizer.1 man page)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#272583: fixed in webalizer 2.01.10-27 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#275288: marked as done (: [INTL:ca] Catalan debconf translation should be named ca.po)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#272316: fixed in webalizer 2.01.10-27 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#265070: marked as done (webalizer: Please add German translation of the debconf templates)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#265070: fixed in webalizer 2.01.10-27 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#269358: marked as done (webalizer: [INTL:pt_BR] Please add Brazilian translation of the debconf template)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#269358: fixed in webalizer 2.01.10-27 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#269359: marked as done (webalizer: [INTL:pt_BR] Brazilian translation po file (sorry, I forgot the attachement on last report))

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#269359: fixed in webalizer 2.01.10-27 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#207943: marked as done (README.Debian refers to already closed bug)

Your message dated Mon, 10 Oct 2005 22:32:18 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#207943: fixed in webalizer 2.01.10-27 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#188175: marked as done (ITA: filerunner -- X-Based FTP program & file manager)

Your message dated Mon, 10 Oct 2005 22:32:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#188175: fixed in filerunner 2.5.1-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 no

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

Your message dated Tue, 11 Oct 2005 00:35:51 -0400 with message-id <[EMAIL PROTECTED]> and subject line spamassassin no longer uses debconf 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#318698: marked as done (INTL:vi Vietnamese translation for spamassassin)

Your message dated Tue, 11 Oct 2005 00:35:51 -0400 with message-id <[EMAIL PROTECTED]> and subject line spamassassin no longer uses debconf 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#316891: marked as done ([l10n] Initial Czech translation of spamassassin debconf messages)

Your message dated Tue, 11 Oct 2005 00:35:51 -0400 with message-id <[EMAIL PROTECTED]> and subject line spamassassin no longer uses debconf 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#322644: marked as done (FTBFS: Test failure)

Your message dated Mon, 10 Oct 2005 21:22:47 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322644: FTBFS: Test failure 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#333070: marked as done (libvisual0.2: Doesn't build on ppc)

Your message dated Mon, 10 Oct 2005 18:32:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#333070: fixed in libvisual 0.2.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

Bug#318544: marked as done (liboil: FTBFS: Unknown register name 'mm0' in 'asm')

Your message dated Mon, 10 Oct 2005 18:40:33 -0700 with message-id <[EMAIL PROTECTED]> and subject line Fixed in 0.3.3-1 upload 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#312325: marked as done (liboil0.3: Illegal instruction in idct8x8_s16_mmx)

Your message dated Mon, 10 Oct 2005 18:41:57 -0700 with message-id <[EMAIL PROTECTED]> and subject line Fixed in 0.3.3-1 upload 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#331567: marked as done (mozilla-firefox: parse bug with "--" in comment, in XHTML mode)

Your message dated Mon, 10 Oct 2005 20:37:21 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#331567: mozilla-firefox: parse bug with "--" in comment, in XHTML mode has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wit

Bug#333034: marked as done (gretl: FTBFS (Build-Depends on imlib1-dev or gdk-imlib1-dev))

Your message dated Mon, 10 Oct 2005 17:18:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line gretl: FTBFS (Build-Depends on imlib1-dev or gdk-imlib1-dev) 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 n

Bug#289772: marked as done (planner: Wrong namespace on document element - incorrect)

Your message dated Mon, 10 Oct 2005 18:25:11 -0600 with message-id <[EMAIL PROTECTED]> and subject line close 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 the

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

Your message dated Mon, 10 Oct 2005 17:02:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332550: fixed in irqbalance 0.12-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

Bug#285830: marked as done (mozilla-firefox: save regets page with causes problem with post)

Your message dated Mon, 10 Oct 2005 19:59:02 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#285830: mozilla-firefox: save regets page with causes problem with post has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wi

Bug#332845: marked as done (Uncorrect named file)

Your message dated Mon, 10 Oct 2005 16:32:21 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332845: fixed in zope3 3.1.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 your

Bug#326597: marked as done (FTBFS: does not find ftheaders.h)

Your message dated Tue, 11 Oct 2005 01:02:49 +0200 with message-id <[EMAIL PROTECTED]> and subject line No longer happens with 0.4.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 respo

Bug#333107: marked as done (pbuilder: Cannot install python2.3-dev)

Your message dated Tue, 11 Oct 2005 00:55:44 +0200 with message-id <[EMAIL PROTECTED]> and subject line [Pkg-openssl-devel] Processed: reassign 333107 to openssl 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#333191: marked as done (pcre3: new upstream release 6.4 available as of 05-Sep-05)

Your message dated Mon, 10 Oct 2005 15:32:22 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#333191: fixed in pcre3 6.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 is now your r

Bug#317103: marked as done (wp2x: should have relationship to the libwpd-tools package)

Your message dated Mon, 10 Oct 2005 15:02:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#317103: fixed in wp2x 2.5-mhi-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 is now you

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

Your message dated Tue, 11 Oct 2005 00:04:15 +0200 with message-id <[EMAIL PROTECTED]> and subject line Mtink 1.11 closes 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 respons

Bug#332892: marked as done (python2.3 - needs rebuild for openssl)

Your message dated Mon, 10 Oct 2005 14:07:03 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332892: fixed in openssl097 0.9.7g-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 no

Bug#74337: marked as done (pgrep does not support the -f option)

Your message dated Mon, 10 Oct 2005 21:43:44 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#74337: pgrep does not support the -f option 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#333106: marked as done (edict: new files found upstream)

Your message dated Mon, 10 Oct 2005 13:17:17 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#333106: fixed in edict 2005.10.04-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#332889: marked as done (atmel-firmware: udev supercedes hotplug)

Your message dated Mon, 10 Oct 2005 13:17:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332889: fixed in atmel-firmware 1.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 n

Bug#332192: marked as done (ifile: sample scripts use ksh but work just as well with Debian-standard bash)

Your message dated Mon, 10 Oct 2005 13:17:39 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332192: fixed in ifile 1.3.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 your

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

Your message dated Mon, 10 Oct 2005 13:17:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331830: fixed in galeon 1.3.21-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 yo

Bug#331728: marked as done (removing galeon-common fails if gconf2 already removed)

Your message dated Mon, 10 Oct 2005 13:17:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331728: fixed in galeon 1.3.21-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 yo

Bug#328315: marked as done (galeon-common: missing depends)

Your message dated Mon, 10 Oct 2005 13:17:24 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#328315: fixed in galeon 1.3.21-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 yo

Bug#314177: marked as done (libhk-classes-sqlite: No support for sqlite3)

Your message dated Mon, 10 Oct 2005 14:14:56 -0600 with message-id <[EMAIL PROTECTED]> and subject line libhk-classes-sqlite: No support for sqlite3 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#306800: marked as done (jta: Please allow building with sun-j2sdk1.5 and recognize the JAVA_HOME directories used by java-package)

Your message dated Mon, 10 Oct 2005 21:18:47 +0200 with message-id <[EMAIL PROTECTED]> and subject line jta: Please allow building with sun-j2sdk1.5 and recognize the JAVA_HOME directories used by java-package has caused the attached Bug report to be marked as done. This means that you claim that

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

Your message dated Mon, 10 Oct 2005 13:03:01 -0600 with message-id <[EMAIL PROTECTED]> and subject line (no subject) 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#308357: marked as done (dillo: 0.8.4 update)

Your message dated Mon, 10 Oct 2005 11:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#308357: fixed in dillo 0.8.5-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#328351: marked as done (dillo: please rebuild against latest libpng)

Your message dated Mon, 10 Oct 2005 11:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#328351: fixed in dillo 0.8.5-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#303126: marked as done (dillo: manpage refers to old URL)

Your message dated Mon, 10 Oct 2005 11:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#303126: fixed in dillo 0.8.5-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#295466: marked as done (New upstream dillo package with security fix and memory leak fixes)

Your message dated Mon, 10 Oct 2005 11:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#295466: fixed in dillo 0.8.5-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#323755: marked as done (dillo: new upstream version 0.8.5 available since 2005-06-15)

Your message dated Mon, 10 Oct 2005 11:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323755: fixed in dillo 0.8.5-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#279216: marked as done (Manpage says dillo still alpha)

Your message dated Mon, 10 Oct 2005 11:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#279216: fixed in dillo 0.8.5-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#193177: marked as done (dillo: doesn't display png images correctly)

Your message dated Mon, 10 Oct 2005 11:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#193177: fixed in dillo 0.8.5-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#150073: marked as done (dillo: Doesn't show umlauts)

Your message dated Mon, 10 Oct 2005 11:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#150073: fixed in dillo 0.8.5-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#192586: marked as done (dillo: URL of help page is incorrect)

Your message dated Mon, 10 Oct 2005 11:47:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#192586: fixed in dillo 0.8.5-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#322109: marked as done (tcpdump: BPF filters don't work with pcap file captured by ulogd)

Your message dated Mon, 10 Oct 2005 11:32:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#322109: fixed in libpcap0.8 0.9.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 is now

Bug#317103: marked as done (wp2x: should have relationship to the libwpd-tools package)

Your message dated Mon, 10 Oct 2005 11:32:11 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#317103: fixed in wp2x 2.5-mhi-8 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#333098: marked as done (openssl transition (libssl0.9.7 -> libssl0.9.8))

Your message dated Mon, 10 Oct 2005 20:40:48 +0200 with message-id <[EMAIL PROTECTED]> and subject line ntop: openssl transition (libssl0.9.7 -> libssl0.9.8) 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#330935: marked as done (gnugo: GNU Go said I stepped on a bug)

Your message dated Mon, 10 Oct 2005 11:17:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#330935: fixed in gnugo 3.7.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

Bug#299642: marked as done (filter expressions not working in tcpdump and tethereal)

Your message dated Mon, 10 Oct 2005 20:05:57 +0200 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 reopen t

Bug#332758: marked as done (openssl: FTBFS: Still uses asm/$arch.o for some arches.)

Your message dated Mon, 10 Oct 2005 11:02:30 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332758: fixed in openssl 0.9.8-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 yo

Bug#332968: marked as done (tgif: FTBFS: debconf-2.0 is not an alternative to debhelper)

Your message dated Mon, 10 Oct 2005 11:17:19 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332968: fixed in tgif 1:4.1.44-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#332905: marked as done (udev: Does not load mousedev automatically; loads nvidiafb)

Your message dated Mon, 10 Oct 2005 10:17:35 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332905: fixed in udev 0.070-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

Bug#332899: marked as done (udev: framebuffer load when we doesn't want it)

Your message dated Mon, 10 Oct 2005 10:17:35 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332905: fixed in udev 0.070-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

Bug#332970: marked as done (Permissions of /dev/random and /dev/urandom should match)

Your message dated Mon, 10 Oct 2005 10:17:35 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332970: fixed in udev 0.070-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

Bug#332946: marked as done (udev: timeout default not long enough on slower machines and doc about it)

Your message dated Mon, 10 Oct 2005 10:17:35 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332946: fixed in udev 0.070-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

Bug#332905: marked as done (udev: Does not load mousedev automatically; loads nvidiafb)

Your message dated Mon, 10 Oct 2005 10:17:35 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332899: fixed in udev 0.070-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

Bug#332899: marked as done (udev: framebuffer load when we doesn't want it)

Your message dated Mon, 10 Oct 2005 10:17:35 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332899: fixed in udev 0.070-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

Bug#332898: marked as done (serio hotplug broken?)

Your message dated Mon, 10 Oct 2005 10:17:35 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332898: fixed in udev 0.070-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

Bug#333113: marked as done (sarge rc3 dist-upgrade FAILS)

Your message dated Mon, 10 Oct 2005 13:13:28 -0400 with message-id <[EMAIL PROTECTED]> and subject line Bug#333113: sarge rc3 dist-upgrade FAILS 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#323108: marked as done (libapache2-request-perl: apreq2-config emits braindead information)

Your message dated Mon, 10 Oct 2005 10:02:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323108: fixed in libapreq2 2.06-dev-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 n

Bug#323891: marked as done (/usr/share/doc/pkgsync/README.Debian instead of (...)/README.Debian.gz in cron error messages)

Your message dated Mon, 10 Oct 2005 09:47:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#323891: fixed in pkgsync 1.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 your r

Bug#332438: marked as done (please add examples)

Your message dated Mon, 10 Oct 2005 09:47:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332438: fixed in pkgsync 1.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 your r

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

Your message dated Mon, 10 Oct 2005 09:47:08 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332150: fixed in witalian 1.7.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#331473: marked as done (fltk1.1: [INTL:sv] Swedish debconf templates translation)

Your message dated Mon, 10 Oct 2005 09:32:07 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#331473: fixed in fltk1.1 1.1.6-8 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#332016: marked as done (mailcrypt depends on debconf without | debconf-2.0 alternate; blocks cdebconf transition)

Your message dated Mon, 10 Oct 2005 09:17:05 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332016: fixed in mailcrypt 3.5.8+CVS.2005.04.29.1-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 th

Bug#333132: marked as done (Won't start if old_passwords=1 is in my.cnf)

Your message dated Mon, 10 Oct 2005 18:05:42 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#333132: Won't start if old_passwords=1 is in my.cnf 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#295606: marked as done (autofs-ldap: ldap automount map is incompatible with version in woody, makes it hard to upgrade)

Your message dated Mon, 10 Oct 2005 18:15:11 +0200 with message-id <[EMAIL PROTECTED]> and subject line autofs-ldap: ldap automount map is incompatible with version in woody, makes it hard to upgrade has caused the attached Bug report to be marked as done. This means that you claim that the probl

Bug#332435: marked as done (m4: changeword not activated)

Your message dated Mon, 10 Oct 2005 17:28:41 +0200 (CEST) with message-id <[EMAIL PROTECTED]> and subject line Bug#332435: m4: changeword not activated 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#328887: marked as done (dash/ash question)

Your message dated Mon, 10 Oct 2005 15:09:30 + with message-id <[EMAIL PROTECTED]> and subject line Bug#328887: dash/ash question 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#333121: marked as done (xdm: cannot be installed on Debian unstable)

Your message dated Mon, 10 Oct 2005 16:58:48 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#333121: xdm: cannot be installed on Debian unstable 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#333051: marked as done (Presario 2100 Keyboard stuck on Caps Lock)

Your message dated Mon, 10 Oct 2005 07:52:38 -0700 (PDT) with message-id <[EMAIL PROTECTED]> and subject line Presario 2100 Keyboard stuck on Caps Lock 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: Oops...sorry for the goof up...

Processing commands for [EMAIL PROTECTED]: > close 333119 Bug#333119: gcc-4.0: Segfaulting code generated for gtkboard-0.11pre0 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to "R.Ramkumar" <[EMAIL PROTECTED]> > thanks Stopping

Bug#327572: marked as done (xpdf: zooming does not increase viewable area)

Your message dated Mon, 10 Oct 2005 07:02:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#329112: fixed in xpdf 3.01-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 r

Bug#326888: marked as done (xpdf-reader: sets document bounding size arbitrarily)

Your message dated Mon, 10 Oct 2005 07:02:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#329112: fixed in xpdf 3.01-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 r

Bug#324172: marked as done (xpdf-reader: Resizing xpdf results in garbled display)

Your message dated Mon, 10 Oct 2005 07:02:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#329112: fixed in xpdf 3.01-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 r

Bug#329112: marked as done (xpdf resize problem)

Your message dated Mon, 10 Oct 2005 07:02:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#329112: fixed in xpdf 3.01-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 r

Bug#329112: marked as done (xpdf resize problem)

Your message dated Mon, 10 Oct 2005 07:02:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#327572: fixed in xpdf 3.01-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 r

Bug#326888: marked as done (xpdf-reader: sets document bounding size arbitrarily)

Your message dated Mon, 10 Oct 2005 07:02:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#327572: fixed in xpdf 3.01-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 r

Bug#332704: marked as done (FTBFS: Missing build-dependency on debhelper)

Your message dated Mon, 10 Oct 2005 07:02:06 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#332704: fixed in crossfire-maps-small 1.5.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

Bug#332475: marked as done (low priority questions are not being asked)

Your message dated Mon, 10 Oct 2005 16:09:37 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#332475: low priority questions are not being asked 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#324172: marked as done (xpdf-reader: Resizing xpdf results in garbled display)

Your message dated Mon, 10 Oct 2005 07:02:09 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#327572: fixed in xpdf 3.01-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 r

  1   2   >