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

Bug#321102: Bug#350851 & Bug#321102: KMail data loss still not fixed



Hi Adam,

On Tue, Jan 09, 2007 at 06:18:25AM -0600, Adam Porter wrote:
> >
> > So, you do not use kmail anymore, go to the kde bugzilla and see people
> > is still suffering this bug in kubuntu and decide to re-open this bug
> > in the Debian BTS?
> >
> > The commit that should fix this bug was not committed before the kde3.5.5
> > release, so only distributions that have hand-picked the fix from svn had
> > it included.
> > It is 'closed' in kde bugzilla. 'Verified' is the 'step' after 'fixed'
> > in bugzilla wordings. Verified that it is fixed). Don't mix it with
> > 'confirmed' which is a confirmation that the bug exists.
> >
> >
> > Ana
> 
> Ana,
> 
> If you check the latest reports on KDE #104956, you'll see that Christian 
> Maluck reports mail loss with the 1.9.5 version in Kubuntu, which checking 
> the changelog reveals to have the patch that is merged upstream in 3.5.5, 
> which means it has the same patch that Debian has.
> 
> Clearly, regardless of the upstream bug tracker's "status" field (which I and 
> others would change but are unable to), this bug is not solved.  I just 
> experienced it myself a short time ago, and others are also experiencing it.  
> Why don't you just reopen this bug, rather than asking me to open an entirely 
> new bug and throwing away the logs associated with this one?
> 
> This is a severely damaging bug resulting in mail loss both locally and on the 
> server.  Please reopen it until it is truly fixed.
>

As i told you i think you have a different problem that is not the same bug.
You can never swear a bug is totally fixed, but so far, we have no evidence
to think this bug is still unfixed.
 
Kubuntu's packaging of kde 3.5.5 was done separately from ours, and from what 
I have seen they're not applying the patch that fixes this issue.  
Upstream bug 104956 (http://bugs.kde.org/104956) has a patch attached to it 
that was applied to KDE's 3.5 branch after 3.5.5 was tagged. We have included 
that patch and it seems to fix the issue. This problem still occurs in other 
distros (like Kubuntu) because they have not included that patch yet.  
It will be fixed for them in KDE 3.5.6.

Ana






Reply to: