'Problem' has been solved. The clue was in 'syslog' .... it recorded that MySQl had been unable to open the directory "/home/xxxx/xxxx/xxxx/Database" because it was too full.
Now with a 500gig drive in this box and 250gig on my 'home' directory and only 7% used it couldn't possibly be 'too full'. On taking a look I spotted that somehow the directory (and all it's siblings at that same level) were no longer made up of titles that began with a single upper case and the rest in lower case .. but were all upper case (viz --- Database was now DATABASE) renamed it back to the original and reran the installation through synaptic, ... and it ran flawlessly and my data is still intact. I am being verbose in my explanation in case anyone else comes across a similar issue. Why the directories at that level (seven of them) became renamed to all upper case is the bigger mystery.... but as the original problem has been 'cured' my plea for assistance has been fulfilled. Thanks folks. Ian On Sat, 2007-10-27 at 16:00, Mumia W.. wrote: > On 10/27/2007 06:15 AM, ieb wrote: > > [...] > > E:mysql-server-5.0: sub-process post-installation script returned error > > exit status 1 > > E: mysql server: dependency problems - leaving unconfigured > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
