Hi Sean -


have you tried the later version of mysql-server?


Just the 4.1 in testing. And it works great.

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.



So you've had reports of this problem from other people too? I wonder if it might be architecture-dependent - like optimizations or something, in -2. This machine is a vernerable Pentium Pro.


i'd really appreciate if you could find out if the latest 4.0 fixes the
problem, so we can authoritatively close this bug.



Sean, what a pain... ;)

OK - I went and grabbed stuff from unstable, all the necessary dependencies.

At first it was behaving the same way - but it turned out to be the database structure of 4.1 not being right with 4.0....

So wiped the databases and used the 4.0 format...

Verified that the 4.0.24-5 actually works - whereas 4.0.24-2 does not.

So yes, the latest 4.0 (-5) fixes whatever problem existed in -2.

But I've gone back to 4.1 ... ;)

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.



I'm curious - how was -2 built differently? Apparently that might be the problem, if that's what you're suspecting...





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.



hehehe.... Yes. And thank you for helping me sort through it so I could help in my little way.

The coexistence will be nice!

Thanks Sean,
Mark



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



Reply via email to