Bug#413933: marked as done (zorp: policy.boot cannot be found)

Your message dated Mon, 19 Mar 2007 07:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413933: fixed in zorp 3.0.8-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 you

Bug#415399: marked as done (exim4 manpage should mention return codes)

Your message dated Mon, 19 Mar 2007 08:35:32 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#412537: exim.8.gz: mention exit status, etc. has caused the attached 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

Processed: closing 414669

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.1 > close 414669 Bug#414669: [PATCH] missing link for libwfb.so 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to [EMAI

Bug#336890: marked as done (portaudio: FTBFS on GNU/kFreeBSD)

Your message dated Mon, 19 Mar 2007 06:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#336890: fixed in portaudio 18.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#370294: marked as done (gccxml(GNU/k*BSD): FTBFS: out of date config.sub/config.guess)

Your message dated Mon, 19 Mar 2007 06:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#370294: fixed in gccxml 0.7.0+cvs20070318-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 i

Bug#413945: marked as done (rxvt-unicode: crashes on U+FFFD; sid version lesser affected)

Your message dated Mon, 19 Mar 2007 04:44:56 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#413945: rxvt-unicode: crashes on U+FFFD; sid version lesser affected has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#372824: marked as done (xfce4: property windows should not always be on top)

Your message dated Sun, 18 Mar 2007 22:54:26 -0400 with message-id <[EMAIL PROTECTED]> and subject line close 372824 has caused the attached 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#405294: marked as done (ipe: fixed names of temporary files cause race condition)

Your message dated Mon, 19 Mar 2007 02:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#405294: fixed in ipe 6.0pre28-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 you

Bug#413397: marked as done (ifcico: purging the package fails (update-inetd unavailable))

Your message dated Mon, 19 Mar 2007 02:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413397: fixed in ifmail 2.14tx8.10-19.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

Bug#415386: marked as done (security issues in testing)

Your message dated Sun, 18 Mar 2007 18:50:49 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#415386: security issues in testing has caused the attached 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

Processed: Close bug

Processing commands for [EMAIL PROTECTED]: > unmerge 325568 Bug#325568: Upgrade path for udev needs documenting Bug#383982: release-notes: Describe replace of kernel-image package with linux-image package Disconnected #325568 from all other report(s). > close 383982 Bug#383982: release-notes: De

Bug#415019: marked as done (jabref: wrapper script should exec java)

Your message dated Mon, 19 Mar 2007 00:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415019: fixed in jabref 2.2-01-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 yo

Bug#400725: marked as done (release-notes: How to view logs generated by 'script'?)

Your message dated Mon, 19 Mar 2007 01:23:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line Section expanded with better explanation has caused the attached 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#402980: marked as done (typo in section 3.1 (popcon))

Your message dated Mon, 19 Mar 2007 01:01:28 +0100 with message-id <[EMAIL PROTECTED]> and subject line Paragraph rewritten has caused the attached 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#408710: marked as done (release-notes: mentions XFree86, which is no longer in etch)

Your message dated Mon, 19 Mar 2007 00:47:09 +0100 with message-id <[EMAIL PROTECTED]> and subject line Reference to Xfree86 removed has caused the attached 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#405096: marked as done (release-notes: Section 2.1: GNOME 2.14 and OpenOffice.org 2.0 are not current)

Your message dated Mon, 19 Mar 2007 00:27:46 +0100 with message-id <[EMAIL PROTECTED]> and subject line No longer marked as current has caused the attached 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

Bug#404637: marked as done (libgstreamer0.10-0: segfaults in gaim in _gst_parse_yylex see #403343)

Your message dated Sun, 18 Mar 2007 23:02:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#404637: fixed in gstreamer0.10 0.10.10-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 i

Bug#410444: marked as done (ebview: FTBFS: build-depends on non-available libeb7-dev)

Your message dated Sun, 18 Mar 2007 23:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#410444: fixed in ebview 0.3.6-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 y

Bug#400602: marked as done (crash related to gstreamer)

Your message dated Sun, 18 Mar 2007 23:02:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#404637: fixed in gstreamer0.10 0.10.10-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 i

Bug#403343: marked as done (Crash when using IRC)

Your message dated Sun, 18 Mar 2007 23:02:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#404637: fixed in gstreamer0.10 0.10.10-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 i

Bug#400602: marked as done (crash related to gstreamer)

