Ubuntu Dapper in qemu (or rather no Ubuntu Dapper in qemu)

I received an email saying that epilicious didn’t work very well in epiphany 1.9.x. Since Debian isn’t packaging pre-releases of GNOME 2.14 I decided to try to get Ubuntu Dapper installed in a qemu image. I tried using the age-tested method of installing a stable version first (Breezy), and then upgrading to the unstable, not-yet-released version (Dapper).

It literally took hours to get Breezy installed. A small change of /etc/apt/sources.list later I was ready to move on to Dapper. More than 500 packages were needed to be downloaded for the upgrade. During the upgrade there was a conflict due to a file that had been moved from one package to another. There seemed to be no easy way out of the situation as the proposed solution (apt-get -f install) would remove the kernel itself. I gave up and I’ll be looking elsewhere to find a way to check out the GNOME pre-releases.

I’ve never had any problems at all taking a Debian system from stable to unstable. It has required a few steps sometimes, but I’ve always been able to rely on the packaging tools to take me from point A to point B. This really goes to show that Ubuntu, despite it’s origins, isn’t Debian.

I’m gaining more and more confidence that my decision to move back to Debian was the correct decision.

Share

2 Comments

  1. Hi, I’m running Dapper and have just come to try del/epilicious today. Initially, nothing worked, but I think I’ve made some progress. I began by branching with bzr, so I’ll expose my copy if anything worthwhile comes of it.

    So far the changes that have been needed: * Resave the fr.po file as UTF-8, so that make doesn’t fail. * Ignore the idea that you can install single user, as I have no idea how to set gconf keys with no schemas, and I don’t feel like finding out. * Change to make string from the README suggested version to ‘sudo make DESTINATION=/usr/lib/epiphany/2.14/extensions GCONF_INSTALL_SCHEMAS=y LOCALE_INSTALL_LANGS=y uninstall’, so that it actually installs. * Do all the gconf schema install by hand, the entire related section of the makefile never seems to run.

    If I can work out the Makefile problem, I’ll let you know.

    As for installing dapper, starting from a flight cd image is the way to go, but there will probably be people who would appreciate if you report the problems moving from breezy too!

  2. I’m glad you’re interested in epilicious. I’m even more glad you’re willing to improve on it. Let me know whe your bzr repo is available.

    I’ve received and applied a patch that converts fr.po to UTF-8.

    I’ve never actually tried the part of the makefile that installs the GCONF schema (I know, my bad!). Any improvements you make to it will be most appreciated.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>