Bug#217969: marked as done (aqsis always aborts)

Your message dated Thu, 26 Apr 2007 08:59:42 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#217969: aqsis always aborts has caused the attached Bug report to 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#324025: marked as done (aqsis: FTBFS on 64 bit arches: error: cast from 'void*' to 'int' loses precision)

Your message dated Thu, 26 Apr 2007 08:57:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#324025: aqsis: FTBFS on 64 bit arches: error: cast from 'void*' to 'int' loses precision has caused the attached Bug report to be marked as done. This means that you claim that the problem

Bug#419285: marked as done (ipplan: Please fix postgresql-client dependencies)

Your message dated Thu, 26 Apr 2007 07:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419285: fixed in ipplan 4.82-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#420373: marked as done (ipplan : [INTL:pt] Portuguese updated translation for debconf messages)

Your message dated Thu, 26 Apr 2007 07:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420373: fixed in ipplan 4.82-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#420335: marked as done (gprolog: FTBFS: epstopdf: Command not found)

Your message dated Thu, 26 Apr 2007 07:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420335: fixed in gprolog 1.3.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#412671: marked as done (gprolog: Homepage discarded from debian/control)

Your message dated Thu, 26 Apr 2007 07:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412671: fixed in gprolog 1.3.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#5587: marked as done (man2html gets options(n) wrong)

Your message dated Thu, 26 Apr 2007 08:47:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#5587: fixed in man2html 1.6e-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#406098: marked as done (man2html: double quotes gone)

Your message dated Thu, 26 Apr 2007 08:47:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#406098: fixed in man2html 1.6e-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#385158: marked as done (man2html renders parts of the terminfo(5) manual page unreadable)

Your message dated Thu, 26 Apr 2007 08:47:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#385158: fixed in man2html 1.6e-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#418771: marked as done (man2html: Unable to show manpage of dpkg-gencontrol)

Your message dated Thu, 26 Apr 2007 08:47:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#418771: fixed in man2html 1.6e-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#361951: marked as done (man2html does not parse .opt correctly)

Your message dated Thu, 26 Apr 2007 08:47:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#408232: fixed in man2html 1.6e-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#408232: marked as done (Options output for man2html of ps(1) is garbled)

Your message dated Thu, 26 Apr 2007 08:47:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#408232: fixed in man2html 1.6e-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#416924: marked as done (binutils-avr: Upstream 2.17 available)

Your message dated Thu, 26 Apr 2007 10:50:30 +0200 with message-id <[EMAIL PROTECTED]> and subject line Thank you for patching. has caused the attached Bug report to 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#275846: marked as done (smarteiffel: New upstream version 2.0 available)

Your message dated Thu, 26 Apr 2007 10:15:42 +0100 with message-id <[EMAIL PROTECTED]> and subject line New SmartEiffel uploaded has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsib

Bug#421062: marked as done (zabbix - FTBFS: Build-depends against unavailable package: libsnmp9-dev)

Your message dated Thu, 26 Apr 2007 09:17:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#421062: fixed in zabbix 1:1.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 y

Bug#421072: marked as done (aircrack-ng: remote exploitable buffer overflow, Secunia #SA24880, DSA 1280)

Your message dated Thu, 26 Apr 2007 11:21:09 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#421072: Acknowledgement (aircrack-ng: remote exploitable buffer overflow, Secunia #SA24880, DSA 1280) has caused the attached Bug report to be marked as done. This means that you claim that

Bug#421074: marked as done (clamav: several vulnerabilities, CVE-2007-2029, CVE-2007-1745, CVE-2007-1997, DSA 1281)

Your message dated Thu, 26 Apr 2007 11:26:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#421074: Acknowledgement (clamav: several vulnerabilities, CVE-2007-2029, CVE-2007-1745, CVE-2007-1997, DSA 1281) has caused the attached Bug report to be marked as done. This means that you

Bug#421068: marked as done (gpomme -c fails due to missing glade file)

Your message dated Thu, 26 Apr 2007 09:32:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#421068: fixed in pommed 1.3~dfsg-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#421072: marked as done (aircrack-ng: remote exploitable buffer overflow, Secunia #SA24880, DSA 1280)

Your message dated Thu, 26 Apr 2007 11:45:07 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#421072: Acknowledgement (aircrack-ng: remote exploitable buffer overflow, Secunia #SA24880, DSA 1280) has caused the attached Bug report to be marked as done. This means that you claim that

Bug#421074: marked as done (clamav: several vulnerabilities, CVE-2007-2029, CVE-2007-1745, CVE-2007-1997, DSA 1281)

