I just reproducted this myself now
My complete system is debian unstable with MySQL 5.1.25rc1 from experimental
But that shouldn't matter libmysqlclient15off is still from 5.0.x
The MySQL Client library from 5.1 has 16 not 15off
I have only libapache2-mod-php5, php5-mysql,php5-mcrypt and php5-gd
installed
and of course all depencys of them.
I always used
ab -n 10000 -c 1000 http://localhost/
I downgraded libaprutil1 and libmysqlclient15off to the etch versions
worked fine
I upgraded libaprutil1 to the version currently in testing/unstable
produces one defunct apache process
So the problem is the combination of current libaprutil1 with the old
libmysqlclient15off from etch
Depency is always libmysqlclient15off >= 5.0.27-1
Am I right that this is automatically generated by the shlibs number which
should always be incremented on ABI/API changes, so packages automatically
depend on the new version IF they are regenerated with the new one?
Maybe it's not even worth to discuss that, I didn't found any versioned
depency on libaprutil1 so it won't ever automatically upgraded if just a few
packages are updated from etch to lenny
I'll reply again to Apache bug #480210 so they know about that problem, too
Seems like PHP 5.2.6 is working fine with the old libmysqlclient15off from
etch, if the new libaprutil1 isn't used
So libaprutil1 should be changed not PHP
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
