On Fri, Apr 01, 2005 at 05:15:08PM -0800, Mark Rushing wrote: > I'm curious - doesn't the next Debian release come from sarge, not sid?
from sarge, but it has to trickle through sid to sarge. have you tried the later version of mysql-server? > I think that severity "grave" is what's supposed to be assigned when a > package doesn't start at all - which is a little bit more than it just > not "not doing something it's supposed to do". if it didn't work for anyone, then i think that would qualify as grave. but -2 only seemed to have problems with some people and not others, which makes it fall under something closer to a important classification imo. see: http://www.debian.org/Bugs/Developer#severities for the official classification. > I was following the testing path - in apt - and changed away from the > mysql-server package to mysql-server-4.1 package instead. > > The mysql-server-4.1 package in testing works great. i'd really appreciate if you could find out if the latest 4.0 fixes the problem, so we can authoritatively close this bug. > There is nothing related to NIS or LDAP going on. No mention of it in > nsswitch.conf i'm still suspecting it might be related to mysql was built in -2, and like i said we can't know without working more on the bug. > Seems to me that in testing, the mysql-server package should be replaced > with the mysql-server-4.1 package ah, if only life were that simple. both packages provide different and sometimes incompatible libraries (libmysqlclient), which many other packages depend upon. it is a truly tangled web we weave. after sarge, 4.0 will probably disappear in place of 4.1 and 5.0 existing side-by-side. sean --
signature.asc
Description: Digital signature
