Hi, On Thu, Oct 25, 2012 at 03:44:26PM +0200, Christoph Anton Mitterer wrote: > Hi. > > On Thu, 2012-10-25 at 21:26 +0900, Osamu Aoki wrote: > > But if you read history of bug report including patches, you could have > > written a bit kinder tone message. I feel a bit sad to see this message. > Well it wasn't meant particularly personally or offensive,... I just > think the issue is quite serious. > > I see now, that you considered this just to be a documentation > problem... > > IMHO, one needs to look throughout all Debian, to find any places where > mboxo is still used.
Python ! http://docs.python.org/2/library/mailbox.html#mbox and links from there. It argues why it does so. > The problem is, that using mboxo itself (even if documented) is IMHO a > serious bug, as the format is utterly broken. Hmmmm... I thought differently ... But I take this as a chance to improve after your good work with upstream. > Especially no user expects that when he stores mail it's being > irrecoverably cluttered up (which is what mboxo does). > Actually I'd say that most people even don't know that there are > different subformats of mbox. ... I know .... this is old discussion we do not repeat here... > > > 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. > > mboxo has been always so and have been widely used. > I know, and this is actually quite a problem. As I wrote above, most > people don't know this... and AFAIU the corruption inherent to this > format can't be undone. > > > mboxrd is technically superior. > Yes,... an alternative is mboxcl2... but it has also it's drawbacks. > > > > anyone who stores file in mbox should know there are risks as you > > describe. > Phew... I mean I wouldn't call myself uneducated ;-) ... and I was > really shocked when I learned about this recently. > I asked around at my friends, all studied computer scientists and decent > sysadmins... noone knew. I am not arguing this with you. Not all smart people know how much stupidity has been commited by human before. I do not expect it either. My point is it was knowen and documented issue as seen on python. This package only used python as is ... thus suffered. > > I think you are a bit exxagurating severity of trivial part of data > > change. > Actually most people seem to see it like this. I can't join that opinion > however. > I mean the change is little, arguably, but a) it can't be undone > automatically and b) given, that storing mail is the core functionality > of e.g. getmail, it think it's quite severe. That would be the same if > your paint program changes all the colours (just a tiny bit) when you > save your image. > > > > Let's ask release manager how this should be handled now. > Saw your mail :) Thanks for your efforts :) I realize that ML is not for discussion. I post this message to mark this bug actively cared. This bug fix will be my next work within a week :-) Osamu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
