[01:00]  * ebroder grumbles
[01:00] <ebroder> has dbus, like, forgotten how to support eavesdropping at some point?
[01:09] <ebroder> oh, no. my match expression to dbus-monitor was just wrong
[02:20] <ebroder> hmm...i just saw a zombie process parented to init that wasn't getting reaped. that seems unexpected, no?
[02:20] <ebroder> (i'm not sure yet whether i can reproduce it)
[04:39] <happygilmoregent> hey room
[04:40] <happygilmoregent> anyone a developer for ubuntu?
[04:41] <micahg> happygilmoregent: indeed
[04:41] <happygilmoregent> why didd you chhoose to start in runlevel 2?
[04:41]  * micahg didn't choose it :)
[04:42] <happygilmoregent> what do you mean?
[04:43] <happygilmoregent> why does ubuntu start in runlevel two?
[04:43] <RAOF> Because runlevels are, roughly speaking, an entirely obsolete legacy idiom?
[04:43] <kees> happygilmoregent: that's a default ubuntu inherited from debian
[04:44] <happygilmoregent> ok i run gentoo and it does graphical login in runlevel 5
[05:50] <ebroder> different distributions interpret the different runlevels differently
[05:50] <ebroder> debian doesn't distinguish between graphical and non-graphical boots by changing runlevels
[05:50] <ebroder> so ubuntu doesn't either
[06:58] <jon8> Hey guys, i completely understand that this is developer's channel but many people in #ubuntu can provide me with a solid answer.
[06:59] <jon8> Is there anything other than, https://lists.ubuntu.com/mailman/listinfo/maverick-changes -- that can provide a person with some sort of interface as to when new packages come out and why? Almost like an RSS Feed of sorts if you think about it.
[07:00] <mase_wk> jon8: you mean other than just using apt it's self ?
[07:00] <jon8> yes
[07:00] <ebroder> jon8: googling for [natty-changes rss] gets me http://ubuntuforums.org/showthread.php?t=1596437
[07:00] <jon8> i do sudo apt-get update/upgrade atleast once a day
[07:01] <jon8> sorry, i should of speficied maverick
[07:01] <mase_wk> jon8: what are you trying to achieve?
[07:01] <ebroder> jon8: i'd encourage you to look at the link i just sent and make the obvious modification
[07:01] <jon8> yah :P
[07:02] <jon8> mase_wk nothing specific really.. just a way to keep up with updates eaiser and to see whats being made available
[07:02] <jon8> was just a general question at the end of it tbh.. and no one in #ubuntu really had an answer when i asked earlier today
[07:02] <jon8> but http://feeds.ubuntu-nl.org/MaverickChanges is pretty much exactly what i was looking for, thank you.
[07:02] <jon8> I'll take off now as I dont belong here :)
[07:03] <jon8> Thanks for the awesome OS you guys work so hard on!
[08:16] <dholbach> good morning
[08:29] <pitti> Good morning
[08:29] <pitti> andreserl: I am; but why are you polling it? shouldn't select() work just fine on this?
[10:40] <ebroder> Oh man. I bet the CD space reclamation session at UDS-O will be fun
[11:14] <apw> if i pull a bzr branch for a package and it only contains the debian directory, is there a magic incantion to instantiate the source i should be aware of, or am i on my own
[11:15] <TeTeT> apw: try ./debian/rules get-current-source
[11:15] <pitti> apw: uusally "bzr bd-do" or "bzr bd -S" or "bzr bd -- -b", depending on what you want to do
[11:16] <pitti> apw: the second/third build source/binaries, the first throws you into a shell with the upacked source, lets you hack on it, and if you exit with 0, it copies back the changes to debian/ to the original tree
[11:16] <pitti> apw: that's from bzr-builddeb
[11:17] <TeTeT> pitti: nice, never knew about bd-do
[11:17] <apw> pitti i want to apply a patch to the package, so i guess i want the former
[11:17] <pitti> TeTeT, apw: documentation (shocking!): https://wiki.ubuntu.com/DesktopTeam/Bzr
[11:17] <TeTeT> he he
[11:17] <pitti> apw: yes, there you can try it out, and if it works, exit 0
[11:18] <apw> pitti, thanks will give it a bash
[11:28] <pitti> apw: bd is actually quite clever with that; if the orig.tar.gz is not there already, it first tries apt-get source, then debian/watch, then uscan, and finally get-orig-source
[11:28] <pitti> i. e. if there is any automatic way to get the source at all, it should get it
[11:33] <apw> pitti, ahh yes, it has a watch cool
[11:37] <apw> can someone tell me how to unlink a bzr branch which is in 'svn mode' and trying to push my changes on commit?
[11:38] <pitti> apw: try "bzr unbind"?
[11:38]  * ogra sighs, webkit still uninstallable ?
[11:38] <pitti> ogra: today's CDs finaly built, so it should work now
[11:38] <ogra> pitti, not for arm
[11:38]  * ogra wonders why he  doesnt get any biold failure mails for x86 anymore
[11:39] <apw> pitti, thats the ticket, thanks
[11:39] <ogra> oh, because i only get mails for ubuntu-netbook ...
[11:46] <apw> so i have found a bug in avahi, triggered by kernel changes to fix a bug, now i've pushed that change to the avahi upstream, would we normally apply things like that in ubuntu as well?
[11:46] <apw> given it has to get released by them, then picked up by debian, and then sync'd to ubuntu
[11:47] <apw> (the fix to the kernel won't hit ubuntu for a few days yet)
[11:48] <sladen> apw: is it a OMG critical/data loss/unbootable machines/BIOS bricker?
[11:49] <apw> sladen, it prevents avahi working in such a way that remote logins no longer seem to work
[11:49] <sladen> apw: main thing is to ensure that it's tracked, so you can keep tabs on its progress via upstream and Debian and knowingly know when it actually hits the distro kernal packagse
[11:50] <sladen> apw: what type of remote logins?  10.04 LTS server SSH logins?
[11:50] <apw> sladen, i mean ssh logins, the issue only affects natty at the moment
[11:50] <sladen> apw: does it have a reasonable workaround, eg. typing an IP address in directly?
[11:50] <apw> sladen, nope, no work around that i've found other than shutting down avahi on the machine itself
[11:50] <apw> sladen, ie none that helps if you are remote
[11:51] <sladen> apw: what's the bug number?
[11:51] <cjwatson> it's not unreasonable to backport a change to Ubuntu ahead of the usual trickle-down, if it's needed
[11:51] <apw> bug #704372
[11:52] <apw> sladen, as i say, its something that won't hit until i upload the first 2.6.38 based kernel, but thats not likely to be more than a week out
[11:52] <Laney> yeah, avahi isn't currently in sync anyway
[11:52] <Laney> I wouldn't say it's a big deal to backport the patch
[11:52] <apw> i am only seeing it because my dogfood is extremly warm
[11:52] <Laney> you might consider making Debian aware though if it's going to affect them
[11:53] <ogra> Riddell, around ?
[11:53] <apw> Laney, good point, will mention it over there ->
[11:53] <sladen> apw: is there scope to upload the avahi package first and set the appropriate Depends:/Breaks: ?
[11:54] <sladen> apw: which should hopefully mean that regardless of how warm or creative people's dogfood is they can never actually manage to get themselves into a corner
[11:55] <cjwatson> relationships against kernel packages never work very well due to the constantly shifting package names
[11:55] <apw> sladen, cirtainly there isn't any difficulty waiting till the avahi changes are in the archive
[11:55] <apw> cjwatson, indeed ...
[11:56] <apw> for now i will wait and see how quick upstream reacts to the report
[11:56] <apw> i have the changes for ubuntu in a branch on that bug, should we need to apply it locally first
[11:59] <sladen> apw: I'd defer to cjwatson for the best solution.  My personal hunch would be to send it upstream (which you've done), wait a couple of days and if it gets to the stage of knowing that the kernel upload needs to be done, apply the avahi fix to natty (which you've got in the branch) and after that has cleared, then upload the kernel update
[12:00] <apw> sladen, sounds like a reasonable plan to me
[12:01] <sladen> apw: the bigger stress is knowing that if the kernel gets backported to 10.04/10.10 to upload avahi to those first too (if those versions are similiarly afflicted)
[12:01] <apw> sladen, oh crap, good point, lts backports ... bah
[12:02] <apw> will add that to the checklist
[12:02] <apw> wh
[12:02] <apw> which i will go and invent
[13:25] <lifeless> pitti: hi
[13:25] <lifeless> pitti: looks like some retracer service is still using edge
[13:45] <amitk> how often is the NEW queue processed?
[13:51] <cjwatson> amitk: a few times a week to varying depths
[14:20] <andreserl> pitti: howdy!! To tell you the truth I didn't write the Monitor, someone contribute it. However, I simplified/integrated it with PowerNap. I'll make it available in a bit for you to take a look at it
[14:23] <pitti> lifeless: hi; yes, that's possible, I don't update them that often
[14:32] <micahg> pitti: good morning, I was wondering, should I worry about changing from a native to a non-native package for an SRU if it's more appropriate?
[14:32] <pitti> micahg: I wouldn't do it; it shouldn't help to fix a real problem for the user, and might just cause confusion
[14:33] <micahg> pitti: ok, I'll fix it in natty though, I need to update the thunderbird translations for the lucid point release
[14:37] <pitti> micahg: that sounds good, thank you
[14:54] <andreserl> pitti: http://bazaar.launchpad.net/~andreserl/powernap/monitors/view/head:/powernap/monitors/InputMonitor.py
[14:59] <pitti> andreserl: ah, that looks fine
[15:00] <andreserl> pitti: awesome them. Should be integrating them completely with PowerNap within this week
[15:30] <mdeslaur> Is a broken messaging indicator a known issue? Ie: I click on it and nothing happens? (other indicators work)
[15:31] <Tanguy> Hello.
[15:31] <mdeslaur> tedg: ^
[15:32] <Tanguy> I am a Debian Maintainer, and I am planning to maintain the package libasyncns on Debian, which has been quite abandonned the last years.
[15:32] <Tanguy> I have just seen that it has been updated in Ubuntu.
[15:32] <Tanguy> The Maintainer fields names “Ubuntu Developers”.
[15:33] <Tanguy> Is there something I should do to coordinate with them to maintain it in Debian?
[15:33] <ogra> Tanguy, if y package was eitrher manually merged or touched in any other way in ubuntu, the maintainer field is rewritten
[15:33] <ogra> best is to check the changelog in ubuntu
[15:33] <Tanguy> ogra: This is what I did.
[15:34] <Tanguy> Ubuntu currently has a fork of the Debian package.
[15:34] <bdmurray> doko_: bug 504198 seems to have regressed for me
[15:34] <ogra> a fork ?
[15:34] <Laney> If there are no changes in Ubuntu that aren't in Debian (or if they can be dropped) then the package can be synced
[15:34] <ogra> right
[15:34] <tedg> mdeslaur, If you're talking about anything with webkit, probably.  It seems like everything is segfaulting for me right now (liferea/gwibber/etc)
[15:34] <Tanguy> ogra: Well, I mean, it has been modified, that makes it a kind of forked development.
[15:34] <ogra> we usually dont fork packages
[15:34] <cjwatson> "branch" :)
[15:35] <ogra> there might be ubuntu patches on top indeed
[15:35] <mdeslaur> tedg: the menu just doesn't draw at all, nothing
[15:35] <Tanguy> Well, this patch is: update from oooold version 0.3 to the last version 0.8.
[15:35] <ogra> yeah, branch + ubuntu patches is possible, the core should still be debian
[15:35] <ogra> awww, thats indeed a big patch
[15:35] <Tanguy> It is not maintained as a patch.
[15:35] <tedg> mdeslaur, Uhm, that's odd.  Do you have any menus?  Sometimes they end up getting stacked behind the desktop.
[15:35] <Tanguy> This is why I am speaking of a fork.
[15:35] <cjwatson> if a new version of the package in Debian can be shown to be a superset of what we currently have in Ubuntu, then it's fairly straightforward for us to go back to just copying the package from Debian verbatim
[15:36] <cjwatson> fork/branch terminology notwithstanding
[15:36] <Tanguy> Yes, sure, this is what I would like to see. :-)
[15:36] <cjwatson> https://wiki.ubuntu.com/SyncRequestProcess
[15:36] <ogra> yeah, just make 0.8 available in debian
[15:36] <mdeslaur> tedg: this is with classic desktop. Indicator sound and the network manager indicators are working fine
[15:36] <Tanguy> cjwatson: Does that fact that the package has been forked affect the sync process?
[15:37] <cjwatson> Tanguy: it just means that somebody has to assess whether any of the Ubuntu changes are still needed; not otherwise
[15:37] <mdeslaur> tedg: the message indicator, when clicked, draws the decorations around the icon as if it's displaying the menu, but no menu gets drawn underneath
[15:37] <cjwatson> Tanguy: oh, since it's a new upstream in Ubuntu, the .orig.tar.gz will need to match between Debian and Ubuntu
[15:38] <Tanguy> It will. :-)
[15:38] <cjwatson> hopefully it's just a copy of the upstream tarball, but I haven't checked
[15:38] <ogra> if it will, its likely very trivial
[15:38] <Tanguy> (unless it has been repacked in Ubuntu, but it hsould not be the case)
[15:38] <tedg> mdeslaur, Hmm.  Classic desktop ==  Legacy old-crufty-stick-in-the-mud-developer interface?  ;)
[15:38] <cjwatson> judging from the modification timestamps, it hasn't
[15:38] <tedg> mdeslaur, Is the indicator-messages-service running?
[15:38] <mdeslaur> tedg: classic desktop = waiting for unity workspace support to not suck
[15:39]  * cjwatson just loves being pejoratively labelled ...
[15:39] <cjwatson> (tedg)
[15:39] <mdeslaur> tedg: yes, it's running
[15:39] <Tanguy> So, when I update the package in Debian, I should file a bug report asking for a sync, right?
[15:39] <cjwatson> Tanguy: yep
[15:39] <Tanguy> Thanks.
[15:40] <cjwatson> for best results, use 'requestsync --lp libasyncns natty'
[15:40] <cjwatson> (ubuntu-dev-tools)
[15:40] <cjwatson> that writes the bug report in a form such that our automated tools can pick it up easily
[15:41] <mdeslaur> tedg: I'll switch to unity in a few minutes, to see if it's working there
[15:41] <tedg> mdeslaur, Hmm, yeah.  I'm not sure what's up then.  You can try Unity, but it really shouldn't be different...
[15:41] <tedg> mdeslaur, Basically, for the menus, the same code runs.
[15:41] <mdeslaur> weird
[15:42]  * mdeslaur -> log out, log in
[15:46] <mdeslaur> tedg: all menus are broken in unity
[15:46] <tedg> mdeslaur, you can try to see if you get a menu with this: /usr/lib/libdbusmenu/dbusmenu-dumper -d com.canonical.indicator.messages -o /com/canonical/indicator/messages/menu
[15:46] <tedg> mdeslaur, Uhg
[15:46] <mdeslaur> tedg: I don't seem to have dbusmenu-dumper
[15:47] <hallyn> oh, yeah - and 'unity --reset' is no longer  an option bc unity disappeared
[15:47] <tedg> mdeslaur, http://apt.ubuntu.com/p/libdbusmenu-tools
[15:49] <mdeslaur> tedg: http://paste.ubuntu.com/555436/
[15:51] <tedg> mdeslaur, Uhm... that seems completely reasonable...
[15:51] <mdeslaur> tedg: hmm...clicking on the unity launcher makes it disappear
[15:51] <mdeslaur> tedg: and when I click the desktop again, it comes back
[15:52] <didrocks> mdeslaur: sounds like a stacking issue, does it still react when you click on it (when disappeared)?
[15:54] <mdeslaur> didrocks: I made it disappear like 10 times in a row, and then the top panel disappeared, reappeared and now the launcher is behaving properly
[15:54] <didrocks> mdeslaur: probably the stacking then
[15:54] <mdeslaur> oh! and I now have menus!
[15:55] <mdeslaur> oh, except menus are drawing underneath all the other windows
[15:55] <mdeslaur> didrocks: yeah, stacking issue :(
[15:55] <didrocks> mdeslaur: known issue then :(
[15:56]  * mdeslaur goes back to the old-crufty-stick-in-the-mud-developer interface
[15:56] <tedg> mdeslaur, heh ;)
[16:14] <Riddell> cjwatson: I trained up didrocks in archive admin tasks last week, can you add him to ~ubuntu-archive?
[16:16] <cjwatson> Riddell: excellent!  done, please file an RT for the shell access bit.  is he going to take an archive day, or do any particular tasks?
[16:17] <didrocks> cjwatson: Riddell: thanks! on the archive day, I'll do random stuff first (still a little busy with unity this cycle), but I plan to take an archive day next cycle
[16:18]  * cjwatson nods
[16:19] <kklimonda> jdstrand: any idea why would python-django fail on buildds out of the blue? It still builds in maverick ppa, and it did build before maverick release. Build-Depending on locales-all | locale-pack-en-base seems to be the only way to do what I want, dropping it would only introduce another delta.
[16:20] <kklimonda> (some tests are expecting unicode locales to be set, and they fail otherwise)
[16:20] <cjwatson> you could generate the locale at build time instead
[16:20] <cjwatson> (localedef)
[16:20] <cjwatson> see e.g. lintian's postinst
[16:20] <kklimonda> cjwatson: where were you when I was asking people for advice? :)
[16:20] <cjwatson> I know you wouldn't want to do it in the postinst, but the command-line invocation would be about the same
[16:20] <cjwatson> heh
[16:23] <kklimonda> cjwatson: thanks for the idea, I'll check lintian and see if that helps
[16:24] <nigelb> 7
[16:24] <nigelb> gah, sorry
[16:36] <pitti> bryceh, RAOF: FYI, xorg-edgers holding up well for three days already, including about 10 suspend/resume cycles (I basically didn't reboot again after the upgrade on Sunday)
[16:36] <bryceh> pitti, excellent
[16:36] <bryceh> pitti, yeah it's been running solidly on my netbook as well
[16:37] <bryceh> pitti, there's still some bits and pieces needing attention that have turned up, but I expect we're on schedule to see it in main within a week or so
[17:04] <SpamapS> anybody else have a problem on natty where gdm doesn't work on bootup? I have to switch to tty1 and restart it.
[17:04] <SpamapS> I get a blank screen and I'm clearly in X (have to do ctrl-alt-f1)
[17:05] <SpamapS> seems like maybe plymouth doesn't deactivate properly or something
[17:09] <cjwatson> SpamapS: does anything in https://wiki.ubuntu.com/FoundationsTeam/Grub2BootFramebuffer/Whiteboard ring a bell?
[17:09] <cjwatson> try each of the two workarounds in the top section, preferably individually (those go in /etc/default/grub, and run update-grub after each)
[17:14] <SpamapS> cjwatson: will try them out shortly, thanks. :)
[17:14] <bjf> just installed Alpha 1, then a dist-upgrade, then a reboot and am sitting at a purple screen, can't switch to tty1
[17:15] <davmor2> bjf: is it just dark purple?
[17:16] <davmor2> bjf: as in it isn't the desktop background?
[17:17] <bjf> davidm, correct, it should be the screen with the logo and the dots under it
[17:18] <davmor2> bjf: does your caps lock key flash?
[17:18] <bjf> davidm, yes, flashing right now
[17:18] <davmor2> bjf: If so welcome to the wonderful world of kernel panic
[17:20] <davmor2> bjf: for some reason that isn't easily reproducible on my system I get it,  just power off give it a few seconds and switch back on, you'll be greeted by the grub screen select the top entry and away you go
[17:20] <bjf> davmor2, if i hold the left shift to get into grub, i get screen corruption (after powering down and back up)
[17:21] <bjf> davmor2, ie. the grub menu is corrupted (visually)
[17:22] <davmor2> bjf: you should need to press any key it should just go to it after a kernel panic
[17:22] <cjwatson> bjf: when it's corrupted, move the cursor down/up so that it doesn't time out
[17:22] <cjwatson> bjf: then press c
[17:22] <cjwatson> bjf: then type 'terminal_output console' and press enter.  does that get you a prompt?
[17:23] <cjwatson> (yes, you have to type this blind)
[17:23] <bjf> cjwatson, grub>
[17:24] <cjwatson> bjf: type 'videoinfo' - what does it say the EDID preferred mode is?  (should be near the end)
[17:25] <bjf> cjwatson, dont see it, "Adapter 'VGA Video Driver': No info available"
[17:25] <cjwatson> try 'set pager=1' before 'videoinfo', and page through the output
[17:26] <bjf> cjwatson, my bad, EDID version: 1.3 Preferred mode: 1440x900
[17:26] <cjwatson> thinkpad?
[17:26] <bjf> cjwatson, thinkpad x301
[17:26] <cjwatson> you have the sixth entry under Problems in https://wiki.ubuntu.com/FoundationsTeam/Grub2BootFramebuffer/Whiteboard
[17:26] <cjwatson> workaround:
[17:26] <cjwatson> set gfxmode=1440x900
[17:26] <cjwatson> er, sorry
[17:26] <cjwatson> set gfxmode=1440x900x16
[17:26] <cjwatson> terminal_output gfxterm
[17:27] <cjwatson> background_color 44,0,30
[17:27] <cjwatson> then press escape and you'll be back in the menu
[17:27] <cjwatson> then try booting
[17:27] <bjf> cjwatson, thanks, will give it a go
[17:27] <cjwatson> this is a BIOS bug - the X VESA driver suffers from it in pretty much exactly the same way (according to RAOF's tests).  I'm hoping to think of a workaround that doesn't suck
[17:28] <cjwatson> you can make the above sticky by editing /etc/default/grub and putting 'GRUB_GFXMODE=1440x900x16' there, then 'sudo update-grub'
[17:28] <bjf> cjwatson, worked so far
[17:29] <bjf> cjwatson, however now it looks like i'm still getting a kernel panic, cursor in upper left of screen and flashing capslk key
[17:30] <cjwatson> OK, try the above but with 'set linux_gfx_mode=text' as well
[17:30] <bjf> cjwatson, will do
[17:30] <cjwatson> we didn't see the kernel panic on the laptops with this problem that we tested at the sprint
[17:31] <cjwatson> apw: ^- FWIW, this may be straying into your domain
[17:31] <davmor2> cjwatson: I've had them with this amilo-li-2727 on and off but not predictably but only on restarts
[17:32] <apw> cjwatson, /me reads
[17:33] <cjwatson> davmor2: only on restarts as opposed to ...?
[17:34] <davmor2> cjwatson: I don't get it if I halt the system, and power on from cold,  only on restarts
[17:34] <cjwatson> davmor2: and you're seeing specifically the display corruption when trying to display the grub menu?
[17:35] <davmor2> no I don't get that bit nice clear grub screen
[17:35] <cjwatson> (the distinction between grub and the kernel and X is vitally important here)
[17:35] <davmor2> I just get the kernel panic
[17:35] <apw> bjf, so does it boot ok without with linux_gfxmode=text and without splash on the kernle command line ?
[17:35] <cjwatson> davmor2: have you seen it since upgrading to linux 2.6.37-8.20?
[17:36] <cjwatson> (linux_gfxmode doesn't exist FWIW)
[17:36] <bjf> apw, no, same result
[17:37] <apw> hrmphf
[17:37] <bjf> indeed
[17:37] <davmor2> cjwatson: I'm currently on 2.6.37-12-generic
[17:37] <cjwatson> linux_gfx_mode=text + no quiet + no splash should at least get you a text panic ...
[17:37] <apw> bjf what changed to get you here ?  upgrade to natty
[17:38] <cjwatson> actually, rather than 'set linux_gfx_mode=text', it might be worth going into the grub menu editor (same screen as where you remove quiet and splash) and changing 'set gfxpayload=$linux_gfx_mode' to 'set gfxpayload=text'
[17:38] <bjf> apw, yes, I re-installed natty this a.m. (alpha 1) and then did a dist-upgrade to get caught up, that gave me this result
[17:38] <cjwatson> just in case I got my logic wrong there
[17:41] <bjf> cjwatson, apw, did as last suggest and same result
[17:42] <cjwatson> could you repeat exactly what you did just so that we're on the same page?
[17:42] <cjwatson> this is so much harder when not in front of the box
[17:42] <bjf> cjwatson, ok, one sec
[17:46] <ogra> WTF
[17:46]  * ogra curses
[17:46] <bjf> cjwatson, apw: hold shift key to get to grub
[17:46] <bjf> cjwatson, apw: move arrow keys to not get timeout
[17:46] <bjf> cjwatson, apw: pressed "c" to get into a command mode
[17:46] <bjf> cjwatson, apw: typed "terminal_output console"
[17:46] <bjf> cjwatson, apw: typed "set gfxmode=1440x900x16"
[17:46] <bjf> cjwatson, apw: typed "terminal_output gfxterm"
[17:46] <bjf> cjwatson, apw: typed "background_color 44,0,30"
[17:46] <bjf> cjwatson, apw: typed "Esc" to get back to the grub menu
[17:46] <bjf> cjwatson, apw: typed "e" to get to the editor
[17:46] <bjf> cjwatson, apw: replaced "$linux_gfx_mode" with "text"    (no dbl-quotes)
[17:46] <bjf> cjwatson, apw: removed "quiet splash"
[17:46] <bjf> cjwatson, apw: pressed "F10" to boot
[17:46] <ogra> so ubuntu-netbook is installable in my chroot ... but antimony still chokes on libwebkitgtk
[17:47] <cjwatson> ogra: make sure you don't have universe/multiverse on
[17:47] <ogra> i dont get that
[17:47] <ogra> cjwatson, in my chroot ? i dont
[17:47] <ogra> its newly bootstrapped
[17:47] <cjwatson> dunno then, but I bet it's not antimony choking, surely a livefs buildd instead
[17:47] <cjwatson> bjf: that looks plausible then.  do you get a text panic now?
[17:47] <ogra> both then
[17:48] <bjf> cjwatson, no, still cursor in upper left of screen, capslk flashing
[17:49] <cjwatson> ogra: and did you try ubuntu-netbook^ (the task) rather than ubuntu-netbook (the metapackage)?
[17:49] <davmor2> cjwatson, bjf: would it be worth trying to boot into rescue mode that'll give you text output and maybe the panic?
[17:49] <ogra> cjwatson, ah, no, i didnt
[17:49]  * ogra tries
[17:49] <cjwatson> ogra: it fails in chdist for me
[17:50] <ogra> yeah, task fails
[17:50] <bjf> davmor2, that's where i'm heading right now
[17:50] <ogra> phew
[17:50] <cjwatson> davmor2: recovery mode is pretty much equivalent to removing 'quiet splash', which he's already done
[17:50] <ogra> i thought i'd go insane ... indeed PEBCAK
[17:50] <cjwatson> the only other difference is that it doesn't save the default entry
[17:51] <cjwatson> bjf: oh, you might try removing vt.handoff=7 from the kernel command line
[17:51] <cjwatson> (which, come to think of it, is another difference in recovery mode)
[17:51] <bjf> cjwatson, recovery mode worked better, have text which shows the panic now
[17:52] <cjwatson> bjf: so just to make sure, try normal mode but remove quiet splash and vt.handoff=7
[17:52] <bjf> cjwatson, will do
[17:52] <cjwatson> apw: I guess this is more or less on your turf now
[17:53] <ogra> ah !
[17:53] <ogra> rhythmbox pulls in the old webkit
[17:53] <pitti> ogra: hm, I thought I uploaded a rebuild for that
[17:53] <ogra> yeha, i see an upload
[17:54] <ogra> ftbfs on arm
[17:58] <ogra> error: Dbusmenu-Glib-0.2 not found in specified Vala API directories or GObject-Introspection GIR directories
[17:58] <ogra> hmpf
[18:02] <seb128> ogra, it needs to be updated for the new libdbusmenu
[18:03] <ogra> seb128, yep
[18:03] <seb128> ogra, seems the other archs built before the new libdbusmenu so they were ok
[18:03] <seb128> ogra, I can fix that tomorrow I planned to upload the new rb as well
[18:03] <andreserl> Can anyone from foundations take a look at bug #525287
[18:04] <ogra> seb128, yeah, fine, i wont put work into it then
[18:04] <seb128> ogra, ok
[18:17] <hallyn> cmagina: hey, if you get a chance (since I know you've tested it :) could you comment that you've verified bug 686832 and bug 660597 ?
[18:18] <cmagina> hallyn: will do
[18:19] <hallyn> cmagina: thanks
[18:22] <stgraber> tumbleweed: ping
[18:23] <stgraber> tumbleweed: I'm working on uploading suspended-sentence, I'll put the right version number in there but I'm wondering if you have any issue with me dropping the two first changelog entries
[18:24] <stgraber> tumbleweed: so the first changelog entry for what will hit extra.u.c will match the first upload
[18:34] <janimo> is there a specific team/individual taking care of banshee? If so is 1.9.2 planned soon?
[18:36] <micahg> hyperair: ^^
[18:37] <micahg> hmm, already in Debian experimental
[18:38]  * micahg guesses hyperair can't help with that anymroe
[18:38] <micahg> *anymore
[18:40] <micahg> janimo: it's on the Desktop Team's list of packages to update now, you might want to ask in #ubuntu-desktop if it's urgent
[18:41] <hyperair> micahg: oi
[18:41] <janimo> micahg, thanks, not urgent, just good to know, as it may affect an armel bug
[18:41] <hyperair> who said i'm not working on it?
[18:41] <hyperair> i'm waiting on banshee-community-extensions
[18:42] <micahg> hyperair: I meant about getting it merged into Ubuntu :), unless you got PPU already for it
[18:42] <hyperair> there's this dude who has a suspicious jamendo icon there i'm not sure comes from where
[18:42] <hyperair> micahg: it is in the PPA.
[18:42] <hyperair> micahg: AND i will be getting it merged into ubuntu. i just don't want to break banshee-community-extensions.
[18:43] <hyperair> micahg: so whoever touches banshee... better not mess it up, or his/her head will roll.
[18:43] <micahg> hyperair: ok, just noticed it's in main now
[18:43] <hyperair> we have package sets now
[18:43] <hyperair> being in the debian-cli team i retain upload access to banshee
[18:43] <hyperair> now that that's clarified, let me get back to my book
[18:43] <micahg> hyperair: ah, ok, cool, didn't realize it was in there :)
[18:43] <hyperair> lisbeth salander is ♥
[18:44] <micahg> janimo: so hyperair's the one :)
[18:45] <micahg> package sets, FTW!
[19:01] <tumbleweed> stgraber: fine with me
[20:49] <SpamapS> jelmer: w000t ty for the paramiko update! :)
[20:55] <jelmer> SpamapS: please thank StevenK for sponsoring :-)
[21:04] <SpamapS> StevenK: thanks for sponsoring the paramiko upload! :)
[21:07] <StevenK> SpamapS: :-)
[21:30] <superm1> pitti, would you mind doing another release of jockey before the next alpha?  i'd like to be able to test with some of the modaliased-driver package things as the media starts to stabilize again
[22:07] <lifeless> bdrung: ping (bug 704657)
[22:08] <bdrung> lifeless: merge proposals are welcome
[22:34] <tumbleweed> lifeless, bdrung: I noticed that a while back, but knew the new launchpadlib was about to land, it will probably mean manage-credentials is no longer needed
[22:36] <maxb> How long is the ubuntu-backporters review queue these days? (>20 days seems quite a lot)
[22:37] <ebroder> maxb: it's pretty long, and the amount of backlog unfortunately tends to make working on it discouraging
[22:37] <maxb> How long is considered an acceptable demonstration of patience before trying to hunt people down on IRC? :-)
[22:38]  * micahg thought there was a helper script now and it was built in to AA duties
[22:38] <ebroder> micahg: yes, but that's only once backporters have approved it
[22:39] <maxb> Hmm, https://bugs.launchpad.net/~ubuntu-backporters/+subscribedbugs is "only" 27 entries
[22:39] <micahg> ebroder: oh, he means the actual approval
[22:39] <maxb> That's not as dire as it could be
[22:39] <ebroder> maxb: that's only bugs that ~u-b are explicitly subscribed to, i think. you want to look at https://bugs.launchpad.net/lucid-backports/+bugs and similar
[22:42] <ebroder> maxb: if you haven't already, you can make your request more appealing to review by making sure that you've tested that the packages build, install, and run
[22:42] <maxb> done that :-)
[22:42] <maxb> and listed the reverse-depends too
[22:42]  * ebroder sighs
[22:42] <ebroder> fine, you've got my attention. i can at least look at it and tell you what additional checking i think would need to be done
[22:43] <ebroder> (note: i'm not currently a backporter, but i do a lot of backports)
[22:45] <lifeless> tumbleweed: its trivial to fix - s/edge/production
[22:45] <lifeless> bdrung: a mp seems overkill when you can just do the replace and commit directly.
[22:45] <tumbleweed> lifeless: indeed
[22:49] <maxb> bug 695108 is the one I'm interested in
[22:49] <ebroder> maxb: should this be an sru instead of a backport?
[22:50] <ebroder> we don't usually backport to fix bugs - we backport to add features
[22:50] <maxb> It's a "bring in the latest upstream, which is better" rather than a "targetted application of specific bugfixes"
[22:50] <maxb> That seems more backport than SRU territory to me
[22:55] <micahg> ebroder: a backport to maverick is required for an upgrade path as well, right?
[22:56] <ebroder> yes, it would be
[22:58] <micahg> ebroder: I agree with you, this seems more SRU material since the version in the archive is broke
[22:59] <micahg> maxb: a backport helps UDD, but not other people without backports enabled
[22:59] <bdrung> lifeless: then just push the change to the ubuntu-dev-tools branch. it's owned by ubuntu-dev
[23:01] <maxb> micahg: A SRU requires a minimal patch. I don't think it's in anyone's interests to take the time to prepare one for this package
[23:02] <lifeless> bdrung: maybe I'm looking at the wrong place; whats the lp url for the branch ?
[23:02] <bdrung> lifeless: lp:~ubuntu-dev/ubuntu-dev-tools/trunk
[23:03] <maxb> The pristine-tar in the archive for lucid does break on a small proportion of the tarballs of packages in the archive, it's true. But the target audience that needs it to work is small indeed.
[23:03] <maxb> james_w`: around?
[23:03] <james_w`> hi maxb
[23:04] <maxb> james_w`: Hi. We're discussing whether pristine-tar can be backported to lucid, or whether it gets bumped from the backports process on the grounds of being a bugfix that ought to be SRUed
[23:05] <lifeless> bdrung: pushed
[23:07] <james_w`> maxb, my hunch is that it would be bumped from the SRU process due to it being too instrusive
[23:08] <maxb> That was what I was thinking. I hope it doesn't fall down a crack between the backports and SRU processes and be lost forever :-/
[23:09] <ebroder> maxb, james_w`: you should probably get ScottK or one of the other backporters to weigh in - his opinion is official; mine is not
[23:13] <james_w`> the change that fixed it is: "zgz now includes a trimmed down copy of the compressor from bzip2 0.9.5d."
[23:14] <james_w`> sounds quite intrusive
[23:20] <maxb> I think that can be sold as a "feature"
[23:21] <ebroder> maxb: look, if you can just point me at any new feature that was added to pristine-tar... :-P
[23:22] <maxb> "Include a copy of the compressor from bzip2 0.9.5d"
[23:32] <andreserl> jml: howdy!! So, do you have any ideas on how to do what you proposed for testdrive?
[23:32] <jml> andreserl: some
[23:32] <jml> andreserl: I'd copy code from lp:start-hacking, and muck around a bit, basically
[23:35] <andreserl> jml:righ but I mean, how could we pass information to a VM to launch the specific application
[23:38] <andreserl> btw.. is there anyone from foundations around that can take a look at bug #525287
[23:48] <james_w`> andreserl, cloud-init!
[23:50] <andreserl> james_w`: yes that's what I was thinking too :)
[23:51] <andreserl> smoser: would it be possible to use cloud-init with uec images that run in testdrive?
[23:52] <james_w`> desktop images?
[23:52] <andreserl> james_w`: yes, desktop images
[23:52] <andreserl> james_w`: testdrive already supports launching UEC server images