Processing commands for [EMAIL PROTECTED]:
> tags 285126 -sarge
Bug#285126: CAN-2004-1171: plain text password exposure
Tags were: sarge patch security
Tags removed: sarge
> tags 271256 -sarge
Bug#271256: EXPLANATION: Why testing lacks some kde packages in some
architectures
Tags were: sarge
Tag
Your message dated Mon, 3 Jan 2005 21:59:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line KDE 3.3.1 in sarge, closes many RC bugs
has caused the attached Bug report to 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 message dated Mon, 3 Jan 2005 21:59:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line KDE 3.3.1 in sarge, closes many RC bugs
has caused the attached Bug report to 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 message dated Mon, 3 Jan 2005 21:59:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line KDE 3.3.1 in sarge, closes many RC bugs
has caused the attached Bug report to 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 message dated Mon, 3 Jan 2005 21:59:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line KDE 3.3.1 in sarge, closes many RC bugs
has caused the attached Bug report to 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 message dated Mon, 3 Jan 2005 21:59:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line KDE 3.3.1 in sarge, closes many RC bugs
has caused the attached Bug report to 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 message dated Mon, 3 Jan 2005 21:59:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line KDE 3.3.1 in sarge, closes many RC bugs
has caused the attached Bug report to 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 message dated Mon, 3 Jan 2005 21:59:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line KDE 3.3.1 in sarge, closes many RC bugs
has caused the attached Bug report to 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 message dated Mon, 3 Jan 2005 21:59:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line KDE 3.3.1 in sarge, closes many RC bugs
has caused the attached Bug report to 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 message dated Mon, 3 Jan 2005 21:59:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line KDE 3.3.1 in sarge, closes many RC bugs
has caused the attached Bug report to 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 message dated Mon, 3 Jan 2005 21:59:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line KDE 3.3.1 in sarge, closes many RC bugs
has caused the attached Bug report to 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 message dated Mon, 3 Jan 2005 21:59:38 -0800
with message-id <[EMAIL PROTECTED]>
and subject line KDE 3.3.1 in sarge, closes many RC bugs
has caused the attached Bug report to 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
# severity 285128 important
# severity 286516 important
# severity 286521 important
# thanks mate, see you again after the transition
# dato: would you care to bump those security bugs back up to RC
severity?
severity 285128 grave
severity 286516 grave
severity 286521 grave
thanks. vorlon: don
Processing commands for [EMAIL PROTECTED]:
> # severity 285128 important
> # severity 286516 important
> # severity 286521 important
> # thanks mate, see you again after the transition
> # dato: would you care to bump those security bugs back up to RC
> severity?
> severity 285128 grave
Bug#2851
The following bugs against KDE packages were tagged sarge. I've done a
quick review of them and all can be closed now that the 3.3 transition
is finished.
To submitters: the KDE 3.3 packages will be available in your mirror
in about 12 hours.
Thanks to all the people that made the tra
Your message dated Tue, 4 Jan 2005 10:08:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Any chance that, after all error corrections, this gets
included in Sarge?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with
Your message dated Tue, 4 Jan 2005 10:15:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line more bugs closed by the KDE 3.3 tranisition
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 4 Jan 2005 10:15:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line more bugs closed by the KDE 3.3 tranisition
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 4 Jan 2005 10:15:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line more bugs closed by the KDE 3.3 tranisition
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 4 Jan 2005 10:15:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line more bugs closed by the KDE 3.3 tranisition
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 4 Jan 2005 10:15:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line more bugs closed by the KDE 3.3 tranisition
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 4 Jan 2005 10:15:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line more bugs closed by the KDE 3.3 tranisition
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 4 Jan 2005 10:15:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line more bugs closed by the KDE 3.3 tranisition
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 4 Jan 2005 10:15:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line more bugs closed by the KDE 3.3 tranisition
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 4 Jan 2005 10:15:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line more bugs closed by the KDE 3.3 tranisition
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 4 Jan 2005 10:15:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line more bugs closed by the KDE 3.3 tranisition
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Your message dated Tue, 4 Jan 2005 10:15:47 +0100
with message-id <[EMAIL PROTECTED]>
and subject line more bugs closed by the KDE 3.3 tranisition
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is
Filip Van Raemdonck wrote:
reopen 282416 [EMAIL PROTECTED]
tags 282416 + patch
thanks
On Thu, Dec 09, 2004 at 02:17:13PM -0500, Jose Luis Tallon wrote:
We believe that the bug you reported is fixed in the latest version of
bacula, which is due to be installed in the Debian FTP archive:
Hi!
This bug has also bitten me, and a lot of other people it seems.
It is noted upstream in this report:
http://bugs.kde.org/show_bug.cgi?id=90320
From comment #11 and #14, the fix has not made it too 3.3.2, it seems. I
figured it may be useful for the maintainers too, in case the fix could
b
Processing commands for [EMAIL PROTECTED]:
> tags 285794 + upstream fixed-upstream
Bug#285794: kmail crashes when deleting all messages of a folder
There were no tags set.
Tags added: upstream, fixed-upstream
> forwarded 285794 http://bugs.kde.org/show_bug.cgi?id=90320
Bug#285794: kmail crashes w
Processing commands for [EMAIL PROTECTED]:
> reassign 288553 kgpg
Bug#288553: all encryption fails with "public key not found"
Bug reassigned from package `gnupg' to `kgpg'.
> retitle 288553 writes invalid encrypt-to line to gpg config file
Bug#288553: all encryption fails with "public key not fo
forwarded 281628 http:
=?iso-8859-15?q?//bugs=2Ekde=2Eorg/show=5Fbug=2Ecgi=3Fid=3D73999=0D=0Athanks?=
=?iso-8859-15?q?_=0D=0A***_Please_type_your_report_below_this_line_***=0D=0AI_h?=
=?iso-8859-15?q?ave_been_bitten_by_this_bug_too_=28have_a_backtrace_somew?=
=?iso-8859-15?q?here=29=2C_=0D=0Ao
Better quality, better prices, better choice!
We are waiting for you here:
http://6eo30dg.mnlenekn.info/?sK.Qu4Z8w0zaXsszWxEa0r
Remove me from the list:
http://6eo30dg.mnlenekn.info/EOsrWP1Oc?ASCsCI5M88bi344HpzQ4pS5
Processing commands for [EMAIL PROTECTED]:
> tags 281628 + upstream fixed-upstream
Bug#281628: kmail: crashes when filtering more then one mail
There were no tags set.
Tags added: upstream, fixed-upstream
> forwarded 281628 http://bugs.kde.org/show_bug.cgi?id=73999
Bug#281628: kmail: crashes when
Package: kdelibs-data
Version: 4:3.3.1-4
Severity: normal
While upgrading my system with aptitude from KDE 3.3.2 to KDE 3.3.1,
the package kdelibs-data could not be installed. The installation
aborted with the error message
Preparing to replace kdelibs-data 4:3.2.3-2 (using
.../kdelibs-data_4%
I solved the problem in the following way:
1. I uninstalled the package kjscmd by hand, using dpkg. After that,
aptitude was able to continue without problems.
2. I re-installed kjscmd. This also worked without a problem.
-erik
--
Erik Schnetter <[EMAIL PROTECTED]> http://www.aei.mpg.de/~
Good morning
The KDE 3.3 transition seems to be over and to be a success.
At this point I want to send you KDE-Maintainers a big thank you for your work
and wish you (and all readers) the best for the new year.
Thank you
Mario
Subject: kopete silently disconnects from yahoo - possible protocol issue?
Package: kopete
Version: 4:3.3.1-2
Severity: important
*** Please type your report below this line ***
Yahoo plugin connects properly and displays users, but after a random
(and short) period of time, disconnects silently w
38 matches
Mail list logo
