Ricardo Mones @ 2006-02-07 (Tuesday), 09:50 (+0000)
>   It's not a measure of how important the bug is for you, it has a
> quite different and precise meaning.

I'm aware of the meaning of the bug severities, but misread the
sentences on security holes. Now it seems pretty clear to me, that a
grave problem has to give full access to all of the users data. Sorry
about that unjustified escalation.

>   Sorry, not reproducible here. Can you provide more details about
> your config: type of accounts you're reading and composing, library
> versions (you should have used bugreport for this), any other detail
> about the system that make it different (custom kernel, custom
> libraries you may have).

I keep my messages on an imap server running Courier. Not sure about the
version, but probably the one from sarge. My client is tracking etch,
without any oddities in its setup.

>   This is not the first time you report a bug and say you're not
> willing to help solving it. I don't figure out why do you think that
> attitude will encourage me to spend my free time in solving it for you.

This might be a problem of cultural difference. I'm not having a bad
attitude, I'm considering myself being honest. Sorry about speaking bad
about your country, but one thing I hated when I lived in Spain was
when people gave promises, and then did nada de nada. When we up in
Scandinavia say we shall do something, we do it. When we're not sure
about it, we say no - even if it might mean the same as a maybe-style
yes in the Mediterranean.

As long as you continue to show that you take your role as a maintainer
seriously, I'll try to help solving the problem. One thing to remember
here is that I am not even using the software. The only thing motivating
me to file the report is the over all quality of Debian.
 
>   Certanly the cause was not found but the reason for closing is clearly
> stated as well as the actions you could have taken.

Fair enough. I would probably have taken another approach if I were a DD,
but you're free to work in that way if it works best for you.

> > I might set up a test environment, with toy servers - if asked to.
> 
>   This is only valid if bug gets exposed in test environment too.
>   Can you create a clean chroot in your problematic box and try inside?

I'll try to reproduce this in an environment where it wont hurt
production data, and get back when done.

>   We don't hide problems by removing packages. Furthermore I have the
> sensation that the rest of Sylpheed-Claws users in testing won't agree
> with your suggestion :-P

Packages with unfixable RC bugs should be removed, but since we now
agree this one isn't RC - it's not relevant.
--
/Martin


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to