Bug#315766: Forwarded

2006-04-24 Thread Filipus Klutiero
tags 315766 + upstream forwarded 315766 http://bugs.kde.org/98390 thanks Please note that it would be nice to notify Debian's BTS when you forward a bug upstream. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Forwarded

2006-04-24 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 315766 + upstream Bug#315766: kmail: crash after question for sending a receive notification There were no tags set. Tags added: upstream > forwarded 315766 http://bugs.kde.org/98390 Bug#315766: kmail: crash after question for sending a receive no

Bug#358035: marked as done (kmail crashes when viewing the source of a message)

2006-04-24 Thread Debian Bug Tracking System
Your message dated Tue, 25 Apr 2006 01:35:58 -0400 with message-id <[EMAIL PROTECTED]> and subject line Should be 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

Processed: Merge

2006-04-24 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > merge 354658 301966 Bug#301966: kmail: crash when changing spell check language (probably race condition) Bug#354658: kmail: kmail segfaults when changing language Merged 301966 354658. > found 301966 3.5.2-1 Bug#301966: kmail: crash when changing spe

Bug#364705: libcvsservice-dev: libcvsservice.la refers to libXrender.la

2006-04-24 Thread Jeremy Laine
Package: libcvsservice-dev Version: 4:3.5.2-1 Severity: important $ grep libXrender.la /usr/lib/libcvsservice.la dependency_libs=' -L/usr/lib -L/usr/share/qt3/lib -L/usr/X11R6/lib /usr/lib/libkdecore.la /usr/lib/libDCOP.la -lresolv -lutil /usr/lib/libart_lgpl_2.la /usr/lib/libidn.la /usr/lib/libkd

Bug#341360: marked as done (sudo kwifimanager creates a root owned .ICEauthority which stops Gnome from logging in)

2006-04-24 Thread Debian Bug Tracking System
Your message dated Tue, 25 Apr 2006 11:22:32 +0800 with message-id <[EMAIL PROTECTED]> and subject line Closing 341360 has caused the attached Bug report to be 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 r

Processed: Forwarded

2006-04-24 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 303138 - fixed-upstream #considering that the fix is incomplete and Unknown tag/s: #considering, that, the, fix, is, incomplete, and. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge

Bug#342003: marked as done (IMAP Attachment Size = 0)

2006-04-24 Thread Debian Bug Tracking System
Your message dated Mon, 24 Apr 2006 21:32:40 -0400 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 the

Bug#312315: marked as done (kmail: kdepim-kio-plugins version should be sepecified in Recommends)

2006-04-24 Thread Debian Bug Tracking System
Your message dated Mon, 24 Apr 2006 19:38:20 -0400 with message-id <[EMAIL PROTECTED]> and subject line Obsolete has caused the attached Bug report to be 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

Bug#318033: marked as done (Kmail Errore avvio)

2006-04-24 Thread Debian Bug Tracking System
Your message dated Mon, 24 Apr 2006 19:42:53 -0400 with message-id <[EMAIL PROTECTED]> and subject line Obsolete has caused the attached Bug report to be 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

Bug#263860: marked as done (kmail: relocation error: /usr/lib/libkmailprivate.so.0)

2006-04-24 Thread Debian Bug Tracking System
Your message dated Mon, 24 Apr 2006 19:31:09 -0400 with message-id <[EMAIL PROTECTED]> and subject line Obsolete has caused the attached Bug report to be 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

Bug#292059: marked as done (kmail: crashes while starting)

2006-04-24 Thread Debian Bug Tracking System
Your message dated Mon, 24 Apr 2006 19:31:09 -0400 with message-id <[EMAIL PROTECTED]> and subject line Obsolete has caused the attached Bug report to be 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

Bug#351029: marked as done (kmail: crashes on startup)

2006-04-24 Thread Debian Bug Tracking System
Your message dated Mon, 24 Apr 2006 19:14:27 -0400 with message-id <[EMAIL PROTECTED]> and subject line Seems obsolete has caused the attached Bug report to be 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 r

Bug#364677: Knode rejects e-mail address for posting

2006-04-24 Thread Jan Luehr
Package: knode Version: 3.5.2-1+b1 Hello, I'm currently unable to post anything with knode. Everytime I try to post a message, knode complains about my e-mail address being invalid (translated: Please enter a valid e-mail address in settings -> identity) However, I entered [EMAIL PROTECTED], w

kdepim 4:3.5.2-1 MIGRATED to testing

2006-04-24 Thread Debian testing watch
FYI: The status of the kdepim source package in Debian's testing distribution has changed. Previous version: 4:3.4.3-1 Current version: 4:3.5.2-1 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information.

Bug#364630: FTBFS with GCC 4.2: invalid use of incomplete type

2006-04-24 Thread Martin Michlmayr
Package: koffice Version: 1:1.5.0-1 Your package fails to build with GCC 4.2. Version 4.2 has not been released yet but I'm building with a snapshot in order to find errors and give people an advance warning. I assume the problem below is because G++ is constantly becoming stricter regarding the