Bug#296084: marked as done (/etc/kernel-img.conf mkimage option fails)

Your message dated Sun, 20 Feb 2005 01:32:02 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#296084: fixed in kernel-package 8.124 has caused the attached Bug report to 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#295709: marked as done (/usr/bin/make-kpkg: Kernel built with Debugging is not larger than "normal" kernel - debug doesn't work?)

Your message dated Sun, 20 Feb 2005 00:21:43 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#295709: /usr/bin/make-kpkg: Kernel built with Debugging is not larger than "normal" kernel - debug doesn't work? has caused the attached Bug report to be marked as done. This means that you

Bug#293533: marked as done (clamav-milter: unsafe socket permissions?)

Your message dated Sat, 19 Feb 2005 23:46:16 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#293533: clamav-milter: I accept the risk has caused the attached Bug report 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#293767: marked as done (openoffice.org-kde: er, it doesn't work :()

Your message dated Sat, 19 Feb 2005 23:27:57 -0500 with message-id <[EMAIL PROTECTED]> and subject line Fixed? has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen th

Bug#295405: marked as done (pcb description needs updating)

Your message dated Sat, 19 Feb 2005 22:02:03 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295405: fixed in pcb 1.99j+20050127-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#269578: marked as done (pcb: incorrect pointer to html docs in README.debian)

Your message dated Sat, 19 Feb 2005 22:02:03 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#269578: fixed in pcb 1.99j+20050127-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#294319: marked as done (pcb: FTBFS (amd64/gcc-4.0): static declaration of 'abs' follows non-static declaration)

Your message dated Sat, 19 Feb 2005 22:02:03 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#294319: fixed in pcb 1.99j+20050127-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#295404: marked as done (typo in pcb depends list - should be tk8.4)

Your message dated Sat, 19 Feb 2005 22:02:03 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295404: fixed in pcb 1.99j+20050127-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#188080: marked as done (pcb: .ps files outputted by PCB seem to be broken)

Your message dated Sun, 20 Feb 2005 13:31:20 +1100 with message-id <[EMAIL PROTECTED]> and subject line Fixed in 1.99j+20050127-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 responsi

Bug#293750: marked as done (mysql-client-4.1 should provide mysql-client)

Your message dated Sat, 19 Feb 2005 21:02:19 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#293750: fixed in cacti 0.8.5a-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#285002: marked as done (cacti: Depends on mysql-client not virtual-mysql-client)

Your message dated Sat, 19 Feb 2005 21:02:19 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#285002: fixed in cacti 0.8.5a-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#275045: marked as done (cacti logrotate shouldn't be using delaycompress.)

Your message dated Sat, 19 Feb 2005 21:02:19 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#275045: fixed in cacti 0.8.5a-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#292770: marked as done (ITA: cacti)

Your message dated Sat, 19 Feb 2005 21:02:19 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#292770: fixed in cacti 0.8.5a-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#291283: marked as done (libgnome-mag2 should conflict with libgnome-mag2)

Your message dated Sat, 19 Feb 2005 20:32:06 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#291283: fixed in gnome-mag 1:0.11.14-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#291298: marked as done (should rawdog depend on python-xml?)

Your message dated Sat, 19 Feb 2005 19:27:41 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#291298: should rawdog depend on python-xml? has caused the attached Bug 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#296063: marked as done (gimp: refuses to save XPM)

Your message dated Sat, 19 Feb 2005 19:30:51 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#296063: gimp: refuses to save XPM has caused the attached Bug report to be 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#295236: marked as done (qprof do not use/link correctly with libpfm{2,3} and libunwind)

Your message dated Sat, 19 Feb 2005 19:17:27 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295236: fixed in qprof 0.5.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 the case it is now your

Bug#294784: marked as done (ld cannot load libqprof_libpfm3.so)

Your message dated Sat, 19 Feb 2005 19:17:27 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#294784: fixed in qprof 0.5.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 the case it is now your

Bug#289215: marked as done (lostirc: french translation, two entries of view menu have the same shortcut)

Your message dated Sat, 19 Feb 2005 19:17:09 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#289215: fixed in lostirc 0.4.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 yo

Bug#292758: marked as done (lostirc: conversion to utf-8 fails on german umlaut in fullname)

Your message dated Sat, 19 Feb 2005 19:17:09 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#292758: fixed in lostirc 0.4.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 yo

