puredyne-team team mailing list archive

[danstowell <danstowell+launch@xxxxxxxxx>]

Yes I think that's how they do it, however on the backports webpage they
do warn that the combination is less tested than the main repos.

I tested out enabling karmic-backports and it works fine to build a
working liveUSB. The ubiquity is 2.0.9 and so it happily installs on my
Eee without complaints. (However, the resulting install is still
nonbooting but let's assume for now that's a local issue.) So I think
enabling backports would be OK, however I do warn you that it ups the
footprint a bit, presumably because quite a few things get updated. When
I install onto my Eee HD it takes up this much disk according to df:

-backports: 2.9G  87%
+backports: 3.0G  91%

So that says backports grows the installed footprint by something like
4%. It's not much but it's not nothing. If this seems OK then fine;
alternatively the ubiquity issue could be fixed by adding a patch in
chroot_local-hooks.

-- 
Ubiquity 2.0.6 crashes when installing on Eee; need >=2.0.7
https://bugs.launchpad.net/bugs/493189
You received this bug notification because you are a member of puredyne
team, which is the registrant for Puredyne Live.

Status in Puredyne liveCD/DVD/USB/HD: New

Bug description:
Launchpad bug #462462 stops me from doing a ubiquity install on my Eee 701. Ubiquity 2.0.6 (in karmic repos) has this problem; said to be fixed in 2.0.7 (in karmic-updates repos). Is it reasonable to add karmic-updates to the repos list used to build p:d? If so that would probably fix this.

(It's worth mentioning that I manually patched the bug and repeated to get a happy installer; however the resulting installation won't boot - maybe connected, maybe some other issue)