Your message dated Sun, 18 Mar 2007 23:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#404637: fixed in gstreamer0.10 0.10.12-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 i

Bug#404637: marked as done (libgstreamer0.10-0: segfaults in gaim in _gst_parse_yylex see #403343)

Your message dated Sun, 18 Mar 2007 23:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#404637: fixed in gstreamer0.10 0.10.12-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 i

Bug#400602: marked as done (crash related to gstreamer)

Your message dated Sun, 18 Mar 2007 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403343: fixed in gstreamer0.10 0.10.10-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 i

Bug#403343: marked as done (Crash when using IRC)

Your message dated Sun, 18 Mar 2007 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403343: fixed in gstreamer0.10 0.10.10-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 i

Bug#404637: marked as done (libgstreamer0.10-0: segfaults in gaim in _gst_parse_yylex see #403343)

Your message dated Sun, 18 Mar 2007 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403343: fixed in gstreamer0.10 0.10.10-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 i

Bug#404637: marked as done (libgstreamer0.10-0: segfaults in gaim in _gst_parse_yylex see #403343)

Your message dated Sun, 18 Mar 2007 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#400602: fixed in gstreamer0.10 0.10.10-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 i

Bug#403343: marked as done (Crash when using IRC)

Your message dated Sun, 18 Mar 2007 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#400602: fixed in gstreamer0.10 0.10.10-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 i

Bug#404637: marked as done (libgstreamer0.10-0: segfaults in gaim in _gst_parse_yylex see #403343)

Your message dated Sun, 18 Mar 2007 23:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#400602: fixed in gstreamer0.10 0.10.12-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 i

Bug#404637: marked as done (libgstreamer0.10-0: segfaults in gaim in _gst_parse_yylex see #403343)

Your message dated Sun, 18 Mar 2007 23:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403343: fixed in gstreamer0.10 0.10.12-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 i

Bug#403343: marked as done (Crash when using IRC)

Your message dated Sun, 18 Mar 2007 23:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403343: fixed in gstreamer0.10 0.10.12-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 i

Bug#403343: marked as done (Crash when using IRC)

Your message dated Sun, 18 Mar 2007 23:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#404637: fixed in gstreamer0.10 0.10.12-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 i

Bug#400602: marked as done (crash related to gstreamer)

Your message dated Sun, 18 Mar 2007 23:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403343: fixed in gstreamer0.10 0.10.12-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 i

Bug#400602: marked as done (crash related to gstreamer)

Your message dated Sun, 18 Mar 2007 23:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#400602: fixed in gstreamer0.10 0.10.10-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 i

Bug#400602: marked as done (crash related to gstreamer)

Your message dated Sun, 18 Mar 2007 23:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#400602: fixed in gstreamer0.10 0.10.12-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 i

Bug#414460: marked as done (Unnecessary build depend on automaken)

Your message dated Sun, 18 Mar 2007 23:02:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414460: fixed in ebview 0.3.6-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 y

Bug#403343: marked as done (Crash when using IRC)

Your message dated Sun, 18 Mar 2007 23:02:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#400602: fixed in gstreamer0.10 0.10.12-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 i

Bug#415378: marked as done (wajig: should suggest locales instead of base-config)

Your message dated Mon, 19 Mar 2007 09:57:00 +1100 with message-id <[EMAIL PROTECTED]> and subject line Bug#415378: wajig: should suggest locales instead of base-config has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#415365: marked as done (wajig: Should depend on dselect)

Your message dated Mon, 19 Mar 2007 10:01:42 +1100 with message-id <[EMAIL PROTECTED]> and subject line Bug#415365: wajig: Should depend on dselect has caused the attached 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#407603: marked as done (libsoqt-dev: package wants to remove Nvidia GLX driver)

Your message dated Sun, 18 Mar 2007 17:54:13 -0500 with message-id <[EMAIL PROTECTED]> and subject line New SoQt should fix dependency 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 now

Bug#411101: marked as done (exim4 not using /etc/mailname during SMTP connections)

Your message dated Sun, 18 Mar 2007 23:01:23 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#411101: exim4 not using /etc/mailname during SMTP connections has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#414790: marked as done (CVE-2007-1420: Single Row Subselect DoS)

Your message dated Sun, 18 Mar 2007 21:32:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414790: fixed in mysql-dfsg-5.0 5.0.32-7etch1 has caused the attached 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#414457: marked as done (coolkey(GNU/k*BSD): FTBFS: out of date config.sub/config.guess)