Bug#295916: marked as done (openoffice.org-bin: installs unstripped (huge) binaries)

Your message dated Sun, 20 Feb 2005 01:25:25 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#295916: openoffice.org-bin: installs unstripped (huge) binaries has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#295900: marked as done (Depends on gnomelibs)

Your message dated Sat, 19 Feb 2005 19:04:57 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#293551: fixed in openoffice.org 1.1.3-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#293551: marked as done (openoffice.org-bin: Depends on gnomelibs.)

Your message dated Sat, 19 Feb 2005 19:04:57 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#293551: fixed in openoffice.org 1.1.3-6 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#295343: marked as done (athcool: Support for AMD-762)

Your message dated Sat, 19 Feb 2005 19:02:16 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295343: fixed in athcool 0.3.10-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Processed: Re: Bug#296055: exim permissions screwed

Processing commands for [EMAIL PROTECTED]: > package exim Ignoring bugs not assigned to: exim > # severities must match for merge to succeed > severity 296055 important Bug#296055: exim permissions screwed Severity set to `important'. > close 296055 Bug#296055: exim permissions screwed 'close' i

Bug#289024: marked as done (rosegarden4: doesn't get localized)

Your message dated Sat, 19 Feb 2005 18:47:49 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#289024: fixed in rosegarden4 1.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

Bug#197850: marked as done (rosegarden4: Some menus are titled "No text!")

Your message dated Sat, 19 Feb 2005 18:47:49 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#197850: fixed in rosegarden4 1.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

Bug#244910: marked as done (libatomic-ops_0.5-1(hppa/unstable): Needs porting work for non-i386,ia64)

Your message dated Sat, 19 Feb 2005 18:47:31 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#244910: fixed in libatomic-ops 0.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

Bug#245417: marked as done (rosegarden4: text does not display correctly with french locales)

Your message dated Sat, 19 Feb 2005 18:47:49 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#245417: fixed in rosegarden4 1.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

Bug#287276: marked as done (libatomic-ops: Support for amd64.)

Your message dated Sat, 19 Feb 2005 18:47:31 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#287276: fixed in libatomic-ops 0.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

Bug#296045: marked as done (seahorse: incorrect name in debconf message)

Your message dated Sat, 19 Feb 2005 18:17:08 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#296045: fixed in seahorse 0.7.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 y

Bug#296044: marked as done (Confusing debconf question)

Your message dated Sat, 19 Feb 2005 18:17:08 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#296044: fixed in seahorse 0.7.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 y

Bug#295401: marked as done (gnump3d-index dies on uninitialised numeric value in a less-than operation)

Your message dated Sat, 19 Feb 2005 22:16:38 + 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#287226: marked as done (nvidia-glx: X crashes with kernel 2.6.10 and GeForce2 MX 400)

Your message dated Sat, 19 Feb 2005 17:17:20 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#287226: fixed in nvidia-graphics-drivers 1.0.6629+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

Bug#280224: marked as done (Missing GLX components?)

Your message dated Sat, 19 Feb 2005 17:17:20 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#280224: fixed in nvidia-graphics-drivers 1.0.6629+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

Bug#281640: marked as done ( Support for 2.6.10-rc2 kernel)

Your message dated Sat, 19 Feb 2005 17:17:20 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#281640: fixed in nvidia-graphics-drivers 1.0.6629+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

Bug#295853: marked as done (reportbug includes sensitive information in report)

Your message dated Sat, 19 Feb 2005 15:51:23 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#295853: reportbug: Well done! has caused the attached Bug report to be 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#283614: marked as done (console-data: [INTL:ar] Arabic debconf templates translation)

Your message dated Sat, 19 Feb 2005 21:35:30 + 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#282512: marked as done (tagtool: should not rename files to . .mp3 if track & title are empty)

Your message dated Sat, 19 Feb 2005 15:29:28 -0600 with message-id <[EMAIL PROTECTED]> and subject line Bug#282512: tagtool: should not rename files to . .mp3 if track & title are empty has caused the attached Bug report to be marked as done. This means that you claim that the problem has been de

Bug#291224: marked as done (Undocumented: dpkg-reconfigure needed after plugin customisation)

Your message dated Sat, 19 Feb 2005 15:47:17 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#291224: fixed in nagios-plugins 1.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 n

