[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mandrake-cooker
Subject:    Re: Fwd: [Cooker] Mandriva kmail sucks (buggy mandriva patch)
From:       Laurent Montel <lmontel () mandriva ! com>
Date:       2006-05-10 15:11:23
Message-ID: 200605101711.24744.lmontel () mandriva ! com
[Download RAW message or body]

On Wednesday 10 May 2006 16:24, Olivier Thauvin wrote:
> Still no reply, retrying...

Read spec file before to write email
patch10 is never apply into kdepim.
Regards.

> Some people comment already.
>
> ----------  Message transmis  ----------
>
> Subject: [Cooker] Mandriva kmail sucks (buggy mandriva patch)
> Date: Mercredi 12 Avril 2006 21:19
> From: Olivier Thauvin <nanardon@nanardon.zarb.org>
> To: cooker@mandrivalinux.org
>
> For long time now (2 or 3 mandriva release) kmail try to move ~/Mail to
> ~/.Mail. I wasn't sure this behavior was mandriva specific. Now I am sure.
>
> First why mandriva choose to change the change the default kmail behavior
>  ???? This add bug that only appear into mandriva.
>
> Second point: Dear kde team, YOUR PATCH IS BUGGY. I hope they will take
> care...
>
> The patch in kdepim is called: kdepim-3.2-move-mail.patch
>
> The issue, on NFS network, the patch try to move the ~/Mail, which is used
> by the imap server w/o maildir format, and also other mailer, and even a
> ~/.Mail already exists kmail is still complaining at startup, worst, saying
> no it exit, yes, it failed to move the directory.
>
> Into this patch:
>
> void KMKernel::transferMailToPointMail(void)
> {
>   QDir dir = QDir::home();
>   int rc;
>
>   if (!dir.cd("Mail")) return;
>
> Adding a test to check if ~/.Mail already exists before checking is ~/Mail
> exists would save time of many administrator, probably something like
> (untested, no time to loose):
>
> void KMKernel::transferMailToPointMail(void)
> {
>   QDir dir = QDir::home();
>   int rc;
>
>   if (dir.cd(".Mail")) return;
>   if (!dir.cd("Mail")) return;
>
> I can also open a bug report, but I don't want to loose my time on a
> private package that only one or two guy can touch.
>
> Yes I am angry, because this issue appear only on large network, typically
> in a society or research lab where there is many users. The proof that the
> choice of working and making choice alone is bad (which is the case of
> KDE).
>
> -------------------------------------------------------
[prev in list] [next in list] [prev in thread] [next in thread]