Your message dated Sun, 18 Mar 2007 21:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414457: fixed in coolkey 1.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 yo

Bug#392994: marked as done (konsole: "bold" changes color instead of going bold)

Your message dated Sun, 18 Mar 2007 22:21:33 +0100 with message-id <[EMAIL PROTECTED]> and subject line konsole: "bold" changes color instead of going bold has caused the attached 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#415026: marked as done (mysql-dfsg-5.1_5.1.16beta-1(sparc/experimental): FTBFS: misparses /proc/cpuinfo)

Your message dated Sun, 18 Mar 2007 21:02:07 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415026: fixed in mysql-dfsg-5.1 5.1.16beta-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#411439: marked as done (mysql-5.0: [INTL:ru] Updated Russian debconf translation)

Your message dated Sun, 18 Mar 2007 22:01:09 +0100 with message-id <[EMAIL PROTECTED]> and subject line Closing duplicate has caused the attached 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 t

Bug#325568: marked as done (Upgrade path for udev needs documenting)

Your message dated Sun, 18 Mar 2007 22:01:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line This is already covered in the latest version of the Release Notes has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#383982: marked as done (release-notes: Describe replace of kernel-image package with linux-image package)

Your message dated Sun, 18 Mar 2007 22:01:21 +0100 with message-id <[EMAIL PROTECTED]> and subject line This is already covered in the latest version of the Release Notes has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#337779: marked as done (release-notes do not suggest re-running lilo)

Your message dated Sun, 18 Mar 2007 21:54:55 +0100 with message-id <[EMAIL PROTECTED]> and subject line New section added in the Release Notes has caused the attached 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#415026: marked as done (mysql-dfsg-5.1_5.1.16beta-1(sparc/experimental): FTBFS: misparses /proc/cpuinfo)

Your message dated Sun, 18 Mar 2007 20:32:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415026: fixed in mysql-dfsg-5.0 5.0.32-10 has caused the attached 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#415151: marked as done (regionset: FTBFS on GNU/kFreeBSD: tiny tweak needed)

Your message dated Sun, 18 Mar 2007 20:32:11 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415151: fixed in regionset 0.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 yo

Bug#382764: marked as done (ogre-contrib: FTBFS (gcc-4.1): extra qualification 'Ogre::Image::' on member 'loadDynamicImage')

Your message dated Sun, 18 Mar 2007 20:32:10 + with message-id <[EMAIL PROTECTED]> and subject line Bug#382764: fixed in ogre-contrib 1.0.6-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

Bug#415348: marked as done (uqm: file conflict with uqm-content)

Your message dated Sun, 18 Mar 2007 19:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415348: fixed in uqm 0.6.2.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 y

Bug#415237: marked as done (mysql-server-5.0: Prefer /etc/mysql/my.cnf => /etc/mysql/config (or mysql.conf))

Your message dated Sun, 18 Mar 2007 20:39:30 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#415237: mysql-server-5.0: Prefer /etc/mysql/my.cnf => /etc/mysql/config (or mysql.conf) has caused the attached Bug report to be marked as done. This means that you claim that the problem h

Bug#404891: marked as done (Fans unreliable under load, permanent memory leak)

Your message dated Sun, 18 Mar 2007 19:50:57 +0100 with message-id <[EMAIL PROTECTED]> and subject line Patch committed to CVS, bug 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

Bug#415316: marked as done (yaz: FTBFS: /usr/bin/ld: cannot find -lssl)

Your message dated Sun, 18 Mar 2007 19:39:27 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#415316: yaz: FTBFS: /usr/bin/ld: cannot find -lssl has caused the attached 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#415346: marked as done ()

Your message dated Sun, 18 Mar 2007 19:35:48 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#415346: succesfull install (now closed) has caused the attached 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#414265: marked as done (mpdscribble: [INTL:ru] Russian debconf templates translation)

Your message dated Sun, 18 Mar 2007 18:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414265: fixed in mpdscribble 0.2.12-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#414132: marked as done ([INTL:gl] Galician debconf templates translation for mpdscribble)

Your message dated Sun, 18 Mar 2007 18:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414132: fixed in mpdscribble 0.2.12-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#414862: marked as done ([l10n:ro] mpdscobbler: Romanian translation of the po-debconf templates)