Your message dated Thu, 26 Apr 2007 11:47:07 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#421074: Acknowledgement (clamav: several vulnerabilities, CVE-2007-2029, CVE-2007-1745, CVE-2007-1997, DSA 1281) has caused the attached Bug report to be marked as done. This means that you

Bug#420872: marked as done (xfdesktop4: segfaults in libc.so.6)

Your message dated Thu, 26 Apr 2007 10:02:41 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420872: fixed in xfdesktop4 4.4.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

Bug#369383: marked as done (Offer le to be an editor alternative )

Your message dated Thu, 26 Apr 2007 10:02:40 + with message-id <[EMAIL PROTECTED]> and subject line Bug#369383: fixed in le 1.9.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 re

Bug#421081: marked as done (FTBFS: plr.c:195: error: too few arguments to function 'R_ParseVector')

Your message dated Thu, 26 Apr 2007 13:00:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#421081: FTBFS: plr.c:195: error: too few arguments to function 'R_ParseVector' has caused the attached Bug report to be marked as done. This means that you claim that the problem has been d

Bug#414027: marked as done (rosegarden: Help->Rosegarden Tutorial fails with "Could not find service 'kfmclient'")

Your message dated Thu, 26 Apr 2007 11:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414027: fixed in rosegarden 1:1.5.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 n

Bug#392181: marked as done (rosegarden: Documentation in README.Debian about rtc / jackd / low-latency needs to be updated)

Your message dated Thu, 26 Apr 2007 11:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#392181: fixed in rosegarden 1:1.5.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 n

Bug#419371: marked as done (rosegarden: ought to depend on lilypond as it uses it for the track editor)

Your message dated Thu, 26 Apr 2007 11:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419371: fixed in rosegarden 1:1.5.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 n

Bug#421031: marked as done (suggest transcode for "Ripping Video DVD Titles")

Your message dated Fri, 27 Apr 2007 00:21:17 +1200 with message-id <[EMAIL PROTECTED]> and subject line Bug#421031: oops has caused the attached Bug report to 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#420580: marked as done (Error in package description)

Your message dated Thu, 26 Apr 2007 12:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420580: fixed in cakephp 1.1.14.4797-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#363625: marked as done (Spelling mistake in package description)

Your message dated Thu, 26 Apr 2007 15:12:38 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#363625: Spelling mistake in package description has caused the attached 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#420357: marked as done (freeciv: civclient-gtk looks for .mo's in the wrong place.)

Your message dated Thu, 26 Apr 2007 13:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420357: fixed in freeciv 2.0.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 is now yo

Bug#413241: marked as done (graphviz: Hex colors show up as grey)

Your message dated Thu, 26 Apr 2007 15:59:19 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#413241: graphviz: Hex colors show up as grey has caused the attached Bug 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#420964: marked as done (pysnmp-se: patches from/for zenoss)

Your message dated Thu, 26 Apr 2007 14:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420964: fixed in pysnmp-se 3.5.2-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

Bug#421040: marked as done (sawfish: GTK save file dialogs 'flicker' in size)

Your message dated Thu, 26 Apr 2007 09:12:34 -0500 with message-id <[EMAIL PROTECTED]> and subject line [EMAIL PROTECTED]: Re: RFH: Weird bug in sawfish's handling of gtk save file dialogs] has caused the attached Bug report to be marked as done. This means that you claim that the problem has bee

Bug#420387: marked as done (mga-vid-common: mga-vid udev integration not properly done out-of-box)

Your message dated Thu, 26 Apr 2007 14:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420387: fixed in mga-vid 2.6.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 y

Bug#421104: marked as done (squid segfaults after distupgrade)

Your message dated Thu, 26 Apr 2007 10:38:42 -0400 with message-id <[EMAIL PROTECTED]> and subject line squid segfaults after distupgrade has caused the attached Bug report to 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#175575: marked as done (linuxdoc text rendition contains escape sequences)

Your message dated Thu, 26 Apr 2007 14:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#175575: fixed in linuxdoc-tools 0.9.21-0.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#194941: marked as done (sgml2txt and sgml2latex has problems with underscore characters)

Your message dated Thu, 26 Apr 2007 14:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#194941: fixed in linuxdoc-tools 0.9.21-0.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#419324: marked as done (Linuxdoc-Tools text output contains overstrikes and escape sequences)

Your message dated Thu, 26 Apr 2007 14:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#419324: fixed in linuxdoc-tools 0.9.21-0.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#368522: marked as done (graphviz: Does not set the XML encoding when producing SVG)

