[00:01] <hedkandi> hi
[00:01] <hedkandi> folks, you know you write like gcc -lsomething main.o -o out
[00:02] <hedkandi> well why doesn't it like it when I write
[00:02] <hedkandi> gcc -llibsome.so main.o ?
[00:20] <cjwatson> hedkandi: why do you want to use -llibsome.so rather than -lsome? the latter is the standard and correct form
[00:21] <cjwatson> hedkandi: it'll work without -o, it'll just write to a file called 'a.out' rather than any other default you might have wanted
[00:25] <hedkandi> cjwatson: if you write -lsome it'll go and find libsome.a which is not what I want
[00:27] <cjwatson> hedkandi: the ld manual page states that on ELF systems ld will search for libsome.so before libsome.a (and indeed this matches all my experience), so if it finds libsome.a that's only because it's the best it can do
[00:37] <hedkandi> ooh
[00:37] <hedkandi> cjwatson: I read the gcc man page, and that's what it says
[00:38] <hedkandi> here it is:
[00:38] <bluefoxicy> Every 2.0s: ls /tmp/user/1000/ -l                       Mon Nov 23 19:38:28 2009
[00:38] <hedkandi> The linker searches a standard list of directories for the library,
[00:38] <hedkandi>            which is actually a file named liblibrary.a.
[00:38] <bluefoxicy> hey guys I just realized
[00:38] <hedkandi> so that's WRONG!
[00:38] <bluefoxicy> I've been using pam-tmpdir for like, 2 or 3 releases
[00:39] <bluefoxicy> how about setting this shit up by default?  Huh?
[00:39] <bluefoxicy> or is this gonna be a whiny "IT MIGHT BREAK SOMETHING" argument (because yeah, some stuff will probably scream) like everyone normal in the world?
[00:40] <cjwatson> bluefoxicy: if you can't be polite, please leave
[00:40] <cjwatson> hedkandi: yes, it does seem to be an incomplete description of reality
[00:40] <cjwatson> hedkandi: (perhaps because this varies a lot between platforms)
[00:40] <tsimpson> hedkandi: read the ld manual
[00:41] <hedkandi> it's RUBBISH!!
[00:41] <hedkandi> typical GNU
[00:41] <tsimpson> the gcc is not the linker, it just calls the linker for you
[00:41] <cjwatson> hedkandi: same admonition about politeness goes for you
[00:41] <maco> wow there's a big lack of polite here. do i need to hand out cookies?
[00:41] <hedkandi> I'll leave soon
[00:41] <hedkandi> cheerio
[00:43] <greg-g> maco: if I say something impolite, may I have a cookie?
[00:43] <maco> hahah you can have a cookie anyway
[00:43] <greg-g> :)
[00:43]  * maco gives greg-g a cookie
[00:44] <maco> its more of "if i give you cookies, will you play nice?"
[00:44]  * greg-g takes his cookie and ignores the rules
[00:47] <cjwatson> bluefoxicy: personally I think libpam-tmpdir would be a good idea, and I suggest that you suggest it to the Ubuntu security team in a less hostile way so that it doesn't just put them off wanting to deal with it
[00:49] <bluefoxicy> cjwatson:  I've done so in other cases before, in other contexts, on other distros, ages ago.  I've learned to just skip to the end and see if anyone actually comments meaningfully.
[00:49] <ebroder> Wait, cjwatson, are you looking for http://debathena.mit.edu/pam_mktemp/ ?
[00:50] <bluefoxicy> But at any rate, what's the proper contact for that
[00:50] <bluefoxicy> mailing list or bugfile?
[00:51] <cjwatson> ebroder: I'm referring to the libpam-tmpdir package in Ubuntu
[00:51] <ebroder> Oh, hmm - I wasn't aware of that
[00:51] <cjwatson> bluefoxicy: I'm personally not inclined to give preferential treatment to people who turn up and swear at us; maybe others are more masochistic
[00:52] <cjwatson> bluefoxicy: at this time of night I don't know the contact address offhand, although I can't imagine it would take long to find ...
[00:52] <bluefoxicy> alright.
[00:52] <bluefoxicy> mailing list then.  I'll go find it.
[04:29] <LucidFox> Hmm, so Nouveau is going to be default on Lucid?
[04:29] <LucidFox> Does it support Compiz?
[04:35] <pwnguin> LucidFox: not well
[04:36] <pwnguin> however, it supports resolutions better than nv
[04:41] <HFSPLUS> !ops
[04:57] <mneptok> please ignore the following
[04:57] <mneptok> !ops
[04:58] <nixternal> heh
[04:58]  * Amaranth pokes mneptok
[04:58] <mneptok> please ignore the preceding
[04:58]  * Hobbsee gives mneptok the boot
[04:58] <nixternal> I can't even get op in here...so why am I on that list?
[04:58] <mneptok> ubottu's regex is *horridly* broken
[04:58] <Hobbsee> haha
[04:58] <nixternal> nice
[04:58] <mneptok> i doubt that, you stupid pile of python
[04:58] <Amaranth> nixternal: He dropped the channel specific one so it went back to the #ubuntu one
[04:58] <nixternal> hahahaha
[04:59] <nixternal> ahh
[04:59] <mneptok> and the stupid thing can't learn a new factoid. escaping the - in the channel name allows him to learn, but then you have to escape the channel name in the trigger, as well.
[05:00] <mneptok> ridiculous.
[05:00] <Amaranth> mneptok: The source is available ;)
[05:00] <mneptok> Amaranth: thanks for offering. let us know when you're done.
[05:01]  * StevenK prefers "Noted. Patches welcome"
[05:01] <Amaranth> mneptok: I'll put that on my TODO list right after "rewrite compiz plugin loader"
[05:01] <StevenK> mneptok: Tell me it doesn't do the silly thing and use - as a seperator?
[05:02] <mneptok> StevenK: hear that a lot these days at home, eh? aren't new relationships *awesome*?  :P
[05:02] <mneptok> StevenK: the channel name uses it. apparently that causes some sort of mental breakdown.
[05:03] <Amaranth> StevenK: Channel specific factoids are specified like !foo-#channel
[05:03] <mneptok> anyone have a katana, firearm, or martial arts training and that knows where Supybot core devs live can make some money.
[05:04] <StevenK> Amaranth: Which is silly, yes
[05:04] <Amaranth> mneptok: If you pay for transportation I'm game
[07:55] <dholbach> good morning
[08:03] <pitti> Good morning
[08:06] <dholbach> hi pitti, mvo, MacSlow
[08:08] <MacSlow> hey pitti, dholbach, mvo
[08:08] <\sh> moins
[08:08] <mvo> hey dholbach, MacSlow, pitti
[08:09] <micahg> hi \sh
[08:09] <micahg> ZF is about to release 1.9.6
[08:09] <micahg> what would you like me to do for it?
[08:09] <dholbach> hi \sh
[08:11] <\sh> micahg, when 1.9.6 hits lucid, please do some backports on the ppa and file a bug for a backport and inform scottk that it works (builds) and that he could push the backports from lucid to any release downto hardy
[08:11] <micahg> \sh: should I file a separate bug for each backport, or one massive one with 4 tasks?
[08:11] <\sh> micahg, and did you have a look on the dojo packages I created? (forget the packagenaming right now ;))
[08:12] <micahg> \sh: will you be uploading to lucid?
[08:12] <micahg> \sh: not yet
[08:12] <\sh> micahg, I think a massive one with 4 task should be ok...I really don't know how the backport team is handling those requests
[08:12] <\sh> hey dholbach
[08:13] <\sh> micahg, yepp...
[08:13] <\sh> (for upload to lucid)
[08:14] <micahg> ok \sh, I'll watch for it, do you want me to ping you when they release?
[08:14] <\sh> micahg, I'm following zend :)
[08:14] <micahg> ok
[10:36] <otacon> hi
[10:44] <Keybuk> cjwatson: I have a rough "bzr commit" plugin now ;)
[10:44] <Keybuk> if you have changed ChangeLog, the new lines are put into the commit log
[10:48] <otacon> I'm using linux from late 2007, and i love it. I have a base knowledge of linux, security and networks. I know VBA, BASH scripting, PHP, CSS,and I'm learning python right now. I want to work with linux, but don't know where to turn. I hope someone here can have some suggestion for me. What I must learn, which language is better to learn?
[10:53] <otacon> no one have some suggestion about what must learn a novice developer?
[10:57] <lifeless> mvo: care to merge/deploy my deprecation fix for conflict checker?
[10:58] <mvo> lifeless: I can do that, has sbeattie not gotten write access to this as well?
[10:58] <lifeless> mvo: EDUNNO
[10:59] <mvo> ok
[11:27] <mpt_> amitk, hi, I have a question about the kernel's handling of batteries. Are you a good person to ask?
[11:28] <mpt_> or perhaps apw
[11:29] <apw> come chat to us on #u-kernel
[11:31] <mpt_> ok
[11:51] <dholbach> asac: in thunderbird3.0 is there a way to open tabs with special folders (like starred messages) or can I just open messages in tabs?
[11:51] <dholbach> asac: if not, can I create a special folder for "show me all starred messages"?
[11:55] <seb128> dholbach, traitor ;-)
[11:56] <dholbach> seb128: I still have it running on the laptop - I just wanted to try it out on the desktop because evolution decided to forget about all my preferences/accounts, etc.
[11:56] <seb128> ok
[11:57] <seb128> you can use gconftool --dump /apps/evolution and --load to copy the config if you want
[11:57] <seb128> between the laptop and desktop I mean
[11:57] <asac> dholbach: that works
[11:57] <asac> dholbach: right click ... open new tab
[11:57] <asac> doesnt work?
[11:58] <dholbach> asac: doesn't work - where should I right-click?
[11:58] <asac> on the folder
[11:58] <Keybuk> seb128: not forgetting to copy the .evolution folder too ;-)
[11:58] <seb128> Keybuk, I doubt that one got erased
[11:59] <dholbach> asac: which one? any of them?
[11:59] <seb128> Keybuk, seems dholbach is having gconf config issues, not the first time he got the gconf keys wiped out
[11:59] <Keybuk> seb128: right, but there's a few folder names in there that have to match gconf, etc.
[11:59] <asac> dholbach: err... not sure whta you mean.
[11:59] <asac> dholbach: i can do that for all folders displayed
[11:59] <dholbach> asac: which one should I right-click?
[11:59] <asac> like for my gmail: "starred" works
[11:59] <dholbach> asac: ah ok, so I need to find a way to create that starred virtual folder, then right click it - gotcha
[12:01] <asac> hmm... maybe that exists just because its gmail here
[12:01] <asac> :/
[12:01] <Chipzz> Keybuk: topic got truncated
[12:02] <dholbach> asac: can you create virtual folders or something?
[12:02] <asac> i thought that was possible in the past :/
[12:03] <asac> cant remember out of my head how that was done though
[12:03] <asac> dholbach: join #ubuntu-mozillateam ... i will ping a tbird dev there
[12:04] <dholbach> thanks asac
[12:05] <Keybuk> Chipzz: x-chat thinks that's the longest it can go
[12:05] <pitti> apw: so, for apport's "failed to resume" detection, I guess it uses /var/lib/pm-utils/status? how is the apport report created then? I don't see a sleep.d script in pm-utils which would call apportcheckresume?
[12:05] <Keybuk> Chipzz: in fact, from the log, that's all the topic there was ;)
[12:08] <apw> pitti, in the apport startup script we check for status and report then, so its a boot check
[12:09] <pitti> apw: ah, I see; thanks
[12:09] <pitti> apw: I think I'll move the "record status" portion of 000record to apport proper then
[12:09] <pitti> apw: I committed the "inhibit hibernate" portion to debian's pm-utils now
[12:09] <apw> pitti, thanks for that
[12:16] <pitti> apw: do you know what creates /var/lib/pm-utils/resume-hang.log ?
[12:17] <pitti> nevermind, found it
[12:17] <apw> pitti, .. cool
[12:19] <pitti> apw: FYI, I move the logs/stamps to /var/run/pm-utils
[12:19] <pitti> so that they get cleaned up properly on boot
[12:20] <pitti> if that's okay with you?
[12:21] <apw> pitti, the location was chosen somewhat arbitrarily ... i am comfortable for them to move ... but, they need to be checked during boot before /var/run gets zapped ...
[12:21] <pitti> oh, right
[12:21] <pitti> nevermind, leaving as it is then
[12:21] <apw> if /var/run gets moved to ramfs we are in the poop
[12:27] <Keybuk> apw: moved to?  /var/run *is* a tmpfs
[12:27] <apw> Keybuk, heh then we would be in the poop :)
[12:29] <Keybuk> I don't follow
[12:30] <apw> Keybuk, i mean if pitti hadn't already decided moving those files there would be bad, then we'd be doing the wrong thing
[12:32] <Keybuk> these files need to survive a reboot?
[12:32] <pitti> I think the use case is "suspend, fails, reboot, collect the error"
[12:32] <pitti> so, yes
[12:32] <Keybuk> right
[12:33] <Keybuk> then /var/run is very definitely not the right place for them <g>
[12:33] <Keybuk> FHS-wise, /var/cache or /var/lib would be right
[12:33] <Keybuk> you could probably even argue for /var/spool
[12:33] <pitti> we are using /var/lib/pm-utils/ now, and clean it up in apport's upstart job after checking
[12:34] <pitti> s/now//
[12:34] <Keybuk> ok
[12:37] <bluefoxicy> ugh
[12:37] <bluefoxicy> can't suspend.
[12:37]  * bluefoxicy dd's a 2 gig swap file and tries.
[12:39] <bluefoxicy> huh that didn't work...
[14:00] <smoser> slangasek, can you let me know what you run to publish an image on nectarine ? ie, take a nightly and make it a "release"
[14:02] <soren> Riddell: Could you sync libcloud from unstable, please?
[14:02] <smoser> i'm guessing : cdimage/bin/publish-release but i'm not sure.
[14:04] <Riddell> soren: what's your LP id?
[14:05]  * Riddell takes a guess at soren
[14:09] <soren> Riddell: It is indeed.
[14:12] <Riddell> done
[14:12]  * soren hugs Riddell 
[14:21] <pitti> hey mathiaz
[14:21] <pitti> mathiaz: WDYT about the current karmic-proposed eucalyptus? Most bugs got verified, so in sum it got quite a large number of verification results now
[14:22] <mathiaz> pitti: IIUC there are two bugs left for verification
[14:22] <mathiaz> pitti: I'd like to perform a quick review of them
[14:22] <pitti> mathiaz: ack
[14:22] <mathiaz> pitti: and let you know what to do after that
[14:22] <pitti> thanks
[14:22] <mathiaz> pitti: do you have the two bugs left to be verified?
[14:23] <pitti> mathiaz: bug  #454405 and bug #458163
[14:23] <mathiaz> kirkland: could you verify/review/comment on bug 458163?
[14:24] <kirkland> mathiaz: sure ...
[14:24] <mathiaz> pitti: for bug 458163 I trust upstream for the fix
[14:25] <mathiaz> pitti: so once kirkland acked bug  458163, I think the eucalyptus sru is good to go to -updates
[14:25] <pitti> mathiaz: NB that it is not a real problem if the version does not actually/fully fix a bug
[14:25] <pitti> mathiaz: then we can just reopen it
[14:25] <pitti> mathiaz: however, it must not cause any regressions
[14:25]  * mathiaz nods
[14:25] <pitti> great, so I'll wait for kirkland's ping
[14:25] <pitti> kirkland: cheers
[14:26] <mathiaz> pitti: both ttx and I have tested the sru
[14:29] <kirkland> mathiaz: pitti: I don't currently have a UEC setup
[14:29] <kirkland> mathiaz: pitti: I'll need to install from scratch
[14:29] <kirkland> this will take a while
[14:29] <pitti> kirkland: btw, thanks for your kvm lightning talk; very impressive!
[14:30] <pitti> during that week I learned about the hot add/removal of block devices, qcow2 (both used myself), and the live migration (didn't use that, but is utterly cool!)
[14:31] <kirkland> pitti: you actually inspired that talk :-)
[14:33] <superm1> pwnguin, i dont see why noueveau would support resolutions better than nv.  they're still queried via the EDID for both scenarios
[14:34] <kirkland> pitti: it was this comment by you that made me realize that there are some very knowledgeable people using kvm, but not knowing some of the advanced features:
[14:34] <kirkland> Jul 22 14:33:57 <pitti> seb128: I just learned about "virtio" kvm drives, which are apparenlty go-faster stripes
[14:34] <kirkland> :-)
[14:35] <pitti> yeah, that rocks
[14:35] <kirkland> pitti: i just committed a fix to rootskel yesterday that should make kvm -curses work on ubuntu alternate and server cd's too
[14:35] <kirkland> pitti: which means that we can test server installs in a terminal more easily
[14:36] <pitti> oh, what did you change?
[14:38] <soren> kirkland: Err...
[14:38] <soren> kirkland: How do you expect to test the framebuffer stuff in kvm with this change?
[14:38] <kirkland> pitti: not modprobing the fbcon if running on QEMU cpu's
[14:38] <kirkland> soren: on real hardware
[14:39] <soren> kirkland: How do you expect to test the framebuffer stuff *in kvm* with this change?
[14:39] <kirkland> soren: i do not; i expect to test that on real hardware
[14:40] <soren> I see.
[14:43] <soren> Maybe I'm just being an old curmudgeon here, but I'm not sure I agree that deliberately limiting the amount of bugs we can catch by testing in a VM is a plan filled with awesome.
[14:50] <kirkland> soren: so i could agree that we should allow for an override, like fb=1 or fb=true on the ISO command line
[14:50] <kirkland> soren: but is there any situation (besides testing) where it makes sense to have a kvm running with its console in a much slower framebuffer?
[14:50] <soren> The fact that it's slower is a bug.
[14:51] <soren> kvm is mindbogglingly fast.
[14:51] <soren> QEmu (without kvm) seems to have better fb performance.
[14:51] <soren> I've no clue why this is, though.
[14:57] <soren> kirkland: Is there any reason (besides running kvm on the console) where it's necessary to run without the framebuffer?
[14:58] <kirkland> soren: a) it's amazingly faster, more responsive, reduces install time significantly
[14:58] <kirkland> soren: b) makes it possible to use -curses, do an install through vanilla kvm directly on a remote server in a shell
[14:59] <kirkland> soren: which makes it possible to log the entire session too, copy, paste, etc.
[14:59] <kirkland> soren: so what about my question?
 soren: but is there any situation (besides testing) where it makes sense to have a kvm running with its console in a much slower framebuffer?
