Update for OurDelta 9.04 Jaunty builds of MySQL

We had to apply a weird tweak as the default Ubuntu Jaunty packages are named something like 5.1.30really-5.0.xx. Several people have filed bugs on it with Ubuntu on Launchpad.

What I suspect happened (unconfirmed!) is that Canonical was contemplating putting 5.1 into Jaunty, had it in a beta but went back to 5.0  before release. Since downgrading by version number is a manual process in apt-get, the above hack allows a downgrade that looks like an upgrade…

Our original Jaunty build worked fine if you were starting from scratch, however an upgrade from the default MySQL on Jaunty would not work. Peter has built 5.1.30really-5.0.77-d8-ourdelta, which upgrades happily from the default Jaunty install or any other earlier install (such as from Intrepid). If you upgrade from an earlier Ubuntu version, do make sure you fix up your /etc/apt/sources.list.d/ourdelta.list with the release name jaunty. Easy as. Then run apt-get update then apt-get upgrade.

Tags: , ,

2 Responses to “Update for OurDelta 9.04 Jaunty builds of MySQL”

  1. Colin Watson Says:

    No, that wasn’t what happened. See the changelog:

    mysql-dfsg-5.0 (5.1.30really5.0.75-0ubuntu1) jaunty; urgency=low

    * No change upload. Rebuild so that libmysqlclient15-dev is again available
    in jaunty. mysql-dfsg-5.1_5.1.30-2ubuntu1 provided a libmysqlclient15-dev
    transitional package. -2ubuntu2 doesn’t provide libmysqlclient15-dev
    anymore. (LP: #316280).

    — Mathias Gug Tue, 13 Jan 2009 13:24:13 -0500

    We pulled in MySQL 5.1 from Debian experimental, because some other packages needed it (Amarok, if I remember correctly, though I haven’t checked). I don’t believe it was ever intended to become the default for everything. Unfortunately the uploader didn’t notice that the mysql-dfsg-5.1 source package delivered a libmysqlclient15-dev, which took over the one previously delivered by mysql-dfsg-5.0. In order to undo this mistake, there was no alternative but to increase the version number.

    Regardless of the structure of the version numbers, any add-ons you deliver to an Ubuntu release will need to have higher version numbers than the packages in the release in order to work properly; it makes no difference at all why the version numbers were changed. You can use dpkg --compare-versions to test this.

  2. arjen Says:

    Thanks for the clarification Colin!