On Wed, 2006-01-18 at 12:41 +0100, Christian Hammers wrote: > reopen 316297 > tags 316297 - moreinfo > notfound 316297 4.0.24-10 > thanks > > Hello Marcos > > On 2006-01-18 Marcos Marado wrote: > > > Those bugs were tagged unreproducible and were waiting for more user > > > input for too long, are for an experimental version or are change > > > requests specific to MySQL 4.0 which will vanish soon (and cannot get > > > into Sarge). Closing them therefore. > > > > This particular bug is reproducible, and is about an issue existent on > > all mysql-server packages: 4.0, 4.1 and 5.0. > > Ok, it was tagged wrong, I reopen it. The issue will not be fixed though. > (regarding the "robustness", all errors are although been logged to syslog, > too!)
Sorry, I may not understand what you really want to say with this. Do
you mean with "will not be fixed" that you see that the dependence on
mailx isn't really necessary and shouldn't be obligatory but only
recommended? If so, why is it not going to be fixed? Lack of
time/man-power/interest in doing so? Or on the other hand you don't see
this as a problem? If not, why do you think that, unlike other distro's,
Debian should force mysql-server users to have mailx?
Thanks,
--
Marcos Marado <[EMAIL PROTECTED]>
Sonaecom ISP
$ perl
''=~('(?{'.('^)@@*@'^'.[).^`').'"'.('`@@[EMAIL
PROTECTED]//[*;)@`//)@|'^'-).[`<@@(^^[`.@@[)^').',$/})')
^Z
signature.asc
Description: This is a digitally signed message part