Your message dated Sun, 18 Mar 2007 18:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414862: fixed in mpdscribble 0.2.12-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#412929: marked as done (mpdscribble: [INTL:de] German po-debconf template translation)

Your message dated Sun, 18 Mar 2007 18:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412929: fixed in mpdscribble 0.2.12-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#414593: marked as done (mpdscribble: [INTL:de] initial German debconf translation)

Your message dated Sun, 18 Mar 2007 18:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414593: fixed in mpdscribble 0.2.12-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#414213: marked as done (mpdscribble : [INTL:pt] Portuguese translation for debconf messages)

Your message dated Sun, 18 Mar 2007 18:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414213: fixed in mpdscribble 0.2.12-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#414238: marked as done ([INTL:ta] debconf PO translations for the package mpdscribble)

Your message dated Sun, 18 Mar 2007 18:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414238: fixed in mpdscribble 0.2.12-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#414642: marked as done ([INTL:pt_BR] Please consider adding the attached Brazilian Portuguese (pt_BR) debconf template translation)

Your message dated Sun, 18 Mar 2007 18:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414642: fixed in mpdscribble 0.2.12-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#412306: marked as done (wine: [INTL:ca] Catalan debconf templates translation update)

Your message dated Sun, 18 Mar 2007 18:17:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412306: fixed in wine 0.9.31-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#412315: marked as done (please provide uninstaller.desktop)

Your message dated Sun, 18 Mar 2007 18:17:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412315: fixed in wine 0.9.31-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#409556: marked as done (Cyrillic input in wine does not work)

Your message dated Sun, 18 Mar 2007 18:17:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#409556: fixed in wine 0.9.31-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#411761: marked as done (suggesting clamav and friends)

Your message dated Sun, 18 Mar 2007 18:17:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#411761: fixed in wine 0.9.31-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#409314: marked as done (i810 modesetting driver claims "no modes found on either pipe")

Your message dated Sun, 18 Mar 2007 18:56:18 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#409314: Solved has caused the attached 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#406508: marked as done (ITA: gtans -- Tangram (puzzle) game using GTK+)

Your message dated Sun, 18 Mar 2007 17:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#406508: fixed in gtans 1.2-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 your r

Bug#413706: marked as done ([INTL:nl] Dutch po-debconf translation)

Your message dated Sun, 18 Mar 2007 17:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413706: fixed in mldonkey 2.8.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 y

Bug#414436: marked as done (No further debconf questions asked after "launch at startup = no")

Your message dated Sun, 18 Mar 2007 17:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414436: fixed in mldonkey 2.8.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 y

Bug#412793: marked as done ([INTL:gl] Galician debconf templates translation for mldonkey)

Your message dated Sun, 18 Mar 2007 17:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412793: fixed in mldonkey 2.8.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 y

Bug#410779: marked as done (mldonkey_server)

Your message dated Sun, 18 Mar 2007 17:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#410779: fixed in mldonkey 2.8.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 y

Bug#413778: marked as done (mldonkey: [INTL:es] Spanish po-debconf translation)

Your message dated Sun, 18 Mar 2007 17:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413778: fixed in mldonkey 2.8.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 y

Bug#415065: marked as done (mldonkey-server : [INTL:pt] Portuguese translation for debconf messages)

Your message dated Sun, 18 Mar 2007 17:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415065: fixed in mldonkey 2.8.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 y

Bug#413090: marked as done (mldonkey-server (2.8.1-2etch1): fails to configure (on upgrade))

Your message dated Sun, 18 Mar 2007 18:11:17 +0100 with message-id <[EMAIL PROTECTED]> and subject line Issue solved? has caused the attached 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#270476: marked as done (mldonkey-server: html-gui asks for username and password after upgrade)

Your message dated Sun, 18 Mar 2007 17:56:31 +0100 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#391814: marked as done (/usr/sbin/ed2k script)

Your message dated Sun, 18 Mar 2007 17:41:38 +0100 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#391821: marked as done (/usr/sbin/ed2k script)

Your message dated Sun, 18 Mar 2007 17:41:38 +0100 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#355629: marked as done (sound-juicer: Cannot extract to WAV)

Your message dated Sun, 18 Mar 2007 17:14:07 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#355629: Debian bug follow up (Re: bug 355629) has caused the attached 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#393268: marked as done (gksu does says 'wrong password' even when correct one is tryped)

