[00:07] <RAOF> SpamapS: Oooh, while you're here - is there a way of extracting the changes file from the unapproved queue?
[00:08] <SpamapS> RAOF: the name of the package in the queue listing is a link to the changes file
[00:09] <poolie> bug 806940 is part of this
[00:09] <poolie> though, perhaps eventually that will be duped onto a more generic one
[00:09] <RAOF> SpamapS: …oh.  Bah! :)
[00:11] <Yewbacca> What path does patches to the Ubuntu Xorg Intel driver take? Xorg.freedesktop -> Debian -> Ubuntu?
[00:12]  * SpamapS signs off for the day
[00:14] <RAOF> Yewbacca: Generally, yes; we're not slavish about it, though.
[00:14] <infinity> @pilot out
[00:28] <Yewbacca> RAOF: Thanks for the reply. I was working with Wu Fengguang of Intel fame on fixing two major problems. ELD autodetection over HDMI support now added, meaning the HDMI output finally supports multichannel audio rather than just stereo.
[00:28] <Yewbacca> The other fix involves reading the extended CEA mode block to finally detect all display modes rather than just the ones that fit in the basic mode block.
[00:28] <Yewbacca> These are major fixes and I am concerned with how we can get them into Ubuntu's driver quickly.
[00:28] <Yewbacca> They've been reviewed at Intel and released to the Xorg mailing list.
[00:29] <Yewbacca> But they're of course drowning in all the other patches and discussions.
[00:29] <RAOF> Right.
[00:30] <Yewbacca> Do you have any suggestions? Should I focus on alerting Xorg.freedesktop.org to it and then let it trickle to Ubuntu? Or do you sometimes apply important fixes on your own and if so, who do I talk to?
[00:30] <RAOF> That would involve both kernel and DDX fixes, yes?  In either case, we really do prefer that patches are at least applied to a development tree.  These sound like fairly large changes, so we'd want upstream to have signed off first.
[00:30] <poolie> TheMuso, hi
[00:31] <TheMuso> poolie: Good morning.
[00:31] <Yewbacca> Actually they're only DDX modifications :)
[00:31] <poolie> hi
[00:32] <poolie> i just saw your post about the pulseaudio packaging branch
[00:32] <Yewbacca> Oh yeah and I see your point, I'll alert some Xorg maintainers to review and apply them there first. Thanks for the advice.
[00:33] <RAOF> Yewbacca: Then that's a bit easier :).  Still, we'd prefer them to be upstream first.
[00:33] <TheMuso> poolie: The desktop team maintains similar branches for desktop packages as well.
[00:33] <poolie> similar in the sense of debian-only
[00:33] <TheMuso> Right.
[00:33] <poolie> is this mostly for the sake of faster checkouts of it?
[00:34] <poolie> as you know the general plan is to get the ubuntu namespace branches being official, and being complete branches
[00:34] <TheMuso> poolie: No, its because thats how they were originally stored in bzr since before I really got involved with audio packaging.
[00:35] <Yewbacca> RAOF: Thank you. I'll talk to some Xorg maintainer. Have a good night :)
[00:35] <poolie> do you think we could migrate them to the standard form at some point?
[00:35] <poolie> that would remove a special case from the piloting/contribution process
[00:35] <RAOF> Yewbacca: I'm in UTC+10.  It's a good day for me.  Have fun with upstream :)
[00:36] <TheMuso> poolie: Actually I was hoping to eventually move Ubuntu packaging to Debian git.
[00:37] <poolie> hm, really?
[00:37] <TheMuso> poolie: And what about the ubuntu-desktop packaging? How does that go in terms of patch piloting?
[00:37] <poolie> because you're also the debian mantainer?
[00:37] <TheMuso> poolie: Yes, easier to pull from either side patch wise.
[00:37] <TheMuso> THe X guys do the same thing, I do the same thing with accessibility packages, and I am sure others working on Ubuntu, like the multimedia/MOTU guys do as well.
[00:38] <poolie> the same thing here meaning maintaining it on debian.org, or meaning having only debian/ versioned?
[00:38] <TheMuso> The same thing as in Ubuntu packaging maintained in alioth/debian git vcs.
[00:40] <poolie> hm, ok
[00:40] <poolie> so, this seems like a plan around having lp branches and contributions on lp may be on the wrong track
[00:41] <RAOF> poolie: *Or* launchpad grows git support, I guess :)
[00:41] <TheMuso> Yeah that too.
[00:41] <poolie> so, what would happen in that case?
[00:42] <RAOF> pkg-cli-* and pkg-mono also have all their canonical branches in alioth git.  I think it's a fairly popular mode of operation.
[00:42] <poolie> you'd have the ubuntu branches on lp, but be able to more transparently merge them?
[00:42] <poolie> or they'd stay primarily on alioth?
[00:43] <RAOF> They'd probably stay primarily on alioth, but we could pull merges from launchpad.
[00:43] <RAOF> That said, git is terrible at that workflow. :(
[00:43] <TheMuso> I'm not sure. If the ubutu branches were on alioth, thats the only place I'd want to work with them.
[00:43] <TheMuso> SO yeah, merging from lp would be useful.
[00:44] <poolie> i mean there's no point in adding that support, which might not be cheap, if it's not actually helping ubuntu
[00:45] <RAOF> It would help Ubuntu insomuch as merge requests against UDD branches would be useful.
[00:46] <poolie> it seems like one of the things that makes them problematic at the moment is that people do the work essentially in the wrong place
[00:46] <poolie> either directly in the tree when it should be in patches, or in an ubuntu branch when it should be an upstream change
[00:47] <poolie> one of the working assumptions was that having different branches be more consistent (eg whole tree etc) would make that a simpler story to do properly
[00:51] <poolie> raof, so would having the merge proposals be useful as compared to having patches on the bugs, or patches on debian bugs for that matter
[00:51] <RAOF> Patches on the bugs are great; debdiffs on bugs are also great.
[00:52] <RAOF> Patches on Debian bugs are also fine, but our stack is generally different enough that there are a fair number of bugs which aren't in common, and you need to be running Debian on bare-metal to usefully report a Debian bug on the stack.
[00:53] <infinity> poolie: One of the general issues I have with UDD (or any of its predecessors) is statements about "doing work in the wrong place".
[00:54] <infinity> poolie: Any contribution is the right place, and debdiff, or simple patches are all perfectly fine.
[00:54] <poolie> because it can always be moved around later?
[00:54] <infinity> poolie: (I'll admit that this sometimes makes the UDD stuff feel more like a hundrance than a help, but there must be clever ways to make it all work together more smoothly)
[00:55] <poolie> i guess what i'm really asking is, how can canonical's infrastructure best be helping ubuntu?
[00:56] <infinity> poolie: I dunno.  I might be in a vanishing minority, but I'd like to be able to just do dpkg-source work the way I've always done and upload a dsc/diff/tar/orig that integrates seamlessly into branch-based work other people want to do.  We're sort of there, and imports mostly work, but not quite.  And it's discouraging when people blame it not working on "the old way" being "the wrong way".
[00:57] <infinity> poolie: But, some people love the shiny and new here too, so saying it's not worth making it as shiny as possible if it's not the way old farts like me work isn't helpful either.  It seems like a real value add.  It's just a value-add *I* don't care about. :)
[00:59] <infinity> (And I realise I missed out on half the conversation here, and this is just a drive-by commenting on my way to beer, but if you want actual opinions, ask me sometime.  You know I'm full of 'em, some even useful)
[00:59] <poolie> :)
[01:03] <TheMuso> For me personally, I am happy working in alioth with git, because everything I track upstream uses git, which at times, can be very handy should one want to make a git snapshot release for a package. Just merge a git branch into the upstrea branch locatino or whereever you want, cherry-pick individual commits, etc. Bzr's biggest advantage is its merge algorithm however.
[01:03] <TheMuso> gah typing.
[01:03] <poolie> infinity: i see your point about not wanting to denigrate things people are doing that are working
[01:04] <poolie> obviously technically the importer is supposed to handle merging them together and it generally does
[01:04] <poolie> so themuso, if you were writing our plan for the next year (for udd/lp/bzr), what would you ask for?
[01:06] <TheMuso> poolie: I am not the one to ask. Like infinity, I am happy with existing tools, and don't care much for UDD, probably because the majority of thigns I touch already are in alioth git, or will soon be.
[01:07] <TheMuso> I don't mind having to do the extra legwork to make sure a particular patch author is credited for their work properly in a vcs.
[01:08] <TheMuso> SO I guess all I'd prefer is patches/debdiffs.
[01:08] <poolie> so your answer is essentially, "don't get in the way of using allioth?" or "improve the bug tracker instead?" or something?
[01:08] <RAOF> Actually, that might be worthwhile.
[01:09] <RAOF> Generate debdiffs from merge requests.
[01:09] <poolie> or is it "make changes from branches and mps available as diffs/debdiffs?"
[01:10]  * RAOF would also like bzr to be slightly better at being a git frontend, too. :)
[01:10] <poolie> me too
[01:11] <poolie> what sort of thing in particular?
[01:11] <poolie> i guess, also, it's useful to know when you prefer using bzr-git  to git, and how we could build on that
[01:11] <TheMuso> I lie RAOF's idea in generating debdiffs from merge proposals.
[01:11]  * TheMuso will never use bzr-git, I'm happy with using git proper, as much as it can be quirky at times.
[01:12] <RAOF> poolie: I prefer to use bzr-git to git anytime it works.  Mainly that's when I don't have to deal with a non-master branch, because there's no way of doing that with bzr-git (that I know of).
[01:13] <poolie> i'll file a bug for debdiffs
[01:19] <poolie> raof, i don't think there's a way to do that at present but there should be soon
[01:20] <RAOF> I think a combination of git's colocated branches and bzr's sane way of actually pulling from other people would be great :)
[01:20] <poolie> for native bzr branches, bzr-colo is pretty good
[01:21] <poolie> ok, https://bugs.launchpad.net/launchpad/+bug/816757
[01:21] <poolie> can you help me improve the description?
[01:22]  * TheMuso looks.
[01:23] <RAOF> Actually, can we already download a diff from the merge proposal?
[01:23] <poolie> yes; though apparently there may be a ui bug :)
[01:23] <TheMuso> RAOF: You might be right. Let me go to the merge that started all this convo. :)
[01:23] <RAOF> 'Cause there's basically no difference between a debdiff and a branch diff in that case.
[01:23] <poolie> Ctrl-f "download diff"
[01:24] <TheMuso> Right
[01:24] <poolie> oh, i thought you were asking for more of debdiff's policy intelligence
[01:24] <poolie> though, for packaging branches, that may reduce to not much
[01:24] <TheMuso> Yup, works here.
[01:25] <RAOF> Oh, right.  So there is.
[01:25] <TheMuso> Thinking about it further though, as pilots, things get more sticky if we are working on a package that has an Ubuntu packaging branch in alito that we cannot directly write to. If we want to upload the change...
[01:25] <TheMuso> alioth
[01:26] <RAOF> That's the main problem with hosting on alioth, yeah.
[01:27] <poolie> the problem being that ubuntu access control rules don't carry over?
[01:30] <TheMuso> Yes, but one wouldn't expect them to I guess.
[01:32] <poolie> so, is this bug valid?
[01:33] <TheMuso> Probably not now that we know of the download diff link.
[01:33] <RAOF> Maybe as a UI bug?
[01:33] <poolie> saying "people didn't notice they could download the diff?"
[01:33] <RAOF> Pretty much :)
[01:33] <poolie> that seems ilke something we could possibly test on
[01:42] <poolie> ok, updated
[01:42] <poolie> thanks for the information
[05:53] <didrocks> good morning
[05:53] <lamont> fact
[05:54] <ion> that.
[05:59] <mwhudson> if an upstart job fails to start during a package upgrade, but runs fine when started with "sudo start $service", where can i start looking?
[06:01]  * mwhudson finds http://upstart.ubuntu.com/wiki/Debugging
[06:36] <cinerama_> hi folks, i have a query from a user about the mirror lists in synaptic....can anyone help?
[07:02] <dholbach> good morning
[08:32] <evfool> thanks mvo for merging
[08:40] <mvo> evfool: thank you!
[08:40] <mvo> evfool: I'm doing some gtkbuilder fixes and then I will upload
[09:00] <evfool> mvo: remember that problem I told you about, with update-manager not being able to update because package names in dbus.strings instead of python strings?
[09:01] <mvo> evfool: yes
[09:01] <evfool> mvo: I have had the exact same problem on two different computers chroot, and after branching the latest aptdaemon and installing it, It's gone
[09:03] <mvo> evfool: ok, let me do a update then
[09:03] <mvo> evfool: sorry, I mean to look at it yesterday, but did not found the time
[09:19] <mvo> evfool: hm, that is a bit odd, oneiric has the latest trunk
[09:19] <mvo> evfool: of aptdaemon
[09:20] <evfool> mvo: yep, but I still can't find out why I get this behavior. any ideas what should I be looking for? Getting this on two absolutely unrelated chroots isn't normal behavior
[09:21] <mvo> evfool: right, let me try in a vm. are you using i386 or amd64?
[09:21] <evfool> mvo:i386
[09:21] <mvo> thx
[09:22] <mvo> and a simple apt-get install --reinstall aptdaemon python-aptdaemon does not help?
[09:23] <evfool> mvo: I'll try
[09:24] <evfool> I've tried that, and it's working now, and when I get to the other PC, I'll try it there too
[09:24] <evfool> don't know what could cause this
[09:26] <mvo> woah, really odd
[09:57] <jml> howdy
[10:52] <jml> Hitting the "Delete" key doesn't seem to delete files any more. Known bug? Local config problem?
[10:53] <seb128> jml, it's ctrl-delete now
[10:54] <jml> seb128: oh. huh. is changing keyboard bindings an allowed thing now?
[10:54] <jml> (I don't really have a problem with it. Heaven knows we could use more coherent default keyboard bindings.)
[11:52] <seb128> ok, nobody freaks out but soyuz syncing testing bugged and did a sync-source on oneiric it seems
[11:53] <seb128> normal "sync what is newer in Debian" we do before DIF
[11:53] <seb128> but still we are after DIF...
[11:53] <seb128> they are trying to figure what happened
[11:53] <Laney> an accidental autosync run?
[11:54] <seb128> yes
[11:54] <seb128> testing the manual "one source syncing"
[11:54] <Laney> whoops
[11:54] <seb128> seems like it did trigger the wrong action somewhat and did a autosync run
[11:54] <seb128> indeed whoops...
[11:56] <directhex> awesome, oneiric gets to be super up-to-date
[11:57] <jtaylor> should at least empty the sync queue ^^
[12:33] <ahasenack> hi guys, will someone from the sru team look at the queue today? https://launchpad.net/ubuntu/lucid/+queue?queue_state=1&queue_text=
[12:33] <ahasenack> my interest is landscape-client
[13:02] <tuxcrafter> hi all
[13:03] <tuxcrafter> what is the root pw for the ubuntu daily live
[13:03] <tuxcrafter> http://cdimage.ubuntu.com/daily-live/current/
[13:03] <tuxcrafter> tried live|ubuntu|<empty>
[13:10] <tuxcrafter> somebody?
[13:11] <Pici> tuxcrafter: 1) This isn't a support channel, try #ubuntu
[13:12] <Hobbsee> tuxcrafter: from memory, it's ubuntu
[13:12] <Hobbsee> or at least, used to be
[13:13] <geser> tuxcrafter: just to be sure: you try sudo from the user account and not a login as root or su?
[13:13] <tuxcrafter> sudo su -
[13:15] <tuxcrafter> Hobbsee: sandly not working
[13:15] <tuxcrafter> but id shows i am some kind of guest user
[13:15] <Hobbsee> tuxcrafter: ah.  Then no idea.
[13:57] <bdrung> seb128: do you use the new sync feature from launchpad for the syncs?
[13:58] <seb128> bdrung, "sort of", cf what I said 2 hours ago
[13:58] <seb128> there was an autosync run by mistake by the new sync feature
[13:58] <seb128> so now I'm closing the sync requests which got done in that buggy run
[13:59] <bdrung> ah, ok.
[14:00] <ScottK> Ah.  That's what happened.
[14:03] <smoser> barry, around ?
[14:25] <hallyn> sbuild -d oneiric *.dsc
[14:25] <hallyn> Only one build is permitted
[14:25] <hallyn> eh?
[14:25] <hallyn> oh, haha
[14:30] <hallyn> kees: hm, on uptodate oneiric, my laptop appears to have no entropy?
[14:31] <hallyn> dd if=/dev/random of=x count=8  hangs forever
[14:31] <hallyn> (and so i can't sbuild-update --keygen, and so i can't build packages...  well i guess i'll set up pbuilder)
[14:32] <hallyn> oh, 8 bytes came through
[14:46] <dupondje> https://launchpad.net/ubuntu/+source/ginkgocadx/2.5.1.0-1
[14:46] <dupondje> that changelogs look drity ass :p
[14:47] <Laney> it's right in debian
[14:47] <Laney> 's pts
[14:48] <seb128> right, launchpad formatting for debian changelog is buggy
[14:49] <dupondje> seems like all the syncs that are done 2 hours ago are that way
[14:49] <dupondje> not nice :)
[14:49] <seb128> i.e
[14:49] <seb128> https://launchpad.net/debian/+source/tomboy/1.6.1-1
[14:49] <seb128> dupondje, yeah, "known bug"
[15:35] <bdrung> hallyn: you can move the mouse to increase the entropy
[15:42] <hallyn> bdrung: no, neither mouse nor kbd was doing it
[15:43] <bdrung> hallyn: then buy entropy in the super market ;)
[15:43] <hallyn> i wonder if plugging in my phone might have helped
[15:44] <hallyn> but i am wondering if this is a 3.0 kernel regression.
[15:44] <bdrung> or pipe the entropy from another computer :)
[15:44] <mdeslaur> hallyn: I'll sell you entropy for $1 per kb
[15:45] <hallyn> mdeslaur: how do i know it's real?
[15:45] <bdrung> mdeslaur: i'll sell it for 10 euro cent per dekabyte
[15:45] <hallyn> i don't want any of that inferior walmart entropy
[15:47] <mdeslaur> hallyn: purest entropy a 20-sided die can generate
[15:48] <hallyn> mdeslaur: new service on amazon mechanical turk!
[15:48] <mdeslaur> lol
[16:14] <smoser> anyone know how doku usually handles python changes ?
[16:14] <smoser> i added a merge proposal at https://code.launchpad.net/~smoser/python/lp-813295/+merge/69491
[16:16] <ScottK> smoser: he's at debconf this week.  I'd ask barry to look into it.
[16:17] <smoser> it looked like doku is the only one that touched python
[16:17] <smoser> and the Vcs-Bzr is http://bazaar.launchpad.net/~doko/python/pkg2.7-debian
[16:17] <smoser> thus the question.
[16:19] <ScottK> Normally that's the case.
[16:19] <ScottK> I also know is his laptop fan died so the odds of him attending to it this week are low.
[16:38] <maco> i think firefox should be in the "special cases" section, but i don't actually know what the new policy is https://wiki.ubuntu.com/StableReleaseUpdates ...help?
[16:40] <kees> hallyn: do more network/disk/mouse activity! :)
[16:40] <infinity> maco: Firefox was previously listed in https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions ... That probably needs updating.
[16:40] <maco> since they stopped micro-ing?
[16:40] <infinity> Yeah.
[16:40] <hallyn> kees: was doing a lot of all of the above!
[16:40] <kees> hallyn: entropy generating sucks in the kernel, so doing strong key generation isn't generally something you can automate
[16:41] <hallyn> kees: i didn't notice this under natty on this laptop.  i do under oneiric.  <shrug>
[16:41] <hallyn> jdstrand: are you syncing libvirt from sid by chance?
[16:41] <infinity> kees: I shouldn't tell you that I automate it, should I?
[16:41] <jdstrand> hallyn: no
[16:41] <kees> hallyn: I use this for good entropy: http://www.entropykey.co.uk/
[16:41] <hallyn> drat :)
[16:41] <jdstrand> hehe
[16:42] <jdstrand> hallyn: fyi, I'm out the next two weeks starting monday
[16:42] <kees> hallyn: nothing that I know of has changed between natty and oneiric
[16:42] <hallyn> jdstrand: ooh, I can push SRUs!  :)
[16:42] <kees> infinity: it's totally possible, sometimes it might just take a long time
[16:42] <hallyn> kees: maybe i should pick one onf those up
[16:42] <jdstrand> hallyn: :)
[16:42] <hallyn> hm, a bit steep.  Wonder if i can solder my own
[16:43] <infinity> kees: My trick is to background gpg --batch before an ISO image build. :P
[16:43] <kees> hallyn: I have 2. they generate WAY the hell more bits than I could ever use
[16:43] <hallyn> but seriously, i was typing like mad and downloading an iso
[16:43] <kees> infinity: sounds good to me :)
[16:43] <infinity> kees: It hasn't yet failed to complete before the image does.
[16:43] <infinity> kees: (yet)
[16:43] <kees> heh
[16:54] <nemo> infinity: firefox is still microing though
[16:55] <nemo> infinity: in fact, that page has an exception for chromium, and firefox is basically doing the chromium playbook now
[16:55] <maco> nemo: by "its not microing" i meant they stopped having it be the .x that changes all the time
[16:55] <nemo> ah
[16:55] <maco> they give microreleases major version bumps
[16:55] <infinity> ^
[16:55] <nemo> right. well. that matches chromium
[16:56] <infinity> And that certainly doesn't match what they used to do.
[16:56] <infinity> Not just the cosmetic change. :P
[16:56] <nemo> well. in terms of ubuntu policy, still would want to push out FF5, 6 etc for Natty
[16:56] <infinity> But the new firefox versions are "rapid feature releases", not just bugfixes.
[16:57] <nemo> infinity: they used to push new features into .x
[16:57] <nemo> admittedly, not that many
[16:57] <infinity> And yes, we're still pushing new versions.
[16:57] <nemo> had to be a really useful one
[17:00] <stgraber> @pilot in
[17:06] <persia> If anyone is about that could moderate a post to technical-board@, I'd appreciate it :)
[17:08]  * infinity squints at Kate's mail to ubuntu-devel-announce.
[17:37] <jdstrand> hallyn: fyi, I will be publishing another libvirt update today
[17:37] <hallyn> for o?
[17:37] <jdstrand> hallyn: no, lucid - natty
[17:37] <hallyn> ok
[17:38] <jdstrand> I already did oneiric last week
[17:42] <smoser> barry, ^^ would you be able to look at/merge the python bug above?
[17:42] <smoser> i'd like to have the images for alpha3 work on eucalyptus, and they will not without this fix.
[17:43] <smoser> never mind, i see that you responded to the merge proposal
[17:43] <barry> smoser: i just reviewed it ;)  looks good to me, but i want to get the patch into upstream py 2.7 first.  i will work on that in a few minutes.  assuming that goes okay, i'll merge your change (which is basically the upstream changeset) and push an update
[17:44] <smoser> the commit is in the 2.7 branch
[17:44] <smoser> upstream
[17:44] <smoser> thats where i pulled it from
[17:44] <barry> oh, the issue tracker didn't include the changeset that i could see.  it was just the default (3.3) and 3.2 changesets
[17:44]  * barry looks again
[17:45] <smoser> http://code.activestate.com/lists/python-checkins/98577/
[17:46] <smoser> i didn't see it in the issue tracker either, and tried to backport the 3.2 change
[17:46] <smoser> then got cpython and noticed it was already there.
[17:46] <barry> smoser: huh.  yeah, weird that it didn't make it to the tracker
[17:46] <barry> smoser: in that case, i'll merge and push in a few minutes (want to finish something up first)
[17:46] <smoser> barry, thanks.
[18:59] <bdmurray> lucas: I'm looking at the udd and the archived_bugs table seems to be empty I'm not sure if its just my copy of it or something else
[19:02] <lucas> bdmurray: looks like it's your copy.
[19:02] <lucas> udd=> select count(*) from archived_bugs; count
[19:02] <lucas> -------- 527700
[19:02] <lucas> (1 row)
[19:04] <bdmurray> lucas: okay thanks
[19:46] <jdstrand> hallyn: fyi if you are preparing libvirt SRUs: bug #817187
[19:51] <stgraber> rsalveti: looking at https://code.launchpad.net/~rsalveti/ubuntu/oneiric/base-files/run-transition/+merge/67444 is it still needed after all the /run changes that happened lately (including new releases of base-files)?
[19:56] <hallyn> jdstrand: I'm not touching SRUs, maybe at all this week
[19:56]  * hallyn goes to look in case he misunderstood
[19:56] <jdstrand> hallyn: ack-- I just spent some time investigating the issue, so wanted to spare you that
[19:57] <hallyn> jdstrand: i'm convused, it builds fine for oneiric, what fails?
[19:57] <jdstrand> hallyn: I probably wasn't clear. If you are preparing srus and running an oneiric kernel, then you'll get ftbfs. the bug details all of this and what to do to fix the situation
[19:57] <hallyn> ah
[19:58] <hallyn> thanks!
[19:58] <jdstrand> hallyn: right, change in kernel behavior in oneiric is exposed in chroots that cause ftbfs
[20:23] <evfool> ping ev
[20:46] <hallyn> ok, so as SpamapS noticed, since at least yesterday, if you debootstrap an image, you have to explicitly add the ubuntu-keyring package for apt to work.  That wasn't the case a few days ago.  Expected?
[20:50] <kirkland> are there any good debhelper8 backports to lucid?
[20:50] <kirkland> perhaps in a PPA, or something?
[20:55] <kirkland> nevermind, i've worked around it
[20:56] <maco> there's a debhelper8?
[20:56] <maco> *now* how tiny is debian/rules?? O_o
[20:58] <chrisccoulson> hmmm, i still haven't even converted firefox to use dh7 ;)
[20:58] <chrisccoulson> and my debian/rules is huge
[20:58] <chrisccoulson> **its
[21:00] <stgraber> @pilot off
[21:00] <udevbot> (pilot (in|out)) -- Set yourself an in or out of patch pilot.
[21:00] <stgraber> @pilot out
[21:13] <galfly> Hey guys. Anybody here working for canonical lexington office?
[21:14] <carif> here
[21:14] <carif> don't ask me to do something difficult
[21:14] <galfly> Hi carif. Not too difficult I hope
[21:15] <galfly> any idea how long it takes HR to respond to new applications?
[21:15] <galfly> haven't heard for weeks, kind of depressing
[21:17] <carif> galfly, your irc nick isn't in https://directory.canonical.com/search/
[21:18] <galfly> how come? I am on launchpad
[21:20] <carif> galfly, i think you'll need to ask is at #is to add you and entry, take a picture, etc
[21:21] <galfly> I'm not sure if I understand
[21:21] <carif> galfly, oh perhaps I've mixed you up, I didn't read carefully enough
[21:22] <carif> galfly, you've applied to Canonical for a job?
[21:22] <galfly> carif, I applied to an opening at canonical and I'm on launchpad etc.
[21:22] <galfly> carif yeap
[21:22] <carif> galfly, so sorry, I was talking "internal speak"
[21:22] <galfly> carif, I'm not there yet :)
[21:23] <galfly> soon, I'll be fluent in internal
[21:23] <galfly> I hope :)
[21:23] <carif> galfly, me too, so how did you submit your application and to whom?
[21:25] <galfly> cairf, I emailed my resume to hr@canonical.com with a cover but am not sure if that was the best way
[21:26] <brianchidester> galfly: https://tbe.taleo.net/NA3/ats/careers/jobSearch.jsp?org=CANONICAL&cws=1&rid=86
[21:26] <brianchidester> going through that would be a better start
[21:27] <galfly> brianchidester thanks a lot. any idea how long it takes them to respond on average?
[21:27] <maco> they say on the applications if its over 6wk with no response, might as well give up
[21:27] <maco> i think
[21:28] <maco> though im not sure with the new application system
[21:28] <infinity> galfly: If you don't apply with the shiny new system, there's a fair chance it might slip through the cracks.
[21:28] <infinity> galfly: (ie: don't email directly)
[21:28] <maco> it kinda depends when the hiring manager has set aside to go through the Pile O' Stuff, but iirc from when i applied 3-4 wk?
[21:29] <galfly> you guys all rock
[21:29] <galfly> thanks a lot
[21:29] <brianchidester_> galfly: sorry, battery died
[21:30] <carif> galfly, good luck, later
[21:30] <galfly> countdown from 6 weeks stars as of today
[21:30] <galfly> looking for an apartment in lexington area as well
[21:30] <galfly> ha ha!
[21:36] <rsalveti> stgraber: no, it's not needed anymore
[21:36] <rsalveti> just deleted the merge proposal
[21:41] <stgraber> rsalveti: thanks
[22:05] <hallyn> I wonder whether dpkg should detect failure to unpack a .deb and automatically remove+re-fetch one or two times
[23:28] <barry> i'm having a hard time understanding an apt-get install error.  try installing python-qt4-dbus on oneiric and you'll get a broken package.  but afaict, python-qt4-dbus depends on python-dbus >= 0.80.0 and python-dbus 0.84.0-2 is installed
[23:31] <infinity> barry: python-dbus : Breaks: python-qt4-dbus (< 4.8.3-3) but 4.8.3-2 is to be installed
[23:33] <barry> infinity: ah, i had an out of date control file i think.  thanks.  still the apt-get error message sure isn't helping much ;)
[23:33] <barry> infinity: thanks
[23:37] <infinity> barry: It's a bit easier to sort if you "apt-get install python-qt4-dbus python-dbus"
[23:38] <barry> infinity: yep, that makes much more sense
[23:38] <poolie> hi again barry
[23:38] <infinity> barry: Now, it would be hugely helpful if there was a new python-qt4 to sync that had the changes that I assume are required...
[23:39] <barry> poolie: time files doesn't it? ;)
[23:39] <ScottK> barry: python-qt4 4.8.3 is supposed to switch to dh_python2.  Now if only someone would upload it to Debian.
[23:39] <barry> infinity: yes, there is that.
[23:39] <barry> ScottK: maybe someone who had debian upload privs? :)
[23:39] <barry> ScottK: i think this is fallout from the unintended sync
[23:39] <ScottK> infinity: It would.  It would help even more if someone would upload such a change to Debian.
[23:40] <ScottK> barry: That and the python-dbus upload being done slightly too soon in Debian.
[23:40] <barry> ScottK: yep
[23:40] <barry> ScottK: is there anything i can do to help?  i'm blocked on it atm.
[23:41] <ScottK> barry: You can take that patch I pointed you at to review the other day and put it in dpmt svn for me to review/upload.
[23:41] <poolie> barry i was wondering if after the holiday period we should do something to shake up the meetings a bit
[23:41] <ScottK> (after suitable testing)
[23:41] <poolie> i'm glad we started them and it's good to stay in touch but perhaps something new is needed now
[23:41] <barry> ScottK: let me see if i remember where that is
[23:41] <barry> poolie: i totally agree
[23:42] <infinity> ScottK: is this in need of Debian NMU love, or is the maintainer on top of it?
[23:42] <ScottK> barry: http://paste.debian.net/124320/
[23:42] <ScottK> infinity: The maintainer is a team that all tries to avoid this one because it's painful.
[23:43] <ScottK> I'll upload it once barry's blessed it.
[23:43] <barry> ScottK: thanks.  let me test that
[23:43] <barry> poolie: i think we should cut out the boilerplate and concentrate on what's really valuable
[23:44] <infinity> ScottK: oh, fair enough.  Happy to sync it once you land it in incoming, then.
[23:44] <poolie> yeah
[23:44] <poolie> i don't have anything specific at the moment but i was going to ponder it over the holidayish period
[23:45] <ScottK> barry: You mean assigning work to people that skipped the meeting?
[23:45] <barry> ScottK: if by "people who skipped the meeting" you mean "you" then yes :)
[23:45] <barry> poolie: agreed!  i'll do the same
[23:46] <ScottK> barry: No problem.  I have a consulting rate related to having work assigned to me.  win-win.
[23:46] <barry> ScottK: no problem, since i know you're familiar with my referral cut
[23:47] <ScottK> Definitely win-win then.
[23:48] <barry> ScottK: if only we were running the gubmint.  debt crisis solved
[23:49] <ScottK> Mine anyway.
[23:49] <barry> right :-D
[23:49] <barry> ScottK: hey, when will debian policy force people to put each build-dep on a separate line?
[23:50] <ScottK> Probably never.
[23:50] <barry> everyone who puts one huge block of build-deps should be forced to read 100 diffs of them
[23:52] <barry> anyway, i'm going to grab some dinner and let this build
[23:54] <SpamapS> barry: for those diffs, I use vimdiff :)
[23:57] <ScottK> barry: You'll want to merge python-defaults from experimental (I just uploaded it)