tags 690741 -fixed-upstream stop Hi.
Guess that fixed-upstream was automatically set, remove it as ignoring/denying cannot really be called "fixed-upstream". Anyway, Michael, have you had time to look in to the upstream ticket? What do you think about my suggestions, i.e. putting warnings into the NEWS file and release notes and also the package description? As far as I understand upstream, there is even after loads of discussion still no insight that something is severely wrong; and not just with respect to the technical range of the issue itself. Warning at so many places about the corruption may seem overkill (especially as current versions of Evolution use mbox no longer as it's default local storage)... but it's important to realise that people may have used it for years already and should be informed about their archive probably being corrupted. Even _if_ upstream would provide a fix now, then IMHO we would still have to add big warnings in at least the NEWS file and release notes (but no longer the package description), for the above reason. For the time the issue is not fixed, a warning in the package description is IMHO justified and necessary, as mails are being the core business of Evolution... so if their handling is broken, we must warn. Just as we warn e.g. about the security issues in mcrypt's package description. Cheers, Chris.
smime.p7s
Description: S/MIME cryptographic signature