Your message dated Sun, 18 Mar 2007 17:11:35 +0100 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#333960: marked as done (config script should honour preseeded debconf value for keyboard/options)

Your message dated Sun, 18 Mar 2007 16:51:25 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#333960: config script should honour preseeded debconf value for keyboard/options has caused the attached Bug report to be marked as done. This means that you claim that the problem has been

Bug#413052: marked as done (erlang-mode in sets wrong font-lock face if an space is used after "->")

Your message dated Sun, 18 Mar 2007 15:02:08 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413052: fixed in erlang 1:11.b.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

Bug#414251: marked as done (mplayer: [INTL:ru] Russian debconf templates translation)

Your message dated Sun, 18 Mar 2007 15:02:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414251: fixed in mplayer 1.0~rc1-12etch has caused the attached 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#413120: marked as done (mplayer: [INTL:ja] Japanese debconf templates translation)

Your message dated Sun, 18 Mar 2007 15:02:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413120: fixed in mplayer 1.0~rc1-12etch has caused the attached 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#409431: marked as done (mplayer: [ia64] unaligned access messages during playback)

Your message dated Sun, 18 Mar 2007 15:02:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#409431: fixed in mplayer 1.0~rc1-12etch has caused the attached 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#414075: marked as done (CVE-2007-1246: DMO decoder heap allocation overflow)

Your message dated Sun, 18 Mar 2007 15:02:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414075: fixed in mplayer 1.0~rc1-12etch has caused the attached 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#405360: marked as done (erlang: license of RSA derived sources should be documented)

Your message dated Sun, 18 Mar 2007 15:02:08 + with message-id <[EMAIL PROTECTED]> and subject line Bug#405360: fixed in erlang 1:11.b.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

Bug#413476: marked as done (concalc - FTBFS: error: 'powl' was not declared in this scope)

Your message dated Sun, 18 Mar 2007 15:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413476: fixed in concalc 0.7.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 yo

Bug#413880: marked as done ([INTL:nl] Dutch po-debconf translation)

Your message dated Sun, 18 Mar 2007 15:02:12 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413880: fixed in mplayer 1.0~rc1-12etch has caused the attached 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#415300: marked as done (linux-libertine: Duplicated font definition)

Your message dated Sun, 18 Mar 2007 14:47:25 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415300: fixed in linux-libertine 2.4.9-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 i

Bug#412440: marked as done ([INTL:ta] debconf PO translations for the package ulogd)

Your message dated Sun, 18 Mar 2007 14:47:33 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412440: fixed in ulogd 1.23-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 your

Bug#407629: marked as done (man ulogd has an incorrect FILES section)

Your message dated Sun, 18 Mar 2007 14:47:32 + with message-id <[EMAIL PROTECTED]> and subject line Bug#407629: fixed in ulogd 1.23-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 your

Bug#411727: marked as done ("When installed in d-i, uswsusp creates broken uswsusp.conf with devfs style dev-nodes")

Your message dated Sun, 18 Mar 2007 14:47:34 + with message-id <[EMAIL PROTECTED]> and subject line Bug#411727: fixed in uswsusp 0.3~cvs20060928-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

Bug#414394: marked as done ([INTL:ja] Japanese po-debconf template translation)

Your message dated Sun, 18 Mar 2007 14:47:33 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414394: fixed in ulogd 1.23-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 your

Bug#412499: marked as done (Ulogd don't log MAC-addresses correctly thrue LOGEMU)

Your message dated Sun, 18 Mar 2007 14:47:33 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412499: fixed in ulogd 1.23-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 your

Bug#412855: marked as done (nullmailer: INTL:de)

Your message dated Sun, 18 Mar 2007 14:47:28 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412855: fixed in nullmailer 1:1.03-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#413153: marked as done (nullmailer: [INTL:de] updated German debconf translation)

Your message dated Sun, 18 Mar 2007 14:47:28 + with message-id <[EMAIL PROTECTED]> and subject line Bug#413153: fixed in nullmailer 1:1.03-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#415184: marked as done (nullmailer: [INTL:es] Spanish po-debconf translation)

Your message dated Sun, 18 Mar 2007 14:47:28 + with message-id <[EMAIL PROTECTED]> and subject line Bug#415184: fixed in nullmailer 1:1.03-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

  1   2   >