Bug#295917: marked as done (nagios-plugins: check_https uses -ssl instead of --ssl)

Your message dated Sat, 19 Feb 2005 15:47:17 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295917: fixed in nagios-plugins 1.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 n

Bug#287940: marked as done (jpilot: synchronisation on ttyS0 is broken on kernel 2.4.27)

Your message dated Sat, 19 Feb 2005 21:56:42 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#287940: jpilot: synchronisation on ttyS0 is broken on kernel 2.4.27 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with.

Bug#296003: marked as done (nagios-plugins: check_proc uses bad ps syntax)

Your message dated Sat, 19 Feb 2005 15:47:17 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#296003: fixed in nagios-plugins 1.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 n

Bug#293661: marked as done (sympa: New upstream 4.1.3 available)

Your message dated Sat, 19 Feb 2005 15:32:11 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#293661: fixed in sympa 4.1.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#282103: marked as done (function do_arc_delete missing in wwsympa.fcgi)

Your message dated Sat, 19 Feb 2005 15:32:11 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#282103: fixed in sympa 4.1.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#291462: marked as done (Wrong libnet-ldap-perl depends version)

Your message dated Sat, 19 Feb 2005 15:32:11 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#291462: fixed in sympa 4.1.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#295411: marked as done (sympa: CERTA-2005-AVI-078 : bouncequeue and queue can execute arbitrary code because of a buffer overflow)

Your message dated Sat, 19 Feb 2005 15:32:11 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295411: fixed in sympa 4.1.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#295981: marked as done ([l10n] Initial Czech translation of sympa debconf messages)

Your message dated Sat, 19 Feb 2005 15:32:11 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295981: fixed in sympa 4.1.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#296025: marked as done (Lost "/dev/nvidiax" after reboot)

Your message dated Sat, 19 Feb 2005 20:58:14 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#296025: Lost "/dev/nvidiax" after reboot has caused the attached Bug report 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#295894: marked as done (hf: FTBFS: Old config.guess/config.sub files.)

Your message dated Sat, 19 Feb 2005 14:47:15 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295894: fixed in hf 0.7.2-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your re

Bug#295896: marked as done ([lionel@mamane.lu: Bug#270587: dhttpd: /etc/default, not /etc/defaults])

Your message dated Sat, 19 Feb 2005 14:32:03 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295896: fixed in dhttpd 1.02a-13 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#295895: marked as done ([lionel@mamane.lu: Bug#270587: dhttpd: /etc/default, not /etc/defaults])

Your message dated Sat, 19 Feb 2005 14:32:03 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295895: fixed in dhttpd 1.02a-13 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now yo

Bug#253770: marked as done (tag file parsing broken)

Your message dated Sat, 19 Feb 2005 20:43:55 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#253770: tag file parsing broken has caused the attached Bug report to be 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#295712: marked as done (sleuthkit: Wrong SHARE_DIR in /usr/bin/sorter)

Your message dated Sat, 19 Feb 2005 14:17:17 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295712: fixed in sleuthkit 1.73-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#295065: marked as done (xsl compilation error)

Your message dated Sat, 19 Feb 2005 14:17:03 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295065: fixed in db2latex-xsl 0.8pre1-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#277824: marked as done (Important hotkeys bug, with a patch)

Your message dated Sat, 19 Feb 2005 13:47:14 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#277824: fixed in hotkeys 0.5.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 yo

Bug#294795: marked as done (FWD: [SECURITY] [DSA 677-1] New sympa packages fix potential arbitrary code execution)

Your message dated Sat, 19 Feb 2005 19:57:53 +0100 with message-id <[EMAIL PROTECTED]> and subject line Acknowledge NMU has caused the attached Bug report to be 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#285711: marked as done (seahorse: Display of subkeys is off-by-one)

Your message dated Sat, 19 Feb 2005 13:32:07 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#285711: fixed in seahorse 0.7.6-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#284156: marked as done (seahorse: Keyserver support)

Your message dated Sat, 19 Feb 2005 13:32:07 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#284156: fixed in seahorse 0.7.6-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#279845: marked as done (can't load online-help from seahorse directly)

Your message dated Sat, 19 Feb 2005 13:32:07 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#279845: fixed in seahorse 0.7.6-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#294179: marked as done (seahorse: doesn't work with gnupg 1.4)

