[00:08] <bryce> heh, people are still complaining about CAB - https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/343690/comments/3
[04:59] <tjaalton> jcristau: asac dropped the debconf templates from fontconfig..
[04:59] <tjaalton> I'm not sure why
[05:26] <bryce> tjaalton: libdrm has one bug left, but I'm uncertain what to do about it
[05:28] <tjaalton> bryce: actually it should be fixed by the one we have
[05:29] <tjaalton> jcristau fixed it, libdrm1-intel.symbols referenced libdrm and not the package itself :)
[05:29] <bryce> ok, so can we just close it then?
[05:29] <tjaalton> yes
[05:29] <bryce> awesome
[05:29] <tjaalton> and -intel could drop the direct dependency
[05:30] <bryce> ok... I'll add that for my next -intel upload
[05:34] <bryce> tjaalton: hmm, what was the specific change in libdrm that enabled this to be dropped?  I'm sort of sketchy understanding this
[05:46] <tjaalton> bryce: commit a87c1a081b77a29fe3430d
[05:48] <bryce> hmm, we seem not to have that change?
[05:48] <bryce> libdrm_intel.so.1 libdrm2 #MINVER#
[05:49] <tjaalton> oh
[05:49] <bryce> wait nevermind, I was looking at the wrong git checkout
[05:50] <tjaalton> it should be merged
[05:51] <bryce> yep, it's good.  I just have a lot of stray broken git trees from when I did the libdrm merge.  Guess I need to tidy up a bit.
[05:53] <tjaalton> btw, -joystick is uninstallable, but maybe it's time for a FFe as well since the current one doesn't build
[05:53] <bryce> what needs done?
[05:54] <tjaalton> upload a new upstream version
[05:54] <tjaalton> there's 1.4.0 available
[05:55] <bryce> can we sync?
[05:55] <tjaalton> it's not in debian
[05:55] <bryce> oh
[05:56] <bryce> er, weird.  why not?
[05:56] <tjaalton> because hardly anyone uses it, and xserver 1.6 is still in experimental
[05:56] <bryce> oh you mean 1.4 isn't in debian, not that -joystick isn't in debian
[05:57] <tjaalton> so when it's moved to unstable, every driver needs to be rebuilt
[05:57] <tjaalton> yeah
[05:57] <bryce> sorry, it's late, my brain must be going, again
[05:57] <tjaalton> heh
[05:57] <tjaalton> and early here
[05:57] <bryce> ok, if it's just a matter of updating to the new tarball I can take care of that right now
[05:58] <bryce> but I see there's some notes... "drop the fdi file and push for hal recognising joysticks (patch by mjg59)" - not sure what that means
[05:58] <tjaalton> well, I could sort that out
[05:58] <tjaalton> the fdi file needs a cleanup
[05:59] <bryce> ok thanks
[05:59] <bryce> I should have this uploaded in 15 min or so
[06:02] <tjaalton> k, gotta go now ->
[06:07] <bryce> tjaalton: ok, 1.4 uploaded.  Have at it with the fdi changes whenever's convenient.
[06:50] <tjaalton> bryce: sure, thanks
[08:29] <tjaalton> seb128: what nick does alex use?
[08:29] <seb128> alex_
[08:29] <seb128> he's not there yet apparently
[08:29] <tjaalton> ok, not there yet
[08:29] <tjaalton> right
[20:06] <federico1> tseliot: any further progress on bgo#572876, by the way?
[20:07] <tseliot> federico1: no, sorry, I've been very busy with my new job. It's on my TODO list though
[20:08] <federico1> ah, ok
[20:09] <federico1> new job?
[20:10] <tseliot> federico1: at Canonical ;)
[20:10] <tseliot> federico1: I work for the OEM team on X stuff now
[20:11] <federico1> oooh, the pain of OEMs
[20:11] <federico1> good luck, and congrats :)
[20:12] <tseliot> thanks :-)


[09:54] <om26er> Hi! what's the package name I need to install to get started with Ubuntu' App Development using the SDK on Zesty ?
[09:54] <om26er> zsombi: can you tell ^
[09:55] <om26er> ubuntu-sdk does not seem to be available on zesty.
[10:38] <tomreyn> om26er: i think the sdk is only available on LTS releases
[10:48] <Mirv> om26er: I'll try a build on zesty, it'll appear at https://launchpad.net/~ubuntu-sdk-team/+archive/ubuntu/tools-development/+packages in a few hours
[10:48] <Mirv> om26er: currently there's none that's true
[10:49] <Mirv> zsombi: zbenjamin: bzoltan: ^ just FYI
[10:50] <zsombi> k


 @mitya57 FYI https://mail.kde.org/pipermail/distributions/2020-June/000365.html
 In case you are not aware...
 I saw it, yes. It it's not urgent I would wait until the fix is merged upstream.


 As long as I caffinate sufficiently then I'm fine.
[06:25] <Kilos> lol
[06:30] <Vince-0> sup!
[06:30] <Vince-0> aarg, its work time bbl
[06:47] <inetpro> oh and a very good mornings tp everyone else as well and Kilos
[06:47] <Kilos> hehe ty sir
[07:05] <superfly> ohi
[07:06] <inetpro> anyone else having performance issues to security.ubuntu.com or is it just me?
[07:08] <Kilos> i get here fine albeit slow
[07:08] <Kilos> http://www.ubuntu.com/usn/
[07:08] <inetpro> apt-get update taking forever
[07:08] <Kilos> lemme try
[07:09] <Kilos> Fetched 4 946 kB in 28s (175 kB/s)
[07:09] <Kilos> thats with neology
[07:11] <Kilos> ai! another 109m upgrades
[07:11] <Kilos> 102
[07:15] <Kilos> Fetched 102 MB in 4min 10s (408 kB/s)
[07:15] <inetpro> ok, looks like whatever it was it is better now
[07:16] <inetpro> was just the part going to security.ubuntu.com that was slow
[07:16] <Kilos> internet been flaky for a while now
[07:16] <inetpro> s/going to/pulling from/
[07:16] <Kilos> ai! system restart needed
[07:16] <Kilos> wbb
[07:18] <inetpro> eish man!
[07:18] <inetpro> now we have a Hash Sum mismatch at ubuntu.mirror.neology.co.za
[07:18]  * inetpro should probably just wait
[07:19] <inetpro> or maybe time to switch to Kenya
[07:41] <inetpro> ok looks like it was a caching issue... resolved with 'sudo apt-get update -o Acquire::http::No-Cache=true'
[07:42] <Kilos> local cache?
[07:43] <inetpro> upstream cache
[07:43] <Kilos> ah
[11:24]  * Padroni waves
[11:25] <Kilos> hi Padroni
[11:27] <Padroni> hi
[11:27] <Padroni> how are you?
[11:27] <Kilos> ok ty and you?
[11:27] <Padroni> I'm good
[11:28] <Padroni> Ubuntu is making me dumb :/
[11:28] <Kilos> making?
[11:28] <Padroni> just saw a BSOD for the first time in so long, I at first thought it was part of a website I was browsing
[11:28] <Kilos> what are you battling with
[11:28] <Padroni> then memory dump, then reboot
[11:28] <Padroni> then I remembered - windows does this sometimes...
[11:28] <Kilos> whats a BSOD
[11:29] <Padroni> Blue Screen Of Death
[11:29] <Kilos> oh my
[11:29] <Padroni> stop error in windows
[11:29] <Kilos> ya but that doesnt happen on ubuntu
[11:29] <Padroni> pc reboots automatically after that
[11:29] <Padroni> I know - been using ubuntu so long I forgot what a BSOD is
[11:29] <Kilos> lol
[11:29] <Padroni> so when it happened to me now, it completely confused me
[11:30] <Kilos> oh you on win?
[11:30] <Padroni> I was like - what an odd color for a web page background...
[11:30] <Kilos> lol
[11:30] <Padroni> and then I recognized it
[11:30] <Kilos> bad site you went to
[11:30] <Padroni> must be
[11:30] <Kilos> think of all the poor win peeps that are gonna be crying
[11:31] <Padroni> lol
[11:31] <Padroni> i found a use for my ipad again
[11:31] <Padroni> I download linux books in pdf and read it when I have to fly somewhere
[11:32] <Padroni> gives me something to do on the plane
[11:32] <Kilos> thats useful
[11:46] <cal_py> Anyone here taken a gander at Unity 8?
[11:46] <superfly> I'm a firm KDE fanboi
[11:47] <Kilos> lol
[11:47] <Kilos> cal_py learn to use kde
[11:47] <cal_py> KDE is easy
[11:47] <cal_py> very windows like
[11:47] <Kilos> i hear everyone raving about plasma 5
[11:47] <cal_py> But also very polished
[11:48] <Kilos> oh dont you want easy
[11:48] <cal_py> Unity 8 looks good thou, I just dont like the fact that they have taken some ideas from windows when the app's are loading
[13:31] <Padroni> hi
[13:33] <Padroni> 35 people and no one is speaking
[13:33] <Padroni> what is the point of being connected then?
[13:39] <Kilos> sshhhh
[13:40] <Kilos> i just had a beard cut and busy repairing flymo where rats ate the wires near the coils
[13:41] <chesedo> cal_py: have test driven it for a few minutes
[13:41] <cal_py> and?
[13:41] <chesedo> just wish it was more complete
[13:42] <Padroni> test driven what?
[13:42] <chesedo> unity next
[13:43] <chesedo> ...more complete at the time that is
[14:10] <superfly> Padroni: http://www.datamation.com/osrc/article.php/3693951/Linux-Is-Boring.htm
[14:27] <squish102> what is the speed of wifi G network?
[14:28] <squish102> i want to set up a rasberry pi to take snapshots of speedtest every hour
[14:28] <squish102> but it is connected to wifi
[14:32] <dlPhreak> hi
[14:47] <chesedo> squish102: 54Mbits/s
[14:47] <chesedo> max, will be lower at all times
[15:17] <williamk> Hi All
[15:18] <chesedo> hi williamk
[15:20] <williamk> Hi chesedo
[15:31] <Kilos> hi williamk
[15:31] <Kilos> what happened to wwk
[15:40] <williamk> I am still here, trying to cook at same time
[15:40] <Kilos> dont burn your supper
[15:59] <williamk> Have not burnt it so far
[16:00] <Kilos> lol
[16:02] <williamk> was talking to  Kapanda Phiri via ubuntu-za list, about end-user certificates,
[16:03] <Kilos> i saw
[16:03] <Kilos> you should have told him to come here
[16:03] <williamk> as Ubuntu had training manuals, which looks like they are not keeping up to date,
[16:03] <Kilos> mail reading is a pain
[16:04] <williamk> Possibly we can start some Certifications
[16:04] <Kilos> thats a great idea its just getting them reconised or certied govt wise
[16:05] <Kilos> you might have to affiliate wit a varsity or college
[16:05] <Kilos> young peeps will have more knowlege about how things work nowadays
[16:06] <williamk> possibly with Siyavula : http://www.siyavula.com/ they have some with the DBE : http://www.education.gov.za/Curriculum/SiyavulaTextbooks/tabid/591/Default.aspx
[16:08] <Kilos> ah
[16:15] <williamk> supper is ready, cheers, might see you later
[16:59] <cal_py> Yo yo yo good evening!!
[17:28] <Kilos> pieter2627 chesedo dies again
[17:28] <Kilos> died
[17:51] <Kilos> padroni why so quiet?
[18:05] <inetpro> Kilos: why so quiet?
[18:05] <inetpro> good morning everyone
[18:05] <Kilos> im trying that new thing out
[18:05] <Kilos> and the older one
[18:06] <Kilos> chill and mellow
[18:06] <Kilos> and thinking about julle tweetjies
[18:07] <Kilos> and everyone always busy so that leaves
[18:07] <Kilos> Maaz coffee on
[18:07]  * Maaz washes some mugs
[18:09] <Kilos> i actually thought i wasnt connected for a while inetpro so share a cuppa with me'
[18:10] <Kilos> Maaz tell padroni So rude, not even a toodles before going
[18:10] <Maaz> Kilos: Okay, I'll tell Padroni on freenode
[18:11] <Kilos> haha
[18:11] <Maaz> Coffee's ready for Kilos!
[18:12] <Kilos> Maaz danke
[18:12] <Maaz> Bitteschön
[18:13] <chesedo> Kilos: it's alive!!
[18:14] <Kilos> yay
[18:14] <Kilos> you need to change the order of nicks in your client
[18:15] <Kilos> make first one chesedo then add a tail ot two
[18:15] <Kilos> or
[18:16] <chesedo> when the connection drop and it reconnects the server still thinks chesedo is taken so goes to second
[18:16] <Kilos> nee man
[18:16] <Kilos> chesedo- as second choice
[18:17] <Kilos> and chesedo-- as thrid choice
[18:17] <Kilos> third
[18:17] <chesedo> yay can do that too
[18:17] <Kilos> lol
[18:19] <Kilos> ohi who_da_fly
[18:19] <Kilos> you on cell now?
[18:20] <Kilos> oh no, server
[18:23] <superfly> Kilos: no, the data centre my server is in was having some problems
[18:23] <Kilos> ah
[18:23] <Kilos> wb then superfly
[18:25] <Kilos> peeps are clever (͡° ͜ʖ ͡°)
[19:19] <Kilos> night all. sleep tight
[19:19] <inetpro> good night oom Kilos


