What I ended up doing was simply re-generating a image. If you look at: http://wiki.meego.com/Image_Creation#Installation
It'll give you instructions on how to create your own image. Also the image-creator (mic2) repo has an examples/ folder with kickstart scripts. I used the 2.1-developer-final.ks which I presume is the latest greatest one. the main thing to watch for when creating an image is the --format flag. One of the formats it can't mount. I ended up creating a kvm image and a live-CD image. I forget which one worked, but one of them gave me the same error you got. sudo mic-image-creator --config=examples/2.1-developer-final.ks --format=<replaceMe> --cache=mycache which will generate an image. I *believe* the live cd is the format you want. I created a KVM one as well, which booted into a non-functional X11. As far as I can tell.. currently when you chroot into it, it'll extract everything to a temporary location, mount -o bind a few directories and chroot into that location. But as far as I can tell the changes aren't written back into the image. I might be mistaken about this... but if isn't.. it sure would be nice if there was a way to save changes back to image. You can probably find an image online instead of generating your own... but this should work just fine. Keep in mind, all you get is a Linux environment essentially with no GUI, though there are packages in the repo...and I presume as they release more code.. it'll simply be a matter of yum update to get the latest and greatest toys. On a side note, I was wondering if Nokia or anyone in the community wanted to create a user driven wiki/documentation website/knowledge base? I've found more then a few locations where I wish I could have been able to edit the page and fix it. Replacing the mic2 with mic for one. Pointing problems/solutions to setting up meego etc. -- Samir On Fri, Apr 2, 2010 at 4:58 PM, Graham Cobb <[email protected]> wrote: > On Friday 02 April 2010 22:33:48 Samir Faci (Dev) wrote: > ... >> which generated a .deb installation file. >> >> which I've uploaded here. >> >> http://www.assembla.com/spaces/dummyMeego/documents/b0Vv4-pP4r35fieJe5d-aX/ >>download/pykickstart_1.69.-2_all.deb >> >> I've done this on a Ubuntu 64bit installation, I'm sure there are >> differences between Ubuntu and debian, but you can repeat the process >> or just download the .debian. > > Thanks for your instructions. > > Your .deb didn't work for me because it is for python 2.6 -- Debian Testing > seems to still be using python 2.5. However, I have created a .deb for > python2.5 using your instructions, which can be found here: > > http://www.cobb.uk.net/pykickstart_1.69-2_all.deb > > That fixes the missing pykickstart problem. Now when I try to do: > > su -c "mic-chroot meego-codedrop-ia32-developer-201003311106.img" > > I get the following error message: > > Error: I can't recognize this image type. > > Any ideas (note that this is the IA32 image, not the ARM image so I presume it > is not a QEMU problem). > >> Either ways, condemning Meego because a package is missing from your >> own distro isn't really meego's fault. Especially when it's something >> as simply as install a python egg. > > It is the application developers fault if their application doesn't work on my > system if their intent is to support my system. Unfortunately I am not a > python programmer so I have no idea what a python egg may be. > > Graham > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > -- -- Samir Faci *insert title* fortune | cowsay -f /usr/share/cows/tux.cow _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