Your message dated Sat, 19 Feb 2005 13:32:07 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#294179: fixed in seahorse 0.7.6-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Bug#287132: marked as done (seahorse: Can't manually encrypt to self)

Your message dated Sat, 19 Feb 2005 13:32:07 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#287132: fixed in seahorse 0.7.6-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now y

Processed: Re: Bug#295956: cupsys: 1200 dpi mode broken?

Processing commands for [EMAIL PROTECTED]: > close 295956 Bug#295956: cupsys: 1200 dpi mode broken? 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Ian Zimmerman <[EMAIL PROTECTED]> > thanks Stopping processing here. Please co

Bug#272480: marked as done (replicator: Keymap installation on the target fails)

Your message dated Sat, 19 Feb 2005 13:17:15 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#272480: fixed in console-common 0.7.50 has caused the attached Bug report to 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#295038: marked as done (console-common: [INTL:tl] Tagalog translation of program and debconf templates)

Your message dated Sat, 19 Feb 2005 13:17:15 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295038: fixed in console-common 0.7.50 has caused the attached Bug report to 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#293004: marked as done ([l10n] Initial Czech translation of jpilot debconf messages)

Your message dated Sat, 19 Feb 2005 13:02:28 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#293004: fixed in jpilot 0.99.7-0.99.8-pre8-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#295971: marked as done (jpilot: Hidden records can be viewed/modified without password)

Your message dated Sat, 19 Feb 2005 13:02:28 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295971: fixed in jpilot 0.99.7-0.99.8-pre8-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#278635: marked as done (jpilot: cut and paste does not works if you switch from memo to the phonebook)

Your message dated Sat, 19 Feb 2005 13:02:28 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#278635: fixed in jpilot 0.99.7-0.99.8-pre8-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#295564: marked as done (dcgui-qt: Fails to load config due to xml problem)

Your message dated Sat, 19 Feb 2005 12:32:16 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#293865: fixed in libdc0 0.3.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 you

Bug#293865: marked as done (libxml2 2.6.16 does not work with DCGUI-QT)

Your message dated Sat, 19 Feb 2005 12:32:16 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#293865: fixed in libdc0 0.3.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 you

Bug#292488: marked as done (sylpheed-claws-gtk2: please package 1.0.0)

Your message dated Sat, 19 Feb 2005 18:33:15 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#292488: sylpheed-claws-gtk2: please package 1.0.0 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#280562: marked as done (jpilot: Does not respect gtk keybindings)

Your message dated Sat, 19 Feb 2005 18:27:08 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#280562: jpilot: Does not respect gtk keybindings has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#287966: marked as done (proftpd: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment)

Your message dated Sat, 19 Feb 2005 18:05:16 +0100 with message-id <[EMAIL PROTECTED]> and subject line Processed: Fixed in NMU of proftpd 1.2.10-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 i

Bug#295149: marked as done (kernel-package: it fails to build my kernel with strange error message)

Your message dated Sat, 19 Feb 2005 11:47:03 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295149: fixed in kernel-package 8.123 has caused the attached Bug report to 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#295838: marked as done (vdr: restarts itself before it can really work)

Your message dated Sat, 19 Feb 2005 11:02:48 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#295838: fixed in vdr 1.2.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 your r

Bug#286888: marked as done (gpgkeys: FTBFS (amd64/gcc-4.0): non-local variable ' tabs []' uses anonymous type)

Your message dated Sat, 19 Feb 2005 10:02:52 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#286888: fixed in gpgkeys 0.3.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#245621: marked as done (gpgkeys: Three "Options" tabs, but all the same.)

Your message dated Sat, 19 Feb 2005 10:02:52 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#245621: fixed in gpgkeys 0.3.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#285853: marked as done (ipw2100-source: Compiled module doesn't work)

Your message dated Sat, 19 Feb 2005 16:14:10 +0100 with message-id <[EMAIL PROTECTED]> and subject line Unreproducible, no answer has caused the attached Bug report to be 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#278905: marked as done (doodle: Bus error when building database)

Your message dated Sat, 19 Feb 2005 09:49:41 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#278905: fixed in doodle 0.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 you

Bug#279057: marked as done (doodle: 0 byte database not recovered)

