severity 633799 critical
forwarded 633799 http://article.gmane.org/gmane.mail.getmail.user/4576
stop

Guys... I really can't believe what you did here,... talking about
marking such a highly severe issue that leads to irrecoverable data
corruption back to severity normal.
This is really outrageous.


I recently found the same issue in Evolution:
Debian bug #690741
upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=686258

And it made me really sick how they dealt with it, just to see now that
Debian, from which I'd really have thought it would do better in such a
situation does the same and more or less "hide" things away.


Not aware of this issue, I used both Evolution and when on vacation
getmail and I have now a total of nearly 17000 mails in my archive that
are corrupted.

Osamu, I can't believe my eyes why you severity-normal-ised such an
issue, if you'd not... I (and others) would have had the chance to see
it e.g. via apt-listbugs.


Before I saw this bug at Debian, I reported the same issue again
upstream:
http://article.gmane.org/gmane.mail.getmail.user/4576
which does of course not mean that now they're smarter.


But from Debian side this clearly needs to be handled better. What I
suggested at the Debian bug on the analogous Evolution issue is:
big fat warnings in:
- the NEWS file
- the package descripting
- if possibly in a priority-high dialogue via debconf


If upstream is stupid and doesn't want to fix this, then we really
really must warn our users on that issue.
And even if upstream would fix it, we still would need to warn our users
at least in the NEWS file / release notes... that all their mail from
previous years is likely corrupted.


For the above reasons, reseting the severity again to critical, as it
causes serious (because irrecoverable) data loss.


If you don't want to apply the solving patch in only debian (if upstream
rejects it) I'd be fined with closing this bug (as wontfix) if the above
warnings (NEWS file, package description, debconf dialogue) are
installed.

Again, I need to point out that I'm really disturbed and sad that such a
bug got hidden away in Debian :(



Cheers,
Chris.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to