[01:16] <sarnold> doko,infiniti,jdstrand, curtin's MIR still requires a MIR team member review: 1220434
[01:21] <Noskcaj> Has anyone looked at bug 823254  recently?
[01:47] <FourDollars> Laney: Yes. Please see my comment at https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1065979/comments/37.
[05:31] <pitti> Good morning
[06:32] <asac> o/
[07:12] <dholbach> good morning
[08:11] <infinity> smoser: Can you get a team subscription to curtin set up?
[08:40] <doko> infinity, did you see 1203496 in other packages too?
[08:42] <infinity> doko: I don't remember if I saw it elsewhere, sorry.
[09:19] <snowyrooftops> Hi!
[09:19] <snowyrooftops> I read about plans to include only Python 3 in Ubuntu 14.04
[09:20] <snowyrooftops> I'd love to help, but don't know where to look
[12:01] <cjwatson> jamespage: could you add a server team (or whatever) bug subscription to curtin?
[12:02] <jamespage> cjwatson, done
[12:02] <cjwatson> ta
[12:20] <smoser> infinity, done.
[12:22] <infinity> smoser: Danke.
[12:53] <mantas-baltix> xnox: Hi Dmitrijs
[12:54] <mantas-baltix> Latest ubiquity build fails on amd64, see https://launchpad.net/ubuntu/+source/ubiquity/2.15.25
[12:56] <mantas-baltix> It would be nice if you update ubiquity-debconf translations from Launchpad in next build -  Lithuanian translation is missing in Ubuntu one step because of bug #1235192
[12:57] <mantas-baltix> I'm currently finishing translation of missing strings in Ubiquity-debconf template
[12:59] <mantas-baltix> cjwatson: few years ago you helped us to update ubiquity-debconf translations from Launchpad, could you help again ? ;)
[13:05] <cjwatson> mantas-baltix: Too late
[13:05] <cjwatson> mantas-baltix: That's an arm64 build failure, not amd64.  ubiquity/arm64 is not yet expected to work.
[13:07] <cjwatson> mantas-baltix: And I updated translations four days after the non-language-pack translation deadline, I don't think that's unreasonable ...
[13:07] <xnox> cjwatson: well the strings to be translated weren't there 4 days ago.
[13:08] <cjwatson> Although I know that those strings were only added four days after *that*, but I believe that was on the understanding that they weren't expected to be translated for release
[13:08] <xnox> ah, ok.
[13:13] <ScottK> xnox: Did you figure out what the boost version for "T" is?
[13:13] <mantas-baltix> cjwatson: ok, sorry, our translation team isn't very fast...
[13:13] <cjwatson> mantas-baltix: I think this was just not expected to be translated; we accepted the bug-fix because having it untranslated and in the .pot is no worse than having it untranslated and not in the .pot, and gives translators more of a head-start for next release
[13:14] <cjwatson> mantas-baltix: If there's another build, I'll update, but I don't know of a cause for one at this point
[13:14] <xnox> ScottK: 1.54 with multiarch.
[13:15] <ScottK> xnox: OK.  That's probably worth a mail to u-devel or u-d-a.
[13:15] <xnox> ScottK: also thinking libav9,  emacs24 as default.
[13:15] <xnox> ScottK: yeah I know, but I'm not yet preparing / evaluating for T opening yet.
[13:15] <cjwatson> perl 5.18 too
[13:16] <ogra_> do we have a name yet btw ?
[13:16] <cjwatson> rickspencer3: ^-
[13:16] <ogra_> no-name-yeT Tiger
[13:16] <ogra_> :)
[13:17] <mantas-baltix> cjwatson, xnox: OK, thanks, Lithuanian users will be happy if you update ubiquity-debconf translations from Launchpad in next build - we will create localized Ubuntu 13.10 installation image next week using ubuntu-defaults-builder, it would be nice to see fully translated installation :)
[13:17] <xnox> tclk/tk 8.6 maybe.
[13:17] <cjwatson> mantas-baltix: I'll do it in bz rnow
[13:17] <cjwatson> *bzr now
[13:17] <rickspencer3> *sigh*
[13:17] <rickspencer3> every
[13:17] <rickspencer3> single
[13:17] <rickspencer3> time
[13:17] <rickspencer3> :)
[13:17]  * mdeslaur votes for Tasty Turkey
[13:17] <cjwatson> sing it
[13:17] <ogra_> lol
[13:17]  * xnox says Tasty TinTin
[13:17] <xnox> mdeslaur: don't still my adjective!
[13:17] <ogra_> TinTin isnt an animal
[13:18] <rickspencer3> if it helps to know, I made several suggestions last week, but they each got shot down
[13:18] <ogra_> Terrific Tapir !
[13:18] <mdeslaur> Toxic Tuna
[13:18] <Laney> Quality LTS name :P
[13:18] <mdeslaur> hehe
[13:18] <mantas-baltix> cjwatson: please wait 5 minutes, I'm finishing translation
[13:19] <cjwatson> mantas-baltix: *sigh*
[13:19] <cjwatson> don't ask before you're finished :)
[13:28] <jibel> barry`, lool I reported bug 1240516
[13:30] <barry> jibel: will look
[13:31] <jibel> barry, I'm looking at the failure on amd64, it is a timeout in download.py but on different tests between my run and automated runs
[13:32] <lool> jibel: thanks
[13:32] <barry> jibel: sigh.  i've been fighting this one for days.  i think there's a weird problem with download manager
[13:33] <barry> jibel: it's hard for me to tell from that jenkins page what exactly is going to stdout
[13:34] <barry> *stderr
[13:35] <mantas-baltix> cjwatson: thanks for waiting, I've just finished :)
[13:36] <mantas-baltix> good luck with Ubuntu 13.10 :)
[13:36] <cjwatson> mantas-baltix: ok, re-requested a tarball
[13:38] <infinity> smoser: Is curtin itself (and python3-curtin) meant to be seeded to main, or are you happy with just the bits that maas depends on being in main?
[13:39] <smoser> i really dont care about 'curtin' and 'python3-curtin' themselves at the moment.
[13:39] <smoser> infinity, i have a related question though...
[13:39] <infinity> smoser: Alright, good.
[13:40] <infinity> smoser: What's the related question?
[13:40] <smoser> what is the reason why you'd have something split like that?
[13:41] <infinity> smoser: Because we only have binaries in main that are needed in main.
[13:41] <smoser> is there any real beneift?
[13:41] <smoser> since we have to support the source package anyway.
[13:41] <smoser> ok. thats fine.
[13:41] <infinity> smoser: The benefit is for times when a binary produced from a main package happens to be something we don't WANT to support, so we only have things in main explicitly.
[13:41] <infinity> smoser: nscd being the pathological case here.
[13:42] <smoser> infinity, ok. then one more related question.
[13:42] <smoser> give binary upackage 'foo', is there a way that i can easily
[13:42] <smoser> a.) know what the source package is (other htan 'apt-cache show')
[13:42] <smoser> b.) know if other binaries from that source are in main
[13:42] <smoser> infinity, i know you're busy
[13:44] <infinity> smoser: For (b), 'rmadison -S foo' works.
[13:44] <infinity> smoser: For (a), apt is the simplest method.
[13:44] <smoser> thanks infinity
[13:47] <ScottK> xnox: While you're multi-arching boost, you might look at splitting the python binaries into python and python3 packages so they can have proper depends.
[13:48] <xnox> ScottK: maybe. but boost is already multi-arched.
[13:48] <xnox> ScottK: (1.53 in saucy)
[13:48] <ScottK> Oh.
[13:48] <xnox> i just was going to multiarch 1.54 into debian and sync it.
[13:48] <ScottK> In any case, it needs doing.
[13:48] <xnox> ScottK: true. but at the moment those boosts libs are still not abi-tagged and there is a request for dbg builds.
[13:49] <ScottK> Yes, but they don't have correct python/python3 depends at all right now.
[13:49] <ScottK> So even splitting py/py3 would be progress.
[14:03] <jibel> barry, ah, I pasted a link to the console, on https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-system-image/5/ARCH=i386,label=adt/ stderr is dsc0t-unittests-stderr
[14:04] <barry> jibel: so *all* the test output is going to stderr?
[14:04] <jibel> barry, yes
[14:04] <barry> jibel: okay
[14:09] <mpt> mvo_, hi, do you have five minutes to look at <https://code.launchpad.net/~brunonova/software-properties/update-apt-on-exit/+merge/190498>?
[14:14] <mvo_> mpt: hi, sure! done - sorry I saw your question yesterday but did not quite manage to get to it
[14:14] <mpt> thanks!
[14:29] <bdmurray> mvo_: Hi, I was wondering if you might have a look at bug 1024590.
[14:29] <mvo_> bdmurray: sure, I can do that later this evening, gtg now :) but thanks for the pointer to the report
[15:06] <barry> jibel, didrocks, lool i'm uploading this change now: http://paste.ubuntu.com/6246069/
[15:07] <lool> barry: keep it for next release
[15:07] <barry> lool: ?
[15:07] <lool> barry: I mean it doesn't need to be uploaded
[15:07] <lool> barry: we've forced system-image in
[15:07] <lool> barry: unless you want to use uploads to debug autopkgtests issues
[15:07] <barry> lool: ah, okay.  no, i don't ;)
[15:09] <lool> barry: there was another issue on the other arch too
[15:10] <barry> lool: i haven't seen that.  i'll bet it was a timeout error in the autopkgtest
[15:10] <lool> barry: one has FAILED (SKIP=3, errors=1)
[15:10] <lool> barry: the other one FAILED (SKIP=3, errors=4, failures=2)
[15:10] <barry> lool: were those all timeouts?
[15:10] <lool> barry: https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy-adt-system-image/
[15:10] <lool> barry: jibel looked into reproducing these, you might want to sync with him to debug
[15:11] <barry> lool: those are going to be extremely difficult to debug.  we may need to enlist mandel to get more debugging out of u-d-m
[15:15] <lool> barry: sounds good
[15:15] <barry> lool: it'll be a fun project for tremendous tadpole
[15:15] <lool> barry: cant wait for the fun
[16:06] <seb128> tedg, hey, do you know if anyone is looking at https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1230222 ?
[16:06] <seb128> not sure if that's a libnih or unity issue
[16:06] <seb128> that's the most reported unity bug in saucy
[16:07] <tedg> Hmm, no I don't know if anyone has.
[16:07] <syeekick> im willing to upgrade its just that, im having trouble with my wificard not being supported properly
[16:07] <tedg> But it'd be a no-op.
[16:07] <seb128> tedg, wdym "no-op"? if the error is harmless we shouldn't bother users with apport prompt for it...
[16:08] <syeekick> would the bcm4312 work fine in the beta?
[16:08] <tedg> seb128, yeah, I think that's the solution.
[16:08] <seb128> tedg, who would be the right person to own it? you? bregma? ;-)
[16:08] <tedg> seb128, Though, has it been in recent versions?  I think slangasek was changing that code to fire-and-forget.
[16:09] <slangasek> who am I firing and forgetting?
[16:09] <tedg> slangasek, The nih signals in unity
[16:09] <seb128> tedg, https://errors.ubuntu.com/problem/bdbd27d4a927ab7cb0fa8edbd1787564e7be8852
[16:09] <seb128> tedg, yes, still happening
[16:09] <seb128> slangasek, ^
[16:09] <slangasek> "still happening" - seems unrelated to the changes we were making
[16:09] <bregma> I think that bug started happening when u-p-s was moved to an upstart job
[16:10] <bregma> dbus stops first, u-p-s barfs and dies
[16:10] <tedg> I think it's related to the indicator signals
[16:10] <tedg> Those are the only ones using libnih
[16:11] <tedg> slangasek, Oh, were you only changing the Unity8 ones?
[16:12] <slangasek> tedg: that's the only code we touched
[16:12] <tedg> K
[16:13] <slangasek> that's a strange backtrace - is it really throwing an error in an exit handler?
[16:13] <tedg> \o/  NIH!
[16:15] <tedg> Hmm, interesting, we're emiting the events sync...
[16:18] <jodh> slangasek: nih registers an atexit handled to make sure the app dealt with all errors.
[16:19] <slangasek> ok
[16:19] <slangasek> tedg: so basically, this backtrace can only occur when u-p-s is exiting, so why is u-p-s exiting?
[16:20] <tedg> slangasek, user logged out?
[16:20] <jodh> tedg, slangasek: all the calls need their return checking to ensure no NihErrors are lurking.
[16:20] <tedg> jodh, But they're all _sync calls.
[16:20] <tedg> jodh, Wouldn't that do that already?
[16:20] <slangasek> tedg: the bug report says "Unity doesn't load, no Launcher, no Dash appears" - are we looking at a user-affecting bug here, or not?
[16:21] <slangasek> tedg: a sync call just means you know immediately whether an error occurred; you still have to check the retval to handle the error itself, AIUI
[16:22] <tedg> slangasek, So we're checking to see if it's non-zero, but we need to remove it from the nih stack?
[16:22] <jodh> tedg: if we're talking about indicatorsmanager.cpp, nih_dbus_proxy_new() isn't checked and it can return an error and create an NihError in the process. That code doesn't handle the failure scenario by consuming the NihError if there is one.
[16:22] <tedg> jodh, We're talking about panel-service.c
[16:22] <slangasek> right
[16:23] <jodh> tedg: package?
[16:23] <tedg> jodh, unity
[16:24] <bregma> the bug is confusing, because the stack dump is from unity-panel-service but he's complaining about Unity proper not working (which is unrelated)... then apport marked a bunch of other u-p-s crashes as dups
[16:24] <jodh> tedg: right - my comments still apply.
[16:25] <jodh> tedg: if priv->upstart = nih_dbus_proxy_new () fails, you need to call "NihError *err = nih_error_get(); nih_free (err);"
[16:26] <tedg> jodh, Okay, and the same for the emit events?
[16:26] <jodh> tedg: you may want to print err->message somewhere before freeing the object to get a human-readable message.
[16:27] <slangasek> tedg: this is the only nih_dbus_* call in the code, FWICS, so the only place it needs to be handled.  However, fixing that nih api issue will prevent apport crashes from being generated, but not actually get to the heart of why this error is happening
[16:29] <slangasek> tedg: oh, but of course the upstart_* calls could also raise nih errors, yes
[16:29] <jodh> tedg: Looking at the auto-generated code, yes, it does seem to raise NihErrors on failure.
[16:29] <tedg> slangasek, Sure, this is probably masking another error, but we have to get this cleaned up before the other becomes visible.
[16:29] <slangasek> tedg: well, no, because handling the error is going to give you the exact same message: "Connection was disconnected before a reply was received"
[16:31] <tedg> slangasek, Sure, but I'm fairly certain that's unrelated to the comment on the bug.  Which is probably a different error.
[16:31] <slangasek> right, that seems likely, since if upstart crashed I would expect the session to end
[16:32] <slangasek> (crashed, was killed, whatever)
[16:32] <tedg> So does this look correct? https://code.launchpad.net/~ted/unity/nih-signals-complete/+merge/191457
[16:32] <tedg> (for the proxy)
[16:33] <tedg> Do I need to check if nih_error_get() returns NULL?
[16:33] <bregma> I'm actually using https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1236720 to track that particular bug to avoid confusion
[16:34] <slangasek> tedg: that code looks correct to me; none of the upstart code checks for a NULL return in that scenario, it's pretty safe to assume it won't be
[16:38] <tedg> Okay, now building Unity... we should have a fix by tomorrow.
[16:38] <tedg> :-)
[16:41] <seb128> tedg, thanks for working on that one ;-)
[16:47] <chiluk> bdmurray, or any other coredev can one of you guys revert the fix that went in for 1150413...   It seems to have cause a regression bug 1157643..
[16:55] <bdmurray> chiluk: bug 1157643 seems to deal with a couple of different issues, can you explain what happened with your SRU to me?
[16:55] <chiluk> bdmurray... I'm still trying to figure it out myself.
[16:56] <chiluk> I just found out 5 minutes ago that a number of users are complaining about procps in bug 1157643 since yesterday when the update was released
[16:56] <chiluk> I can run service start procps just fine..
[17:14] <slangasek> chiluk, bdmurray: I don't think it's a regression; I think 'service procps start' fails for these users every time they boot, but it doesn't block anything when it happens at boot
[17:14] <slangasek> so the issue is that this is the first time they've upgraded procps since making whatever customizations they have made to /etc/sysctl*
[17:16] <bdmurray> slangasek: I agree I was just testing with an lxc container and the old version of the package had the same issue
[17:16] <chiluk> phew...
[17:17] <verterok> chiluk: I'm here :)
[17:17] <seb128> hey
[17:18] <seb128> so my laptop is not booting anymore since today's update
[17:18] <seb128> is there a known issue in saucy?
[17:18] <chiluk> verterok, slangasek and bdmurray think this is not a regression, but instead simply the first time procps has been upgraded
[17:18] <seb128> the boot stops on plymouth and displays "waiting for network" after a bit
[17:19] <slangasek> bdmurray: it still seems an SRUable issue in its own right, but it's not a regression and trying to revert the change won't help ;)
[17:19] <sidnei> chiluk: ah, that's likely yes. i mean, i do remember now trying to restart procps for some other reason and the start always failed
[17:20] <seb128> hum
[17:20] <slangasek> seb128: "waiting for network" should only wait for 120 seconds max
[17:20] <seb128> intel driver fails to load as well... kernel issue?
[17:20] <slangasek> shouldn't be any kernel changes in today's update
[17:20] <seb128> slangasek, I got bored enough 120s, went to a vt and did startx from there
[17:21] <slangasek> looking to see what came in with the latest updates
[17:21] <slangasek> new X packages yesterday
[17:21] <seb128> slangasek, well, I didn't update yesterday either
[17:22] <seb128> dmesg has
[17:22] <seb128> [   16.371270] wlan0: Limiting TX power to 27 (30 - 3) dBm as advertised by 18:3
[17:22] <seb128> 3:9d:16:e7:e0
[17:22] <seb128> [   17.492514] init: Failed to spawn nmbd main process: unable to execute: No su
[17:22] <seb128> ch file or directory
[17:22] <seb128> [  128.597580] audit_printk_skb: 180 callbacks suppressed
[17:22] <verterok> sidnei, chiluk: so, what are our options here? fix lxc config to allow access to those sysctl keys?
[17:22] <slangasek> "no such file or directory"? is your fs corrupted? :/
[17:23] <slangasek> or is the samba package in state 'rc'?
[17:23] <sidnei> verterok: i think procps needs an update to fix the start/restart initscript target
[17:23] <sidnei> verterok: or something along these lines
[17:23] <seb128> rc  samba                                                 2:3.6.9-1ubuntu1                               i386         SMB/CIFS file, print, and login server for Unix
[17:23] <seb128> slangasek, yeah, I uninstalled it some days ago to test something
[17:23] <slangasek> ok, so ignorable
[17:24] <seb128> hum, I wonder if uninstalling samba is what created the issue
[17:24] <sidnei> verterok: although, yeah, the failure is because of perms
[17:24] <slangasek> seb128: not sure how it would
[17:24] <seb128> slangasek, yeah, me neither...
[17:25] <seb128> ok, let me fsck and try old kernel (and need to get lunch)
[17:25] <seb128> bbiab
[17:25] <slangasek> seb128: oh; except you're waiting for network, and the nmbd job starts on network, so if the job managed to get itself into a bad state...
[17:25] <slangasek> well, timing
[17:26] <slangasek> tedg: so I have a question about dbus best practices, maybe this is something you can help me with
[17:27] <verterok> sidnei: looks like the apparmor profile is the culprit
[17:27] <verterok> sidnei: /etc/apparmor.d/abstractions/lxc/container-base
[17:27] <slangasek> tedg: we've been working on the memory leak in upstart, and jodh has succeeded in pinpointing the source of the leaking memory, and thinks he has a way around it - when we go to send messages, if the client still has one queued we drop instead of appending to the queue.
[17:27] <sidnei> verterok: that's in the host?
[17:28] <verterok> sidnei: yes
[17:28] <slangasek> tedg: but my question is... why are we sending these messages to all clients anyway.  Apparently any time we see an upstart event we broadcast the message to all clients, and rely on the clients to filter out which events they care about... is that really the dbus way?  Because this seems to me to be an awful lot of cycles wasted sending messages that the clients know they don't care about
[17:29] <sidnei> verterok: uhm, that's not even installed on my machine, im using a precise host
[17:30] <verterok> sidnei: this is a saucy host
[17:31] <verterok> sidnei: probably in another file?
[17:31] <sidnei> verterok: which line you think it's the culprit on that apparmor profile for saucy host?
[17:31] <sidnei> deny @{PROC}/sys/kernel/*/** wklx ?
[17:32] <verterok> sidnei: yes: https://pastebin.canonical.com/99156/
[17:33] <sidnei> verterok: right, so /etc/apparmor.d/lxc/lxc-default in precise
[17:33] <verterok> sidnei: see the part: # deny writes in /sys except for /sys/fs/cgroup
[17:34] <sidnei> verterok: so yes, while it's the apparmor profile that's blocking it, i don't think that needs to be changed. perhaps the fix is to not try to set those keys when running within lxc, or to fail gracefully instead.
[17:35] <verterok> sidnei: you'r probably right :)
[17:36] <sidnei> and the files that try to set those keys are part of the procps package
[17:37] <bdmurray> smoser: did you see my comments in bug 1239893?
[17:38] <sidnei> verterok: so if i understand the whole context, procps start has always been broken in lxc, but when called from upstart the failure to start is ignored. dpkg is not as forgiving, so trying to upgrade the package blows up because the service start step blows up.
[17:38] <sidnei> verterok: and we only hit this on lxc because of the apparmor profile
[17:38] <verterok> sidnei: I think that's the whole thing
[17:38] <sidnei> chiluk: ^ dropping that into a bug, against procps i suppose?
[17:41] <smoser> bdmurray, it doesn't seem to make sense to me to ad dthe newline there.
[17:41] <smoser> (in your ocmment 8)
[17:42] <smoser> fwiw, i'm not terribly personally interested in this. i think its not good that there is apparently a regression (but i've never tested ppa: in the gtk box on raring).
[17:42] <smoser> i was primiarily concerned that i'd cauased a regression so thats why i initially  jumped in.
[17:44] <chiluk> thanks sidnei...I'm really not the one to decide where the fix needs to be ..
[17:46] <sidnei> chiluk: i'll append that as a comment to the existing bug then, let someone else sort it out.
[17:46] <chiluk> so sidnei if I understand this correctly this only happens in an lxc guest
[17:47] <sidnei> chiluk: yes, best i can tell.
[17:47] <chiluk> or some other virtualization guest...
[17:47] <chiluk> that has sys mounted from the host?
[17:47] <sidnei> chiluk: possibly, or anything that has an apparmor profile restricting /sys?
[17:47] <chiluk> sorry, I haven't had much of a chance to play with lxc..
[17:48] <chiluk> alright.. I need to step away for a bit, but I'll take a look later today with this... at least document in the public bug what the understanding of the problem is.
[17:51] <sidnei> slangasek: do you have any opinion on this? since the sysctl setup that's breaking under this environment is added by procps itself, but the failure only manifests under lxc (and apparently openvz too?) im unsure if the bug should be filed on procps or lxc.
[17:55] <slangasek> sidnei: which option is breaking under lxc/openvz?
[17:55] <slangasek> or are they all breaking?
[17:55] <bdmurray> In my case it was the kernel ones
[17:56] <slangasek> what kernel ones are those?
[17:56] <sidnei> slangasek: there's 3 of them, let me get you a list
[17:56] <bdmurray> kernel.printk
[17:56] <bdmurray> kernel.kptr_restrict
[17:56] <bdmurray> kernel.yama.ptrace_scope
[17:56] <slangasek> ok
[17:56] <sidnei> thanks bdmurray
[17:57] <bdmurray> np
[17:57] <slangasek> stgraber, hallyn: ^^ so /etc/init/procps.conf does not work reliably in containers because lxc doesn't want us writing to /proc/sys/kernel (apparently).  What should we do here?
[18:00] <stgraber> slangasek: what's the problem caused due to LXC preventing writes in there?
[18:00] <stgraber> slangasek: most of the files under /proc/sys/kernel aren't namespace aware so we certainly don't want to allow writing to them
[18:00] <stgraber> (kernel.yama.ptrace_scope is one of those at least, I suspect the two others might be too)
[18:00] <hallyn> accept that it might fail?  not run in containers?  what exactly is it failing on?
[18:01] <bdmurray> upgrading the procps package
[18:01] <hallyn> which variables i mean
[18:01] <sidnei> hallyn: see a couple lines above
[18:01] <hallyn> i thought procps used to proceed if it couldn't st seomthing
[18:01] <slangasek> stgraber: the problem is that we expect the sysctl command to be reliable, and the procps maintainer script expects the upstart job to be reliable, and so these writes, which are allowed in a normal system, will fail
[18:02] <hallyn> there are cases where the sysctl ceases to exist too right?  how are those handled?
[18:03] <slangasek> hallyn: '-e': 'Use this option to ignore errors about unknown keys'
[18:03] <slangasek> but that's specifically unknown keys, not "ignore errors when the kernel hates us" ;)
[18:04] <stgraber> so if we want the upstart job to succeed we'll have to teach sysctl to ignore EACCESS
[18:04] <slangasek> interesting, sysctl now has a --system option that makes the cat in /etc/init/procps.conf gratuitous
[18:04] <stgraber> as there's no way we'll allow it writing to those files in a container
[18:04] <slangasek> stgraber: and they can't be hidden in the container?
[18:04] <slangasek> I guess you still want to be able to read them
[18:04] <stgraber> unfortunately not, short of doing some very bad magic like using a fuse overlay on /proc
[18:04] <stgraber> and indeed you still want read access
[18:05] <stgraber> and some of those should actually be writable (and probably are, we unblock any entry that we know is namespace aware)
[18:15] <bdmurray> smoser: fwiw I tested software-properties in raring and it doesn't have the bug
[18:16] <smoser> so it is regression, probably shoudl tag that on the bug.
[18:16] <bdmurray> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/software-properties/saucy-proposed/revision/126
[18:16] <bdmurray> in line 707 you can see a strip()
[18:18] <smoser> bdmurray, yeah, that would make sense. but i tested.
[18:19] <smoser> i tried with version before my changes. and it was present.
[18:19] <smoser> unless i just completely screwed that up
[18:20] <tedg> slangasek, So the clients set up filters in the dbus daemon, so it doesn't really send them to all clients.
[18:21] <tedg> slangasek, So from the perspective of the sender, they're going everywhere, but we're not waking everyone up.
[18:21] <slangasek> in the case of a dbus daemon, right
[18:21] <slangasek> but these are direct connections to the upstart server
[18:21] <slangasek> tedg: what's the api for the client to set up the filter?
[18:22]  * tedg looks for a link
[18:23] <tedg> slangasek, http://dbus.freedesktop.org/doc/dbus-specification.html#bus-messages-add-match
[18:24] <tedg> slangasek, And then click on the match rules link to see the format of the string.
[18:24] <tedg> slangasek, Generally, point to point DBus interfaces don't install match rules.
[18:24] <slangasek> tedg: got it, thanks.
[18:24] <tedg> slangasek, Is there a reason we're not putting the session Upstart on the session bus?
[18:25] <bdmurray> smoser: anyway, will you fix it or should I?
[18:26] <slangasek> tedg: I don't know.  Up to now, the clients of upstart's dbus service have been either upstart bridges or short-lived clients
[18:26] <slangasek> so there probably was no perceived need
[18:26] <stgraber> tedg: the session bus doesn't exist when upstart starts, though that's fixable with something like is done for the system bus. I think we just assumed it wouldn't gain us much since the socket address is exported to all sub-processes anyway
[18:26] <slangasek> tedg: but even if we put it on the session bus, we would still have point-to-point clients (the bridges), for whom these emitted events are *also* a waste
[18:26] <tedg> Yeah, I was just noticing how the system bus worked there.  Was thinking that might be a nicer solution.
[18:26] <smoser> bdmurray, you're welcome to.
[18:27] <tedg> slangasek, The bridges could send directed signals.
[18:27] <slangasek> tedg: meaning the bridges become dependent on the dbus session bus
[18:28] <tedg> I'm probably more okay with everything being dependent on dbus than you are :-)
[18:28] <slangasek> yep
[18:28] <slangasek> stgraber: curiously, I see that all the bridges in the user session already 'start on started dbus'
[18:28] <slangasek> stgraber: do you happen to know why that is?
[18:29] <sidnei> stgraber, hallyn: as a result of this sysctl issue, anyone using (precise, at least) lxc containers has a broken system since procps landed on precise-updates yesterday. the maintainer script fails, and further apt invocations fail until that's resolved.
[18:30] <stgraber> slangasek: no idea. I know that the first version of my event bridge was using upstart on session bus, but I changed that a bit later on. Maybe I forgot to change the start condition and everyone else copied it without thinking much about it? :)
[18:31] <slangasek> sidnei: workarounds are possible (e.g., editing /usr/sbin/policy-rc.d to ignore requests for procps; or editing the config file in the container to comment out the problematic bits).  A proper fix is going to take a bit.
[18:31] <slangasek> and it's going to have to be fixed in procps, not in lxc.
[18:31] <slangasek> stgraber: heh, could be
[18:33] <hallyn> sidnei: is there an open bug to track that?
[18:33] <slangasek> tedg: so you would argue for having upstart register on the session bus and moving its clients over there, where we get filtering for free and only have to send our signals to one "client" (dbus); and not for adding support to upstart for supporting matches, which in the common case would avoid us having to send any signals about upstart events?
[18:33] <sidnei> hallyn: bug #1157643 seems like it could be it
[18:34] <tedg> slangasek, Yes, that would be my suggestion.
[18:34] <tedg> slangasek, I think it also masks sense for the "DBus in the kernel" possible future, where we wouldn't want that support in Upstart as well.
[18:34] <hallyn> sidnei: th
[18:34] <hallyn> x
[18:34] <smoser> bdmurray, please go ahead and apply your fix.
[18:34] <slangasek> tedg: wouldn't want what support in Upstart?
[18:35] <smoser> i verify that it *was* broken by me. :-(
[18:35] <tedg> slangasek, The matches.   It would be dead code as we'd use the kernel support.
[18:35] <slangasek> tedg: I don't follow you at all
[18:35] <slangasek> is moving to the kernel intended to change the API for matches?
[18:36] <tedg> slangasek, I'm just saying that adding support to Upstart to allow for matches on point to point connections wouldn't be used in the future.
[18:36] <slangasek> still not following
[18:36] <slangasek> having dbus in the kernel changes nothing about what interfaces upstart exposes
[18:36] <slangasek> upstart is still a server that speaks dbus
[18:37] <hallyn> slangasek: stgraber: so would teaching sysctl to check whether it is in a container, and, if so, check access(2) to the file, and not try writing if it gets EACCESS; seem reasonable?
[18:37] <tedg> Sure, the question would be whether it's a service that talks to a DBus server or supports more DBus server functionality on its own connection.
[18:37] <slangasek> hallyn: the "check whether it's in a container" worries me a little
[18:38] <slangasek> tedg: upstart will *always* support more on its own connection, there are privileged operations that upstart (as pid 1) only allows on its private socket, not from the system bus
[18:38] <hallyn> slangasek: well we *could* just not do that.  but /bin/running_in_container is supposed to be trustworthy...
[18:38] <hallyn> i can see why that would be unsettling though
[18:38] <slangasek> hallyn: I don't think sysctl should be shelling out to /bin/running_in_container
[18:39] <tedg> slangasek, Why is that?
[18:39] <slangasek> hallyn: and I don't like having to invoke running_in_container, because I don't like it when things are different inside containers than out :)
[18:39] <slangasek> tedg: because upstart doesn't trust the system bus ;)
[18:39] <tedg> slangasek, Does Upstart trust the kernel?  :-)
[18:39] <slangasek> tedg: not as far as it can throw it
[18:39]  * tedg may know the answer
[18:40] <hallyn> slangasek: EACCESS is probably a good enough check.
[18:40] <hallyn> the question is only, if you're on the *host*,. then you may want startup to actually break if you weren't able to set /proc/sys/FOO_i_rm-rf-/-if-unset
[18:40] <stgraber> hallyn: just ignoring EACCESS seems reasonable, there's nothing sysctl can do about it, so just plain failing on it seems suboptimal. We can have it whine about it though.
[18:41] <hallyn> stgraber: nothing it can do about it, but it *could* be a case where you're better off breaking boot (or upgrade) if it failed.
[18:41] <stgraber> well, it wouldn't actually block startup though
[18:41] <hallyn> then i guess it's worthless :)
[18:41] <hallyn> ok lemme whip up a patch
[18:41] <hallyn> (i assume noone else is yet?)
[18:41] <stgraber> nothing appears to block on procps, so having it fail wouldn't really do anything
[18:51] <seb128> back from lunch
[18:51] <seb128> still no booting laptop though :/
[18:52] <slangasek> seb128: so I think you're right about nmbd being involved
[18:53] <seb128> slangasek, oh?
[18:53] <slangasek> seb128: you're waiting for network, and the nmbd job starts on network, so if the job managed to get itself into a bad state, maybe it's blocked the static-network event
[18:54] <seb128> slangasek, how do I see what is blocked?
[18:54] <slangasek> seb128: do you have interfaces configured through ifupdown besides lo?
[18:54] <slangasek> (i.e.: is NM in charge of everything?)
[18:54] <seb128> nm is on charge of everything afaik
[18:54] <slangasek> ok
[18:54] <slangasek> that shoots a hole in that theory, then
[18:54] <slangasek> as for seeing what's blocked, have a look at the output of 'sudo initctl list' and see if anything looks askew
[18:55] <slangasek> (or pastebin it and I can have a look)
[18:56] <seb128> slangasek, that's a bootchart: http://ubuntuone.com/2RwScS79hEMlQA7oxsRLmU
[18:57]  * seb128 gets initctl list
[18:57] <stgraber> seb128: are you at the office?
[18:58] <seb128> slangasek, http://paste.ubuntu.com/6247160/
[18:58] <seb128> stgraber, yes
[18:58] <stgraber> I was thinking of coming to say hi, I guess I could take a look at that directly if that helps
[18:59] <seb128> stgraber, that would be nice, but no hurry, I've a "working" system through ctrl-alt-f1/startx, so I'm not stucked
[19:08] <seb128> stgraber, slangasek: does the pastebin gives you any clue?
[19:10] <seb128> half of that list is stop/waiting :/
[19:14] <hyperair> hmm, odd. for some reason i had a root-owned ~/.config/upstart and ~/.cache/upstart which blocked upstart from starting up in 13.10.
[19:23] <slangasek> seb128: ... "boot-hooks/unity8-setcap"?  so you have unity8 packages installed on your laptop?
[19:23] <seb128> slangasek, yes
[19:25] <seb128> slangasek, ok, that was it
[19:25] <seb128> slangasek, moving the boot-hook unblocked immediatly things
[19:25] <slangasek> ok
[19:25] <seb128> stgraber says it's lool's fault
[19:25] <stgraber> that boot-hooks is "on starting lightdm" and was introduced this morning I believe
[19:25] <stgraber> so anyone with that hook on a non-touch machine (that doesn't get the boot-hooks event) will get stuck
[19:25] <seb128> lool, thanks for making my desktop not booting... :-(
[19:26] <seb128> we have lot of unity8 testers/hackers on desktop
[19:26] <stgraber> the solution would quite likely be to only ship the boot-hook on machines that have boot-hooks
[19:26]  * seb128 reboots in a proper session
[19:29] <seb128> stgraber, slangasek: thanks! system back to normal
[19:31] <chiluk> so stgraber, slangasek... did we ever decide how to fix the lxc, procps not starting issue?
[19:32] <chiluk> or was teaching sysctl how to and eaccess the proposed solution.
[19:33] <stgraber> chiluk: yep, hallyn is working on patching sysctl not to fail on EACCESS
[19:33] <chiluk> stgraber, ok... can I make a suggestion to make it print an error in the log on failure... that..
[19:34] <chiluk> way, people who expect it to fail on error should hopefully still see a log entry
[19:34] <stgraber> I'm fine with it printing a permission denied or similar error, not sure whether hallyn did that already
[19:35] <seb128> lool, stgraber, slangasek: so, any taker on making unity8 not screw non-touch systems, before that bites more users?
[19:36] <slangasek> stgraber, chiluk: hallyn has already posted a patch which does output a message to stderr, which means it'll go to /var/log/upstart/procps.log
[19:36] <chiluk> close enough
[19:37] <chiluk> do we have a new bug number?
[19:37] <slangasek> seb128: no immediate ideas, other than moving the job to a separate package as stgraber said
[19:37] <slangasek> chiluk: no, there's an existing bug report
[19:38] <chiluk> ah nm.. I reloaded.
[19:38] <chiluk> my earlier comment was based on trusting that others had done their due diligence.
[19:39] <hallyn> yeah i didn't make a change, sysctl already prints out an error message and i left that there.
[20:14] <alkisg> Hi, the last version of firefox in 12.04 no longer reads /etc/firefox/pref/apturl.js, breaking all apt:// URLs like e.g. https://apps.ubuntu.com
[20:14] <alkisg> If we move apturl.js to e.g. /usr/lib/firefox/defaults/pref, then it works fine again
[20:56] <smoser> joy. firefox now has 1.8g resident.
[20:56] <smoser> this is possibly related to recent pentadactyl upgrade
[21:45] <lool> seb128: Bah
[21:45] <seb128> lool, just got somebody else here bitten by it
[21:45] <lool> seb128: the worst is that I tried to design the contents friendly for desktop, but didn't remotely imagine it was already used
[21:45] <lool> so
[21:45] <seb128> lool, well, it's used to screw boot only it seems...
[21:45] <lool> I guess one option is to move it to another package
[21:45] <lool> another option is to remove it
[21:46] <lool> seb128: problem is that this thing will also break apt/dpkg upgrades of unity8
[21:46] <lool> not an issue on touch though
[21:48] <seb128> lool, well, just move the conffile to the lxc package (what stgraber suggested before) and clean the conffile behind in unity8
[21:49] <lool> seb128: Yes, that's what I was thinking by moving
[22:10] <lool> slangasek: Mind reviewing r114 and r115 of lxc-android-config?
[22:11] <lool> slangasek: in lp:ubuntu/lxc-android-config
[22:11] <lool> slangasek: I wish I remembered the code.launchpad.net/ name for these branches
[22:11] <slangasek> code.launchpad.net/ubuntu/+source/lxc-android-config - much too long to type, not worth remembering :P
[22:12] <stgraber> the real branch is code.launchpad.net/~ubuntu-branches/ubuntu/saucy/lxc-android-config/saucy (and that's defnitely not worth remembering :))
[22:13] <lool> Ah didn't try with +source
[22:14] <slangasek> lool: structurally, it looks fine; I'm assuming the only thing you changed was the [ -e /usr/bin/unity8 ] check and that the job is otherwise unmodified from the previous version, so not reviewing that part
[22:14] <lool> and the stgraber syntax is the one I dind't remember
[22:14] <lool> slangasek: correct
[22:14] <lool> slangasek: and it should work even if both jobs are in
[22:14] <lool> so will upload this now
[22:15] <slangasek> ok
[22:19] <lool> slangasek: and https://code.launchpad.net/~lool/unity8/drop-setcap-conf/+merge/191520
[22:21] <slangasek> lool: acked
[22:21] <lool> thanks
[22:21] <slangasek> lool: so taking a step back... why is this crazytown 'exec' mount needed?
[22:23] <lool> slangasek: so yesterday I was told unity8 had to be setcap CAP_SYS_RESOURCE, but this didn't work on ext2
[22:23] <lool> slangasek: we use ext2 because we only have mkfs.ext2
[22:23] <lool> slangasek: I also didn't really like shipping xattr over system-image updates
[22:24] <lool> slangasek: I chekced whether /etc/system-image/writable-paths would allow taking a tmpfs copy of unity8 to patch it there, but it didn't
[22:24] <lool> slangasek: so the best option we found was a job to copy it before it starts, and add the xattr -- ugly, as noted there
[22:24] <lool> slangasek: the hunt for writable locations only returned /run, but that's noexec
[22:25] <lool> slangasek: hence the tmpfs on top of run; could also have been /var
[22:25] <lool> slangasek: a proper way would be to use some root utility to gain this
[22:25] <lool> slangasek: but the truth is we dont even truly need this
[22:25] <lool> so we ought to revert it soon
[22:25] <stgraber> in short it's a terrible hack for a case where we should have a service to do that kind of stuff (oom_adj changes) instead of giving fs caps to unity8
[22:27] <stgraber> CAP_SYS_RESSOURCE isn't something you usually want to give to your users to begin with
[22:27] <stgraber> man capabilities if you want to know why ;)
[22:27] <slangasek> lool: right, what was the original justification for giving unity8 privileges to fill up the filesystem? ;)
[22:28] <slangasek> I guess maybe it was for naughty rlimits
[22:28] <stgraber> slangasek: unity8 apparently needs to set oom_adj
[22:29] <slangasek> hmm
[22:29] <slangasek> so of course, upstart supports this natively, as we discussed before
[22:29] <slangasek> but you only get that from the system upstart
[22:29] <lool> slangasek: So unity-mir gained yesterday the ability to set oom_score_adj as to recommend the Android OOM killer to prefer backgrounded apps
[22:29] <stgraber> wouldn't exactly help for a user session
[22:29] <stgraber> unless you give upstart cap_sys_ressource
[22:30] <lool> the truth is you need no power to set oom_score_adj
[22:30] <stgraber> which would be just as difficult (and arguably wrong) as giving it to unity8
[22:30] <lool> you can do it, if you use a higher score than yours
[22:30] <stgraber> right
[22:30] <lool> so I think unity8 should just set scores higher thann its own
[22:30] <slangasek> aha
[22:30] <slangasek> yeah, agreed
[22:30] <lool> also, the whole session is already started with -10, but that too isn't needed
[22:31] <lool> (this is via upstart BTW  :-)
[22:31] <lool> /etc/init/lightdm.override from lxc-android-config
[22:31]  * slangasek nods
[22:31] <lool> slangasek: Do you know why the released image need to match archive?  is this for GPL compliance?
[22:31] <lool> does that imply we should do the same for touch?
[22:32] <stgraber> lool: this is amongst other things to avoid re-downloading the whole release pocket indexes after install, match between the source CDs and the binary CDs is another reason for that indeed
[22:32] <slangasek> lool: yes, broadly speaking it's about making sure we have the source for the images; less of an issue for touch where the images will be superseded soon after release
[22:37] <lool> ok
[23:01] <lool> seb128, slangasek: http://people.dooz.org/~lool/unity8-drop-setcap-conf/
[23:01] <lool> seb128, slangasek: Tested by dpkg -i -O installing .debs here; I had the boot-hooks before, and now it's gone
[23:01] <seb128> lool, great
[23:02] <slangasek> lool: looks good print it
[23:02] <seb128> lool, the files permissions are wrong on that people page, can't see those
[23:02] <lool> ah sorry
[23:02] <seb128> in fact only some of the files
[23:02] <lool> fixed
[23:02] <seb128> thanks
[23:03] <lool> not sure why either, source file coming out of sbuild or something
[23:07] <seb128> lool, your debdiff has code source changes, the debian diff looks fine to me
[23:12] <lool> seb128: debdiff only misses changelog update for me: http://paste.ubuntu.com/6248252/
[23:12] <lool> this is from unity8_7.83+13.10.20131016.1-0ubuntu1.dsc
[23:13] <seb128> lool, oh, your version is unity8_7.83+13.10.20131016-0ubuntu1dooz1.diff.gz
[23:14] <seb128> lool, so I diffed with 16 not 16.1
[23:15] <seb128> lool, so yeah, looks fine to me like that
[23:15] <lool> seb128: yeah; the root cause of the changelog diff and of that version delta just hit me
[23:15] <lool> the changelog had not been automerged
[23:15] <lool> I've merged it by hand now
[23:15] <seb128> thanks
[23:16] <lool> FYI the broken conf was published ~7 hours ago
[23:26] <cjwatson> It's "distro-info-data is broken" day


[00:05] <nigelb> 26
[00:05] <nigelb> grr
[00:55] <StevenK> wgrant: I have private bug with nothing, with subscriber and with structural subscriber, asserting on what getBugNotificationRecipients() returns. I'm obviously missing a bunch of scenarios
[00:56] <wgrant> There are three implicit subscriber cases: structural subscriptions, dupe subscriptions, and assignees.
[00:57] <wgrant> I'm not sure if dupe assignees and dupe structsubs also count.
[00:58] <StevenK> wgrant: So assignee sounds a good plan -- I've not thought about dupes yet
[01:25] <StevenK> wgrant: Blink.
[01:25] <StevenK> wgrant: IBug.markAsDuplicate() recalculates heat, but so does IBug._markAsDuplicate() which the former calls.
[01:27] <wgrant> StevenK: markAsDuplicate recalculates the heat of the new master, _markAsDuplicate recalculates the heat of the old.
[01:27] <StevenK> Ah
[01:38] <StevenK> wgrant: http://pastebin.ubuntu.com/1107437/
[01:54] <wgrant> StevenK: A good start, indeed.
[01:56] <StevenK> wgrant: Do you think it's worthwhile expanding out to public bugs?
[02:04] <wgrant> StevenK: Certainly
[02:04] <wgrant> StevenK: It is to be a thorough set of tests for getBugNotificationRecipients
[02:04] <wgrant> It's hardly comprehensive or thorough if it doesn't do public bugs too.
[02:15] <lifeless> gary_poster: nice mail :)
[04:15] <StevenK> wgrant: http://pastebin.ubuntu.com/1107562/  bugwatch is up next, and then subscribed to question linked to bug
[04:15] <StevenK> Then I might be done
[04:32] <StevenK> wgrant: So now that hilarity has passed, bugwatches?
[04:34] <wgrant> StevenK: How are watches involved?
[04:34] <StevenK> wgrant: sinzui implicates them
[04:35] <wgrant> Hm
[04:35] <wgrant> That's odd.
[04:35] <StevenK> wgrant: I don't know how they work. :-(
[04:36] <StevenK> Well, I know they link to an external bugtracker and checkwatches does something to some watches and then hangs.
[04:36] <StevenK> But can a watch have subscribers or impact on getBugNotificationRecipients()?
[04:40] <wgrant> No
[04:40] <wgrant> I don't believe they're relevant here at all.
[04:41] <StevenK> I shall ignore them, then
[04:41]  * StevenK moves onto working on how to staple a question and bug together
[05:17] <StevenK> wallyworld, wgrant: https://code.launchpad.net/~stevenk/launchpad/bugnotification-testcases/+merge/116402
[05:23] <wgrant> StevenK: Looking
[05:30] <wgrant> StevenK: https://code.launchpad.net/~wgrant/launchpad/faster-checkCanBeDeleted/+merge/116404
[05:32] <StevenK> wgrant: r=me, looks great
[05:33] <wgrant> Thanks.
[05:33] <StevenK> wgrant: What about my review? :-)
[05:34] <wgrant> StevenK: Looking
[05:34] <wgrant> What's + def test_public_bug_with_duplicate_same_pillar_subscriber(self):?
[05:35] <StevenK> wgrant: Both bugs are against the same pillar
[05:35] <wgrant> Yes, but why?
[05:35] <wgrant> How's it relevant as a separate case?
[05:36] <StevenK> The private case will be different, and I did the same cases for public bugs
[05:36] <StevenK> I can condense the two public duplicate tests if you wish
[05:36] <wgrant> I don't see how the private case is different.
[05:36] <wgrant> It's matters whether the subscriber has access
[05:37] <wgrant> Not whether it's a different pillar.
[05:37] <StevenK> wgrant: It will be -- give an APG against the pillar
[05:37] <wgrant> StevenK: Und?
[05:37] <wgrant> That's the case where there's an APG against the pillar
[05:37] <wgrant> Not the case where they're the same pillar
[05:38] <StevenK> wgrant: Right, so condense the four down to test?
[05:38] <StevenK> Down to two, rather
[05:38] <wgrant> Right
[05:38] <wgrant> Test things that should be tested because they make a difference.
[05:38] <StevenK> I split it out due to sinzui's mail
[05:39] <wgrant> Also, do the tests pass?
[05:40] <StevenK> They do
[05:41] <wgrant> Huh
[05:41] <wgrant> How does the question one work...
[05:41] <wgrant> Oh god
[05:41] <wgrant> Question.linkBug subscribes the question owner
[05:41] <wgrant> What could possibly go wrong.
[05:42] <StevenK> WCPGW, right?
[05:42] <StevenK> :-)
[05:42] <wgrant> Implicit access grants are bad, m'kay.
[05:42] <StevenK> Yes, I'm not sure the two question tests add value
[05:42] <wgrant> They don't.
[05:42] <StevenK> Bin them too?
[05:42] <wgrant> Yes
[05:42] <wgrant> Let me read sinzui's mail
[05:42] <wgrant> Ah
[05:42] <wgrant> So he
[05:43] <wgrant> probably speaks of the bug->question notification forwards
[05:43] <wgrant> I'm not quite sure how they work
[05:43] <wgrant> But they're separate from this
[05:43] <wgrant> So don't need to be considered here, at least not yet.
[05:52] <wgrant> StevenK: Are you sure that all of xx-initial-bug-contacts.txt is duplicated?
[05:54] <StevenK> wgrant: It was sinzui's suggestion that it be binned since much of the test will fail to be true in a few weeks with the bug supervisor and security team playing
[05:55] <wgrant> StevenK: Sure, but it covers a whole lot of stuff that's only barely related to what you're adding tests for
[05:55] <wgrant> Like setting the bug supervisor
[05:55] <wgrant> And the security contact being subscribed by default
[05:56] <StevenK> Bug supervisor is also dying horribly too?
[05:56] <StevenK> Security contact is also changing after we can filter on information type
[06:00] <wgrant> StevenK: Bug supervisor is not dying.
[06:00] <wgrant> Its role is changing.
[06:00] <wgrant> Security contact will probably die entirely.
[06:00] <wgrant> We will still need to be able to set the bug supervisor.
[06:01] <StevenK> I can shuffle that part into a browser test easily
[06:01] <wgrant> Rogjt
[06:01] <wgrant> Right
[06:01] <wgrant> But you can't just delete it
[06:01] <wgrant> Without confirming that it's been replaced, or replacing it yourself
[06:02] <StevenK> lib/lp/bugs/browser/tests/test_bugsupervisor.py:class TestBugSupervisorEditView(TestCaseWithFactory):
[06:02] <StevenK> Does that count?
[06:02] <wgrant> If it tests the same stuff, sure.
[06:08] <wgrant> Oops
[06:31] <StevenK> wgrant: Diff updated, I've added new tests for the Change bug supervisor link
[06:31] <StevenK> And I'm still 164 lines in credit
[06:48] <wgrant> StevenK: Thanks
[06:49] <StevenK> wgrant: Thanks. Did you see the branch I just landed?
[06:51] <wgrant> Aha
[06:51] <wgrant> I think only two of those were mine
[06:53] <wgrant> Yay
[06:53] <wgrant> Only one actual bug in bugsummary maintenance
[06:53] <wgrant> And one in the rebuild script
[07:32] <wgrant> StevenK: https://code.launchpad.net/~wgrant/launchpad/bug-1028279/+merge/116411
[07:32] <wgrant> StevenK: (yes, this is very similar to your thing which broke everything, but I like to live dangerously)
[07:44] <adeuring> good morning
[10:34] <Ergo^> morning
[10:35] <Ergo^> gary_poster, hello, im looking for some info on the position
[10:35] <Ergo^> http://blog.launchpad.net/were-hiring/were-hiring-software-engineers-to-work-on-cloud-projects-in-canonical
[10:35] <Ergo^> czajkowski, said i should be asking you about it
[10:35] <lifeless> or gmb
[10:36] <czajkowski> gmb: ping
[10:36] <lifeless> gary will be asleep right now (I hope!)
[10:36] <Ergo^> haha ok :]
[10:36] <czajkowski> Ergo^: mornign more of the developers are online now
[10:36] <czajkowski> and in fact gmb is on hols
[10:36] <czajkowski> wgrant: might you be able to answer some of Ergo^ questions on lp dev please, he's thinking of applying for one of the roles
[10:38] <wgrant> I'm trying to not be here :)
[10:38] <wgrant> 'cause it's getting late
[10:38] <czajkowski> I know but I cant find any EU folks up atm
[10:39] <wgrant> gmb can't be too far away
[10:39] <Ergo^> wgrant, carry on, i can ask later ;-)
[10:39] <czajkowski> adeuring: allenap ping are either of you about ?
[10:39] <jpds> wgrant: From where you are?
[10:40]  * adeuring is looking
[10:40] <wgrant> Heh
[10:40] <czajkowski> jpds: AU
[10:40] <czajkowski> although he never sleeps
[10:40] <czajkowski> adeuring: thanks
[10:40] <czajkowski> Ergo^: adeuring might be able to answer some of your questions
[10:40] <czajkowski> Ergo^: thanks for coming and asking though
[10:42] <adeuring> Ergo^: I think you should wait for gmb if you have more specific questions about the job.
[10:43] <adeuring> But we can of course anwser more generic questions about Canonical ;)
[10:45] <Ergo^> well, i would be interested to what i would work on and what kind of skill level would be expected for the position
[10:47] <Ergo^> adeuring, i've never worked for a IT organization that would have many employees, so im not sure what i would ask about :-)
[10:50] <adeuring> Ergo^: I don't know much what the the work is about aside from the general "cloudy" stuff... Regarding an org with "many" employees: I myself do not notice that much about the number of people employed by Canonical. You will work i a relatively small team, I assume. four or five people probably.
[11:05] <Ergo^> czajkowski, can i pm you ?
[11:10] <czajkowski> Ergo^: sure
[11:12] <allenap> Ergo^: gmb will be able to tell you more about the team's first project, but, like adeuring, there isn't the feel of "big company IT". We try to produce the best code we can, in a professional way; I have learnt *so* much about how to produce large pieces of software from working here. We're rigorous about testing, and we try to make decisions based on evidence and measurement. We don't always get it right, but we tend to see mistakes a
[11:12] <allenap> s an opportunity to learn rather than to blame.
[11:12] <lifeless> Ergo^: the new squad will be working on ceilometer initially.
[11:12] <lifeless> allenap: +1
[11:12] <czajkowski> lifeless: go sleep!
[11:13] <lifeless> one word: Cynthia.
[11:13] <allenap> Ha!
[11:14] <czajkowski> lifeless: awww
[11:15] <Ergo^> ok, well i work in environment where we dont write tests at all - they move more like early facebook - the boss doesnt want to budget for tests
[11:15] <Ergo^> but theres no problem to write tests
[11:16] <Ergo^> i would love to move to environment where i can learn new things
[11:19] <Ergo^> lifeless, so ceilometer - what kind of web stack will be used for the project? pylons/pyramid? something home brewed ?
[11:23] <lifeless> have a poke around yourself - https://launchpad.net/ceilometer
[11:25] <Ergo^> oh it uses webob
[11:25] <Ergo^> nice :]
[11:25] <Ergo^> and sqlalchemy, even nicer
[11:25] <Ergo^> i was expecting it would be using sqlstorm
[11:25] <rick_h_> Ergo^: hey howdy
[11:26] <Ergo^> ohai rick_h_
[11:26] <rick_h_> Ergo^: you were hacking on some of the min-webhelpers stuff right?
[11:26] <Ergo^> rick_h_, yeah ive made html.grid stuff
[11:26] <rick_h_> Ergo^: heh, not going to see much of the usual stack around :/
[11:26] <rick_h_> but really good dev practices, some stuff to learn for sure
[11:27] <Ergo^> rick_h_, well i would love that because i wont learn new things the place im at atm
[11:27] <Ergo^> different focus
[11:27] <rick_h_> Ergo^: definitely apply if you might be interested and chat with the guys. They're a really good group of smart peeps.
[11:27] <Ergo^> i would be, question is if they would be :P
[11:30] <Ergo^> rick_h_, well even if its not stack im used to it has some parts i know and love, so thats a good start
[11:30] <rick_h_> right, the launchpad stack is kind of strange, but you're allowed to learn it. I didn't know anything more than some articles of zope stuff
[11:30] <rick_h_> but most other things are django based
[11:31]  * Ergo^ knows nothing about django
[11:31] <rick_h_> heh, it's 'easy' :P
[11:32] <Ergo^> i would expect pylons/pyramid based wsgi apps, since i would expect its more flexible for this kind of environment
[11:32] <rick_h_> you'd think...but no. I've not won a battle on that front yet though there are some of us trying
[11:33] <Ergo^> rick_h_, i would expect mramm to help ;-)
[11:33] <rick_h_> hah, I'll have to ask him what his team's up to on that end I guess.
[11:34] <lifeless> go
[11:34] <lifeless> they are all about go
[11:34] <Ergo^> yeah he mentioned he writes in go right now last time ive asked
[11:35] <rick_h_> ah, he's over there
[11:47] <Ergo^> well, the ive browsed the code for ceilometer, it seems understandable and nice for me :]
[12:23] <rick_h_> czajkowski: looks like the report a bug link failure is fixed yay
[12:24] <Ergo^> rick_h_, when do you plan to add a human friendly interface to launchpad ? ;-)
[12:24] <rick_h_> Ergo^: heh, that's huw's job :P
[12:49] <Bert_2> Hi, I have setup an instance of launchpad with an actual domain (not launchpad.dev) and a clean db using wgrant's bootstrap-db-from-scratch and have added users using his user creationscript, now nor the admin nor regular users seem to be able to login into the subdomains of my instance (code, answers, blueprints), when I login with any account it redirects back to the page I came from but I'm still not logged in, does anyone know what'
[12:49] <Bert_2> s wrong ? Did I misconfigure something ?
[13:07] <Ergo^> gmb, ping
[13:11] <deryck> Good morning, all.
[13:17] <abentley> deryck: morning.
[13:18] <abentley> deryck: http://www.goodreads.com/quotes/14559-good-morning-said-bilbo-and-he-meant-it-the-sun
[13:28] <deryck> abentley, heh.  Great passage.
[13:28] <deryck> I knew there was a reason I normally typed only "morning" :)
[13:30] <abentley> deryck: Hehe.
[13:33] <deryck> adeuring, https://plus.google.com/hangouts/_/5c02c8b06ff0d06aaf9314c93315d217f5459977?authuser=0&hl=en
[13:57] <Ergo^> gmb, ping
[14:00] <czajkowski> Ergo^: he's not here. and won't be for two weeks
[14:01] <Ergo^> ah :]
[14:01] <Ergo^> rick_h_, so you say i should apply ? ;-)
[14:01] <rick_h_> Ergo^: give it a go and talk with them.
[14:08] <deryck> Ergo^ is a friend of rick_h_?
[15:49] <abentley> deryck: Currently, the mustache_model and the mustache_template from the server can be used by the javascript verbatim to render an identical result to the server-side rendering.
[15:49] <abentley> deryck: This is because the mustache_model includes control variables that affect the rendering, even though they're not logically part of the model.
[15:50] <deryck> abentley, ok.  are you wanting to change this where only the template can be rendered?  Or something else?
[15:51] <abentley> deryck: With the new pystache, we could remove all control variables from the mustache_model, which would be cleaner, but would break this property that the JS can use the model verbatim.
[15:52] <deryck> abentley, is there a downside to not using the model verbatim?
[15:52] <abentley> deryck: The downside is it's a bit more work to get an identical rendering between client-side and server-side rendering.
[15:53] <abentley> deryck: (but it's work we already do)
[15:54] <deryck> abentley, ah, I think I see.  We just do it via variables in the model, where as we need to specify those values at the call site now. right?
[15:55] <abentley> deryck: Yes, we need to inject the control variables at the call site, if they're not in the data sent by the server.
[15:57] <deryck> abentley, sounds fine to me.  Seems cleaner on both ends to me.  i.e. model is cleaner and rendering is explicit.
[15:57] <abentley> deryck: Cool.
[16:02] <Ergo^> heh i think i should install ubuntu :/
[17:20] <rick_h_> doh, forgot to put myself as ocr
[17:20] <rick_h_> and since I am... jcsackett can I bug you please? https://code.launchpad.net/~rharding/launchpad/lpclient_fix/+merge/116338
[17:24] <jcsackett> rick_h_: sure.
[17:24] <rick_h_> jcsackett: ty much kind sir
[19:05] <jcsackett> rick_h_: sorry, forgot to ping you when i finished reviewing your branch.
[19:05] <jcsackett> it is r=me.
[19:05] <rick_h_72> Thanks it's off to ec2. thanks again!
[19:32] <cody-somerville> Why are some versions listed twice under 'Releases in Ubuntu'? https://launchpad.net/ubuntu/precise/+source/thunderbird
[19:43] <Bert_2> wgrant: are you here ?
[20:00] <abentley> rick_h_: still around?
[20:01] <rick_h_> abentley: yep, what's up?
[20:01] <abentley> rick_h_: Could you please review https://code.launchpad.net/~abentley/launchpad/restore-queue-test/+merge/116534 ?
[20:02] <rick_h_> abentley: loading up now
[20:03] <abentley> rick_h_: Thanks.
[20:05] <rick_h_> abentley: what's task_init meant to do?
[20:06] <rick_h_> abentley: nvm, looking
[20:06] <abentley> rick_h_: It sets up a launchpad scripting environment.
[20:16] <rick_h_> abentley: couple of questions (side notes) r=me ty much
[20:16] <abentley> rick_h_: Thanks.'
[20:35] <rick_h_> jcsackett: ping
[20:35] <rick_h_> jcsackett: in your MP it says the 'helper method is removed' which I'm reading as userCanAccessUserData as being removed but it's not?
[20:39] <Bert_2> Does anyone know why I'm perfectly able to log in on the main section of my launchpad instance but not on the other sections like code and answers ? I don't get any errors but after supplying info to openid I just don't get logged in, any suggestions ?
[21:47] <sinzui> wgrant: StevenK: jcsackett: wallyworld: this is the non-published link of what I did today: http://youtu.be/Vq6VsKuFY_o
[22:04] <wgrant> Bert_2: Did you set cookie_domains to include your new domain?
[22:04] <wgrant> Bert_2: That controls how wildcardy the cookies are
[22:35] <sinzui> wallyworld: you are proposing to fix 3 or more of thses bugs https://bugs.launchpad.net/launchpad/+bugs?field.tag=bug-links
[22:38] <sinzui> wallyworld: http://blog.launchpad.net/general/bug-linking-part-2 "Linking existing bugs"
[22:46] <Bert_2> wgrant: where can I set the cookie_domains ?
[22:47] <wgrant> Bert_2: the development config inherits the default value from lib/lp/services/config/schema-lazr.conf. You can override it in your own config.
[22:47] <wgrant> # Session cookies being sent to a subdomain of the parent
[22:47] <wgrant> # domains listed here will be sent to the parent domain,
[22:47] <wgrant> # allowing sessions to be shared between vhosts.
[22:47] <wgrant> # Domains should not start with a leading '.'.
[22:47] <wgrant> cookie_domains: demo.launchpad.net, staging.launchpad.net, launchpad.net, launchpad.dev
[22:47] <Bert_2> so I shouldn't edit it inside schema-lazr.conf ?
[22:48] <wgrant> Probably not. The configs form an inheritance hierarchy, so you can just override the key in yours
[22:48] <Bert_2> so I would override from launchpad-lazr.conf in my custom configsdir ?
[22:48] <wgrant> Right
[22:49] <Bert_2> awesome, thx a ton :D
[22:49] <wgrant> np
[22:52] <sinzui> wallyworld: StevenK, wgrant: this is the one I was thinking of https://bugs.launchpad.net/launchpad/+bug/1004248
[22:52] <_mup_> Bug #1004248: hook to force page refresh on context url changing is not working <javascript> <regression> <ui> <Launchpad itself:In Progress by rharding> < https://launchpad.net/bugs/1004248 >
[23:10] <rick_h_> sinzui: something up with that?
[23:16] <sinzui> rick_h_: I was asking if a cache issue when a bug was marked a dupe related to that bug
[23:16] <sinzui> The conclusion was no
[23:16] <rick_h_> sinzui: ah ok cool. Wanted to make sure there wasn't anything up since I put that to ec2 today
[23:36] <Bert_2> wgrant: I just noticed that your bootstrap-db-from-scratch's bootstrap-lp-db script is missing the bug-watch-updater Celebrity, is that possible ?
[23:39] <Bert_2> (I have an oops page if you need more info)
[23:40] <wgrant> Bert_2: Yeah, if you look in the script where it creates the celebrities, you'll see comments instead of makeTeam/makePerson calls for some of them. I mainly just created the essential/interesting ones.
[23:40] <wgrant> You can alter the script or create the team manually to resolve it.
[23:40] <wgrant>     bazaar_experts = factory.makeTeam(
[23:40] <wgrant>         name='bazaar-experts', displayname='Bazaar Experts', owner=admins,
[23:40] <wgrant>         subscription_policy=TeamSubscriptionPolicy.RESTRICTED)
[23:40] <wgrant>     # bug_importer
[23:40] <wgrant>     # bug_watch_updater
[23:40] <wgrant>     buildd_admin = factory.makeTeam(
[23:40] <wgrant>         name='launchpad-buildd-admins',
[23:40] <wgrant>         displayname='Launchpad Builder Administrators', owner=admins,
[23:40] <wgrant>         subscription_policy=TeamSubscriptionPolicy.RESTRICTED)
[23:41] <wgrant> Some of the missing ones may be more essential now than they were when I wrote it.
[23:41] <wgrant> But the intention was that it'd get the web UI to work enough that you could create the rest if you needed them.
[23:42] <Bert_2> I see, so I'm missing the bug-watch-updater person then ?
[23:42] <Bert_2> it's apparently required to file a bug ;)
[23:43] <wgrant> Yeah. You can run the makePerson/makeTeam calls in bin/harness to fix that up
[23:44] <wgrant> In bin/harness, say eg. "factory.makePerson(name='bug-watch-updater', displayname='Bug Watch Updater', email='bugwatch@example.com')" then "transaction.commit()"
[23:44] <Bert_2> if you're interested: http://pastebin.com/yFzyDNCU it was on a call to bugs.[maindomain]/[project]/+filebug
[23:45] <wgrant> Ah right
[23:45] <wgrant> That is indeed a relatively recent change.
[23:45] <Bert_2> wgrant: why should I add it to bin/harness and not eg. make a utilities file for it and just execute that ? (just wondering)
[23:46] <wgrant> Well, you can update the script to do it too, but if it's a one-off it's usually easier to do it in bin/harness
[23:49] <wgrant> rick_h_: awk: cannot open build/js/yui-3.3.0/yui/yui.js (No such file or directory)
[23:49] <wgrant> rick_h_: Any idea on that build error?
[23:49] <wgrant> $ ls -l build/js/yui-3.3.0/
[23:49] <wgrant> total 0
[23:49] <wgrant> lrwxrwxrwx 1 wgrant wgrant 30 2012-07-25 09:49 yui-3.3.0 -> ../../../../build/js/yui-3.3.0
[23:50] <wgrant> It's a recursive symlink..
[23:51] <wgrant> rick_h_: Also, your yui buildout changes still use a predictable /tmp name
[23:52] <wgrant> StevenK: Can you build a fresh tree?
[23:52] <rick_h_> wgrant: yes, sorry. While we talked about it, webops didn't have feedback on that part and so only changed that which was required.
[23:52] <StevenK> wgrant: My devel build a few minutes ago worked
[23:52] <rick_h_> wgrant: I can make a follow up that will adjust that dir.
[23:52] <StevenK> wgrant: I can clean and then do a fresh make?
[23:52] <wgrant> StevenK: Try make clean_buildout build
[23:52] <rick_h_> we were tossing stuff at the wall at the time
[23:53] <wgrant> Heh
[23:53] <StevenK> rick_h_: May I suggest you not do that with our Makefile?
[23:53] <rick_h_> wgrant: added a card to move that dir in the morning
[23:53] <Bert_2> wgrant: so bin/harness is meant for one-off scripts ?
[23:53] <StevenK> wgrant: make clean_buildout build worked for me
[23:54] <wgrant> StevenK: Hmm
[23:54] <wgrant> Bert_2: It just gives you a Launchpaddy Python console
[23:54] <rick_h_> StevenK: heh, the sticking to the wall was guessing what issue my change had on qas not our makefile...and it's buildout.cfg now makefile :P
[23:54] <Bert_2> wgrant: I see
[23:54] <StevenK> rick_h_: Even worse, because buildout loves giving obtuse error messages.
[23:56] <rick_h_> StevenK: so think it's ok, will adjust the path to keep things inside of the build dir vs /tmp
[23:56] <Bert_2> wgrant: just so you know, same goes for bug-importer, apparently
[23:56] <wgrant> Yup
[23:58] <wgrant> StevenK, rick_h_: Hm, even 'make clean build' breaks
[23:58] <wgrant> Oh
[23:58] <wgrant> I don't have unzip installed
[23:58] <wgrant> It's nice that buildout doesn't actually notice or display the error
[23:59] <StevenK> [09:54] < StevenK> rick_h_: Even worse, because buildout loves giving obtuse error messages.
[23:59] <StevenK> wgrant: ^
[23:59] <wgrant> StevenK: It also loves not giving any error message at all, though
[23:59] <wgrant> Obtuse errors are fine :)
[23:59] <Bert_2> Does anyone know what the bugtask tasks and nominations table is ?


[11:41] <jedi__> I got a major crash while dl the java packages
[11:41] <Tommy2k4> if kubuntu keeps crashing im gonna have to go back to windows :(
[11:41] <holotone> weird.
[11:41] <driz> NOOOOOO!!!!
[11:41] <holotone> if life doesn't get better, I"m going to have to go back to jesus.
[11:41] <hccmqqr> huoh
[11:41] <driz> lol
[11:42] <jedi__> on the way of reinstalling adept  i lost the adept updater
[11:42] <ZomMes> gatekeeper: no i just want to share it with a friend in the same house through the router
[11:42] <jedi__> , cant put i back
[11:42] <Skizzo21> Hey everyone I just installed kubuntu but i cant get on to the internet
[11:43] <jeff_> ???
[11:43] <jedi__> how come??
[11:43] <Skizzo21> haha no clue
[11:43] <jedi__> you are chatting
[11:43] <Skizzo21> i was hopin u guys would no
[11:43] <Skizzo21> haha
[11:43] <Skizzo21> i have lots of computer
[11:43] <Skizzo21> s
[11:43] <gatekeeper> ZomMes: that's ok :-)
[11:43] <Skizzo21> ive never used linux before :'(
[11:43] <DaSkreech> Skizzo21: How do you get onto the internet?
[11:43] <jeff_> I'll ask again
[11:44] <Skizzo21> through a router
[11:44] <holotone> Skizzo21:  are you trying to connect via wireless or ethernet?
[11:44] <Skizzo21> ethernet
[11:44] <jeff_> how do i get all user to show on login scren
[11:44] <jedi__> hey but how come you can chat with us??? and cant go on the net....
[11:44] <Skizzo21> because i have a router and im on my windows computer ;-)
[11:44] <jedi__> right
[11:45] <jedi__> do you have ethernet  on you linux cmp?
[11:45] <Skizzo21> yea
[11:45] <jedi__> computer
[11:45] <Skizzo21> its connected right now
[11:45] <jedi__> ok
[11:45] <relix> so... how big a partition should I make for kubuntu install?
[11:45] <jeff_> can the linux ping the loop address
[11:45] <jeff_> can it ping the it ip
[11:45] <jeff_> can it ping the router
[11:45] <jedi__> it should have detected it even with the router on....
[11:45] <Skizzo21> how do i ping sorry this is literally my first time
[11:46] <Skizzo21> haha this is like sex HAHA
[11:46] <Skizzo21> sorry
[11:46] <Skizzo21> continue
[11:46] <jedi__> ping ""your ip"
[11:46] <|lostbyte|> relix, >=3gb
[11:46] <jedi__> in a console
[11:46] <Antaran> good day, I'm new to kubuntu, can I synchronize my iPaq with a KDE kalendar, tasks, email etc, how?
[11:46] <jeff_> terminal "ping <IP_ADDRESS>
[11:47] <Skizzo21> i have succesfully pinged it
[11:47] <jeff_> ping the IP
[11:47] <Skizzo21> oo ping my nic
[11:47] <Skizzo21> hold on
[11:47] <Skizzo21> success
[11:47] <Skizzo21> that works
[11:47] <jeff_> ok ping the router
[11:47] <Skizzo21> that works
[11:48] <jeff_> should work
[11:48] <jedi__> oh shit i did not see the time... got to go to sleep damn it tmrw i have a big day at work!!
[11:48] <jedi__> c ya all
[11:48] <Skizzo21> opening konqueror now and testing www.cnn.com
[11:48] <Skizzo21> An error occurred while loading http://www.cnn.com
[11:48] <Skizzo21> Unkown host www.cnn.com
[11:49] <driz> How do i remove wine in it there is the windows version of firefox i was trying to instal shockwave but i gave up?
[11:49] <jeff_> can you send eamil
[11:49] <jeff_> email
[11:49] <Skizzo21> uhh i cant try?
[11:49] <Skizzo21> can*
[11:49] <jeff_> wierd
[11:50] <jeff_> i don't know
[11:50] <jeff_> try pinging google,com
[11:50] <slow-motion> n8
[11:51] <Skizzo21> unable to ping google
[11:51] <jeff_> skizzo21 try ping google.com or something
[11:51] <jeff_> sorry
[11:52] <jeff_> something between router and modem
[11:52] <Skizzo21> hmmmm
[11:52] <Skizzo21> maybe my driver is messed up?
[11:52] <Skizzo21> how do i like update a driver
[11:52] <|lostbyte|> Skizzo21, can your other pc's access the internet
[11:52] <Skizzo21> yes sir
[11:52] <jeff_> duh
[11:52] <jeff_> sorry
[11:52] <negocio> ok, i have install qemu
[11:53] <negocio> but
[11:53] <driz> why is it when i Ping a website it just keeps going and going>
[11:53] <driz> ?
[11:53] <negocio> how can i run DOS in it?
[11:53] <|lostbyte|> Skizzo21, coud you ping <IP_ADDRESS> ?
[11:53] <Skizzo21> hey jeff.... can i update the driver somehow?
[11:53] <Skizzo21> ill try now
[11:53] <jeff_> linux does that
[11:53] <jeff_> there is a command to stop it
[11:53] <jeff_> but i dont know it
[11:53] <jeff_> sorry dont know
[11:53] <Skizzo21> lostbyte that is weird
[11:53] <Skizzo21> i WAS able too
[11:53] <Skizzo21> what IP is that?
[11:53] <daiver> CTRL+C to stop it
[11:54] <jeff_> thks
[11:54] <daiver> np
[11:54] <|lostbyte|> Skizzo21, Googles
[11:54] <jeff_> worked
[11:54] <daiver> ;)
[11:54] <|lostbyte|> Skizzo21, if that worked.. you need to add dns to your resolve.conf in /etc/
[11:54] <Skizzo21> how in gods name do i do that
[11:54] <negocio> anyone have any idea making DOS work in qemu,
[11:54] <negocio> how can i do that?
[11:55] <jeff_> beyound me
[11:55] <Skizzo21> wow that is interesting i can connect to websites by IP haha
[11:55] <|lostbyte|> Skizzo21, kdesu kate /etc/resolv.conf
[11:55] <Skizzo21> good thinking lostbyte
[11:55] <jeff_> no DNS
[11:55] <Skizzo21> is that a command or something?
[11:55] <|lostbyte|> yes it is..
[11:56] <negocio> help running dos in qemu, how?
[11:56] <jeff_> will that update the dns
[11:56] <|lostbyte|> ok ! now i want you to go on your windows pc.. and type in dos ifconfig /all
[11:56] <Skizzo21> ipconfig?
[11:56] <jeff_> iPconfig /all
[11:56] <jeff_> if is linux
[11:56] <|lostbyte|> opps yes ! ipconfig
[11:56] <Skizzo21> haha aight i did thta
[11:57] <Skizzo21> who is kate?
[11:57] <jeff_> show DNS Servers
[11:57] <|lostbyte|> Skizzo21, you will see dns there.. in windows..
[11:57] <Skizzo21> uh huh
[11:58] <negocio> pike, are you there?
[11:58] <|lostbyte|> Skizzo21, Kate is a TextEditor
[11:59] <Skizzo21> ok
[11:59] <Skizzo21> shes up and i have my dns from my windows machine
[11:59] <Skizzo21> whats next
[11:59] <Tommy2k4> Partition 1 does not end on cylinder boundary.
[11:59] <Tommy2k4> i get that for all 3 partitions
[11:59] <Tommy2k4> is that bad
[11:59] <Tommy2k4> (with fdisk)
[11:59] <gatekeeper> Skizzo21: kate has also got a terminal which makes it very usefull
[11:59] <|lostbyte|> Skizzo21, ok ! the format is  --------> nameserver <dns_ip>
[12:00] <|lostbyte|> Skizzo21, and SAVE it !
[12:00] <|lostbyte|> Skizzo21, Now Google.com in your browser will work..
[12:00] <Skizzo21> *crosses fingers*
[12:00] <jeff_> crossed
[12:01] <Skizzo21> wait so once resolv.conf opens jus type  "nameserver <mydnsip?>
[12:01] <negocio> can anyone help me?
[12:01] <|lostbyte|> negocio, huh ? can we ?
[12:01] <Skizzo21> lostbyte is that what I should do?
[12:02] <|lostbyte|> yes.. replacing that with the dns_ip [and no quote]
[12:02] <jeff_> i think he means the DNS address you saw
[12:03] <franz> I'm trying to install kubuntu on a pc with no success:
[12:03] <negocio> yes please
[12:03] <negocio> i need to run dos en qemu
[12:03] <negocio> i have instal qemu
[12:03] <negocio> i was tringy
[12:03] <Skizzo21> okay i went to "start" whatever its called and hit  run command... and typed  "kdesu kate /ect/reolv.conf"
[12:03] <negocio> but my image doesnt have a bootable os
[12:04] <|lostbyte|> franz, DOS !! What is that :P
[12:04] <negocio> Disk Operating System
[12:04] <franz> it's nearly finished the process, but "hardware configuration" is like blocked at 94% since  15 mins
[12:04] <Skizzo21> i then was given an empty text and typed   "   nameserver <<IP_ADDRESS>> and hit save
[12:04] <relix> ok thanks lostbyte
[12:04] <|lostbyte|> Skizzo21, "etc"
[12:04] <negocio> i have a prices list make in DOS and i have to run it
[12:04] <Skizzo21> yea sorry i meant etc***
[12:04] <|lostbyte|> Skizzo21, no need for "<>"
[12:04] <Skizzo21> o
[12:05] <Skizzo21> SUCCESS
[12:05] <Skizzo21> I LOVE YOU GUYS!
[12:05] <franz> |lostbyte|, what you meant before?
[12:05] <negocio> question: how can i run DOS with qemu?
[12:05] <Tommy2k4> kubuntu has crashed for the 7th time today :(
[12:05] <Skizzo21> time to test my wireless card :'( brb
[12:05] <Tommy2k4> next time im going back to windows
[12:06] <robotgeek> Tommy2k4: it cant hard lock, can it?
[12:06] <|lostbyte|> franz, that was for negocio lolz..
[12:06] <jeff_> good stuff
[12:06] <Skizzo21> lostbyte im trying to learn here ... so when you get a chance can u explain what opening kate did exactly.....? whenever u get a chance
[12:06] <franz> ah ok
[12:06] <Tommy2k4> http://ubuntuforums.org/showthread.php?t=204080 theres my problem
[12:06] <gatekeeper> Tommy2k4: you sure you haven't got a hardware problem?
[12:06] <|lostbyte|> franz, Pls explain "no success" ?
[12:07] <|lostbyte|> Skizzo21, kate is a text editor like notepad


  Video: http://www.youtube.com/user/tbemus?v=opFwsEzFs14 , Audio: http://live.smlr.us/streaming
[11:14] <tony-smlr> SMLR is Live!   Did get a free coffee. She's just like "I'm not taking your money.
[18:24] <snap-l> I'm really upset at how they handled this
[18:24] <snap-l> it makes me really reluctant to get too attached to Peets.
[18:25] <brousch> What's going on?
[18:25] <rick_h_> yea, well I can't decide if I'm just sad or upset enough to say $#@$@ it and move CHC anyway
[18:28] <rick_h_> brousch: https://www.facebook.com/cariboucoffee?filter=2 not a lot of 'news' about it
[18:29] <snap-l> I think they're still digesting what it all means
[18:29] <brousch> I don't think I've ever been to one
[18:29] <rick_h_> brousch: so I've been coming to one that's < 1mi from my house for years. When I'm chatting about working from the coffee shop it's been here.
[18:30] <brousch> And they're shutting them all down?
[18:30] <rick_h_> I know all the managers, regional manager (we chat football when he's visiting) lots of employees (half are going through college)
[18:30] <rick_h_> basically 8/10 shutting down it seems.
[18:30] <rick_h_> CHC is held at one of the few that supposedly will be staying open and turned into a peets in the summer/end of year
[18:30] <snap-l> brousch: They're shutting down most of them, and turning the rest into Peets coffee.
[18:30] <brousch> I had a coffee shop like that. It was sad to see it go. When we drive by, George still asks if we can go in there
[18:31] <rick_h_> yea, we bring Michael here on weekends and such
[18:31] <brousch> I haven't ever found a replacement. I've settled on Biggby
[18:31] <rick_h_> he jokes that his cup of juice is a 'coffee cooler like daddy'
[18:31] <rick_h_> :(
[18:31] <snap-l> Biggby is OK, but the one by us is really small and hard to get into
[18:31] <rick_h_> yea, nothing really around but a starbucks that I don't really care for
[18:33] <rick_h_> but yea, so working from there atm and just sad. Want to come up and 'represent' by kind of depressing
[20:14] <Blazeix> pretty neat: http://thejh.net/misc/website-terminal-copy-paste
[20:29] <rick_h_> heh
[20:31] <greg-g> nice
[23:28] <snap-l> https://www.youtube.com/watch?feature=player_embedded&v=KDN1UbFyVwQ#! <- jcastro: Your next bass guitar.
[23:29] <snap-l> https://www.youtube.com/watch?v=HDs95VzOc_o  <- 4 string version


[12:07] <ev> so dh v9 tries to execute .maintscript files if they're +x. Bug or the packager should know better?
[12:23] <xnox> ev: packager should know better, it's documented behaviour.
[12:25] <ev> this whole needing a separate degree to distribute an application thing will never catch on :)
[12:26] <antarus> thats just what developers who don't understand how complex packaging is would say ;p
[12:26] <ev> it doesn't need to be complex
[12:26] <ev> it shouldn't be complex
[12:26] <antarus> heh
[12:26] <antarus> I agree the interfaces are poor
[12:26] <antarus> but it is inherently complex
[12:26] <ev> but yes, the complexity is baked in. "Hey, here's a root shell. Have fun!"
[12:26] <ev> indeed
[12:27] <antarus> you could say the same thing about most programming though ;p
[12:27] <ev> sure - but programming is hard enough. Lets not layer complexity on top of that :)
[12:27] <antarus> (if you are distributing a simple applicatoin I would argue that packaging is fairly trivial)
[12:28] <antarus> at work you can basically in your 'makefile' just write "builddeb(name, version, release, owner, depends=[foo, bar,baz])
[12:28] <antarus> and the system will build you a deb of your code
[12:28] <antarus> now you can't do anything complex with it (conffiles, alternatives, etc..)
[12:28] <antarus> because its hard to make a simple interface for that ;p
[12:32] <xnox> ev: imho it's better than a single monolithic file with pseudo shell functions and requirement to explicitely list every single file & folder that will be 'owned' by the package... (rpm)
[12:33] <antarus> real packages use ebuilds anyway
[12:33] <antarus> ;p
[12:42] <silvos> hi, are you talking about how simple (or not) building ubiquity or just packaging? (having problem to compile and run it here) http://paste.ubuntu.com/1009633/
[12:45] <silvos> http://paste.ubuntu.com/1009648/  config.log
[12:55] <xnox> silvos: ./debian/rules update-local
[12:55] <xnox> silvos: fakeroot ./debian/rules binary
[12:55] <xnox> done
[12:56]  * xnox ubiquity is a non-standard package, because it includes bits and pieces of other packages
[13:05] <silvos> thanks xnox
[13:06] <silvos> I thinks its fails again, I changed value in .po to be sure, and when I run ubiquity its runs ubiquity from the apt-get install one with old .po value.
[13:06] <silvos> I feel I don't understannd every thing
[13:24] <cm-t> Hi
[13:26] <cm-t> I followed same as silvos but I fail to run ubiquity, and I don't find many information on compiling it.
[13:27] <silvos> I might forgot some step, is there a wiki page or something like that explainning the compilation ?
[13:41] <xnox> silvos: after fakeroot ./debian/rules binary
[13:41] <xnox> $ sudo dpkg -i ../*.deb
[13:41] <xnox> to install newly compiled ubiquity
[13:41] <xnox> then run it.
[14:08] <silvos> well, I don't have .deb because of error, I'm trying to understand them
[14:32] <silvos> http://paste.ubuntu.com/1009761/  if ever
[14:33] <xnox> silvos: did you run: fakeroot ./debian/rules binary
[14:33] <xnox> or just ./debia/rules build
[14:33] <xnox> ?
[14:33] <xnox> binary will give you actuall debs to install
[14:34] <silvos> http://paste.ubuntu.com/1009761/  is the result of    fakeroot ./debian/rules binary >> bin.txt
[14:36] <silvos> hum
[14:36] <silvos> i should use the error output
[14:36] <xnox> yes, please. that does look incomplete
[14:37] <xnox> lp:ubiquity currently can only be build on quantal, because it has been ported to python3 and a couple of dependenies are not in precise
[14:37] <xnox> if you want precise's ubiquity get it with $ apt-get source ubiquity
[14:37] <xnox> or there should be a precise branch.
[14:38] <cm-t> oh
[14:46] <silvos> http://paste.ubuntu.com/1009777/
[14:47] <silvos> ( fakeroot ./debian/rules binary &> bin.txt )
[22:23] <CIA-62> debian-installer: cjwatson * r1698 ubuntu/ (build/pkg-lists/gtk-common debian/changelog): ttf-freefont-udeb was renamed to fonts-freefont-udeb.


[20:19] <daker> hi
[20:19] <daker> any good news ?
[21:23] <jenkins-Android> Gobyk ping
[21:28] <jenkins-Android> I have attempted to upload quickshot how ever my laptop is only working with an external screen and that is starting to fail as well. I am having a new pc delivered hopefully this week , i will upload asap.
[21:29] <jenkins-Android> I got 8 inches if snow at the weekend so spent lots if time shifting it so I could get to work today.
[21:35] <godbyk> jenkins-Android: Sounds like you're having a good time, then! :-)
[21:35] <godbyk> jenkins-Android: Thanks for working on Quickshot, though.  We keep getting people popping into the channel asking how to take screenshots.
[21:38] <jenkins-Android2> N I promise to get it uploaded the version in one of the pas should function to some form iirc
[21:40] <godbyk> jenkins-Android, jenkins-Android2, jenkins-Android3: connectivity problems? you're multiplying!
[22:00] <jenkins-Android2> Godbyk yea my WiFi is dogy


[03:46] <dupingping> The awesome software is published, You can use the trial version of Sticky Notes.
[03:46] <dupingping> http://korsoftware.com


[02:48] <Tm_T> moin
[02:49] <Tm_T> hmm, looks like our icon guy isn't here
[02:49] <cas> too bad, but the icons should be in vector right?
[02:50] <cas> I noticed it because I have an sized up trashcan, which now looks very blurry
[02:51] <cas> sorry for the incompleteness for other users, I just wondered why the human icons aren't vector anymore.
[03:21] <Tm_T> hmm
[03:21] <Tm_T> not sure but, I think it has something to do with vector rendering in small sizes