[14:59] <soren> How do you log the installer's ncurses stuff?
[15:00] <soren> 15:50:51 < soren> The fact that it's slower is a bug.
[15:00] <kirkland> soren: screen
[15:00] <soren> kirkland: I think it would be much cooler to fix that bug.
[15:00] <kirkland> soren: that's not an answer to my question ...  in what situation (besides testing) do you *want* a kvm running in fbcon?
[15:00] <kirkland> soren: patches accepted
[15:01] <kirkland> soren: i just launched qemu without kvm, and i don't see where it's any faster in the fb
[15:01] <kirkland> soren: are you sure this is the case?  can you take a screen cast of the two and time them?
[15:01] <soren> I want to run it in an fbcon by default so that I don't have to sit down and actively decide to do testing before I spot a particular class of bugs.
[15:02] <soren> kirkland: Probably.
[15:02] <kirkland> soren: the class of bugs being ... ?
[15:02]  * soren has to run for 10 minutes.
[15:02] <tseliot> pitti: isn't there a meeting in #ubuntu-meeting now?
[15:02] <soren> kirkland: Stuff that relates to the framebuffer, maybe?
[15:02] <pitti> tseliot: I don't know
[15:02] <kirkland> soren: right;  i haven't see a lot of such bugs
[15:03] <tseliot> pitti: didn't you send an email to the motu-council mailing list about it?
[15:03] <Keybuk> mdz, pitti, cjwatson, sabdfl: DMB meeting?
[15:03] <pitti> oh, f****
[15:03] <pitti> I forgot
[15:03]  * pitti joins
[15:03] <tseliot> :-)
[15:31] <soren> kirkland: That's a very poor reason for not testing something.
[15:32] <soren> kirkland: Anyhow, if you just add a way for me to enable it back, I don't have the curmurdgeonry to argue about this for hours, so meh.
[15:35] <dmart> NCommander: dmart, I think the CS conditional code isn't being allowed in the block, but I'm not sure how I'm supposed to work around that:  Building with v7+thumb2, you're effectively telling the assembler to pretend that that (ARM) inline assembler is unified assembler source (this is the new syntax that can be assembler to ARM and Thumb)
[15:36] <dmart> ...however, it is actually the old ARM syntax, to it doesn't contains the IT block annotations needed for Thumb-2.
[15:36] <dmart> gcc -Wa,-mimplicit-it=thumb asks the assembler to guess what the IT blocks should have been instead of barfing
[15:36] <dmart> argh, wrong tab
[15:52] <asac> dmart: thanks. so you think that implicit-it=thumb might help for pulse? (guess thats what its about)
[15:52] <ogra> asac, -marm helps
[15:52] <ogra> (which truns off thumb2 ...)
[15:53] <dmart> asac, ogra: yes and yes.  There are 3 fixes
[15:53] <ogra> implicit-it=thumb should be the default in the toolchain by now
[15:53] <dmart> 1) -marm
[15:53] <dmart> 2) -mimplicit-it=thumb
[15:53] <asac> right. but if implicit-kit helps i would think thats preferable?
[15:53] <asac> hmm
[15:53] <dmart> 3) Port the asm to add IT blocks (this is NCommander's current preference, but it may get loborious)
[15:53] <asac> ogra: since when?
[15:54] <dmart> doko was going to add it, but it may not be merged yet
[15:54] <ogra> my pulse build with -marm gets over the breakage here ...
[15:54] <ogra> asac recently ... not sure when exactly
[15:54] <asac> ok. i know that we had IT breakage in xulrunner just before UDS. so lets assume its not in yet.
[15:55] <dmart> I get a build by masquerading GCC to add -Wa,-mimplicit-it=thumb on the command line; though I haven't tested whether the result actually runs properly.  It _should_.
[15:55] <ogra> well, -marm definately helps in the pulse case ... but indeed we lose thumb2 for it then
[15:55] <asac> ogra: can you double check that implicit-it is used?
[15:55] <asac> otherwise i would think its the preferable attempt unless we really want to fix ASM on our own
[15:55] <dmart> -marm is my preference, since the asm may have been specifically optimised to run in ARM.  But generally people don't like to add per-file flags (unless they're there already)
[15:56] <asac> dmart: ok thanks for the input
[15:56] <ogra> well, in the case of pulse they are ...
[15:57] <pitti> dholbach: where do you usually send "new MOTU" announcements to?
[15:58]  * pitti thought about sending the DMB meeting notes to u-devel@
[15:58] <dholbach> pitti: to inform the councils that delegated their power to us, I send it to: dmb, cc
[15:58] <ogra> asac, seems IT isnt in he defaults yet
[15:58] <ogra> *the
[15:58] <pitti> dholbach: right, I already sent it to dmb, cc
[15:58] <dholbach> pitti: afterwards I send a quick heads-up to ubuntu-motu and ubuntu-devel as a welcome message
[15:59] <pitti> dholbach: right, thanks!
[15:59]  * dholbach hugs pitti
[15:59]  * pitti hugs dholback
[16:00] <dholbach> :-)
[16:30] <nxvl> oh noes! no james_w /o\
[16:30] <nxvl> dholbach: did you have any idea if a package will build if i just commit the branch?
[16:31] <dholbach> nxvl: I dunno if the infrastructure can do that already - #launchpad maybe? :)
[16:31] <ScottK> I'm pretty sure not yet.
[16:31] <nxvl> right, will ask there
[16:31] <nxvl> thanks
[16:31] <nxvl> ScottK: ok, will take that advice and be happy
[16:31] <nxvl> it's taking to long
[16:31] <nxvl> so i'm assuming not aswell
[16:58] <cjwatson> kirkland: it just occurred to me why it's a mindbogglingly bad idea to avoid the framebuffer by default in kvm; I'm sorry I didn't think about it earlier
[16:58] <rtg> can anyone tell me why 'apt-get build-dep linux' doesn't install makedumpfile? Is it because the Build-Depends line has whitespace in the architecture specification string, e.g., 'Build-Depends: debhelper (>= 3), cpio, module-init-tools, kernel-wedge (>= 2.24ubuntu1), makedumpfile [amd64 i386 lpia], device-tree-compiler [powerpc]'
[16:59] <cjwatson> kirkland: disabling the framebuffer limits d-i's language choice very substantially
[16:59] <cjwatson> kirkland: so since soren seems to think that this is a kvm bug that should be fixed, I'm afraid I would prefer that rootskel change to be reverted
[17:00] <cjwatson> kirkland: as I say, sorry I didn't think of this when you asked me in person at UDS
[17:07] <mvo> rtg: I don't think its this, it looks like its confused again over srcpkgname and binary package name
[17:07] <rtg> mvo, it gets everything else right
[17:08] <rtg> I mean, it install the other build dependencies
[17:10] <mvo> rtg: does it help if you pass "-o Apt::get::only-sources=1" ?
[17:11] <mvo> rtg: with that, I get the expected behaviour here in a chroot
[17:11] <rtg> mvo, testing, one sec.
[17:12]  * mvo just got called for dinner and will be back in a bit
[17:13] <rtg> mvo, 'apt-get -o Apt::get::only-sources=1 build-dep linux' isn't working for me (this is in a lucid chroot).
[17:22] <mvo> rtg: ok, thanks. let me update my chroot then
[17:23] <pitti> cjwatson: Archive Upload Rights for ubuntu-desktop: package set 'ubuntu-desktop' in lucid
[17:23] <pitti> cjwatson: does that mean it's working already?
[17:24] <pitti> (looks like it)
[17:47] <cjwatson> pitti: yes, I did that last week after the TB meeting
[17:47] <cjwatson> pitti: sorry I didn't make the DMB meeting today, holidays and all that
[17:47] <pitti> yay
[17:47] <pitti> cjwatson: no prob, we had quorum
[17:47] <pitti> cjwatson: enjoy your holiday!
[18:05] <dscassel> KS DCC DCCMSGS CLIENTNOTICES CLIENTCRAP CLIENTERRORS HILIGHTS
[18:08] <Tm_T> dscassel: ok
[18:08] <dscassel> Tm_T, some day, I will get the hang of this IRC thing...
[18:09] <dscassel> (That was half an /ignore)
[18:22] <hedkandi> yo!
[18:23] <hedkandi> has anyone ever used gnome_keyring item_get_info_sync
[18:23] <hedkandi> ?
[18:59] <pwnguin> superm1: i dont understand it either, but i can show you the bug avalanche if you want
[19:44] <soren> kirkland: fwiw, it's trivially easy to see the difference. Try booting a server or alternate ISO in kvm and compare the screen update rates in the installer to the update rate you get if you also pass -no-kvm. In spite of -no-kvm uses full emulation, screen updates are clearly faster.
[19:46] <kirkland> cjwatson: okay, thanks for the followup
[19:50] <kirkland> cjwatson: i think i recognized this when i asked you
[19:50] <kirkland> cjwatson: i suggested that i could additionally check if the user chose English in the bootloader language choice
[19:59] <florob> Hi, I was wondering where I would go to ask some questions about the indicator applet (python bindings specifically)
[20:00] <soren> kirkland: How do you deal with the gfxboot thing, by the way?
[20:02] <kirkland> soren: i just tap enter
[20:02] <soren> Ah.
[20:12] <kirkland> soren: cjwatson: http://pastebin.ubuntu.com/327103/
[20:19] <zul> is there a programable way to change the whiteboard for a given spec?
[20:19] <zul> ie through launchpadlib?
[20:19] <pitti> zul: not right now; wget POST requests FTW :)
[20:20] <zul> pitti: argh! :)
[20:20] <ajmitch> zul: you need to clean the whiteboard for several specs?
[20:20] <zul> ajmitch: yep
[20:23] <ScottK> florob: #ayatana
[20:23] <florob> ScottK, at the risk of sounding confused. Why?
[20:24] <ScottK> florob: Because that's where the upstream for the indicator-applet is.
[20:24] <ScottK> It's sponsored also by Canonical, but developed as a separate project since it's for more than just Ubuntu.
[20:24] <florob> I have heard people claim otherwise ;) Anyway thank you
[20:25] <ScottK> I know the Qt/KDE version is in Gentoo already.
[20:28] <soren> kirkland: Ah. Fail :(
[20:29]  * soren calls it a day
[20:32] <kirkland> soren: i thought about triggering it on a really strange amount of memory
[20:32] <kirkland> soren: like 420MB of memory
[20:32] <kirkland> soren: if a guest has some magic number amount of memory, then don't modprobe fbcon
[20:34] <kirkland> soren: 409632 kB
[20:35] <kirkland> soren: or 251MB, since 251 in dec = FB in hex :-)
[20:54]  * Keybuk wishes "bzr shelve" had an "undo" option like listadmin
[20:54] <Keybuk> for when I get a bit too punch-happy on the "n" or "y" key
[20:56] <pitti> StevenK: moderating your "retirement of lpia"; please poke someone if you send to u-d-a@
[20:57] <ScottK> \o/
[20:59] <sebner> ScottK: I thought you like server stuff :P
[20:59] <ajmitch> no more lpia patches needed?
[20:59] <ScottK> sebner: I do.  That's pretty unrelated to the death of lpia though.
[20:59] <ScottK> ajmitch: Yep.
[21:00] <sebner> ScottK: the few the merrier ... hmm, wait - something's wrong *cough*
[21:49] <lifeless> lamont: reminder - add notes to bug 470265
[21:58] <ari-tczew> is gcc 4.5 comming as deault in lucid?
[22:00] <ajmitch> gcc 4.5 isn't even released yet, so I'd say that there's little chance of it being the default - the toolchain is pretty much settled in the first week or so of a release cycle
[22:01] <Keybuk> no chance
[22:01] <Keybuk> we nearly always fix our toolchain before the release is even started
[22:01] <Keybuk> simply because it's always gone horribly, horribly wrong when we try and change it ater
[22:01] <ajmitch> 'horribly, horribly wrong' aren't words you'd like to see together with LTS
[22:08] <kirkland> cjwatson: rootskel changes reverted
[22:08] <kirkland> cjwatson: i'm back to sed -i'ing *.iso :-(
[22:16] <wgrant> cjwatson: Hi. I hear you have a hardy dpkg backport that Soyuz needs. Which version is it?
[23:37] <cjwatson> kirkland: I did respond to that ... English in the bootloader choice is basically a no-op, we can't key on it
[23:38] <cjwatson> wgrant: dpkg_1.15.4ubuntu2~0.CAT.8.04
[23:42] <wgrant> cjwatson: Perfect, thanks. Is that a straight backport of Karmic's? I presume it's not available anywhere.
[23:44] <cjwatson> wgrant: straightish. http://paste.ubuntu.com/327212/ applied
[23:45] <wgrant> cjwatson: Aha. Thanks.