Only just! Its only 2 lines of code condensed with &&, the first part updates the package database (a list of what packages are available) and the second part installs a MySQL Webmin module (which is basically just a WebUI for changing the MySQL conf file) and MySQL server itself. If MySQL is installed already then it will update it if a newer version is available, although it shouldn't do anything as the most recent update (about a week ago) was a security update so should have been applied automatically already,
Unfortunately TKL joomla 11rc is not taking the mysql-server part (though there is a server built in).
In other words its already at the latest version. It is the same version as is included in Adrian's Magento patch.
I spent a lot of time (you are welcome to read the lower part of this, but my conclusion is tht this must have something to do with the debian.cnf file (directly above my.cnf) as calling InnoDB as the default, no matter what, kills this version, and any thing apt-get will call, in MySQL.
Not 100% sure how you reached this conclusion (even after reading below) but I strongly suspect that whatever the difference is, you will find it in the overlay files of Adrian's Magento patch. Either that or there is something specific that the Magento install does.
This line is in System Variables of the two systems.
ignore_builtin_innodb OFF
Not sure what this means, but assuming that innodb works in Adrian's Magento patch despite this, but not elsewhere then it would seem to me that this is not relevant and is being ignored or overridden somewhere.
The only variable I believe there is left is that Adrian's Magento Build was built from Core rather than perhaps a LAMP build as I expect Joomla was built (because it has a PostFix server also attached).
But the Devs base all appliances on Core so other than extra bits (which I doubt would make this difference) they are in effect the same.
I will peer a bit into the Magento Patch to see if there isn't some other call that was made when installing MySQL. There is probably an extra line somewhere in the "sources" setup which would tie into why the mysql-server command is not taking. (I can't find the sources just this minute)
As I said I'd have a good look in the overlay folder and see if there is something in a conf file somewhere there. Not quite sure what you mean by "sources" here?
I just did a call to "php5-mysql" and got the response in my SSH box:
"the following packages were automatically installed and are no longer required.
webmin-mount
use 'apt-get autoremove' to remove them."
php5-mysql is a mysql plugin for php and I doubt it is relevant to your issue. The other remark you make about webmin-mount is also completely irrelevant. This is basically a minor bug in my opinion. It is just another Webmin module which is completely unrelated. You can either remove the webmin-mount package using apt-get autoremove as suggested (or apt-get remove webmin-mount) or mark it as manually installed (ie not automatically installed) by running apt-get install webmin-mount.
Lets get this fixed somehow.
I strongly suggest you do some background reading on Linux, package management, etc so you can get a clearer idea of what you are looking for and what may or may not be relevant. Also posting on the Ubuntu forums may be worth a shot. Perhaps someone else over there has a solution.
Bottom line: if this is really important to you and its not working with TKL/Ubuntu 10.04 then perhaps you need to consider building a server from scratch based on the newer Ubuntu 10.10 server (which AFAIK includes MySQL 5.1.49 & InnoDB 1.07). Adrian's Magento patch may work on that also although I couldn't be sure.
My 2c
Only just! Its only 2 lines of code condensed with &&, the first part updates the package database (a list of what packages are available) and the second part installs a MySQL Webmin module (which is basically just a WebUI for changing the MySQL conf file) and MySQL server itself. If MySQL is installed already then it will update it if a newer version is available, although it shouldn't do anything as the most recent update (about a week ago) was a security update so should have been applied automatically already,
In other words its already at the latest version. It is the same version as is included in Adrian's Magento patch.
Not 100% sure how you reached this conclusion (even after reading below) but I strongly suspect that whatever the difference is, you will find it in the overlay files of Adrian's Magento patch. Either that or there is something specific that the Magento install does.
Not sure what this means, but assuming that innodb works in Adrian's Magento patch despite this, but not elsewhere then it would seem to me that this is not relevant and is being ignored or overridden somewhere.
But the Devs base all appliances on Core so other than extra bits (which I doubt would make this difference) they are in effect the same.
As I said I'd have a good look in the overlay folder and see if there is something in a conf file somewhere there. Not quite sure what you mean by "sources" here?
php5-mysql is a mysql plugin for php and I doubt it is relevant to your issue. The other remark you make about webmin-mount is also completely irrelevant. This is basically a minor bug in my opinion. It is just another Webmin module which is completely unrelated. You can either remove the webmin-mount package using apt-get autoremove as suggested (or apt-get remove webmin-mount) or mark it as manually installed (ie not automatically installed) by running apt-get install webmin-mount.
I strongly suggest you do some background reading on Linux, package management, etc so you can get a clearer idea of what you are looking for and what may or may not be relevant. Also posting on the Ubuntu forums may be worth a shot. Perhaps someone else over there has a solution.
Bottom line: if this is really important to you and its not working with TKL/Ubuntu 10.04 then perhaps you need to consider building a server from scratch based on the newer Ubuntu 10.10 server (which AFAIK includes MySQL 5.1.49 & InnoDB 1.07). Adrian's Magento patch may work on that also although I couldn't be sure.