[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#560957: closed by Lisandro Damián Nicanor Pérez Meyer

fixed 560957 4:4.3.1-1

On Sun, Feb 21, 2010 at 08:51:44PM -0900, Florian Aldehoff wrote:
> Hi Lisandro,
> I disagree with closing this bug. As similar bug reports like 
> https://bugs.launchpad.net/kdepim/+bug/158978 and 
> https://bugs.kde.org/show_bug.cgi?id=140443 indicate, a rewrite of the dimap 
> system in newer versions of kmail makes this bug in Kmail 1.9.9 
> unreproducible with KDE 4.2+. However the bug continues to exist in KDE 
> 3.5.10 and makes Kmail unusable unless I have a second backup IMAP server to 
> recover deleted messages. You switched the bug status to "more information" - 
> what else do you need to know?

The bug can be closed with a version (doing it now) marking it is fixed in 4:4.3.1-1.
This will mark the bug fixed in unstable and for the next Debian stable release but 
it will continue appearing as open in stable (KDE 3.5.10)

> Apart from this bug I'm a happy user of 3.5 and not to eager to switch to KDE4 
> prior to the next Debian stable release - actually I consider staying with 
> 3.5 even when Debian 6 is out. Any chance that the improvements in newer 
> Kmail versions are backported to Kmail 1.9.9?

I am afraid the answer is no. KDE 3 and KDE 4 are quite different and development 
of KDE 3 is dead now. 
The only KDE 3 bugs that will be fixed are those security bugs that a real


> Am Sonntag, 21. Februar 2010 17:57:05 schrieb Debian Bug Tracking System:
> > This is an automatic notification regarding your Bug report
> > which was filed against the kmail package:
> >
> > #560957: kmail deleted contents of inbox with dimap
> >
> > It has been closed by Lisandro Damián Nicanor Pérez Meyer
> > <perezmeyer@gmail.com>.
> >
> > Their explanation is attached below along with your original report.
> > If this explanation is unsatisfactory and you have not received a
> > better one in a separate message then please contact Lisandro Damián
> > Nicanor Pérez Meyer <perezmeyer@gmail.com> by replying to this email.

Reply to: