Re: kdepim -> testing migration status
Daniel Schepler schrieb: > for the kmail bugs with disconnected IMAP losing mails, the problem there is > that nobody afaik has been able to tell the kmail developers how to reproduce > the problem consistently; and without that, it's very difficult to find the > cause of the bug and fix it. I'll try to prepare a kdepim upload tonight if > at all possible, fixing the problems on alpha, and upload tomorrow morning. I agree that the bug is hard to reproduce (especially, when reproducing means data loss) but at least one KMail-developer observed the problem twice: http://bugs.kde.org/show_bug.cgi?id=104956#c36 Although he assumes (hopes) this bug is not present anymore in the current version I want to point out that I observed this bug again last month with the kmail version from sid. I strongly assume that the bug is closely related to "rebuild index file" (don't know the correct English menu entry -- rightclick on a folder -> dimap problem -> rebuild index file). Since this bug seems only to occur with dIMAP- but not with IMAP-accounts, one way to get a recent version of KMail into etch would be to disable dIMAP completely. Kind regards Bastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: kdepim -> testing migration status
Le Lundi 13 Mars 2006 13:49, Rainer Dorsch a écrit : > Daniel, > > kdepim is the only KDE component from 3.5.x which did not yet make it into > testing. It seems that there are several open bugs (and the number is > growing) and has problems on alpha. > > I am just wondering if you plan to upload a new version, do we need to wait > for kde 3.5.2 or what is the strategy here? Is there a place where I can > get this answers without disturbing you? Sorry, I had a bad cold the past couple of days which kept me from working on new packages, and over the weekend I was waiting for the results of the GFDL GR to see whether I'd need to split out the docs into a non-free package. As for the kmail bugs with disconnected IMAP losing mails, the problem there is that nobody afaik has been able to tell the kmail developers how to reproduce the problem consistently; and without that, it's very difficult to find the cause of the bug and fix it. I'll try to prepare a kdepim upload tonight if at all possible, fixing the problems on alpha, and upload tomorrow morning. As for the other bugs on kdepim, most are in fact upstream bugs and there are simply too many of them for me to keep up to date on the status of each myself. You're welcome to help with this if you want (by forwarding bugs to the upstream KDE bts, marking bugs as already forwarded/fixed as appropriate, etc). See http://lists.debian.org/debian-kde/2006/01/msg00215.html>. -- Daniel Schepler
Re: kdepim -> testing migration status
Rainer Dorsch schrieb: > Daniel, > > kdepim is the only KDE component from 3.5.x which did not yet make it into > testing. It seems that there are several open bugs (and the number is > growing) and has problems on alpha. > > I am just wondering if you plan to upload a new version, do we need to wait > for kde 3.5.2 or what is the strategy here? Is there a place where I can get > this answers without disturbing you? All four grave bugs of kdepim complain about data loss, three of them belong to KMail. I know that those bugs are confirmed by upstream yet still open now for almost a whole year. Grepping through the relevant bugreports on bugs.kde.org, it seems like those bugs are unlikely to be fixed in the near future since the disconnected IMAP component relies on KDE's IMAP-kioslave. One possible solution in order to get KMail fixed is to disable dIMAP for now in the Debian package until upstream fixed the problem. I for one switched from KMail to Thunderbird last month (having another folder lost...), which has a far better performance on IMAP-folders and has AFAIK not a single open bug regarding data loss. I know this does not help very much, but I would not declare KMail as "stable" until at least the known grave-bugs are fixed. Kind regards, Bastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
