[00:55] hey evand [02:06] ... so i'm working with 8.10 on a system that has an ixgbe NIC... and for some reason it's not built with the installer? looks like perhaps the nic-modules-extra package doesn't get built (ixgbe is in nic-modules-extra for debian unstable's installer) [02:07] (sorry i'm using the initrd extracted from mini.iso) [02:08] i cheated around it by downloading ixgbe source from sourceforge and compiling against the 2.6.27-7-generic kernel, then copying the ixgbe.ko, and dca.ko (which generic config seems to have enabled by default but isn't in the initrd) into the initrd and rebuilding it with cpio... this seems like a hideous work-around-riddled process... anyone have a suggestion for what the right way to do this would have been, short of rebuilding the in [06:53] grub-installer: cjwatson * r806 ubuntu/ (debian/changelog debian/po/et.po grub-installer otheros.sh): merge from Debian 1.43 [06:58] grub-installer: cjwatson * r807 ubuntu/debian/changelog: releasing version 1.43ubuntu1 [08:52] cjwatson: your fix for the cd ejecting worked, but now on exit it is droping out of splash to terminal to display the text to "remove the cd close tray and hit enter:" [08:54] I should point out it works correctly it just doesn't look pretty :)' [10:14] evand: by the way did you and xivulon come to an agreement on whether to allow the size increase on wubi so it works with unr and kne? [10:17] yeah, I think we can take that approach for now [10:40] evand: ahoy, can we haz shtylman's branch for the kubuntu-installer-style package merged and uploaded? [10:40] apachelogger: for ubiquity-slideshow? [10:41] shtylman: what branch is the packaging in? [10:41] evand: that additional package just strips the theming from ubiquity-kde to a seperate package so we can reuse it for other installer-type apps in Kubuntu [10:42] apachelogger: lp:~shtylman/ubiquity/kubuntu-installer-style [10:42] evand: ^ [10:42] oh, I was unaware of the presence of this. Unless shtylman messaged me and I didn't see it. [10:44] evand: there should be a merge request for it... I think... [10:45] yea...there is [10:45] weird, I didn't get an email for that [10:47] Is "Provides: kubuntu-installer-${mangled-version}" necessary? You're not using it in the depends for ubiquity-frontend-kde. [10:52] evand: nope... [10:53] I wasn't 100% on what that did [10:53] okay, fix that and you have my blessing to merge the branch into trunk [10:53] I only need the kubuntu-installer-style package to be a dependency of ubiquity-frontend-kde [10:53] so I just remove that line? [10:54] or write provides: kubuntu-installer-style instead? [10:54] well, you can depend on the exact version, which is what that does [10:55] so Depends: kubuntu-installer-style-${mangled-version} [10:56] would that be the appropriate way? or can I just change to provides: kubuntu-installer-style without ${...} and depend on that? [10:56] what exactly does the ${mangled..} do? [10:57] (see debian/rules) it is a variable containing the version number [10:58] ahh ok ... so is the installer convention to use that for all packages? (that is what I saw to be the case...thus I used it) [10:59] if it's important that new versions of a particular binary package depend on the absolute latest version of the package in question, then yes [11:00] see debian/rules for how mangled-version is generated [11:01] gotcha...so for this package, that will also be used by packages outside of ubiquity, does the Provides line need to provide both with -${mangled-version} and the regular as two things that are provided? or is just specifying the mangled enough? [11:02] but I'd make the Provides be kubuntu-installer-style-${mangled-version} rather than kubuntu-installer-${mangled-version} [11:02] evand: right..I made that change (I think that was a typo from whenever) [11:02] it's fine as you have it (save the change I just mentioned above) [11:03] other packages can depend on kubuntu-installer-style [11:03] evand: cool... I just pushed the fixes to my branch [11:03] awesome [11:03] packaging is new territory for me :) [11:04] sure, I'm often confused by it myself [11:04] the debian policy and new maintainers guide documents are a huge help in my experience [11:04] http://www.debian.org/doc/debian-policy/ http://www.debian.org/doc/maint-guide/ [11:05] oooo [11:07] after I merge this into trunk... is there a process to undergo because this is a new package and we are this late in the release cycle? [11:12] evand: ^ [11:15] binary new [11:16] I'd check in #ubuntu-release to see if they'll grant an exception to let this through before merging [11:16] evand: did you manage to sort out the issue with no pic for the web browser slide? [11:17] davmor2: no, I need to talk to Mozilla Real Soon Now(tm) [11:17] will do [11:22] evand: should that be Really Really Soon Now (tm) [11:23] * evand gets all of this on paper [11:23] davmor2: indeed [11:30] cjwatson: my reading of http://www.mozilla.org/foundation/trademarks/faq.html and http://www.mozilla.org/foundation/trademarks/policy.html leads me to believe that we can temporarily ship the firefox logo *unmodified* in the slideshow while I request to start a conversation with Mozilla on including a version with a reflection. I believe this is the conclusion we came to at the sprint, but I just want to check with you one last time as I very m [11:31] What's the default debconf priority in the server installer? [11:31] medium or high? [11:34] I think high [11:35] if you have a CD handy, debconf-get debconf/priority from a console will tell you [11:35] Handy. [11:35] * soren tries that [11:36] * soren downloads [11:39] soren: do you not have a cd handy I can run it if you want [11:48] evand, kirkland: I've just run the record your passphrase for the first time on Ubuntu. You get a terminal window open with the word passphrase: however when you type in the terminal nothing appears. Once you type in ecryptfs-unwrap-passphrase and hit enter it just closes the terminal window. I'm assuming this is bad [11:48] davmor2: please file a bug on ecryptfs-utils [11:49] evand: wilko [11:53] thanks [11:55] evand, kirkland: bug 429962 [11:55] Launchpad bug 429962 in ecryptfs-utils "terminal displays nothing when trying to record passphrase" [Undecided,New] https://launchpad.net/bugs/429962 [12:05] davmor2: I got it, thanks. [12:06] evand: Default priority on server install is high, fyi. [12:08] ah, good deal [12:12] evand: that's my understanding [12:12] okay cool [12:26] hmm, where did the slideshow go ? [12:26] oh, it just seems to wait until after partitioning now ... [12:27] which gives me a 5min gap at the start on armel [12:48] evand: in end-user setup in an oem install. I select english and click next and get ubi-timezone crashed dialogue window [12:49] davmor2: can you please file a bug with the logs attached? [12:49] evand: yeap I'm just getting them I'm hoping that I might be able to get away with ubuntu-bug but we'll see :) [13:02] evand: bug 429994 [13:02] Launchpad bug 429994 in oem-config "oem enduser setup pops up a crash window" [Undecided,New] https://launchpad.net/bugs/429994 [13:04] davmor2: I'll need /var/log/oem-config.log as well [13:10] evand: no probs I'll grab it after lunch now though [13:45] ubiquity: cjwatson * r3450 ubiquity/ (debian/changelog scripts/install.py): merge lp:~mcasadevall/ubiquity/dove_soc [14:03] good day evand [14:08] evand: added the oem-config.log [14:14] next up wubi [14:18] hi rgreening [14:18] davmor2: thanks [14:18] evand: cjwatson suggestion of apport-collect failed it couldn't find launchpad :( [14:28] mterry: can you figure out bug 429994? it almost looks as though i18n.reset_locale hasn't been called, but I don't see how that could be the case here [14:29] Launchpad bug 429994 in ubiquity "oem enduser setup pops up a crash window" [Undecided,Incomplete] https://launchpad.net/bugs/429994 [14:31] cjwatson, yar, it's on my radar [14:32] thanks [14:41] cjwatson: so does the oem on di still ues ubiquity for the enduser config then? [14:41] use even [14:43] use is the wrong word, I think - oem-config and ubiquity were always pretty similar in a lot of ways, so we merged the code [14:43] and yes, same thing if you did the first stage of installation using d-i [14:46] cjwatson: thanks :) [14:55] davmor2: which desktop environment [14:55] gnome ubuntu [15:13] evand: tried the daily iso last night and it worked in creator.. so presumably the issue resolved itself. [15:14] rgreening: odd === danilo-afk is now known as danilos [15:14] well, it is "casper" so being haunted by weird events shouldn't be a surprise :P [15:17] evand: can you review this and let me know if I can put it in? It fixes the cdrom not showing up if you insert it after creator is running.http://paste.ubuntu.com/271489/ [15:17] It may not be the best way to accomplish it.... but it works... [15:17] http://paste.ubuntu.com/271489/ [15:18] hooray, just got some clarity on the right settings to have for usb-creator in policykit from pitti, should be clear to finish that up [15:19] \o/\o/\o/\o/\o/\o/ [15:19] * rgreening kiks kdesudo to the curb [15:19] rgreening: looks okay, does it work for you? (the system I'm typing from doesn't have a CD drive) [15:19] yes [15:20] I'll commit then. [15:20] please do, thanks a bunch [15:20] how close to policykit do you think we are? Should we release 0.2.6 then get policykit or wait for kit? [15:21] ubiquity: mterry * r3451 trunk/ (debian/changelog ubiquity/i18n.py): Make sure the LANG environment variable is always set (LP: #429994) [15:22] lets wait until tomorrow to release. That way we can at least test the current code some more. [15:22] usb-creator: rgreening * r194 trunk/ (TODO usbcreator/backends/devicekit/backend.py): [15:22] usb-creator: * Update TODO [15:22] usb-creator: * Add support to detect is CD-ROM inserted after creator it started [15:22] but yes, I'm keen on getting a new release in for the impending alpha [15:23] ok. Yeah, we definately want to get a new release in. [15:23] evand: translations pot needs updating.. will you take care of ensureing we update for next release? [15:23] yup [15:23] Riddell and I have kde translations merged in now :) [15:23] as part of the release process for it [15:23] yay! [15:24] so, we should have an app with translations for all front-ends working now :) [15:24] sweet [15:24] unless you mean updating the ubiquity.pot file, in which case that should be done by make update-po (see the Makefile) [15:25] but I'll suck down new translations from Rosetta before I upload the final version [15:25] usbcreator.pot [15:25] and the update-po should work now to include kde and gtk [15:26] usb-creator's in desktop, if you wait until tomorrow you might be too late [15:27] at least if you want it in alpha 6 [15:27] evand: ^^^ [15:27] right, I'll upload it tonight then [15:27] I'm pretty sure we are safe. I have been using and testing like crazy [15:28] evand: not sure if manually running update-po will work... have a look at setup.py for what Riddel helped hack in. [15:28] class usb_creator_build_i18n(build_i18n.build_i18n): [15:28] def run(self): [15:28] build_i18n.build_i18n.run(self) [15:28] print "extracting strings for KDE frontend" [15:28] os.system("./Messages.sh") [15:29] evand: hmm.. though I may not know what I am talking about [15:29] evand: nm. I was wrong [15:29] lol [15:29] it works [15:30] heh [15:31] * rgreening should really go get a coffee [15:31] :) [15:32] ubiquity: mterry * r3452 trunk/ (debian/changelog ubiquity/frontend/kde_ui.py): [15:32] ubiquity: kde: Fix a crasher when using oem-config (don't reference step labels [15:32] ubiquity: that don't exist) [15:32] evand: from the kde perspective, how hard will policykit be? [15:33] evand: still no fix for point to the right place in wubi's grub then :( [15:33] rgreening: the frontend shouldn't need to know about it. The backend communicates with a helper process over dbus that does formatting, image writing, and bootloader installation. If an authorization is needed, policykit will use an agent to ask for it. [15:34] davmor2: point to the right place? [15:34] wiked! [15:34] evand: telling grub where vmlinuz and initrd are [15:34] mterry: r3451> interesting. Why didn't debian-installer/locale exist in the debconf database, though? [15:34] davmor2: yeah, it's not quite all hooked up yet [15:35] we're getting closer [15:35] cjwatson: cool :) [15:35] unfortunately my last test ate my wubi environment so I'm going to have to restart [15:35] cjwatson, rather, it was that 'LANG' didn't exist in env, I think. I could reproduce by unsetting it. Notice the line that says di_locale != os.environ['LANG'] -- it would raise if 'LANG' wasn't a key [15:36] mterry: ah, gotcha [15:36] cjwatson, So I added an explicit check for it, and moved the LANG= code out of the exception so we'd be a bit futureproof [15:36] good catch, I read right over that [15:36] s/exception/try-block/ [15:38] cjwatson: so does that mean the possibility of a working oem install :) [15:39] maybe [15:39] * cjwatson hedges his bets [15:42] evand: what needs to be done to make formatting work? Any progress working around the devicekit bug regarding that? [15:44] cjwatson: the fence gets painful after a bit I found though :) [15:49] https://bugs.freedesktop.org/show_bug.cgi?id=23926 and https://bugs.freedesktop.org/show_bug.cgi?id=23541 need to be fixed [15:49] Freedesktop bug 23926 in operations "Error creating partition: timeout (10s) waiting for partition to show up" [Normal,New] [15:49] rgreening: ^ [15:51] wubi> http://paste.ubuntu.com/271500/ is my current WIP based on lupin trunk [15:59] * davmor2 is now working on m-a against vista and expecting a bang [16:03] cjwatson, evand, I'm looking at a weird python exception in bug 428200. Only crashes for KDE/Russian it seems. If I put a 'print dir(city)' before the crashing line, it works.... If this were C, I would just look for a memory bug, but in Python... Any ideas why such a thing would happen? [16:03] Launchpad bug 428200 in ubiquity "Installer crashed in set timezone" [Undecided,In progress] https://launchpad.net/bugs/428200 [16:08] Oh, nm. I think it's a Qt signals issue. I don't think it's crashing where it says it is [16:08] maybe [16:09] indeed [16:09] * evand happened upon this http://www.nabble.com/Bug-with-non-QObject-signal-callbacks-td24524641.html [16:14] evand, interesting... looks similar [16:16] evand, aha. And the fix is in pyqt 4.5.3, karmic has 4.5.2. [16:28] nice === danilos is now known as danilo-afk [16:37] usb-creator: rgreening * r195 trunk/usbcreator/frontends/kde/frontend.py: [16:37] usb-creator: * Update some of the kde frontend messages to be translated [16:37] usb-creator: * Add unmount source call to __fail method [16:38] we are trying to get the update in for karmic. jump onto kubuntu-devel to see if Riddell has an update [16:39] re: pyqt ^ [16:39] mterry: ^ [16:39] :) [16:40] rgreening, ah, fabulous. I was just looking into filing a sync request [17:08] cjwatson: not surprisingly vista still isn't showing up in grub :( [17:16] usb-creator: evand * r196 usb-creator/usbcreator/frontends/gtk/frontend.py: On second thought, it's better to leave the 'device needs to be formatted message' in place, even though the button is disabled for now. [17:17] usb-creator: evand * r197 usb-creator/usbcreator/frontends/kde/frontend.py: Do the same for the KDE frontend. [17:26] cjwatson: started bug 430141 is there anything else you need adding to the list of log/files I've added? [17:26] Launchpad bug 430141 in grub2 "Vista is not showing up in grub2" [Undecided,New] https://launchpad.net/bugs/430141 [17:50] usb-creator: evand * r198 usb-creator/usbcreator/ (backends/devicekit/backend.py frontends/gtk/frontend.py): [17:50] usb-creator: * Actually set the status to reflect whether a device needs to be formatted (non-VFAT). [17:50] usb-creator: * Use a warning icon when a device needs to be formatted. [18:26] usb-creator: evand * r199 usb-creator/ (40 files in 2 dirs): Updated translations from Launchpad. [18:31] evan: yayayayayayayay go-go creator [18:32] evand: ^ [18:32] hah [18:33] evand: noticing a few translations that could be unified ... [18:33] feel free to make changes where you think it's appropriate [18:33] just not just yet [18:33] evand: the installation is complete messages for gtk, kde and win are out of sync and appear as 3 different strings [18:33] as I have to debcommit -r ;) [18:33] ok [18:34] let me know and I'll clean it up [18:34] * rgreening likes trying to minimize the amount of translations required [18:34] :) [18:36] usb-creator: evand * r200 usb-creator/debian/changelog: releasing version 0.2.6 [18:36] ^ rgreening [18:36] out for the evening [18:36] cheers! [18:40] ty evand. released == uploaded ? :) [18:40] * rgreening assumes yes [20:20] evand, btw, thanks for the MOTU recommendation [22:09] hi all - I'm new here - anyone uber-knowledgable re: Casper? [22:09] (my questions relate to how it adjusts the live system as compared to the source system) [22:11] samba: evand can probably help, but I'm thinking he's turned in for the night (London, UK) [22:11] understood [22:12] evand, when you return - my first question re: autologin - is there a way to disable it? boot-param perhaps? [22:13] casper runs everything in a handful of shell scripts. you can extract that initrd and modify any of them you'd like [22:14] patches can be submitted to make some of them respond to kernel command line parameters i'm sure [22:14] yeah i've been reviewing them, was hoping there's something easier than patching them every time - i'm considering creating and submitting a patch, as you mentione === robbiew is now known as robbiew-afk === robbiew-afk is now known as robbiew [23:35] cjwatson: Got a sec? as noted in livecd-rootfs, ubiquity >= 1.9.4 copies /casper/vmlinuz to /target/boot/vmlinuz-`uname -r` in install.py so livecd-rootfs can strip it from the livefs; for armel+dove we use uImage in the cdimage .img, so no space saving here; the easy solution is to provide a /casper/vmlinuz nevertheless, the expensive solution is to support the two cases in livecd-rootfs and ubiquity; what do you think? [23:36] I already talked with NCommander about this earlier today, and advised him to simply change livecd-rootfs to avoid stripping vmlinuz or uImage or whatever from the livefs [23:36] is there some reason you're revisiting that? [23:37] Reason is he told me to do it in debian-cd [23:37] But that felt like a kludge [23:37] that's nonsense [23:37] well, I mean, one bit of it probably needs to be done in debian-cd [23:37] cjwatson: Should it be a runtime flag or just hardcoded in livecd-rootfs for that subarch? [23:38] grep for vmlinu and you'll see what I mean [23:38] but it's not ALL in debian-cd [23:38] hardcoded for the subarch. we don't have time [23:38] Ok thanks [23:39] sorry, not fair to say it's nonsense, it just doesn't make sense as a complete answer [23:39] cjwatson: flash-kernel uploaded and ubiquity upload wished for at your earliest convenience -- f-k not built yet [23:39] I think it's just adding a kludge [23:39] thanks, it's not in LP yet [23:39] the source is [23:39] yes, it's a kludge, but I wouldn't worry about it if I were you [23:39] err [23:39] I mean cp vmlinuz in debian-cd is one [23:39] oh, right, was looking in the wrong place [23:53] cjwatson: Pushed new livecd-rootfs; thanks for the hints http://paste.ubuntu.com/271749/ [23:54] ubiquity: cjwatson * r3453 ubiquity/ (d-i/manifest debian/changelog): releasing version 1.99.19 [23:55] lool: yeah, looks reasonable [23:55] I hope the cron picks up the new livecd-rootfs [23:55] lool: one thing, could you keep the ubiquity version mentioned in the comment in livecd-rootfs? it's occasionally useful for archaeology [23:56] cjwatson: I kept it at the top I think [23:56] will add down too [23:56] oh, yes, you did [23:56] nah, no need then === robbiew is now known as robbiew-afk