[10:30] <davmor2> cjwatson: I'm running today's live iso to see if it is working.  I get "The installer has detected that the following disks have mounted partitions: /dev/sda ......."
[10:30] <davmor2> however the icon for the disc disappeared as soon as I started the installer
[10:35] <evand1> davmor2: Did you mount those partitions yourself?
[10:47] <davmor2> evand1: nope was on the screen on boot
[10:48] <evand1> was this a CD or USB disk?
[10:48] <davmor2> evand1: cd it's mounting the main hd
[10:48] <davmor2> I'm just going to check a couple of things
[10:49] <evand1> sure
[10:49] <CIA-9> rootskel: cjwatson * r342 ubuntu/ (3 files in 2 dirs): merge lp:~al-maisan/ubuntu/karmic/rootskel/rootskel_1.77ubuntu1
[10:51] <davmor2> evand1: right double checked and it is today's iso. Also when I quit the installer it remounts the hd
[10:51] <evand1> I'll take a look
[10:52] <cjwatson> ... I'm going to uncommit r342, it doesn't seem to be showing up as a proper merge
[10:52] <cjwatson> sorry, should have unbound
[12:10] <evand1> I suspect this has to do with more changes to gnome automounting
[12:13] <davmor2> evand1: could be I clicked on no and the install continued successfully but I think it's odd to have it come up
[12:14] <cjwatson> well, the odd thing is that any partitions are being mounted. IMO we shouldn't be doing that
[12:15] <cjwatson> it sounds like the installer is behaving correctly given the situation
[12:15] <cjwatson> but that the situation is wrong :-)
[12:19] <davmor2> cjwatson: That's my point I think it's odd that it's happening :)
[12:20] <davmor2> the best of it is when the installer starts the icon vanishes like it's been unmounted however if you exit the install the icon comes back which is really weird :)
[12:20] <cjwatson> just saying, desktop bug not installer bug. or maybe casper bug.
[12:20] <cjwatson> which icon?
[12:20] <cjwatson> oh, right, I see what you mean
[12:21] <cjwatson> that's probably because the installer inhibits automounting on startup
[12:21] <cjwatson> and the desktop is responding oddly to that - at a guess
[12:26] <davmor2> cjwatson: Right so it isn't actually unmounted then it's just that the icon is hidden, is that correct?  Or does the drive actually get unmounted?  If the latter is true then should be get the sda is mount text?
[12:27] <davmor2> s/be/we
[12:37] <cjwatson> davmor2: dunno, I'm guessing. You'd have to run 'mount' from a terminal window to tell
[12:37] <cjwatson> davmor2: I would be truly amazed if you got the "following disks have mounted partitions" message if something wasn't actually mounted, though
[12:38] <evand1> they are mounted
[12:38] <evand1> gnome appears to be mounting immediately now
[12:39] <evand1> (this from my reproduction of the issue, things may be different for davmor2)
[12:39] <davmor2> evand1: no sounds about right
[12:46] <davmor2> so should a bug be raised and if so against what?
[12:47] <cjwatson> yes, and not sure where, ask on #ubuntu-desktop
[12:47] <cjwatson> it may be that casper just needs to inhibit something
[12:48] <cjwatson> (since it could be that the behaviour is reasonable for non-live-CD systems, although I wonder how it handles journalled filesystems)
[12:58] <davmor2> cjwatson: could you help out on #ubuntu-desktop I'm not convinced I'm explaining this too well to seb128 please
[15:30] <CIA-9> usb-creator: rgreening * r107 usb-creator/usbcreator/ (backend.py kde_frontend.py): (log message trimmed)
[15:30] <CIA-9> usb-creator: Fix a bug in backend.py (line 144 - incorrect property for mount point)
[15:30] <CIA-9> usb-creator: More work on kde_frontend.py
[15:30] <CIA-9> usb-creator: - implement set_targets (partially completed)
[15:30] <CIA-9> usb-creator: - start for fix add_source
[15:30] <CIA-9> usb-creator: - implement get_target
[15:30] <CIA-9> usb-creator: - fix a unicode to str bug in add_file_source_dialog
[15:57] <CIA-9> usb-creator: rgreening * r108 usb-creator/TODO:
[15:57] <CIA-9> usb-creator: Moved branch development to lp:~kubuntu-members/usb-creator/kde-frontend
[15:57] <CIA-9> usb-creator: (easier for others to contribute)
[15:57] <CIA-9> usb-creator: Added TODO list
[16:45] <NCommander> cjwatson, so I managed to work out why d-i on sparc keeps failing, and why the ia64 kernel keeps causing the floppy image to go insane with its build size (and why the kernels are no longer compressed :-/). I should hopefully have a fix for that as soon as I'm compiling kernels. I also have a fix for the FTBFS on arm which I will (re)post in a branch shortly
[16:50] <cjwatson> NCommander: cool, happy to merge branches for that
[16:51] <NCommander> cjwatson, yeah, well, the kernel compression issue is because didn't do the merge sanely, so we've had decompressed kernels since intrepid :-/
[16:51] <NCommander> I need to just check which architectures are affected, I know ia64 and sparc are, not sure on powerpc
[17:04] <cr3> how can I get the pxelinux.0 file corresponding to a desktop image?
[17:18] <evand1> cjwatson: given that bug 41624 and debian bug 417407 hit dead ends ages ago, and I cannot find any code using blockdev --setro in partman or os-prober, do we account for the case of a hibernated system with a journaled filesystem in some other way?
[17:18] <evand1> I suspect we do, given your earlier comments today, but my grepping isn't coming up with anything.
[17:24] <NCommander> cjwatson, lp:~mcasadevall/debian-installer/arm-ftbfs-fixes - armel fixes (not test built yet, but I'll hop on rimu in a little bit and fully test it, but this change puts armel.cfg and the last kernel upload in sync)
[17:39] <cjwatson> evand1: lots of half-arsed exclusions of journalled filesystems all over the place, basically
[17:39] <cjwatson> evand1: we never really dealt with it completely
[17:39] <evand1> yikes
[17:53] <cjwatson> $ bzr merge lp:~mcasadevall/debian-installer/arm-ftbfs-fixes
[17:53] <cjwatson> Nothing to do.
[17:53] <cjwatson> NCommander: ^-
[17:54] <NCommander> WTF?
[17:54] <NCommander> that's strange
[17:54] <cjwatson> I'll try again, but maybe you hadn't completed the push before mentioning it on IRC?
[17:54] <NCommander> cjwatson, no, I did, and when I did bzr log, i see it
[17:54] <cjwatson> still says the same thing
[17:54] <cody-somerville> https://edge.launchpad.net/~mcasadevall/debian-installer/arm-ftbfs-fixes
[17:54] <cody-somerville> Launchpad is reporting an error for that branch
[17:55] <cody-somerville> Revision {svn-v3-list-QlpoOTFBWSZTWZGF0F4AABPRgAAQABK-bR4AIAAhKgGk0eT0oU0yMTExIMb967Iba8QuvgzkikwSS9mEPH4u5IpwoSEjC6C8:48c42b26-1dd6-0310-b98f-a58d8bce7237:trunk%2Finstaller:40109} not present in "12555@48c42b26-1dd6-0310-b98f-a58d8bce7237:trunk%2Finstaller:build%2Fpkg-lists%2Fcd_drivers%2Fpowerpc.cfg".
[17:55] <NCommander> codehosting been twichy recently
[17:55] <NCommander> I see it when I do: bzr log lp:~mcasadevall/debian-installer/arm-ftbfs-fixes
[17:55] <NCommander> hold on
[17:55] <NCommander> I'll kick it onto rookery
[17:55] <cjwatson> if codehosting reported an error for it, that would mean it might not manage to propagate between the various machines that host bazaar.lp.net
[17:56] <cjwatson> that looks like it might be a potentially interesting interaction between stacking and rich-root, and you should file a bug on launchpad-bazaar about it
[17:56] <NCommander> cjwatson, well, your LP branch is old enough that bazaar tosses a warning whenever I branch off it on stacking
[17:57] <NCommander> cjwatson, try rookery.canonical.com:~mcasadevall/public_html/d-i_arm_ftbfs
[17:58] <cjwatson> it's been a bit of a pain to upgrade rich-root branches historically
[17:58] <NCommander> woo :-/
[18:01] <NCommander> cjwatson, disregard that pull, I'm an idiot when it comes bazaar pushing and assuming it takes scp syntax :-/
[18:23] <NCommander> cjwatson, bzr+ssh://rookery.canonical.com/home/mcasadevall/public_html/d-i_arm_ftbfs
[19:11] <cr3> evand1: I got the ubiquity source to find the available preseed key/value pairs and I would like to suggest perhaps providing an example file like in the installation-guide-* packages
[19:33] <xivulon> hi evan
[19:57] <cr3> evand1: I booted the desktop (live) image with the kernel parameter file=/cdrom/preseed/ubuntu.seed which contains a bunch of preseeds but, when I start ubiquity either with no arguments or with --automatic, it seems that nothing is automated
[19:57] <cr3> by the way, I'm currently testing jaunty
[20:04] <cr3> evand1: nevermind, I think I got it sussed
[20:18] <CIA-9> ubiquity: superm1 * rsupermario@dell-laptop-20090608191826-zo3er6fmiisukipk ubiquity/debian/ (changelog ubiquity-frontend-mythbuntu.links):
[20:18] <CIA-9> ubiquity: Update location of Mythbuntu symlinked glade file for changes in
[20:18] <CIA-9> ubiquity: new mythbuntu-common.
[20:24] <CIA-9> ubiquity: superm1 * rsupermario@dell-laptop-20090608192446-ukwpsj5e10cgvbfz ubiquity/ (debian/changelog scripts/mythbuntu/mythbuntu_install.py):
[20:24] <CIA-9> ubiquity: Update location of Mythbuntu example configuration files for changes
[20:24] <CIA-9> ubiquity: in mythbuntu-common.
[21:49] <cjwatson> superm1: 'cia_send_revno = true' in ~/.bazaar/bazaar.conf would be nice
[21:49] <superm1> cjwatson, I thought the last two revisions I sent came up in irc?
[21:49] <cjwatson> superm1: they did, but with revision ids rather than numbers
[21:50] <cjwatson> which are pretty ugly in irc
[21:50] <superm1> ah, yeah i wasn't sure why that was happening - this is a different notebook than i usually commit from
[21:52] <CIA-9> debian-installer: cjwatson * r1106 ubuntu/ (build/config/armel.cfg debian/changelog): merge lp:~mcasadevall/debian-installer/arm-ftbfs-fixes
[22:05] <CIA-9> grub-installer: cjwatson * r781 ubuntu/debian/ (changelog grub-installer.templates): Use GRUB 2 by default.
[22:05] <NCommander> cjwatson, so launchpad stopped acting up?
[22:06] <cjwatson> NCommander: no, I actually merged from rookery but that wasn't so useful for a commit message
[22:06] <NCommander> cjwatson, oh. bother :-/
[22:07]  * cjwatson shrugs
[22:08] <CIA-9> grub-installer: cjwatson * r782 ubuntu/debian/changelog: releasing version 1.37ubuntu2
[22:09] <CIA-9> usb-creator: rgreening * r109 usb-creator/usbcreator/kde_frontend.py:
[22:09] <CIA-9> usb-creator: Some minor function re-ordering (to match gtk_frontend.py - easier to compare)
[22:09] <CIA-9> usb-creator: Removed erroneous call to self.backend.detect_devices in init
[22:09] <CIA-9> usb-creator: Add connect signal for progress bar
[22:09] <CIA-9> usb-creator: Add remove_source function - works with CD eject
[22:09] <CIA-9> usb-creator: Copied some functions from gtk_frontend.py (commented out until re-write)
[22:09] <CIA-9> usb-creator: Still crashes with KCrash is run with a USB stick inserted, but if inserted after, does not
[22:10] <NCommander> cjwatson, are there any plans to move to GRUB2 on any ports architecture? (I know it works on PowerPC and I think it works on sparc)
[22:10] <cjwatson> up to porters
[22:11] <cjwatson> I have no plans to work on it myself
[22:11] <CIA-9> ubiquity: cjwatson * r3274 ubiquity/ (bin/ubiquity-wrapper debian/changelog):
[22:11] <CIA-9> ubiquity: If devkit-disks is available, use that for desktop storage locking
[22:11] <CIA-9> ubiquity: rather than hal-lock.
[22:17] <CIA-9> ubiquity: cjwatson * r3275 ubiquity/ (d-i/manifest debian/changelog):
[22:17] <CIA-9> ubiquity: Automatic update of included source packages: grub-installer
[22:17] <CIA-9> ubiquity: 1.37ubuntu2.
[22:19] <CIA-9> ubiquity: cjwatson * r3276 ubiquity/debian/changelog: releasing version 1.13.2