[00:00] <superm1> i'd imagine so
=== ptlo_ is now known as ptlo
[06:43] <lukehasnoname> Major effing flaw in the alternate installer
[06:44] <persia> lukehasnoname, More detail and less emotion leads to better response :)
[06:44] <lukehasnoname> persia: I've spent all day trying to figure the problem and only attempting a Fedora install led me to realize the problem:
[06:45] <lukehasnoname> I was allowed to partition my drive in such a way that my bootable partition was on LVM
[06:45] <lukehasnoname> so it tried installing LILO
[06:45] <lukehasnoname> which didn't work
[06:45] <lukehasnoname> then I thought it was a JFS problem
[06:45] <lukehasnoname> so I reinstalled with a different fs
[06:46] <lukehasnoname> still didn't work, Tried installing grub from a rescue disc. Failed. Figured this might be some remnant of the encrypted partitions I had, among other things, and so I reinstalled both Vista AND ubuntu.
[06:46] <lukehasnoname> didn't fix the problem. FINALLY I tried installing Fedora, which threw a warning when I put a bootable partition on LVM
[06:47] <lukehasnoname> thus I remembered that you can't do that.
[06:47] <lukehasnoname> </report>
[06:48] <lukehasnoname> SO might I suggest it be added to the installer a warning when someone has their /boot on an LVM, at least until grub overcomes that issue
[06:49] <persia> Yes.  You'd want to file a bug.  I'd probably start by filing it against partman-lvm, although it might be something else that ends up being the solution.
[06:50] <lukehasnoname> mk
[06:50] <lukehasnoname> seriously. I resinstalled Ubuntu 4 times and Vista once
[06:50] <lukehasnoname> and fedora .2 times
[06:51] <persia> I understand your pain, but there's no quick fix really.
[06:51] <lukehasnoname> if (/boot is on LVM) alert("NOOOOOOOOOO");
[06:52] <lukehasnoname> >_>
=== cjwatson_ is now known as cjwatson
[21:24] <CIA-1> ubiquity: cjwatson * r2922 ubiquity/scripts/install.py: sort difference set (easier to follow while debugging, and matches what I tested)
[21:30] <CIA-1> ubiquity: cjwatson * r2923 ubiquity/debian/changelog: whitespace
[21:56] <xivulon_> cjwatson, it occurred to me that the metalink.md5.gpg for mythbuntu has to be signed with the cdimage key
[21:57] <xivulon_> the mythbuntu guys will not be able to do that, but is it something that can be organized?
[23:30] <cjwatson> no, they'll need to arrange to sign it with some other key, which wubi should trust if that's needed
[23:31] <cjwatson> unless there's a metalink.md5.gpg built on cdimage.ubuntu.com
[23:31] <cjwatson> I'm not willing to have that key sign things we didn't build