[09:21] cjwatson, for a temporary workaround please approve https://code.launchpad.net/~smartboyhw/wubi/bug-1080090/+merge/134776 [09:22] Having a two word distro into Wubi is certainly more difficult than having one... [09:22] No, I'm with bcbc on this - "Ubuntu Studio" is the correct name, and "Ubuntu-Studio" is an accident of cdimage scripts [09:24] Hm, latest bits on that bug suggest it's still a fair amount of work to fix [09:25] Well, OK, I'll push that, but you are misinformed if you think "Ubuntu-Studio" is the correct name, that's all [09:25] cjwatson, em that please at least fix ubiquity also:P [09:25] Huh? [09:25] cjwatson, in ubiquity I also see Ubuntu-Studio [09:25] Sure, that's due to the cdimage bug [09:25] Which I've never got round to fixing [09:26] cjwatson, ah:D [09:26] It's still incorrect [09:26] cjwatson, yeah..... [09:30] smartboyhw: I'm a little concerned that if I push this then nobody will ever care about the underlying wubi bugs, which will mean that the incorrect flavour name in .disk/info gets even more entrenched. Can you commit to following up the underlying bugs (perhaps with bcbc)? [09:33] cjwatson, sure but then it is difficult to communicate with bcbc since I can't find him at all on IRC. [09:33] Not everyone is on IRC :-) [09:33] He's pretty responsive on bugs [09:34] merged with adjustments now [09:34] ev: Please build wubi r276 for raring when you have a chance [09:36] cjwatson, thx [09:42] cjwatson, can you reference to bug number 1080090 instead of bug number 1070682? I want to use that as a better discussion channel. Bug 1070682 is about ADDING Ubuntu Studio into Wubi, while Bug 1080090 is about fixing the name bug... [09:42] Launchpad bug 1070682 in Wubi "wubi and ubuntu studio" [Undecided,Fix released] https://launchpad.net/bugs/1070682 [09:42] Launchpad bug 1080090 in Wubi "When installing Ubuntu Studio in Wubi, it says that it does not match the words in .disk/info" [Undecided,In progress] https://launchpad.net/bugs/1080090 [09:43] smartboyhw: The useful discussion of the problems is in bug 1070682. [09:43] Launchpad bug 1070682 in Wubi "wubi and ubuntu studio" [Undecided,Fix released] https://launchpad.net/bugs/1070682 [09:43] So I think that is the correct reference for a code comment. [09:44] I can't help where the discussion is. [09:45] cjwatson, umm.... I left a message for bcbc to change the discussion. Next time Launchpad to probably have a merge bugs feature.... (let me ask in #launchpad-dev) [09:51] Haha [09:51] Unlikely :) [09:51] cjwatson, let me file a wishlist bug (LOL) [09:52] I'm sure there's one already [09:52] But only maintenance work is really being done on LP at the moment [09:52] cjwatson, let me find one then [09:53] Anyway, whatever. I've changed the code to refer to both bugs [09:53] cjwatson, oh thanks:P [18:05] The initial install dialog takes a very long time to appear in the latest image - known? [18:05] (the one with 'Try Ubuntu', 'Install Ubuntu' buttons) [22:27] wow, I'm surprised that this actually worked ;) I added an extra 4GB to a wubi disk image on the ntfs disk, then resized the partition with resize2fs all of that from the running system ;) [22:41] hmm, I'm a little confused. Using a preseed with the install, last thing the success_command does it a dist-upgrade which installs kernel: 3.5.0-18-generic. [22:41] But after the reboot a uname -r shows: 3.5.0-17-generic. If I then do a sudo reboot the kernel version is *-18-generic [22:41] am I missing something here? [22:47] veebers: You're missing that there's no initial reboot where you think there is. [22:47] veebers: d-i dumps you straight into the installed system. [22:47] infinity: oh. I could have sworn that I saw the HP logo (indicating a reboot) while watching through the KVM [22:48] perhaps just artifacts from the KVM or something perhaps? [22:48] infinity: that would definitely explain that though :) Thanks I'll explore a little more [22:48] Possibly. Dunno. Or I'm mistaken, I haven't done a standard netboot on x86 in a while. [22:49] But I'm preeeeetty sure there's no initial post-install reboot, unless you script one yourself. [22:53] infinity: so would the success-command be a suitable place to do a 'reboot' or is there a better way? [22:55] infinity: actually I might have a better way