Your message dated Thu, 26 Apr 2007 17:09:10 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#368522: graphviz: Does not set the XML encoding when producing SVG 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#420161: marked as done (debmirror fails when mirroring sarge+etch with amd64 arch enabled)

Your message dated Thu, 26 Apr 2007 17:14:05 +0200 with message-id <[EMAIL PROTECTED]> and subject line already fixed in 20060907 has caused the attached Bug report to 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#420962: marked as done (python-twisted-snmp: patches for/from zenoss)

Your message dated Thu, 26 Apr 2007 15:32:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420962: fixed in twistedsnmp 0.3.13-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 n

Bug#421090: marked as done (FTBFS: can't find file `epsf')

> > No pages of output. > Transcript written on manual.log. > make[1]: *** [manual.dvi] Error 1 > make[1]: Leaving directory `/build/tbm/sgf2dg-4.026' > make: *** [common-install-impl] Error 2 > ****

Bug#418559: marked as done (Bad translation strings in exaile for es_ES)

Your message dated Thu, 26 Apr 2007 16:17:05 + with message-id <[EMAIL PROTECTED]> and subject line Bug#418559: fixed in exaile 0.2.9+debian-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

Bug#144371: marked as done (xserver-xfree86: [glint] UseFBDev true always forces high hsync and vsync regardless of mode)

Your message dated Thu, 26 Apr 2007 18:36:18 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#144371: xserver-xfree86: [glint] UseFBDev true always forces high hsync and vsync regardless of mode has caused the attached Bug report to be marked as done. This means that you claim that

Bug#157725: marked as done (xserver-xfree86: [glint] SIGFPE running ygraph client on Permedia 2 rev 1)

Your message dated Thu, 26 Apr 2007 18:35:28 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#157725: xserver-xfree86: [glint] SIGFPE running ygraph client on Permedia 2 rev 1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has bee

Bug#421110: marked as done (Upgrading linux-image-2.6.20-1-686-bigmem should never happen)

Your message dated Thu, 26 Apr 2007 11:19:12 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#421110: Upgrading linux-image-2.6.20-1-686-bigmem should never happen has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with

Bug#397259: marked as done (evolution: message view jumps to the bottom of the message)

Your message dated Thu, 26 Apr 2007 19:27:02 +0200 with message-id <[EMAIL PROTECTED]> and subject line fixed in evolution-2.10.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 respon

Bug#412081: marked as done (Viewing messages always jumps to EOF)

Your message dated Thu, 26 Apr 2007 19:27:02 +0200 with message-id <[EMAIL PROTECTED]> and subject line fixed in evolution-2.10.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 respon

Bug#421057: marked as done (bibtex2html: tetex-extra alternative dropped)

Your message dated Thu, 26 Apr 2007 19:34:45 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#421057: bibtex2html: tetex-extra alternative dropped has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#421001: marked as done (tipa: does not remove old config file on upgrade)

Your message dated Thu, 26 Apr 2007 17:32:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#421001: fixed in tipa 2:1.3-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

Bug#420555: marked as done (sa-exim: Doesn't work with latest exim4 (4.67-1))

Your message dated Thu, 26 Apr 2007 18:47:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420736: fixed in sa-exim 4.2.1-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#420736: marked as done (Latest exim4 in sid breaks sa-exim)

Your message dated Thu, 26 Apr 2007 18:47:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420555: fixed in sa-exim 4.2.1-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#420443: marked as done (sa-exim uses variables not in the local_scan API)

Your message dated Thu, 26 Apr 2007 18:47:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420736: fixed in sa-exim 4.2.1-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#420555: marked as done (sa-exim: Doesn't work with latest exim4 (4.67-1))

Your message dated Thu, 26 Apr 2007 18:47:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420443: fixed in sa-exim 4.2.1-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#420443: marked as done (sa-exim uses variables not in the local_scan API)

Your message dated Thu, 26 Apr 2007 18:47:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420443: fixed in sa-exim 4.2.1-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#420555: marked as done (sa-exim: Doesn't work with latest exim4 (4.67-1))

Your message dated Thu, 26 Apr 2007 18:47:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420555: fixed in sa-exim 4.2.1-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#420443: marked as done (sa-exim uses variables not in the local_scan API)

Your message dated Thu, 26 Apr 2007 18:47:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420555: fixed in sa-exim 4.2.1-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#420736: marked as done (Latest exim4 in sid breaks sa-exim)

Your message dated Thu, 26 Apr 2007 18:47:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420736: fixed in sa-exim 4.2.1-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#420736: marked as done (Latest exim4 in sid breaks sa-exim)

Your message dated Thu, 26 Apr 2007 18:47:17 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420443: fixed in sa-exim 4.2.1-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#420629: marked as done (After upgrading xserver-xorg-core the Xorg process causes about 90% cpu load)

Your message dated Thu, 26 Apr 2007 20:31:41 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#420629: xserver-xorg-core: Working has caused the attached Bug report to 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#418264: marked as done (Should not depend on gnome-themes since gnome-desktop-environment depends on it )

Your message dated Thu, 26 Apr 2007 21:08:29 +0200 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#234582: marked as done (nautilus-cd-burner: Incorrect handling of locale in filenames)

Your message dated Thu, 26 Apr 2007 21:32:57 +0200 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#290538: marked as done (libpango1.0-dev: memory leak in pango_layout_get_extents())

Your message dated Thu, 26 Apr 2007 21:35:49 +0200 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#321832: marked as done (Applications linked to libpango1.0-0 SIGSEGV)

Your message dated Thu, 26 Apr 2007 21:45:50 +0200 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#359835: marked as done (No kerning)

Your message dated Thu, 26 Apr 2007 21:47:09 +0200 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#420480: marked as done (FTBFS due to TeX Live migration)

Your message dated Thu, 26 Apr 2007 19:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420480: fixed in musixtex 1:0.112.2-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 n

Bug#406260: marked as done (libnumber-format-perl: New upstream verison 1.52 available)

Your message dated Thu, 26 Apr 2007 19:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#406260: fixed in libnumber-format-perl 1.52-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

Bug#308427: marked as done (libnumber-format-perl: improved description)

Your message dated Thu, 26 Apr 2007 19:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#308427: fixed in libnumber-format-perl 1.52-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

Bug#416098: marked as done (MegaRAID SAS adapter locks up)

Your message dated Thu, 26 Apr 2007 22:07:02 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#416098: kills my server on install has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#421159: marked as done (gnome-control-center: Gnome settings daemon messes up multimedia keys configuration)

Your message dated Fri, 27 Apr 2007 02:02:43 +0545 with message-id <[EMAIL PROTECTED]> and subject line Dupe has caused the attached Bug report to 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#153299: marked as done (xserver-xfree86: [neomagic] SEGV on NM2160 rev 1)

Your message dated Thu, 26 Apr 2007 22:23:13 +0200 with message-id <[EMAIL PROTECTED]> and subject line Undelivered Mail Returned to Sender has caused the attached Bug report to 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#421157: marked as done (gnome-control-center: Gnome settings daemon messes up multimedia keys configuration)

Your message dated Fri, 27 Apr 2007 02:02:43 +0545 with message-id <[EMAIL PROTECTED]> and subject line Dupe has caused the attached Bug report to 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#308036: marked as done (shared-mime-info: magic for dia is wrong)

Your message dated Thu, 26 Apr 2007 22:29:30 +0200 with message-id <[EMAIL PROTECTED]> and subject line Close 308036 has caused the attached Bug report to 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#419815: marked as done (gnome-system-tools: Unsupported Platform applet appears)

Your message dated Thu, 26 Apr 2007 22:33:02 +0200 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#114698: marked as done (xserver-xfree86: [neomagic] SEGV when running Mozilla 20010916 on NM2200 rev 32)

Your message dated Thu, 26 Apr 2007 22:22:22 +0200 with message-id <[EMAIL PROTECTED]> and subject line Undelivered Mail Returned to Sender has caused the attached Bug report to 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#287369: marked as done (Mis-identifies word97 "unicode text" files as mp3 audio)

Your message dated Thu, 26 Apr 2007 22:29:30 +0200 with message-id <[EMAIL PROTECTED]> and subject line Close 287369 has caused the attached Bug report to 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#292192: marked as done (Misdetected: AFM (Adobe Font Metrics))

Your message dated Thu, 26 Apr 2007 22:29:30 +0200 with message-id <[EMAIL PROTECTED]> and subject line Close 292192 has caused the attached Bug report to 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#420969: marked as done (FTBFS with GCC 4.3: error: extra ';')

Your message dated Thu, 26 Apr 2007 20:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#420969: fixed in gnubiff 2.2.6-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#292184: marked as done (Misdetected: PFA (Postscript Font ASCII))

Your message dated Thu, 26 Apr 2007 22:29:30 +0200 with message-id <[EMAIL PROTECTED]> and subject line Close 292184 has caused the attached Bug report to 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#410446: marked as done (ndtpd: FTBFS: build-depends on non-available libeb7-dev)

Your message dated Thu, 26 Apr 2007 20:32:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#410446: fixed in ndtpd 3.1.5-6.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#222361: marked as done (--menu and others output selected tag to STDOUT, not STDERR)

Your message dated Thu, 26 Apr 2007 23:00:50 +0200 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#367960: marked as done (No formatted help in non-GNOME environments)

Your message dated Thu, 26 Apr 2007 23:04:29 +0200 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#412284: marked as done (unmount doesn't kill smbnetfs)

Your message dated Thu, 26 Apr 2007 21:02:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#412284: fixed in smbnetfs 0.3.9-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#401194: marked as done (libvte4: gnome-terminal uses 100% cpu when the screen is full of email addresses.)

Your message dated Thu, 26 Apr 2007 23:10:25 +0200 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#382005: marked as done (yelp: keeps calling poll with zero time-out with gnumeric documentation)

Your message dated Thu, 26 Apr 2007 23:05:20 +0200 with message-id <[EMAIL PROTECTED]> and subject line Close 382005 has caused the attached Bug report to 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#216994: marked as done (libvte-common: new libvte changes gnome-terminal font size)

Your message dated Thu, 26 Apr 2007 23:11:05 +0200 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#420949: marked as done (New upgrade of libc6 2.5.* renders shells unusable)

Your message dated Thu, 26 Apr 2007 23:14:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#420949: New upgrade of libc6 2.5.* renders shells unusable has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#288853: marked as done (Trouble with Xserver)

Your message dated Thu, 26 Apr 2007 23:13:40 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#288853: Trouble with Xserver has caused the attached Bug report to 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#225335: marked as done (gnome-terminal: display corruption when using "screen" and hardstatus on last line)

Your message dated Thu, 26 Apr 2007 23:19:12 +0200 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#370382: marked as done (xserver-xorg-video-all: Xorg 7.0.20: S3 driver doesn't work)

Your message dated Thu, 26 Apr 2007 23:17:07 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#370382: xserver-xorg-video-all: Xorg 7.0.20: S3 driver doesn't work has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#23193: marked as done (dhcp: Upgrade from dhcpd broken.)

Your message dated Fri, 27 Apr 2007 00:47:42 +0300 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#86196: marked as done (xserver-xfree86: [s3virge] SolidFillRect broken on Trio3D rev 1)

Your message dated Fri, 27 Apr 2007 00:04:17 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#86196: xserver-xfree86: [s3virge] SolidFillRect broken on Trio3D rev 1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wit

Bug#84362: marked as done (xserver-xfree86: [s3virge] pixel corruption and chipset forcing to '86c325' necessary on S3 ViRGE/DX or /GX rev 1)

Your message dated Fri, 27 Apr 2007 00:06:11 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#84362: xserver-xfree86: [s3virge] pixel corruption and chipset forcing to '86c325' necessary on S3 ViRGE/DX or /GX rev 1 has caused the attached Bug report to be marked as done. This means

Bug#415176: marked as done (rhythmbox restarts on close unless doing "kill" on the command line)

Your message dated Fri, 27 Apr 2007 00:06:55 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#415176: rhythmbox restarts on close unless doing "kill" on the command line has caused the attached Bug report to be marked as done. This means that you claim that the problem has been deal

Bug#376942: marked as done (listens on 31416 instead of 1043)

Your message dated Fri, 27 Apr 2007 00:19:20 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#376942: listens on 31416 instead of 1043 has caused the attached Bug report 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#410844: marked as done (gnome-games: tali checks incorrectly for small straights)

Your message dated Fri, 27 Apr 2007 00:32:03 +0200 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#319185: marked as done (add wesnoth-campaigns metapackage)

Your message dated Fri, 27 Apr 2007 00:30:38 +0200 with message-id <[EMAIL PROTECTED]> and subject line add wesnoth-campaigns metapackage has caused the attached Bug report to 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#421156: marked as done (Missing icons in tray)

Your message dated Fri, 27 Apr 2007 00:33:01 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#421156: Missing icons in tray has caused the attached Bug report to 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#414746: marked as done (libxml-twig-perl: FTBFS: failed test t/test_bugs_3_22)

Your message dated Thu, 26 Apr 2007 22:32:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#414746: fixed in libxml-twig-perl 1:3.29-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#408383: marked as done (xml-twig-tools: missing man pages)

Your message dated Thu, 26 Apr 2007 22:32:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#408383: fixed in libxml-twig-perl 1:3.29-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

  1   2   >