> Hello anonymous user ;-) Sorry; I'm scrupulous about keeping my main e-mail address off of publicly trollable archives, and I can either use an obvious alias or make up a plausible one. I'm never sure which is more polite.
> This is more or less intended. mysql-server (4.0.x) is now obsolete. > As the new branch has the package name mysql-server-4.1 (or alternatively > mysql-server-5.0) I needed a way to "force" the user to upgrade to at > least mysql-server-4.1. So everytime they try to upgrade mysql-server > they are now, due to the dependency, forced to install mysql-server-4.1. > This conflicts with mysql-server which should be no problem as this > package is no longer needed. > > That this does not happen fully automated is also partly intended because > I don't like to upgrade a database server to a new major version without > telling the admin. > > In my tests the upgrades worked well this way with dselect and apt-get. > Did it just look "maybe not intended" to you or did it really leave you > with a broken installation? Ah. Yes, it achieves the above goal; I did not get a broken installtion, just confused as to why, when told to install the new version of mysql-server, aptitude marked it for deletion. I gurss it was the description of mysql-server that confused me: > This package forces an update from mysql-server (3.23 and 4.0) which was > shipped in Debian Woody and Sarge to mysql-server-4.1 (and later maybe > mysql-server-5.0 which is currently also available for the very brave). The reference to 5.0 in the future suggested to me that the package was intended to be left around like other transitional packages, and the way it was impossible to do that looked weird to me. (You have to admit, deliberately designing a package to be uninstallable *is* a bit weird.) The more usual way is to have a mysql-server package that just depends on mysql-server-x.y, but since there was no mysql-server-4.0 package, I see how that gets exciting. Perhaps change the text to something like: "This stub package depends on mysql-server-4.1, which in turn conflicts with this package. Thus, it is not installable. The point of this exercise is to cause an upgrade to mysql-server-4.1, but not a silent one. "Upgrading MySQL from 4.0 to 4.1 is generally painless (it's a minor version upgrade), but it's worth checking your database users to make sure there are no problems. Known gotchas are: "- In /etc/mysql/my.cnf, the old_passwords configuration variable is now obsolete and unrecognized. It should be deleted. - (etc.)" (For the benefit of debian-legal's collective sphincter pressure, the above text is placed in the public domain.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