Your message dated Sat, 19 Feb 2005 09:49:41 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#279057: fixed in doodle 0.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 you

Bug#288411: marked as done (rlplot: FTBFS (amd64/gcc-4.0): cast from 'void*' to 'int' loses precision)

Your message dated Sat, 19 Feb 2005 09:47:28 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#288411: fixed in rlplot 0.99.14-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#288166: marked as done (libmpich1.0: libmpich.so and libpmpich.so are missing on alpha, ia64, hppa)

Your message dated Sat, 19 Feb 2005 09:34:47 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#281594: fixed in mpich 1.2.5.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 yo

Bug#287763: marked as done (i.points.html: imagery.ps)

Your message dated Sat, 19 Feb 2005 09:39:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#287763: fixed in grass 5.7.0+6.0.0beta2-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#286725: marked as done (illuminator: FTBFS: configure: error: "PETSc libraries not found")

Your message dated Sat, 19 Feb 2005 09:34:47 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#281594: fixed in mpich 1.2.5.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 yo

Bug#283987: marked as done (Dangling symlink)

Your message dated Sat, 19 Feb 2005 09:34:47 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#281573: fixed in mpich 1.2.5.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 yo

Bug#281573: marked as done (mpiCC.mpich dangling symlink)

Your message dated Sat, 19 Feb 2005 09:34:47 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#281573: fixed in mpich 1.2.5.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 yo

Bug#261726: marked as done (r.lags.1grass.gz: "name" section way too long)

Your message dated Sat, 19 Feb 2005 09:39:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#261726: fixed in grass 5.7.0+6.0.0beta2-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#252299: marked as done (mpich: mpirun doesn't work if curdir has space in name)

Your message dated Sat, 19 Feb 2005 09:34:47 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#252299: fixed in mpich 1.2.5.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 yo

Bug#259655: marked as done (#256208: grass: r.in.bin segfaults)

Your message dated Sat, 19 Feb 2005 09:39:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#259655: fixed in grass 5.7.0+6.0.0beta2-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#242366: marked as done (libmpich++ has no shared version)

Your message dated Sat, 19 Feb 2005 09:34:47 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#242366: fixed in mpich 1.2.5.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 yo

Bug#281594: marked as done (libmpich1.0: libmpich.so.1.0 is a non-PIC library)

Your message dated Sat, 19 Feb 2005 09:34:47 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#281594: fixed in mpich 1.2.5.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 yo

Bug#234275: marked as done (r.in.gdal segfaults)

Your message dated Sat, 19 Feb 2005 09:39:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#234275: fixed in grass 5.7.0+6.0.0beta2-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#264566: marked as done (Please consider upgrade to version 5.7)

Your message dated Sat, 19 Feb 2005 09:39:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#264566: fixed in grass 5.7.0+6.0.0beta2-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#287591: marked as done (grass: help button doc path wrong)

Your message dated Sat, 19 Feb 2005 09:39:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#287591: fixed in grass 5.7.0+6.0.0beta2-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#282567: marked as done (tcltkgrass: start a monitor and the menu bar goes blank)

Your message dated Sat, 19 Feb 2005 09:39:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#282567: fixed in grass 5.7.0+6.0.0beta2-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#282258: marked as done (mpich: broken .so symlinks)

Your message dated Sat, 19 Feb 2005 09:34:47 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#282258: fixed in mpich 1.2.5.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 yo

Bug#287590: marked as done (raster.html: non explained commands)

Your message dated Sat, 19 Feb 2005 09:39:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#287590: fixed in grass 5.7.0+6.0.0beta2-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#287651: marked as done (grass: Multiple vulnerabilities (symlink attacks) due to improper temporary files use in scripts and source code)

Your message dated Sat, 19 Feb 2005 09:39:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#287651: fixed in grass 5.7.0+6.0.0beta2-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#287764: marked as done (i.rectify.html: links to i.vpoints.html do not work)

Your message dated Sat, 19 Feb 2005 09:39:30 -0500 with message-id <[EMAIL PROTECTED]> and subject line Bug#287764: fixed in grass 5.7.0+6.0.0beta2-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#295892: marked as done (Extra columns ":" in "exit 0" lines of initscripts)

Your message dated Sat, 19 Feb 2005 14:03:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#295892: Extra columns ":" in "exit 0" lines of initscripts has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is

  1   2   >