[02:36] <darknesis> hi -- i'm having trouble installing ubuntu hardy server on one of my machines ... it launches the gui installer off the cd, except it can't load the proper drivers for that same cd drive ... out of 3 identical machines, this is the only one giving me this problem ... any ideas or things to try?  i'm lost
[09:27] <davmor2> morning cjwatson :)  Looking at the stats today alt should work and the base is still 22nd on Ubuntu and 18th on kubuntu is that correct?
[09:27] <cjwatson> desktop CD got broken by an upgrade on antimony, it looks like - I just filed an RT ticket asking for python-feedparser to be installed
[09:28] <cjwatson> alternate installability looks promising
[09:29] <davmor2> cool :)
[09:29] <davmor2> all we are waiting for then is you installer updates to go in for oem then correct :)
[09:30] <cjwatson> everything I have uploaded is on the alternate install CD now
[09:30] <cjwatson> if it's still broken I need to do some more stuff
[09:30] <cjwatson> I'm going to give it a go here shortly
[09:31] <davmor2> My updates have nearly finished here so I'll try shortly :)
[09:36] <davmor2> installing now
[10:19] <CIA-2> oem-config: cjwatson * r509 oem-config/ (build/ltmain.sh configure configure.ac): bump to 1.46
[10:20] <davmor2> cjwatson: damn it same thing :(
[10:20] <cjwatson> ok
[10:21] <davmor2> cjwatson: also the package causing the alt issues was it for quick search in synaptic?
[10:21] <CIA-2> oem-config: cjwatson * r510 oem-config/debian/ (changelog oem-config-udeb.postinst): Suppress user-setup's encrypted private directory question in OEM mode.
[10:21] <cjwatson> davmor2: sorry, I don't understand the question?
[10:21] <cjwatson> oh, xapian? yes
[10:25] <davmor2> Okay well quick search is in synaptic but not working correctly I don't think
[10:26] <davmor2> cjwatson: If I type in epiphany the package list goes blank :(
[10:30] <cjwatson> nothing to do with me, no idea
[10:30] <cjwatson> -> somewhere else :)
[10:30] <davmor2> :)
[10:31] <davmor2> I'm bug reporting it anyway :)
[11:08] <cjwatson> davmor2: odd, the whole system seemed to freeze for me; I couldn't even move the mouse
[11:08] <cjwatson> davmor2: was that the same for you?
[11:08] <davmor2> cjwatson: you using hw or vm
[11:10] <cjwatson> vm
[11:10] <cjwatson> I'm just gathering information, not looking for help or advice
[11:10] <cjwatson> was it the same for you?
[11:10] <davmor2> I'm on hw so had no issues there are a whole bunch of faults with vm
[11:10] <cjwatson> you clearly had issues
[11:11] <cjwatson> did the system freeze or not?
[11:11] <cjwatson> you said oem-config locked up, but I would like to know whether you could still use the mouse
[11:11] <davmor2> cjwatson: No system didn't freeze at all that's a vm issue :)
[11:11] <cjwatson> ok, thank you
[14:17] <davmor2> cjwatson: heno has asked me to start looking into debugging and triaging of installer and kernel bugs.  https://wiki.ubuntu.com/DebuggingProcedures is a section on casper and ubiquity but I was wondering if there was anything I should know about debugging d-i too?
[14:17] <cjwatson> it's sort of hard to explain that without teaching you to be a d-i developer :)
[14:17] <cjwatson> http://wiki.ubuntu.com/InstallerDevelopment might help
[14:18] <cjwatson> a lot of the work there is (a) getting logs (I usually ask people to go back to the main menu and select the "save debug logs" item, which gives you various ways to extract them) and (b) figuring out which part of d-i (if any) is responsible for the problem
[14:19] <davmor2> cjwatson: Okay cool I'll have a mooch through those pages too then :)
[14:20] <cjwatson> there's a paper linked from InstallerDevelopment that explains the general layout of d-i; that's probably useful background
[14:21] <CIA-2> oem-config: cjwatson * r511 oem-config/ (debian/changelog oem-config-prepare):
[14:21] <CIA-2> oem-config: Move oem-config init script link from 12 to 29 so that it starts after
[14:21] <CIA-2> oem-config: hal.
[14:21] <cjwatson> ^- might fix oem ...
[14:22] <CIA-2> oem-config: cjwatson * r512 oem-config/debian/changelog: releasing version 1.46
[14:25] <davmor2> cjwatson: when will that be on iso? tomorrow?
[14:26] <cjwatson> usual rules applky
[14:26] <cjwatson> apply
[14:27] <davmor2> cjwatson: okay cool I won't be around till tomorrow afternoon (need to have an interview for passport in the morning) So I'll try it out then.  Any idea when the fix will go through for live too?
[14:29] <davmor2> I've put in fix released on a couple of bugs that have been an issue for a while.
[14:31] <cjwatson> sorry, I thought I'd explained the ISO build processes already :(
[14:32] <cjwatson> I really don't want to work it out for every single update; it would be much easier if you said where you're missing information about how the ISO build processes work, and then you'll be able to work it out for yourself every time
[14:32] <cjwatson> in general, everything gets rebuilt every day
[14:32] <cjwatson> there are three exceptions that I can think of
[14:34] <cjwatson> (1) packages that are in the d-i initrd (basically anything that gets used by d-i up to and including retrieving installer components), or that are copied into the ubiquity or oem-config source packages (any installer component that's reused by ubiquity or oem-config; look in the d-i/source/ directory in the source package), need uploads of those packages in order to be part of ISOs
[14:34] <cjwatson> (2) if a live filesystem build fails (http://people.ubuntu.com/~ubuntu-archive/livefs-build-logs/) or a CD build fails (http://people.ubuntu.com/~ubuntu-archive/cd-build-logs/) then obviously you won't see it
[14:35] <cjwatson> (3) if the archive is frozen (announced on ubuntu-devel-announce, or see https://launchpad.net/ubuntu/intrepid and check for something like "pre-release freeze") then uploads need archive admin approval before being processed
[14:36] <cjwatson> (4) (I lied about three exceptions) if a package build fails (https://launchpad.net/ubuntu/+source/SOURCEPACKAGENAME) then of course the results won't end up in ISOs
[14:36] <cjwatson> but basically it's almost always the case that any upload will be present the next day assuming that there was enough time for it to get built, and if that doesn't happen, then look in the .list and .manifest files alongside the .iso to check version numbers
[14:37] <cjwatson> I think pretty much all the logs are accessible without needing special privileged
[14:37] <cjwatson> privileges
[14:38] <davmor2> right so it's checking the version numbers rather than the .manifest date then?  That I think is where I was getting confused :)
[14:39] <cjwatson> the .manifest timestamp is a useful quick way to tell whether the live filesystem build failed; if it's significantly older than the .iso then the .iso build was just picking up a previous livefs build
[14:39] <cjwatson> for anything finer-grained than that, look at the version numbers inside .list and .manifest
[14:40] <davmor2> so currently the dates for live is 25th and the manifest is the 22nd so that failed right?
[14:40] <cjwatson> right
[14:40] <davmor2> cool I'm getting there slowly :)
[14:40] <cjwatson> so you look at http://people.ubuntu.com/~ubuntu-archive/livefs-build-logs/ to find out why
[14:41] <cjwatson> looking there (-> intrepid -> ubuntu -> latest), you find that in fact the livefs build succeeded
[14:42] <cjwatson> so the next step is to check the CD build log to see if that failed
[14:42] <cjwatson> (which should be a suspicion anyway since 25th ain't today)
[14:42] <cjwatson> http://people.ubuntu.com/~ubuntu-archive/cd-build-logs/ -> ubuntu -> intrepid -> daily-live-20080826.log
[14:42] <cjwatson> and there's a python traceback at the end
[14:43] <cjwatson> that's what I mentioned this morning
[14:43] <cjwatson> 09:27 <cjwatson> desktop CD got broken by an upgrade on antimony, it looks like - I just filed an RT ticket asking for python-feedparser to be installed
[14:45] <davmor2> Okay thanks for that I'll have a play around with that next time I see the manifest date alter :)
[14:46] <cjwatson> 14:45 <elmo> cjwatson: done
[14:46] <cjwatson> so I've just kicked off a new desktop CD build
[14:47] <davmor2> cjwatson: so everything should be listed as 20080826.1 then :)
[14:47] <cjwatson> should be
[14:48] <davmor2> cool :)
[14:49] <davmor2> good couple of hours to build though right?
[14:50] <cjwatson> nah, the ISO build itself is quick
[14:50] <davmor2> Oh okay
[14:51] <cjwatson> in fact it's done
[14:52] <davmor2> runs rsync script
[14:53] <davmor2> 26.2
[14:53] <cjwatson> erm, yeah, whatever
[15:16] <davmor2> cjwatson: so looking at Kubuntu then it's failing is down to a packing issue with adept and so should be reported to the kubuntu team (if they didn't already know) is that correct?
[15:17] <davmor2> sorry livecd i386
[15:17] <davmor2> http://people.ubuntu.com/~ubuntu-archive/livefs-build-logs/intrepid/kubuntu/latest/livecd-20080826-i386.out
[15:19] <cjwatson> there's generally no need to report installability problems, as we have other ways to track that
[15:23] <davmor2> Right okay.  But that is the reason that the manifest is still on the 18th though due to the build issues that the kubuntu team is having with adept so it's fallen back to the last build that worked is that correct?
[15:26] <cjwatson> sure
[15:26] <cjwatson> old manifest and current iso => busted livefs build
[15:27] <davmor2> cool
[15:31] <CIA-2> ubiquity: evand * r2780 ubiquity/ (4 files in 4 dirs): Add a graphical partition bar to the advanced partitioning page.
[15:37] <cjwatson> coo
[16:36] <ebel> I'm trying to automate the hardy alternative install cd. I've got this isolinux.cfg (http://pastebin.com/m3331a477) and this preseed file (http://pastebin.com/m7a848232), however I'm still getting prompted at the very start of the boot for a language
[16:37] <ebel> (i.e. right before selecting which boot option)
[16:37] <ebel> Is there anyway to force this to default to english?
[16:38] <cjwatson> yes, create /isolinux/lang on the CD with just "en" as its contents
[16:52] <ebel> Thanks cjwatson, that worked a treat! :)
[17:00] <cjwatson> you're welcome
=== superm1|away is now known as superm1
[17:17] <davmor2> cjwatson: Oem still broken on 20080826.2 :(
[17:19] <superm1> cjwatson, thanks for catching those whitespace errors.  i had tested in a vm hand editing the files live, and was using a different editor when i committed them
[17:49] <cjwatson> davmor2: not going into oem-config at all, right? just going straight through to the desktop?
[17:52] <cjwatson> davmor2: (it will really speed things up if you describe the problem rather than saying "broken", though)
[18:12] <davmor2> cjwatson: sorry tea.  Yes oem-config is looping back to oem desktop still.
[18:33] <CIA-2> oem-config: cjwatson * r513 oem-config/ (configure configure.ac): bump to 1.47
[18:35] <CIA-2> oem-config: cjwatson * r514 oem-config/ (debian/changelog oem-config-firstboot):
[18:35] <CIA-2> oem-config: Add a vile hack to avoid clashing with kernel-helper over the debconf
[18:35] <CIA-2> oem-config: database lock. Filed LP #261543 to document that we need to do something
[18:35] <CIA-2> oem-config: better.
[18:36] <CIA-2> oem-config: cjwatson * r515 oem-config/debian/changelog: releasing version 1.47
[18:36] <cjwatson> davmor2: ^- fixes it for me, at last
[18:36] <cjwatson> thanks for persisting
[18:46] <davmor2> cjwatson: has it been updated to the iso's and I'll test it tonight for you
[18:53] <cjwatson> see previous conversation
[18:53] <cjwatson> it'll show up tomorrow morning
[18:53] <cjwatson> I would rebuild, but it's the end of my day and I want dinner I'm afraid :)
[18:54] <davmor2> cjwatson: I was actually wondering if it had been rebuilt :) but that's okay that for all the info today :)
[18:55] <davmor2> s/that/thanks