[09:15] <dpm> good morning ev, cjwatson. How is the POT template of ubiquity created (the one for the installer, not the one for the .desktop file on the live installation)? I've had a quick look at the sources and I couldn't quite figure out how. I'm just looking at bug 533859 and I thought it might just be a matter of the template not being up to date and not yet containing those strings missing for translations
[09:28] <cjwatson> dpm: by running debconf-updatepo by hand
[09:28] <dpm> ok, thanks cjwatson
[09:59] <CIA-3> ubiquity: evand * r3897 ubiquity/ (debian/changelog ubiquity/frontend/gtk_ui.py):
[09:59] <CIA-3> ubiquity: Only try to set the focus on the next button when we've handed over
[09:59] <CIA-3> ubiquity: control to the user. Prior to this the quit button was getting the
[09:59] <CIA-3> ubiquity: focus because the next button was insensitive.
[10:07] <cjwatson> dpm: anyway, at least one of those strings has a 'TODO i18n' comment by it
[10:09] <cjwatson> so I think it's just not internationalised yet :(
[10:11] <ev> on it now
[10:11] <dpm> ah, thanks cjwatson, ev :)
[10:51] <CIA-3> usb-creator: evand * r271 usb-creator/ (bin/usb-creator-helper debian/changelog):
[10:51] <CIA-3> usb-creator: Provide a quick workaround for LP 529366 while a better fix is
[10:51] <CIA-3> usb-creator: prepared. Ignore errors on setting the boot flag for the target
[10:51] <CIA-3> usb-creator: partition.
[10:55] <CIA-3> ubiquity: evand * r3898 ubiquity/ (4 files in 3 dirs):
[10:55] <CIA-3> ubiquity: Use translatable strings for the keyboard query widget
[10:55] <CIA-3> ubiquity: (LP: #533859).
[11:00] <CIA-3> usb-creator: evand * r272 usb-creator/debian/changelog: releasing version 0.2.18
[11:02] <ev> michaelforrest: http://people.canonical.com/~evand/tmp/usb-creator-common_0.2.18_all.deb http://people.canonical.com/~evand/tmp/usb-creator-gtk_0.2.18_all.deb
[12:25] <ev> I've heard some reports (one in Millbank, others in bugs) of grub install failing and not going to the "grub install failed, choose a different device to install it on dialog".  Just a heads up, I'm going to run through a test install and see if I can reproduce it.
[12:26] <ev> also, I broke the resize progress bar, fixing nowish
[14:09] <CIA-3> ubiquity: evand * r3899 ubiquity/ (4 files in 3 dirs):
[14:09] <CIA-3> ubiquity: Bring back the resizing partition progress dialog that was removed
[14:09] <CIA-3> ubiquity: with the rest of the automatic partitioning progress dialogs.
[14:09] <ev> cjwatson: your extra parameter to progress_stop ended up having a use after all. ^
[14:14] <cjwatson> ev: can't we keep track of this some other way?  we ought to be able to remember the template used for the topmost progress bar
[14:14] <ev> cjwatson: sure
[14:22] <ev> cjwatson: how's this: http://paste.ubuntu.com/391075/
[14:23] <ev> ah, nesting, damn.
[14:27] <cjwatson> ev: I thought ubiquity.progressposition already kept track of this
[14:34] <ev> Okay. I'll take a look after I'm done hunting down the cause of an apt-setup bug with cruzer micros.
[14:35] <cjwatson> I'm resurrecting a machine to put some giant hard disks in for parted testing
[14:38] <ev> Nice
[15:08] <ev> I really need to pick up a netbook. As much fun as playing roulette with my primary laptop and two USB keys is...
[15:10] <cjwatson> you must be coming up on three years at Canonical soon
[15:10] <cjwatson> laptop refresh benefit ...
[15:10] <davmor2> ev: don't be tempted with the ssd ones ;)
[15:11] <cjwatson> davmor2: why not?  I am :)
[15:11] <ev> May :)
[15:11] <davmor2> cjwatson: not enough space
[15:11] <cjwatson> I've certainly seen laptops with SSDs bigger than my current laptop's hard disk
[15:12] <ev> Ubuntu takes under 3gb...
[15:12] <cjwatson> I'm happy to use fileservers elsewhere for serious storage
[15:12]  * persia has happily used a 4G netbook at UDS.
[15:12] <davmor2> cjwatson, ev: yeah the issue comes when you want to try a side by side with windows :)
[15:13] <cjwatson> davmor2: you can get SSDs much bigger than that
[15:13] <cjwatson> 128GB is not totally unreasonably priced
[15:13] <davmor2> cjwatson: yeah but at the time 8gb was the standard in netbooks :)
[15:13] <cjwatson> yeah, I'm not interested in netbooks :)
[15:14] <cjwatson> not made for people with big hands
[15:14] <davmor2> cjwatson: ev said he was though :)
[15:14] <cjwatson> mm, yeah
[15:15] <ev> Yeah, but my use case for it is only installer development and testing
[15:16] <davmor2> ev: not enough room for side by side or wubi testing.  on 8gb drive windows takes up loads
[15:16] <ev> Sure, I'd plan accordingly.
[15:17] <davmor2> ev: almost certainly I'm just saying :)
[15:17] <ev> Assuming the pound ever rebounds, I can always pick up a big Intel SSD on the cheap in the states
[16:56] <ev> shtylman: can you please provide a changelog message for the outstanding items in your branch?  Also, why did you comment out the progress window code?
[16:57] <cr3> does d-i and/or casper support installation where the installation media is available over an iscsi drive?
[16:59] <cjwatson> cr3: casper doesn't, d-i mostly does
[16:59] <cjwatson> oh, *installation media* available over iscsi
[16:59] <cjwatson> hmm, probably only if your BIOS sets up the iscsi drive to look like scsi
[16:59] <cr3> cjwatson: as opposed to installing onto an iscsi drive
[17:00] <cr3> I have to admit that my knowledge of iscsi is flaky at best
[17:00] <shtylman> ev: I commented it out cause I put back the new style progress bar which was commented out for a quick release right before alpha 3
[17:01] <shtylman> ev: yea...I think I can put some poetry in the changelog
[17:01] <ev> thanks
[17:02] <ev> can you simply delete it then?  We don't need to comment things out when we have a VCS, unless you expect it to be reverted again.
[17:02] <shtylman> ev: yea... I agree... and no.. I hope it doesn't need to be reverted again
[17:02] <shtylman> the goal is for it not to be at least
[17:05] <ev> okay, cool
[18:31] <kirkland> cjwatson: is grub2 taking 3-5 minutes to install the bootloader a bug, or expected behavior?
[18:32] <kirkland> cjwatson: i ask because my automated cloud installations take about 10 minutes per machine, with 3-5 minutes of that being the grub installation step (at least as reported by d-i's status bar)
[19:24] <cjwatson> kirkland: bug
[19:26] <kirkland> cjwatson: okay, i'll reproduce and attach logs
[19:54] <superm1> cjwatson, i grabbed parted 2.2-1ubuntu2 out of NEW and manually installed those binaries (and put symlinks in place so parted_server worked still), but same thing and even calling partprobe still is returning an error, along with new device nodes not being created
[21:22] <shtylman> cjwatson: is there a way to run a script only on the first install of a deb package?
[21:22] <shtylman> and not on subsequent updates?
[21:23] <cjwatson> yes, check debian-policy for the version argument passed to the postinst
[21:27] <shtylman> um... how does one do that...
[21:34] <cody-somerville> shtylman, http://www.debian.org/doc/debian-policy/
[21:34] <shtylman> cody-somerville: yea...I found that document... to say that it helped... well...
[22:04] <cjwatson> shtylman: it's in the section about how maintainer scripts are called
[22:13] <shtylman> cjwatson: yea... I found the order of the parameters and whatnot.. I guess I wan't clear on just how you would check after that... if a simple query against dpkg would do... or if you meant something more complex
[22:17] <cjwatson> you normally use dpkg --compare-versions
[22:17] <cjwatson> although actually, first-install doesn't get a version passed to it
[22:17] <cjwatson> so in fact you'd just test [ -z "$2" ]
[22:18] <shtylman> heh... clever :)
[22:18] <shtylman> thanks
[22:19] <shtylman> my small dabble into the world of deb packages
[22:19] <shtylman> will hopefully end well
[22:20] <shtylman> what does get me ... is that I can't seem to find a way to tell it where to put the generated debs and other files it makes... (when running debuild I mean)
[22:20] <shtylman> maybe I am just not looking in the right places...
[22:25] <cjwatson> they always go in the parent directory
[22:26] <shtylman> and no way to influence that?
[22:26] <cjwatson> it's not configurable, no
[22:26] <shtylman> strange
[22:26] <cjwatson> some things shouldn't be configurable
[22:26] <shtylman> heh
[22:26] <shtylman> location of generated files should be :)
[22:26] <cjwatson> you can always move them with a script if you really care
[22:27] <cjwatson> there's absolutely no point bloating the core development programs with that
[22:27] <cjwatson> there's a 'dcmd' program you can use to get the list of files from the .changes file if you want
[22:27] <shtylman> heh
[22:27] <cjwatson> but many tools work better with them in the parent, so honestly I suggest you get used to it :)
[22:27] <shtylman> will have to do that... I suppose ..
[22:27] <cjwatson> for example if they're in the parent directory then you can invoke debc without arguments to list the contents of the thing just built
[22:28] <cjwatson> or debi
[22:28] <shtylman> thats kinda cool
[22:44] <shtylman> cjwatson: on a different note... what does bzr builddeb do then?
[22:44] <shtylman> cause it puts things in a different directory...
[22:44] <shtylman> voodoo magic?
[22:44] <cjwatson> not especially, it copies the source tree to a different directory and changes to that directory before starting the build
[22:45] <shtylman> :(