[00:22] <nhaines> sn9: German word for oneirick would be träumig.
[00:24] <sn9> no "ei" in that
[07:36] <nhaines> Unity is optimal for playing Minecraft: http://ubuntuone.com/p/kpO/
[16:52] <iheartubuntu> I only had time to pull off one Natty countdown banner idea. Its very simple and uses the Ubuntu orange. Wished I had more time. Will be working well in advance on 11.10 designs! https://wiki.ubuntu.com/Website/NattyCountdownBanner
[17:19] <nhaines> iheartubuntu: I like the elegance of your design.  It's a real shame it doesn't qualify.  :(
[17:23] <pleia2> what's the trouble with it?
[17:24] <nhaines> pleia2: they basically said "no narwhals".
[17:25] <sn9> wtf
[17:27] <nhaines> Some of the designs there are a bit gaudy.... I think Anthony Scarth's design's probably the nicest, or Leandro Gómez's.  But iheartubuntu's is very clean, and that's something most of the others are lacking.
[17:28] <pleia2> ah, I knew they said they didn't want animals a few countdown banners ago, but I didn't realize it had continued (and they didn't include that on the guidelines)
[17:29] <pleia2> "it would probably be inappropriate to over-emphasize narwhal graphics"
[17:29] <pleia2> from the announcement
[17:30] <sn9> pink unicorns
[17:30] <pleia2> they should add that to the guidelines on the wiki, seems like a few people didn't realize
[17:30] <nhaines> Yeah, I was surprised not to find it on the wiki page.
[17:31] <sn9> "they" ? it's a wiki
[17:31] <pleia2> sn9: changing the guidelines for someone else's contest is not good form
[17:32] <iheartubuntu> well, i tried not make the narwhal stand out with any detail. just an outline.
[17:32] <nhaines> iheartubuntu: it's better than the aqua one with the dancing narwhal.  :)
[17:32] <iheartubuntu> there can always be exceptions :) (or not)
[17:33] <pleia2> hehe, I quite like the cartoony one ;)
[17:33] <iheartubuntu> so do i!
[17:33] <iheartubuntu> i tihnk its good to have more than just one or two designs.
[17:33] <iheartubuntu> a cartoon design would work great on, well, my cartoon site
[17:39] <iheartubuntu> DUH - i just figured out i can ftp into my servers right from a "places" folder
[17:41] <nhaines> Any Nautilus folder will let you ftp in.
[17:41] <nhaines> nautilus is pretty awesome.  :)
[17:41] <sn9> unity isn't
[17:43] <nhaines> Unity is awesome, too.
[17:43] <nhaines> It's perfect for playing Minecraft.
[17:43] <nhaines> Q.E.D.
[17:44] <nhaines> Unity's awesomeness is much more recent, though.
[20:14] <nhaines> pleia2: I just picked up the book "15 Minutes Including Q&Q: A Plan to Save the World From Lousy Presentations".  I'll let you know if it's any good.
[20:15] <pleia2> nhaines: thanks :)
[20:15] <nhaines> pleia2: the Slashdot review (plus the title) sounded promising and the $2.99 Kindle price was too good to pass up.  :)
[20:15] <pleia2> ah nice
[20:17] <pleia2> I was asked to submit a keynote talk for a little foss event back east last week, if I'm selected my stuffed animal audience will be well-used by the time I'm ready for it
[20:22] <nhaines> pleia2: oh wow, that's great!  :D
[20:22] <nhaines> Someday I'll give a keynote.  :)
[20:23] <pleia2> yeah, we'll see, it's just a little conference but I have to start somewhere :)
[20:29] <nhaines> pleia2: how many times do you practice a speech before you give it?
[20:36] <pleia2> nhaines: depends on the talk, 8 times is probably average though
[20:36] <pleia2> I always set aside at least 8 hours for just speaking prep
[20:37] <nhaines> pleia2: I'm always a little lazy on setting aside time.  I do a lot of talking out loud as I'm writing notes and creating slides.
[20:38] <nhaines> I even manage to convince myself I'll sound more ad-libbing and off-the-cuff.  :)
[20:38] <nhaines> Even though I know that even when I was an instructor and giving the same 7-hour Excel lesson week after week, my "spontaneous" jokes were all well-planned in advance.
[20:43] <iheartubuntu> so  thats what the stuffed animals are for!
[20:45] <iheartubuntu> pleia2 is going to have lucid dreams of talking to life sized furry humans. i would be worried when they start chasing you
[20:47] <pleia2> cute fluffy things are never aggressive :)
[20:47] <iheartubuntu> :D
[20:49] <iheartubuntu> im going natty on this computer. be back in a few
[20:49] <iheartubuntu> (minutes? hours?)
[22:08] <iheartubuntu> natty still installing on my desktop. doing all the updates
[22:11] <nhaines> pleia2: it was a pretty good book.  :)  Not 100% applicable to every talk I'll give, but definitely had some good ideas in it.
[22:13] <iheartubuntu> 14 min to go for natty. i notice on the desktop im installing with nvidia, the topbar didnt work
[22:15] <nhaines> iheartubuntu: during the Ubiquity installer?  It doesn't work on ATI either.
[22:15] <iheartubuntu> yes
[22:16] <iheartubuntu> i didnt experience that on this laptop with built in graphics
[22:16] <iheartubuntu> but it will work one installed? :)
[22:16] <iheartubuntu> (gulp)
[22:17] <nhaines> Yes, for me there's a missing icon and the top panel is only about 4px high.  It's really annoying.
[22:19] <iheartubuntu> yes, thats exactly what it looks like right now
[22:21] <nhaines> Aww, UDS-S is in Orlando.
[22:21] <iheartubuntu> i saw that. did anyone here go to it last yr?
[22:22] <kdub> wasnt it in orlando last time?
[22:22] <iheartubuntu> yah
[22:25] <kdub> shuttleworth must like florida i guess
[22:27] <pleia2> apparently it was a 2 year deal
[22:32] <broder> UDS-S is, what, 13.10?
[22:33] <broder> ah, the rumor is UDS-P not -S. that's...slightly less absurdly in advance
[22:46] <iheartubuntu> OMGubuntu mentioned it could be in FL again for budget reasons. dont know if they had a source to that or just speculation
[22:48] <broder> I don't have anything to compare against, but I thought the Caribe Royale was nice
[23:12] <iheartubuntu> woohoo! 3rd place in countdown banners!
[23:13] <pleia2> oh, did they announce them?
[23:16] <iheartubuntu> shhh! i didnt finish reading the email. im not supposed to tell anyone!
[23:16] <iheartubuntu> dang
[23:21] <pleia2> hah
[23:39] <iheartubuntu> this station is for nhaines... http://yp.shoutcast.com/sbin/tunein-station.pls?id=1280187
[23:40] <iheartubuntu> "Melodien aus den Bergen"
[23:40] <iheartubuntu> :D
[23:46] <kdub> internet
[23:47] <nhaines> iheartubuntu: congrats!  Your banner is definitely the cleanest.  :)
[23:49] <kdub> whats a banner for?
[23:54] <iheartubuntu> actually, i need to clean up the narwhal. its a bit ragged. i did it this morn early. first time doing all inkscape and i had just imported a jpg. need to trace it and clean it up
[23:54] <iheartubuntu> Countdown Banner... 28 days until Ubuntu 11.04, 27 days, 26 days, etc
[23:55] <iheartubuntu> finally getting a chance to work with unity here
[23:55] <pleia2> kdub: https://wiki.ubuntu.com/Website/NattyCountdownBanner
[23:55] <iheartubuntu> so far i like it
[23:55] <iheartubuntu> couple things im not a fan of
[23:55] <iheartubuntu> like the menu options being in the top panel
[23:55] <iheartubuntu> switching workspaces is an extra step
[23:55] <kdub> sure are a lot of banners...
[23:56]  * crashsystems <3 global menus
[23:56] <iheartubuntu> but unity sure is much improved since SCaLE9x


[22:00] <johnc4510-laptop> The new issue of the Ubuntu Weekly Newsletter is available:
[22:00] <johnc4510-laptop> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue131


[04:35] <Mirv> jhodapp: pong
[10:23] <bzoltan> Mirv:  are you doing someting with that silo?
[10:30] <bzoltan> Mirv:  Ahh, I see your comment.
[10:55] <Mirv> bzoltan: that
[10:56] <Mirv> bzoltan: I'll click Approved again once it has built, although because of the yakkety s390x problem it's currently not going to QA queue automatically still
[10:56] <Mirv> there must be a boatload of people wanting to fix upstart s390x problem in yakkety
[10:57] <bzoltan> Mirv:  it did not fail last time I have built the silo... what changed since?
[10:58] <Mirv> bzoltan: it built fine this time too https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-029/+packages - but as you know, you had the yakkety excuses problem regarding the auto approval tests
[10:58] <Mirv> and that remains unless answering my suggestion on #otherchannel :)
[10:59] <bzoltan> Mirv:  i see, thanks... is there a way to land that silo anyway?
[10:59] <Mirv> bzoltan: by asking qa nicely to get it into their queue, yes. but then it won't migrate from yakkety-proposed to release pocket
[11:00] <Mirv> bzoltan: although that wouldn't be a new thing since the current UITK in yakkety-proposed isn't migrating either...
[11:00] <bzoltan> Mirv:  right
[11:00] <bzoltan> jibel:  would you please? Pretty please :)
[11:01] <Mirv> jibel: so bzoltan is asking QA Signoff Ready for https://requests.ci-train.ubuntu.com/#/ticket/1443 because of remaining yakkety problems that will be solved .. in time
[11:02] <Mirv> right now, as mentioned, no-one probably is jumping to fix upstart s390x
[11:03] <Mirv> well of course unless it's something really easy, there's unrelated upload just done
[11:03] <Mirv> anyway, with yakkety there will be some amount of unresolved issues that won't be immediately solved
[11:07] <jibel> Mirv, bzoltan done
[13:57] <mardy_> Mirv: our tests are failing in Xenial and Yakkety due to a mesa error: https://launchpadlibrarian.net/261581280/buildlog_ubuntu-yakkety-arm64.ubuntu-system-settings-online-accounts_0.7+16.10.20160525.1-0ubuntu1_BUILDING.txt.gz
[13:57] <mardy_> Mirv: any idea on what's wrong? They used to pass
[14:03] <Saviq> plars, krillin-07 seems gone https://unity8-jenkins.ubuntu.com/job/test-ppa-autopkgtest/171/label=phone-armhf,package=unity8,release=vivid+overlay,testname=autopilot.sh/console
[14:18] <plars> Saviq: weird, it's getting unauthorized
[14:18] <plars> Saviq: we should not still be seeing that
[14:18] <plars> Saviq: has something changed with the way you deploy it?
[14:20] <plars> Saviq: should be able to recover it, but I don't see how that can happen right now
[14:21] <plars> and none of the other devices seem to be in that state
[14:41] <Saviq> plars, no, nothing new
[14:42] <sil2100> pstolowski: hey! How far are you guys with silo silo 47?
[14:42] <plars> Saviq: I can try recovering it, but I'm not sure how it could have ended up in that state - or if your job runs recover from lifeboat, then it should also do the same
[14:42] <sil2100> pstolowski: I'm asking since I would like to back-port the arm64 enablement from yakkety and I wouldn't want to break your work
[14:43] <Saviq> plars, yeah that output is from recover, see 13:08:13
[14:43] <plars> let me try it here
[14:43] <pstolowski> sil2100, all built ok, looks ok & approved by me; waiting for autopkg tests to finish
[14:45] <sil2100> pstolowski: excellent, I see arm64 binaries are also built now so the change is included - thanks, we'll be waiting for this to land
[14:45] <sil2100> :)
[14:46] <pstolowski> sil2100, the previous run of autpkg tests on yakkety failed on unity8, probably a flaky test but need Saviq to confirm
[14:47] <Saviq> pstolowski, got link?
[14:47] <Saviq> ah 47
[14:47] <Saviq> hmm not sure if I can get back to that test
[14:48] <pstolowski> Saviq<EMAIL_ADDRESS>[14:50] <pstolowski> Saviq, FAIL!  : qmltestrunner::Wizard::test_passwdPasscode()
[14:51] <Saviq> pstolowski, ah yeah, that's fixed in the u8 released last night
[14:51] <Saviq> so the new run will be fine
[14:51] <pstolowski> cool
[14:54] <plars> Saviq: it seems to have recovered fine when I tried it - give it a try
[14:54] <Saviq> plars, ack, thanks
[15:02] <charles> kenvandine, wrt silo 50, be my guest
[15:07] <kenvandine> charles, someone already published it :)
[15:10] <Mirv> mardy_: arm64 Qt switched to OpenGL ES today (same as armhf), looks like fallout from that since you're using mesa software rendering instead of real hardware and maybe not too many people in the world are using arm64 mesa software rendering... you may need to skip the test on arm64 (and we should test on real accelerated hw)
[15:11] <Mirv> of course we don't have such phone hw either yet though :)
[15:14] <Mirv> mardy_: it might be useful to file against mesa about the issue anyhow
[15:16] <mardy_> Mirv: OK, I will
[15:16] <mardy_> Mirv: about disabling tests, what's the best way? set DEB_BUILD_OPTIONS=nocheck
[15:17] <mardy_> Mirv: set the env variable above at the beginning of debian/rules, depending on the value returned by dpkg-architecture?
[15:17] <Mirv> mardy_: see eg http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/debian/rules - lines 10,11,14,23,29
[15:19] <mardy_> Mirv: excellent, thanks!
[15:33] <pstolowski> sil2100, hmm silo 47 autopkg tests failed, but there are not regressions reported?
[15:54] <pstolowski> Mirv, hey, any idea about silo 47? ^
[15:58] <bschaefer> trainguards, hello. I need a silo for getting a ppa into vivid + overlay
[15:59] <bschaefer> its maliit-framework and maliit-inputcontext-gtk2/3
[15:59] <bschaefer> ppa: https://launchpad.net/~brandontschaefer/+archive/ubuntu/maliit
[15:59] <bschaefer> tested working on the phone
[16:02] <robru> bschaefer: hiya. I guess you need permissions to create the ticket?
[16:02] <bschaefer> robru, i ... think so, since it will require someone here to upload the ppa to the
[16:02]  * bschaefer looks
[16:03] <Mirv> pstolowski: vivid dependency problem, but I can't reach my computer to debug more properly right now (I'm outside spending the evening)
[16:03] <bschaefer> robru, i can create a new request
[16:03] <pstolowski> Mirv, ah..
[16:04] <robru> bschaefer: OK create the request and assign it, I'll copy the package over
[16:04] <Mirv> pstolowski: the arm64 enablement is done on xenial/yakkety so I can't really guess what would be causing a vivid problem... maybe that enablement related regardless, from some triple landing
[16:04] <robru> Just need some breakfast first, brb
[16:05] <bschaefer> robru, cool, (as do i!) (its being assigned now but taking for ever)
[16:06] <bschaefer> robru, https://requests.ci-train.ubuntu.com/#/ticket/1466
[16:06] <bschaefer> thanks!
[16:07] <pstolowski> robru, sil2100 can either of you help with silo 47 (see Mirv's comments above)?
[16:09] <Saviq> pstolowski, Mirv, on vivid: unity-scope-click/arm64 unsatisfiable Depends: ubuntu-sdk-libs
[16:09] <Saviq> Not considered
[16:09] <Saviq> pstolowski, you want uitk as a build dep to never build for arm64 if it's not available there
[16:10] <Saviq> pstolowski, in the mean time someone needs to delete your vivid arm64 binaries for this to go green
[16:10] <Saviq> *or* we need uitk to build for arm64 in vivid overlay
[16:11] <Saviq> oh hum
[16:11] <Saviq> what's ubuntu-sdk-libs? virtual?
[16:11] <Saviq> ah d'oh
[16:12] <Saviq> it's from ubuntu-touch-meta
[16:12] <robru> pstolowski: yeah, that ^
[16:13] <robru> bschaefer: ok, copied
[16:14] <Saviq> pstolowski, ok so to avoid this unity-scope-click needs to B-D on ubuntu-sdk-libs, so it's never built for arm64 unless that is available (and we need to discuss with archive people how to do this, it's been a problem a few times already)
[16:15] <pstolowski> Saviq, ok, preparing MP.. why didn't we see it before in vivid?
[16:15] <robru> Saviq: what do you need to know how to do? build-dep on something that has the correct arches sounds like the right solution to me
[16:16] <robru> pstolowski: because arm64 has only just been enabled for some packages, apparently
[16:16] <pstolowski> ah
[16:23] <bschaefer> robru, awesome thanks!
[16:23] <robru> bschaefer: you're welcome
[16:33] <dobey> robru: why doesn't someone just make the same change to ubuntu-touch-meta in vivid, that was made in yakkety/xenial?
[16:34] <robru> dobey: I have no idea. I guess we don't care about arm64 in vivid?
[16:34] <robru> which would make sense since we're trying to update to xenial
[16:35] <dobey> well, but we aren't updating all devices to xenial
[16:36] <robru> ungh
[16:38] <dobey> and the frameworks files in ubuntu-sdk-libs are a lie on xenial/yakkety anyway, because the ABI is broken
[16:38] <dobey> cest la vie
[16:49] <Mirv> Saviq: robru: so there is certainly some new vivid-overlay problem that needs to be fixed other than starting to undepend on ubuntu-sdk-libs
[16:50] <robru> Mirv: undepend? they were talking about adding a dep on that so it'll follow its arches
[16:50] <Mirv> I'd guess some arm64 enablement targeting xenial/yakkety was triple landed and somehow wonderously causes now a new vivid related problem simply regarding installing the touch packages
[16:51] <Mirv> robru: ah right sorry, now I finally could look into the problem so right this is I guess about pstolowski instead working on arm64 enablement and he has added a new dep on ubuntu-sdk-libs. ok that makes sense and you probably indeed already suggested the correct way to fix it.
[16:51] <Mirv> I just try to do things in haste when running from place to place but I'm glad it seems relatively clear to you at least :)
[16:53] <Mirv> if it seems hard to do vivid only exception for not depending on arm64 meta package, we may still enable ubuntu-sdk-libs for arm64 for these purposes (even though arm64 won't be enabled for real on vivid)
[16:53] <Mirv> ok I'll really go now, it's better to focus on these things during working hours
[16:56] <robru> Mirv: goodnight
[18:34] <rvr> Mirv: Hi
[18:35] <rvr> Mirv: Silo 9
[18:36] <rvr> Mirv: I killed the music app using the spread. Now, music app stucks after start.
[18:36] <rvr> Mirv: I have rebooted, but the application remains in the same state after starting it.
[18:37] <rvr> Mirv: Not sure whether it is related to the silo changes.
[18:37] <rvr> mzanetti: ^
[18:37] <rvr> This is the log of music app http://paste.ubuntu.com/16690390/
[18:45] <rvr> I manually removed the lock file, and the app works again
[18:45] <rvr> It's documented in the silo card
[18:46] <rvr> And yes, the silo packages are installed.
[18:47] <dobey> oh, well ubuntu-sdk-libs isn't installable on xenial arm64 either. yay
[18:48] <dobey> a bit surprised it does install in y
[20:17] <mzanetti> rvr, still here?
[20:17] <mzanetti> and still in that state?
[21:14] <dobey> robru: if britney has "old binaries left" listed for the silo autopkgtests, we need to someone to delete those binaries?
[21:14] <robru> dobey: yep, what silo?
[21:16] <dobey> robru: 47
[21:17] <dobey> robru: click scope arm64 binaries on xenial/vivid
[21:18] <robru> dobey: ok, deleted. will take 1-2 hours for britney to notice
[21:18] <dobey> an eternity by any other name
[21:20] <dobey> robru: thanks
[21:20] <robru> dobey: you're welcome!


[20:09] <mup> Bug #1923246 opened: Unable to compose LXD VM with multiple NICs <MAAS:Triaged> <https://launchpad.net/bugs/1923246>
[20:09] <mup> Bug #1923251 opened: Creating an LXD VM host now requires a project name <MAAS:Triaged> <https://launchpad.net/bugs/1923251>
[20:12] <mup> Bug #1923246 changed: Unable to compose LXD VM with multiple NICs <MAAS:Triaged> <https://launchpad.net/bugs/1923246>
[20:12] <mup> Bug #1923251 changed: Creating an LXD VM host now requires a project name <MAAS:Triaged> <https://launchpad.net/bugs/1923251>
[20:15] <mup> Bug #1923246 opened: Unable to compose LXD VM with multiple NICs <MAAS:Triaged> <https://launchpad.net/bugs/1923246>
[20:15] <mup> Bug #1923251 opened: Creating an LXD VM host now requires a project name <MAAS:Triaged> <https://launchpad.net/bugs/1923251>
[20:18] <mup> Bug #1923246 changed: Unable to compose LXD VM with multiple NICs <MAAS:Triaged> <https://launchpad.net/bugs/1923246>
[20:18] <mup> Bug #1923251 changed: Creating an LXD VM host now requires a project name <MAAS:Triaged> <https://launchpad.net/bugs/1923251>
[20:21] <mup> Bug #1923246 opened: Unable to compose LXD VM with multiple NICs <MAAS:Triaged> <https://launchpad.net/bugs/1923246>
[20:21] <mup> Bug #1923251 opened: Creating an LXD VM host now requires a project name <MAAS:Triaged> <https://launchpad.net/bugs/1923251>
[20:24] <mup> Bug #1923246 changed: Unable to compose LXD VM with multiple NICs <MAAS:Triaged> <https://launchpad.net/bugs/1923246>
[20:24] <mup> Bug #1923251 changed: Creating an LXD VM host now requires a project name <MAAS:Triaged> <https://launchpad.net/bugs/1923251>
[20:27] <mup> Bug #1923246 opened: Unable to compose LXD VM with multiple NICs <MAAS:Triaged> <https://launchpad.net/bugs/1923246>
[20:27] <mup> Bug #1923251 opened: Creating an LXD VM host now requires a project name <MAAS:Triaged> <https://launchpad.net/bugs/1923251>
[21:51] <mup> Bug #1923261 opened: MAAS Beta 2 CLI does not respect the LXD trust password <MAAS:New> <https://launchpad.net/bugs/1923261>
[21:54] <mup> Bug #1923261 changed: MAAS Beta 2 CLI does not respect the LXD trust password <MAAS:New> <https://launchpad.net/bugs/1923261>
[22:03] <mup> Bug #1923261 opened: MAAS Beta 2 CLI does not respect the LXD trust password <MAAS:New> <https://launchpad.net/bugs/1923261>
[22:21] <mup> Bug #1923263 opened: MAAS Beta 2 CLI retains VMs when LXD KVM is deleted <MAAS:New> <https://launchpad.net/bugs/1923263>
[22:24] <mup> Bug #1923263 changed: MAAS Beta 2 CLI retains VMs when LXD KVM is deleted <MAAS:New> <https://launchpad.net/bugs/1923263>
[22:27] <mup> Bug #1923263 opened: MAAS Beta 2 CLI retains VMs when LXD KVM is deleted <MAAS:New> <https://launchpad.net/bugs/1923263>


[02:59] <lfaraone> bernie: btw, we should totally look into setting up monkeysphere for SugarLabs SSL / HTTPS services
[07:04] <bernie> lfaraone: yup
[07:05] <bernie> lfaraone: sunjammer already has a signed gpg key
[07:05] <bernie> lfaraone: signed by me, that is. you might want to sign it as well
[15:14] <manusheel> neeraj, kandarpk: Hi Neeraj and Kandarp.
[15:14] <kandarpk> manusheel: hello sir.
[15:14] <neeraj> manusheel: Hi sir
[15:15] <manusheel> kandarpk: As we are working on the next task on activity development, do we need any help on fixing the bug assigned to you?
[15:15] <manusheel> neeraj: Did we finally arrive at the set of steps for creating a patch?
[15:16] <kandarpk> manusheel: sir, I am not able to reproduce the frame bug on my system.
[15:16] <neeraj> manusheel: Yes. I think so. kandarpk sir, you were able to create patch using quilt and debdiff. Right?
[15:17] <kandarpk> neeraj: ankur had already created the patch.
[15:17] <kandarpk> neeraj: but I understand the process.
[15:17] <neeraj> kandarpk sir: Ok. I thought both of you were working on different bugs.
[15:18] <manusheel> kandarpk: ok.
[15:18] <manusheel> neeraj: Sure.
[15:25] <dfarning> alsroot, manu ping
[15:26] <alsroot> dfarning: yup
[15:27] <manusheel> dfarning: Hi David.
[15:27] <dfarning> alsroot, manusheel lfaraone I just wanted to let manusheel and luke know that you will be mentoring the sugarteam!
[15:28] <manusheel> dfarning: Thank you. Appreciate it.
[15:28] <manusheel> alsroot: Our team looks forward to working under your guidance in the development area.
[15:29] <dfarning> manusheel, can you set up a scheudal that works for alsroot and the developers working on IST (indian standard time)
[15:29] <manusheel> dfarning: Sure.
[15:29]  * alsroot is ok w/ 09.00-21.00 in UTC
[15:30] <manusheel> alsroot: Great.
[15:31] <dfarning> lfaraone, can you show alsroot the ropes on how to mentor a team to make the transformation to sugar hackers.
[15:31] <lfaraone> dfarning: sure.
[15:31] <dfarning> lfaraone, your work with the team has been exceeding my expectations:)
[15:32] <lfaraone> dfarning: did you get my google talk messages earlier today, by the way?
[15:32] <dfarning> alsroot, manusheel, lfaraone thanks.  I'll go away and try to stay out of your way:)
[15:33] <manusheel> alsroot: Let us arrive at a plan on how we could define a series of meetings at IRC to go through - walking through the code, functionalities in operating system, logging levels in Python, how we can build a development roadmap for the next 2 months.
[15:33] <manusheel> dfarning: :-)
[15:33] <dfarning> lfaraone, sorry I am having connection issues.... the sun is shinning.
[15:33] <lfaraone> dfarning: ah, I see :)
[15:34] <dfarning> yes yes said that browse should be ok but .90 might be a problem.
[15:34] <dfarning> lfaraone, I though the timing the ubuntu was to release just after the latest stable gnome release.
[15:35] <dfarning> lfaraone, thus .90 was considered a bug fix to .89 which we are running.
[15:36] <kandarpk> lfaraone, dfarning, alsroot: Hi
[15:36] <alsroot> kandarpk: hi
[15:37] <kandarpk> alsroot: I am following the activity development manual at http://en.flossmanuals.net/
[15:37] <kandarpk> will ask you when in doubt.
[15:37] <dfarning> kandarpk, good morning.  I was just letting the channel know that you guys are now better sugar developer them I am so we had to bring in a expert to help you take the next step:)
[15:37] <alsroot> kandarpk: sure
[15:38] <manusheel> dfarning: Appreciate it.
[15:39] <kandarpk> dfarning: I would love working with alsroot, he sure is an expert at creating actvities :)
[15:39] <kandarpk> and understanding the OS.
[15:40] <lfaraone> dfarning: we're shipping 0.88 in Maverick, not 0.89
[15:41] <dfarning> hmmm. I thogught we had updated it.  Will that be a problem?
[15:41] <lfaraone> dfarning: that, combined with the fact that the FinalFreeze is on Sept 16.
[15:42] <manusheel> lfaraone: Ok.
[15:43] <lfaraone> dfarning: If you want, upstream has a predictable schedule (which SL does), then sure, propose it. (talk in #ubuntu-motu about it)
[15:44] <dfarning> lfaraone, ok, can you see what you can do?  the telepathy refactoring is a significant improvement.... but It is not worth getting anyone riled up about.
[15:45] <dfarning> lfaraone, we can deal with the .91 to .92 update next release.
[15:46] <lfaraone> dfarning: right now I'm reviewing a patch by the SEETA folks in a VM, then I'm writing the bug guidelines, then I'll be testing pyxpcom.
[15:46] <lfaraone> dfarning: If you want I can switch over to lobbying for a FFe now, but I'll have to table all of that other stuff for an hour+ to talk to the right people etc.
[15:47] <dfarning> lfaraone, np .92 is at the bottom of your current todo list.
[15:48] <lfaraone> dfarning: 0.90, you mean?
[15:48] <lfaraone> (which we currently aren't slated to ship until Ubuntu-N, 11.04)
[15:48] <dfarning> lfaraone, yes. but technically .92. is below .90 on your todo:)
[17:28] <lfaraone> dfarning: re browse renaming, I've heard some things about that at DebConf too...
[17:30] <dfarning> lfaraone, what did you hear?
[17:31] <lfaraone> dfarning: iirc zack said that we may at some point in the future have "firefox" in debian.
[17:32] <dfarning> Ahh yes I just read that this morning.  That would help fix the mozilla browser situation in both ubuntu and debian.
[17:45] <ishan> alsroot, hi
[17:45] <alsroot> ishan: hi
[17:49] <ishan> alsroot, where are the changes in the time and wireless radio implemented??
[17:49] <ishan> in sugar
[17:51] <alsroot> ishan: heh :), wireless support was added just recently to glucose.. need to look into code -- what do you mean by "time"?
[17:53] <ishan> alsroot, where are the changes in the time zones implemented in sugar??
[17:53] <manusheel> alsroot; I think Ishan is referring to the time zones setting in the control panel.
[17:54] <alsroot> ishan: see extensions/cpsection/datetime directory, it is datetime control panel component
[17:55] <alsroot> ishan: and also extensions/cpsection/network for wireless
[17:55] <ishan> alsroot, okay let me check
[17:56] <alsroot> ishan: you can just grep sugar sources, for I have all sucrose sources and bunch of activities and periodically grep them for strings
[17:56] <alsroot> s/for /for example/
[17:57] <manusheel> alsroot: Thank you. Ishan, this should be helpful.
[17:57] <ishan> manusheel, yes sir
[18:00] <lfaraone> alsroot: To solve "When opening the control panel some icons are cut off", https://bugs.launchpad.net/ubuntu/+source/sugar-0.88/+bug/617582, neeraj disabled the padding that separated sugar-control-panel from the rest of the UI, making it fullscreen.
[18:01] <lfaraone> alsroot: is that an acceptable deviation? (I'm not sure if it's in the HIG)
[18:01]  * alsroot looks
[18:03] <lfaraone> alsroot: http://img231.imageshack.us/img231/2530/screenshotdl.png <- screenshot of result of patch in a VM
[18:08] <alsroot> neeraj: I think, #617582 might be fixed in more reliable way (otherwise it will be all time a play w/ offsets), /me tries to figure out
[18:15] <alsroot> neeraj: maybe tweaking _MAX_COLUMNS constant according to current screen resolution
[18:16] <manusheel> alsroot: Thanks for the pointer. Neeraj will be back soon. He has gone to the market.
[18:16] <manusheel> alsroot: Will inform him as soon as he comes back.
[18:16] <lfaraone> alsroot: I'll mention that in the bug,t hen
[18:18]  * alsroot has a widget that handles such issues.. but it is in Vala and might in glucose only in 0.92+
[18:18] <alsroot> :/
[18:19]  * lfaraone is on to pyxpcom
[18:53] <neeraj> alsroot: Thanks for the suggestion. At present bys etting _MAX_COLUMNS to 3 (3 items in a row), we can easily view all 9 items. :)
[19:03] <alsroot> neeraj: you can just run sugar-emulator with several "-i <width>x<height>" and "-s (100|72)" combinations to see how it will look like
[19:10] <neeraj> alsroot: Ok. I ran the emulator in different resolution and full screen to. The control panel is adjusting the spacing accordingly. :)
[19:11] <neeraj> s/to/too
[19:14] <manusheel> kandarpk: Around?
[19:14] <kandarpk> manusheel sir: yes sir.
[19:48] <kandarpk> alsroot: around ?
[19:48] <alsroot> kandarpk: yup
[19:49] <kandarpk> alsroot: can you please see http://paste.ubuntu.com/479000/
[19:49] <kandarpk> I've added lines 79 onwards
[19:49] <kandarpk> to add a button
[19:50] <kandarpk> alsroot: but it is not getting displayed.
[19:51]  * alsroot tries
[19:54] <alsroot> hmm.. after last glucose update sugar is not working as assumed, /me tries to fix
[19:58] <kandarpk> alsroot: is the code ok, if we ignore the errors in sugar ?
[20:01] <alsroot> kandarpk: looks like.. /me still trying to figure out why this code doesn't start
[20:02] <kandarpk> alsroot: Ok.
[20:06] <kandarpk> alsroot: do we need to add the button as we have done for the label using 'self.set_canvas(label)' ?
[20:06] <kandarpk> *though self.set_canvas(button) doesn't work
[20:10]  * alsroot reset sugar back to 0.88
[20:11] <alsroot> kandarpk: well, your code works for me what did you mean for "is not working as assumed"
[20:11] <kandarpk> alsroot: I dont see any button on running the activity
[20:16] <alsroot> kandarpk: sorry, had to restart X, you mean button from rotate()?
[20:16] <kandarpk> alsroot: yes.
[20:17] <alsroot> kandarpk: but you don't add it to activity canvas in code you posted before
[20:18] <kandarpk> alsroot: yeah, tried adding it later, but that didn't work.
[20:18] <alsroot> kandarpk: in fact, there is a gtk.Container - canvas, you need to add all widgets there
[20:19] <alsroot> kandarpk: you tried to use set_canvas() once more?
[20:19] <kandarpk> alsroot: I'll try again.
[20:20] <alsroot> kandarpk: just create your container e.g. gtk.VBox, add there button and other widgets and call set_canvas(vbox)
[20:20] <alsroot> s/and/and place/
[20:22] <kandarpk> alsroot: Ok, giving it a try. need to look how to add the controls to the container.
[20:23] <alsroot> kandarpk: http://library.gnome.org/devel/pygtk/stable/class-gtkcontainer.html#method-gtkcontainer--add, and there are special method in containers like gtk.VBox (see the same doc page)
[20:23] <alsroot> *methods
[20:24] <kandarpk> alsroot: Ok, thanks.
[20:26] <alsroot> kandarpk: in fact I don't like pygtk docs, imho, pure gtk is much useful e.g. it shows classes hierarchy http://library.gnome.org/devel/gtk/stable/GtkVBox.html
[20:27] <alsroot> I mean also child class not only parents
[20:34] <kandarpk> alsroot: hmm, that provides better hierarchical info.
[20:37] <kandarpk> alsroot: please see http://paste.ubuntu.com/479029/
[20:38] <alsroot> kandarpk: should work (if you will call rotate())
[20:39] <alsroot> kandarpk: oops, you forgot to call show() for container
[20:40] <kandarpk> alsroot: Ok.
[20:40] <kandarpk> yes
[20:42] <alsroot> kandarpk: btw, there is also show_all(), some time (when there are no hidden by intention widgets), it is useful to show the entirely hierarchy by one call
[20:43] <kandarpk> alsroot: Ok.
[20:43] <kandarpk> alsroot: the button and label are present now.
[20:44] <kandarpk> alsroot: but the label isn't rotating on clicking the button
[20:45] <alsroot> kandarpk: yup, because you recreate it every hello() call, create label as self.label in __init__()
[20:46] <kandarpk> alsroot: isn't the angle changing ?
[20:50] <alsroot> kandarpk: heh, there is another fail, 'clicked' handler, should accept additoinal argument (sender of event)
[20:50] <alsroot> gtk should log about
[20:50] <alsroot> it
[20:51] <alsroot> so in your code "self.button.connect('clicked', self.hello, None)", hello() should take even 3 arguemnts, hello(self, sender, arg-for-None)
[20:51] <kandarpk> alsroot: "TypeError: hello() takes exactly 1 argument (3 given)"
[20:52] <kandarpk> alsroot: great.
[21:00] <kandarpk> alsroot: Its working now. :)
[21:00] <kandarpk> alsroot: thanks
[21:00] <alsroot> yw
[21:19] <kandarpk> Time to sleep.
[21:19] <kandarpk> gn everyone.
[22:56] <ssn> hi
[22:58] <ssn> i installed some activites via apt-get but there is no browser and no interesting activities in the repository ppa:sugarteam/ppa
[23:05] <manusheel> ssn: Ok.
[23:06] <manusheel> ssn: Which activities would you like to see?
[23:07] <manusheel> ssn: Can you please send me an e-mail on the activities that you would like to see in USR at<EMAIL_ADDRESS>[23:07] <manusheel> Thanks.
[23:15] <ssn> ok ignore my email, i just read that browse does not work in ubuntu
[23:17] <manusheel> ssn: It is yet to be packaged.
[23:17] <manusheel> :-)
[23:17] <manusheel> ssn: We'll get it packages soon.
[23:18] <ssn> the problem is, that i want to introduce a couple of teachers to sugar, but i still did not find a good (german language) solution that works live and lets me install also
[23:37] <manusheel> ssn: Ok.
[23:37] <manusheel> ssn: You are right.
[23:38] <manusheel> ssn: We are still in the development phase in USR project. In a couple of months, you'll see a good solution.
[23:38] <ssn> Im looking forward to it
[23:38] <manusheel> ssn: It would be great if you could send me a set of features that you have found missing, or working unexpectedly.
[23:38] <manusheel> ssn: We'll try and make improvements in those lines.
[23:39] <manusheel> ssn: We'll also make efforts in internationalization of Sugar.
[23:40] <ssn> i will, its just a little crazy right now because i am also "developing" a media education distro for my bachelor thesis. now that also  teachers for smaller children got interested in my attempts to push free software into schools, i have to come up with something that works for the little ones
[23:43] <manusheel> ssn: Sure. Please take your time. Appreciate it.


[14:06] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4586 Diff missing (jammy/flash-kernel). Needs rebuild due to higher version at destination (jammy/livecd-rootfs)
[15:07] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4586 Needs rebuild due to higher version at destination (jammy/livecd-rootfs). UNAPPROVED queue (jammy/flash-kernel)
[23:06] -queuebot:#ubuntu-ci-eng- sil2100, https://bileto.ubuntu.com/#/ticket/4586 Needs rebuild due to burned version number (jammy/flash-kernel). Needs rebuild due to higher version at destination (jammy/livecd-rootfs)


[04:16] <johann_> Someone can tell me how to get the source code of unity
[07:18] <MCR1> sil2100: Hi :)
[07:19] <MCR1> sil2100: Are there problems with Unity landings or why is it jamming ?
[07:21] <MCR1> sil2100: Could you also approve this branch ? : https://code.launchpad.net/~brandontschaefer/unity/improve-keyboard-shortcut-overlay-wording/+merge/119071
[07:21] <sil2100> MCR1: unity is still in freeze, I hope to unfreeze it today
[07:22] <sil2100> Starting next week we'll try to use a different release approach
[07:22] <sil2100> So it won't be a problem hopefull
[07:22] <sil2100> *hopefully
[07:23] <MCR1> sil2100: It would be important to have this ^^ in trunk, so I could start working on the elimination of the hardcoded shortcuts that would probably also touch the same code...
[07:23] <didrocks> sil2100: we will probably need a compiz snapshot next Monday/Tuesday FYI once the gsettings g-c-c part is landed FYI
[07:23] <didrocks> (just to keep you up to date)
[07:24] <didrocks> sil2100: there will be a need of two cherry-picks in the unity codebase
[07:28] <MCR1> didrocks: Hi :) My plan is to convert all hardcoded Unity keys to Compiz keys and integrate those that are currently hardcoded to the Unity plug-in. Is thos a good plan and is there something special I should take care of ?
[07:28] <MCR1> *this a good plan
[07:29] <didrocks> MCR1: this is great, you will need to coordinate later on with sam to ensure those are exposed in g-c-c (there are a hardcoded list for that) and how to make those optionals for people not having unity
[07:30] <didrocks> MCR1: just remember that Feature freeze is 2 weeks away, so approx only one week to get things integrated :)
[07:31] <MCR1> didrocks: Ok, I hope I can get this done (weekend is reserved for that task) - I'll try to coordinate stuff with Sam, probably he needs to help me anyway... ;)
[07:32] <MCR1> didrocks: One thing that came to my mind is how Unity-2d will handle stuff if those hardcoded shortcuts are converted for example...
[07:32] <didrocks> no more unity-2d starting next week
[07:33] <didrocks> so don't bother :)
[07:33] <MCR1> didrocks: Oh, ok. One thing less to worry about then, although it works quite nice...
[07:46] <MCR1> duflu: Hi :) If feature-freeze is near, I would be very happy if we could get the most important "lost" plug-ins merged before the freeze. We do not need to activate those in GLES, or do we (afaik trip for example is simply deactivated in GLES) ?
[07:47] <sil2100> mhr3: hello! Will you find a free few moments of your time for releasing tarballs for bamf, libunity and the lenses (files, apps, music) in an hour or so ;)?
[07:47] <mhr3> sil2100, did we have any changes to lenses?
[07:47] <duflu> MCR1: Sorry, am in a mad rush getting the important features completed. The new plugins come after that
[07:48] <sil2100> mhr3: just the vala update, true... so maybe I'll just distropatch those
[07:48] <sil2100> mhr3: so only bamf and libunity for now ;)
[07:48] <mhr3> oh right, that's actually worth a release
[07:49] <mhr3> sil2100, we just finished standup, so i guess it's ok if i do them right away
[07:50] <didrocks> mhr3: sit! :)
[07:50] <mhr3> didrocks, grrrrrrrr
[07:52] <MCR1> duflu: I hope and wish your mad rush is successful and does end before feature freeze ;) - I stop disturbing you now :-X
[07:53] <sil2100> mhr3: I'll just check one more autopilot test and we're ready for release
[07:53] <mhr3> meh, it's not like there could a bug in libunity :P
[07:53] <sil2100> True, but still! ;) Better safe then sorry ;p
[07:54] <mhr3> i'll wait with bamf though :D
[07:54] <didrocks> sil2100: don't believe him, don't believe him!
[07:54] <mhr3> didrocks, ssshushhh
[07:56]  * mhr3 shakes fist at the half broken build system in trunk libunity
[07:56] <didrocks> mhr3: if it's only half broken, it's fine, take the other half!
[07:57] <mhr3> didrocks, right, half of the source files should do, right? :)
[07:57] <didrocks> sure, you write useless code, let's cut it down! :)
[07:58] <mhr3> didrocks, it's a sign of project maturity though, you know that libreoffice has like 20% of code that's unused?
[07:59] <didrocks> mhr3: yeah, I heard about that, it's scary that we have that much code around, and still not real good way to instrumente the code to detect dead part
[08:00] <sil2100> ...;) I'm scared when I listen to you guys ;p
[08:02] <sil2100> Arrgh
[08:02] <sil2100> hm, I need JohnLea!
[08:02] <sil2100> Since either something changed by design, or we have a small regression
[08:03] <mhr3> sil2100, in?
[08:03] <sil2100> mhr3: in switcher - it's probably unity-only though
[08:04] <sil2100> mhr3: checking how it looks in 6.0
[08:05] <mhr3> sil2100, tarball for dee as well?
[08:05] <mhr3> seems like there's wasn't one for quite a while
[08:07] <sil2100> mhr3: hell, why not? If you only feel like it ;)
[08:16] <mhr3> sil2100, what version are we doing now?
[08:16] <mhr3> 6.2?
[08:16] <mhr3> or 6.4?
[08:18] <sil2100> 6.2
[08:20] <sil2100> Ah, no, it seems to work - no regression here
[08:28] <didrocks> sil2100: btw, do not forget to have a google doc with the results of manual tests and autopilot ones :)
[08:28] <sil2100> didrocks: it's already done ;)
[08:34] <mhr3> sil2100, so green to push the tarballs?
[08:35] <mhr3> quick! hide! kamstrup's here
[08:35] <kamstrup> mhr3: hey!
[08:35] <kamstrup> what ever you do - I DISAPPROVE!
[08:35] <kamstrup> ;-)
[08:35] <mhr3> kamstrup, hey, hey! i see holiday has good effect on you :)
[08:37] <kamstrup> i know, right?!
[08:55] <sil2100> mhr3: GREENZ
[09:08] <mhr3> eeek, i have to create 6.0 series for all the lenses :/
[09:10] <gord> sucks to be yoou
[09:18] <mhr3> sil2100, disted, milestoned, uploaded, tagged, pushed
[09:18] <sil2100> mhr3: awesooome! I'll release for unity in nux in a moment
[09:18] <sil2100> s/in/and
[09:58] <mhr3> sil2100, oh dear, i forgot about bamf
[09:58] <mhr3> Trevinho, you here?
[10:02] <Trevinho> mhr3: yep
[10:03] <mhr3> Trevinho, still no big changes in bamf for the major bump?
[10:03] <Trevinho> mhr3: no :(
[10:04] <mhr3> 61st release of 0.2 series then? :/
[10:04] <sil2100> ...;)
[10:08] <sil2100> didrocks: in the changelog, should I also put changes from trunk that weren't assigned to any bugs?
[10:08] <sil2100> Or only the ones with bugs?
[10:09] <didrocks> sil2100: only those with bugs are enough, it's long enough already :)
[10:09] <didrocks> sil2100: btw, IIRC, there are some merges with contains "UIFe" in the bug title (not sure before this release, but some are proposed now)
[10:09] <didrocks> sil2100: if it's the case, you can remove the "UIFe" part :)
[10:10] <sil2100> didrocks: could you later on run unify again to generate the changelog for unity ;p ?
[10:11] <sil2100> didrocks: since for nux and the rest I do manually, since those are small
[10:11] <sil2100> But unity, phew
[10:11] <didrocks> sil2100: sure, tell me once you are ready :)
[10:12] <sil2100> \o/ thank you!
[10:12] <mhr3> sil2100, uploaded bamf
[10:12] <sil2100> mhr3: excellent, thanks!
[10:13] <sil2100> didrocks: for unify, all other unity projects (nux, bamf) should have unity upstream in their bugs as well, right?
[10:13] <didrocks> sil2100: yeah, as usual :)
[10:14] <sil2100> didrocks: last thing, since I forgot - do I need to set the milestone to 6.2 for unity on those as well? For instance, for nux?
[10:14] <didrocks> sil2100: on the unity upstream task, yeah
[11:07] <sil2100> didrocks: can I publish the new unity tarball, or do you need to do it yourself for unify to work?
[11:16] <didrocks> sil2100: no, you can publish it
[11:16] <didrocks> sil2100: just don't close the milestone
[11:19] <sil2100> didrocks: so, I should tick 'keep the 6.2. milestone active'?
[11:22] <didrocks> exactly
[11:53] <sil2100> didrocks: I sent an e-mail with branches and all the release details
[11:59] <didrocks> sil2100: "I checked lintian warnings - had to silence some for unity, but besides that no *new* ones seem to have appeared. "
[11:59] <didrocks> can you detail please?
[11:59] <didrocks> also,should I run unify now as you are telling you are waiting on the changelog?
[12:00] <didrocks> (ok on unify, running now)
[12:00] <didrocks> sil2100: unfreeze should be done by mmrazik
[12:14] <sil2100> didrocks: I know ;) Will ask him once I get  your ACK
[12:15] <sil2100> didrocks: no *new* lintian errors, since I remember getting this one before: E: unity-common: python-script-but-no-python-dep usr/lib/unity/makebootchart.py
[12:15] <sil2100> For unity ;p
[12:15] <sil2100> But since it's like not a main script, I think that's ok?
[12:16] <didrocks> sil2100: all in one commit :/
[12:16] <didrocks> don't remember about the one commit per act I really insisted on
[12:16] <didrocks> that makes the review painful
[12:17] <sil2100> ah, shit, sorry about that - in unity it's like that because I first did merge-upstream ...
[12:17] <sil2100> Could have started from the override branch already
[12:17] <didrocks> sil2100: just remember that for next time :)
[12:18]  * sil2100 writes that down this time
[12:18] <sil2100> My desk is actually getting very messy with all these notes
[12:37] <didrocks> Conflicting tags:
[12:37] <didrocks>     upstream-3.2.0
[12:37] <didrocks> hum, interesting
[12:38] <didrocks> in nux
[12:38] <didrocks> sil2100: you should use unify btw
[12:38] <didrocks> sil2100: you miss bugs
[12:38] <sil2100> :(
[12:39] <sil2100> So I missed one...
[12:39] <sil2100> Actually I though I had them all, hmm
[12:39] <didrocks> 3 in nux
[12:39] <sil2100> Which ones?
[12:40] <didrocks>     - Support for automation (LP: #685199)
[12:40] <didrocks>     - add alpha function on a NuxBaseWindow (LP: #718827)
[12:40] <didrocks>     - Timestamp field on the event structure is always 0 (LP: #735645)
[12:40] <sil2100> Ok, those completely I missed, need to check why
[12:42] <didrocks> I get 20 conflicting tags on unity
[12:42] <didrocks> have you done anything special?
[12:42] <didrocks> or is bzr going crazy?
[12:42] <sil2100> hm, no? 20 conflicting tags? That's a bit too much for a 'mistake'
[12:43] <didrocks> sil2100: no, you made something weird
[12:43] <didrocks> your bzr branch is based on revision 25
[12:43] <didrocks> and you remerged everything from that
[12:43] <sil2100> Which one? lp:ubuntu/unity ?
[12:43] <didrocks> right
[12:43] <sil2100> All I did was bzr branch lp:ubuntu/unity freshly today
[12:43] <didrocks> hence conflicting tags all over your branch when pulling on ubuntu/unity
[12:44] <didrocks> sil2100: look at your revision
[12:44] <didrocks> you start at rev 25
[12:44] <sil2100> And did a bzr merge-upstream
[12:44] <didrocks> or something is really weird in bzr-gtk
[12:44] <didrocks>     revno: 55.813.24 [merge]
[12:44] <didrocks> should rather be revno: 746
[12:45] <sil2100> revno: 747 [merge]
[12:45] <sil2100> committer: Łukasz 'sil2100' Zemczak<EMAIL_ADDRESS>[12:45] <didrocks> yeah, this is your upper commit
[12:45] <sil2100> This is what bzr log |less gives me
[12:45] <sil2100> revno: 746
[12:45] <sil2100> tags: 6.0.0-0ubuntu6
[12:45] <sil2100> This is the one I based on
[12:45] <didrocks> now, look at the first nested entry
[12:45] <didrocks> bzr log -n 1
[12:45] <didrocks> -n 2 sorry
[12:45] <didrocks>     revno: 55.813.24 [merge]
[12:45] <didrocks> this is your merge-upstream
[12:46] <didrocks> same issue with nux btw
[12:46] <didrocks> you started from     revno: 159.3.40 [merge]
[12:46] <sil2100> Wait, so what did I do wrong?
[12:46] <sil2100> I did exactly this:
[12:46] <didrocks> well, tell me you did do :)
[12:46] <sil2100> bzr branch lp:unity
[12:46] <sil2100> bzr branch lp:ubuntu/unity ubuntu
[12:46] <sil2100> cd ubuntu
[12:47] <sil2100> bzr merge-upstream ../unity-6.2.0.blabla ../unity --version=6.2.0 -r -1
[12:47] <sil2100> # changelog editing
[12:47] <didrocks> let me try that with nux
[12:47] <sil2100> debcommit
[12:47] <sil2100> And that's all I did
[12:47] <sil2100> Everything fresh from 0 today
[12:47] <didrocks> well, the log shows that something is wrong, isn't it?
[12:47] <didrocks> btw, when you did merge-upstream, I think it bailed on conflicting tags
[12:48] <didrocks> so you should have noticed that something went wrong (also, look at the logs)
[12:48] <didrocks> so let me redo this for nux
[12:48] <didrocks> and see if it's a merge-upstream issue
[12:49] <sil2100> hmmm, maybe it's something broken on my system?
[12:49] <sil2100> Since I'm doing what I was always doing
[12:50] <didrocks> nux is fine, no tag conflict
[12:50] <didrocks> let me try unity
[12:50] <didrocks> did you uncommit at some point?
[12:51] <sil2100> hm, in the past you mean?
[12:51] <didrocks> like, for the last release?
[12:52] <sil2100> hm, I don't remember :/ I don't think so though
[12:53] <didrocks> sil2100: ok, anyway, the history is good, let me "force" bzr for the tagging issue
[12:53] <sil2100> didrocks: sorry about that, whatever might have caused it :(
[12:53] <didrocks> sil2100: I have unfortunately no idea of what the actual cause is TBH :/
[12:54] <didrocks> maybe something in bzr in quantal
[12:54] <didrocks> ok, forced :)
[12:54] <didrocks> sil2100: on another note…
[12:54] <didrocks> nux broke its abi
[12:55] <didrocks> so, in the build-dep, you need to dep on latest nux as we are pushing everything at the same time
[12:55] <didrocks> (doing it now)
[12:55] <sil2100> Thank you!
[12:55] <didrocks> the abi system will then do the right think to dep on the right version :)
[12:55] <sil2100> Ok, need to attend a meeting now, brb
[13:02] <didrocks> mhr3: does u-l-a, u-l-f or u-l-m needs latest libunity API addition?
[13:03] <mhr3> didrocks, latest being?
[13:03] <mhr3> 94?
[13:04] <mhr3> but actually, no
[13:04]  * mhr3 remembers that the latest changes are only proposed so far
[13:07] <didrocks> mhr3: great, thanks :)
[13:11] <didrocks> sil2100: geis: the build-dep has been bumped in nux to 2.2.10
[13:11] <didrocks> think about doing a diff in configure.ac (again :p)
[13:15] <didrocks> sil2100: oh oh, and we ship the script for transitionning to gsettings
[13:15] <didrocks> sil2100: we shouldn't yet
[13:15] <didrocks> as compiz is not there
[13:17] <didrocks> so you have those changes shipped and not in the changelog as well
[13:22] <sil2100> didrocks: we ship it already? Wait ;)
[13:22]  * sil2100 didn't see it
[13:23] <didrocks> sil2100: yeah, you did
[13:23] <sil2100> didrocks: I don't see any script though
[13:23] <sil2100> didrocks: where is it?
[13:24] <didrocks> sil2100: you do have debian/unity.migrations in your branch, right?
[13:24] <didrocks> let me see, maybe me and some cruft around
[13:24] <sil2100> didrocks: but that's yours
[13:24] <didrocks> rev 750
[13:24] <didrocks> yeah, but it's your branch as well, right?
[13:24] <sil2100> bzr blame unity.migrations
[13:24] <sil2100> 736 didier. | tools/migration-scripts/01_unity_change_dconf_path
[13:25] <didrocks> indeed
[13:25] <didrocks> but it's in the branch you ship, right?
[13:25] <sil2100> Yes, but it was already in lp:ubuntu/unity
[13:25] <didrocks> yes because we were supposed to land the gsettings branch first
[13:25] <didrocks> which didn't happen
[13:25] <sil2100> Ah, shit ;)
[13:25] <didrocks> so we need to revert that
[13:25] <didrocks> no worry, doing it
[13:25] <didrocks> just to tell you: look at everything
[13:25] <didrocks> litterally, everthing :)
[13:25] <didrocks> everything*
[13:26] <didrocks> sil2100: speaking of migration
[13:26] <didrocks> sil2100: as you are not around next week
[13:26] <didrocks> sil2100: the script is in trunk, right?
[13:26] <didrocks> there is nothing you didn't add?
[13:26] <didrocks> (for both compiz and unity)
[13:28] <sil2100> didrocks: yes :)
[13:28] <sil2100> All seems merged in
[13:29] <didrocks> sil2100: excellent, thanks! I'll maybe add more keys due to the g-c-c keybindings migration, but good to know everything is good to go on your side
[13:29] <didrocks> sil2100: finishing with the lenses right now, the rest seems good :)
[13:30] <seb128> sil2100, hey
[13:31] <sil2100> didrocks: I'll double-check with Timo about gsettings in a moment
[13:31] <seb128> sil2100, do you plan to update dee? it was not listed on your ubuntu-release@ email
[13:31] <sil2100> didrocks: thanks!
[13:31] <sil2100> seb128: yes, I missed it in the mail :(
[13:31] <seb128> ok, no worry
[13:31] <seb128> I was just checking you did notice it
[13:33] <didrocks> sil2100: ok, all looks good here, after some dogfooding :)
[13:34] <didrocks> sil2100: I'll only upload on Monday though, still not found of Friday afternoon uploads, you can go on vacation with a light heart, well done!
[13:34] <didrocks> mhr3: FYI ^
[13:34] <didrocks> mmrazik: you can unfreeze the unity stack I guess :)
[13:35] <sil2100> didrocks: thank you! :)
[13:35] <mhr3> didrocks, cool
[13:36] <didrocks> sil2100: thanks to you :)
[13:36] <sil2100> didrocks: unfreezing then!
[13:37] <didrocks> sweet :)
[13:55] <jaytaoko> sil2100: didrocks: thanks for the release
[13:55] <didrocks> jaytaoko: yw ;)
[13:58] <sil2100> jaytaoko: yw - thanks for the help ;)
[14:28] <seb128> sil2100, didrocks: any reason to not upload to proposed? nobody should run proposed or those who do can only blame themself
[14:28] <seb128> speaking about unity 6.2, I saw the "will be uploaded on monday"
[14:29] <didrocks> seb128: not really, but I hope there will be no "copy to release in the wild"
[14:29] <didrocks> if you are confident, I can do it
[14:30] <seb128> didrocks, I'm confident, nobody is here during W.E and I will announce it in the release meeting
[14:30] <didrocks> ok, doing then
[14:32] <seb128> didrocks, thanks
[14:32] <seb128> BRING THE CRACK
[14:32] <seb128> sil2100, your phone number is in the directory right? and you have your phone with you at night, w.e and holidays?
[14:32]  * seb128 hides
[14:32] <didrocks> seb128: just for your pleasure!
[14:32] <sil2100> Erm...
[14:33]  * sil2100 throws away his phone through the window
[14:33] <sil2100> I have no phone
[14:33] <seb128> lol
[14:33] <sil2100> Sorry
[14:33] <sil2100> ;)
[14:34] <didrocks> seb128: I have his address!
[14:35] <sil2100> Need to run!
[14:36] <didrocks> sil2100: you won't run fast enough, why do you think I'm training everyday? :)
[14:43] <sil2100> I'm doomed!
[14:43] <sil2100> ;)
[14:57] <sil2100> mhr3: how busy are you? ;)
[14:58] <mhr3> sil2100, ehm, moderately busy? :)
[15:26] <didrocks> sil2100: you need to ensure that -proposed is added to the merger I guess
[15:27] <didrocks> sil2100: mmrazik and his team should do that, I don't remember if I added it back last time
[15:27] <didrocks> (as the packaging needs latest nux)
[15:28] <sil2100> didrocks: ok, will ping him about that
[15:28] <didrocks> thanks :)
[16:13] <nmarques> anyone can help me with a build issue (unity 6.2.0) ? (http://fpaste.org/tMI3/)
[16:30] <MCR1> bschaefer: Hi :) +1 for re-proposing and fixing conflicts for improve-keyboard-shortcut-overlay-wording.
[16:34] <MCR1> Does someone know why the Jenkins unity-automerger failed to merge so many branches ? The console output https://jenkins.qa.ubuntu.com/job/automerge-unity/1021/console does not really help, but I noticed that many other branches also failed to merge...
[16:51] <nmarques> is unity and nux ready for gcc47 ?
[16:54] <bschaefer> MCR1, you're welcome, and im not sure....I think it's being looked at
[16:55] <MCR1> bschaefer: thx
[16:56] <MCR1> nmarques: I am compiling on Quantal, so I guess the answer is yes
[16:58] <nmarques> MCR1, I'm having here a strange issue around, preventing me from building it
[16:59] <MCR1> nmarques: oh, maybe it is the same issue jenkins has ? I did not try lately - what is your error ?
[16:59] <nmarques> [   16s] CMake Error at CMakeLists.txt:178 (add_subdirectory):
[16:59] <nmarques> [   16s]   add_subdirectory called with incorrect number of arguments
[17:00] <nmarques> strangely somehow it inserts a line in CMakeLists.txt with: add_subdirectory()
[17:00] <nmarques> and it doesnt build :)
[17:00] <MCR1> nmarques: I will try to confírm, wait a minute.
[17:05] <MCR1> nmarques: nux compiled
[17:06] <nmarques> nux also builds here fine :)
[17:09] <MCR1> nmarques: test_launcher.cpp fails
[17:12] <nmarques> I'm not building the tests and documentation :)
[17:14] <MCR1> nmarques: maybe this is a good idea, but here now also BFBLauncherIcon.cpp fails :(, might be my cmake config though
[17:15] <nmarques> MCR1, mine doesn't even start to build :) it fails on the initial config fase
[17:15] <nmarques> http://fpaste.org/tMI3/
[17:16] <MCR1> http://pastebin.com/SZTgxgFD
[17:18] <bschaefer> nmarques, sorry, i haven't seen that error before...
[17:18] <bschaefer> MCR1, for that error you need libgeis
[17:18] <bschaefer> MCR1, and you need to autogen nux with this --enable-gestures
[17:18] <nmarques> bschaefer, CMakeLists.txt gets a 'add_subdirectory()'
[17:18] <MCR1> bschaefer: Ah, thx
[17:19] <nmarques> bschaefer, and it blows, maybe a missing dependency (though they all seem to be there)
[17:19] <bschaefer> nmarques, but I don't get that error, so saying its the make file is odd...
[17:19] <bschaefer> are you trying to build unity on fedora?
[17:20] <nmarques> opensuse
[17:20] <nmarques> :)
[17:21] <MCR1> bschaefer: Do I have to get libgeis from source and compile it also, or is libgeis-dev enough ?
[17:21] <bschaefer> nmarques, hmm well im not sure why you're getting that config error :(
[17:21] <bschaefer> MCR1, if you're on P then yes
[17:22] <bschaefer> P = 12.04
[17:22] <bschaefer> Q = 12.10
[17:22] <MCR1> Q
[17:22] <nmarques> bschaefer, do you know where is the log file from the config? I'm not fluent with cmake
[17:22] <nmarques> bschaefer, maybe the answer lies there :)
[17:22] <bschaefer> nmarques, im not really either :( sadly...
[17:22] <bschaefer> MCR1, yeah that should be good then
[17:22] <MCR1> nmarques: You could try cmake-gui, which is quite nice to configure options
[17:22] <nmarques> bschaefer, I think I found it ;)
[17:22] <nmarques> bschaefer, missing dependency, gtest
[17:22] <bschaefer> nmarques, awesome!
[17:23] <MCR1> bschaefer: thx again :)
[17:23] <bschaefer> MCR1, np!
[17:38] <MCR1> bschaefer: worked now.
[17:38] <bschaefer> MCR1, sweet
[18:06] <nmarques> bschaefer, it's building... but there's hardcoded paths for gtest in the makefile, uncool stuff :)
[18:07] <bschaefer> nmarques, :(, thats no good...if you make a bug report it should get looked at :)
[18:08] <niadh> hey
[18:08] <nmarques> bschaefer, it's commented out, so its something people are aware... (gtest)
[18:08] <nmarques> either way I've disabled the tests and kicked out gtest, hopefully no second effects :P
[18:08] <bschaefer> nmarques, oo alright, it must have been a work around :(
[18:08] <bschaefer> nmarques, you could just not built tests haha
[18:08] <bschaefer> nmarques, yeah! thats the way to do it :)
[18:09] <bschaefer> (there should be none! unless you want to run the gtest :) )
[18:09] <niadh> Hi all, I was looking into packaging Unity for Arch Linux, was wondering if I might be able to get some help here on how to do that?
[18:11] <niadh> I have started with the nux component, but it has various dependencies on utouch libraries some of which I can find, others I cant
[21:00] <MCR1> bschaefer: Still here ?
[21:02] <MCR1> Good news. I guess (hope) I fixed the first of the hardcoded Unity shortcut bugs.
[21:02] <MCR1> \o/
[21:09] <bschaefer> MCR1, yeah im around
[21:09] <bschaefer> cool, hmm what issue was it?
[21:09] <MCR1> bschaefer: It was multiple issues, one moment
[21:10] <MCR1> bug 1022743
[21:10] <ubot5`> Launchpad bug 1022743 in unity (Ubuntu) "Hardcoded Unity shortcuts create multiple Compiz problems" [Low,Confirmed] https://launchpad.net/bugs/1022743
[21:10]  * bschaefer looks
[21:11] <MCR1> the problem was that Unity takes over shortcuts, which Compiz already controls
[21:11] <bschaefer> MCR1, nice. I never noticed that as I usually keep my shortcuts default haha
[21:12] <bschaefer> MCR1, do you have a branch? If so we'll need some tests!
[21:12] <MCR1> maybe you noticed the I don't know comments in the branch you have worked on
[21:12] <MCR1> when you fixed the conflicts
[21:12] <MCR1> the improve wording one
[21:12] <bschaefer> yeah, I was just fixing the conflicts, I noticed some //FIXME conflicts blah blah
[21:13] <MCR1> yeah, somebody did an unfinished job there, haha
[21:13] <MCR1> which introduced bugs
[21:14] <MCR1> because both, Unity and Compiz were watching for those keys...
[21:14] <bschaefer> MCR1, does this just causes problem with the keyboard shortcut layout or actually causes usability issues?
[21:14] <MCR1> usabilty also - no possibility to change shortcuts for example
[21:14] <MCR1> if you change them they jump back currently
[21:14] <bschaefer> oo I should have looked at the code more....yeah. Im surprised it makes the shortcuts there...
[21:15] <MCR1> I guess it was not your fault
[21:15]  * bschaefer just thought it was a nice pretty window
[21:15] <MCR1> somebody was to lazy to search for all the Compiz equivalents, so they just got hardcoded
[21:15] <bschaefer> and that it was 'pulling' the shortcuts from compiz, and if not then it was just hardcoded
[21:15] <bschaefer> yeaah, well if you have a branch that would be an awesome fix :)
[21:16] <MCR1> sure, I am working on it, but it will ofc conflict with yours ;)
[21:16] <bschaefer> hmm yeah that stupid unity merger isn't working
[21:16] <MCR1> maybe I should continue the work on improve-wording ?
[21:17] <bschaefer> though I do like the unity merger it just seems to be always angry :(
[21:17] <MCR1> and make it improve-wording-and-shortcuts ;)
[21:17] <bschaefer> MCR1, you could do that and say its is a umm...
[21:17] <bschaefer> one sec I forgot the name...
[21:18] <bschaefer> MCR1, a Prerequisite Branch
[21:18] <MCR1> the bad thing is that this was the task for the weekend, and now I fixed it already - haha
[21:18] <bschaefer> when you do a merge proposal, and under extra options there is a Prerequisite Branch, put my branch under that so it has to be merged first before yours
[21:18] <bschaefer> haha
[21:19] <bschaefer> MCR1, no worries, I can take a look at it as well. It's only Friday 2pm here
[21:19] <MCR1> bschaefer: yes, I mistakenly used that once already... ;)
[21:19] <MCR1> USA ?
[21:19] <bschaefer> MCR1, yup
[21:19] <bschaefer> it gets lonely on Fridays around this time haha
[21:19] <MCR1> hehe
[21:22] <MCR1> ok, I'll start from your branch and re-fix and fix stuff there and then I submit the proposal with your branch as prerequisite, but it might take a while (I need a break now ;))
[21:23] <bschaefer> MCR1, no worries ping me when it's ready for a review :)
[21:23] <MCR1> ok, ql
[21:52] <cjohnston> me4oslav: ping
[22:14] <MCR1> bschaefer: Part One should be ready for review: https://code.launchpad.net/~mc-return/unity/unity.merge.fix-hardcoded-keys-part1/+merge/119204
[22:16] <bschaefer> MCR1, 32	+ hints.push_back(std::shared_ptr<shortcut::AbstractHint>(new shortcut::MockHint(_("Switching"), "", "", _("Move the focus."), shortcut::HARDCODED_OPTION, _("Left & Right"))));
[22:16] <bschaefer> what was done on that line?
[22:16] <bschaefer> i can't see a change haha
[22:16] <MCR1> bschaefer: foucs -> focus
[22:16] <MCR1> typo
[22:16] <bschaefer> MCR1, nice, im bad at finding those kind of typos haha
[22:17] <MCR1> I am good at those -> they hurt my eyes
[22:17] <bschaefer> MCR1, let me test it. Yeah I was staring at it intensively but still couldn't find it!
[22:18] <MCR1> bschaefer: Unfortunately some of the shortcuts need more investigation, while others, which are Unity-only, need additional options in the unityshell plug-in.
[22:18] <MCR1> bschaefer: Some simply ARE hardcoded, which is bad.
[22:19] <bschaefer> MCR1, yeah...hmm but at lease it's slowly getting fixed...idk why they were hard coded
[22:20] <MCR1> I think someone would have had to add additional code to the unityshell plug-in, but I have to investigate.
[22:20] <bschaefer> MCR1, hmm im still finding it hard to believe this is were shortcuts get generated though...cause im pretty sure events go X11 -> Compiz -> Unity or X11 -> Nux -> unity
[22:20] <MCR1> I think, that when you invent a new feature you do not think about the possibility of configuring it, you simply add the feature first and make it work with some default
[22:20] <bschaefer> yeah
[22:21] <bschaefer> well let me test this out!
[22:22] <bschaefer> cause unity overrides compiz events (which is also a bad workaround...)
[22:22] <bschaefer> sometimes
[22:22] <MCR1> bschaefer: I cannot test the fix at the moment, but it makes sense for me, hopefully it works, but imho it should - or things are more complicated than needed
[22:23] <bschaefer> MCR1, cause what I would think it does is use a Get...to Get the current shortcut so it can draw the correct one
[22:23] <bschaefer> not set it, but if it also Sets it then that would be a problem...haha
[22:24] <bschaefer> (also bad design if it Gets and Sets with 1 function call...)
[22:24] <MCR1> bschaefer: Can you test it ? I am a bit excited...
[22:24] <bschaefer> MCR1, yeah, i have to let it compile first :)
[22:24]  * bschaefer should have merged it to my unity branch...
[22:25] <MCR1> cool, thanks - I'll tell you in the meantime how to best test if it works...
[22:25] <bschaefer> either way though, you're branch is good. As it fixes hard coded problems
[22:26] <bschaefer> well im guessing to test it would be to change the shortcut option in CCSM with one of the ones you changed
[22:26] <MCR1> to test it go to CCSM->General Options->Key Bindings and change the "Window Menu" key to something else than <Alt>space
[22:27] <MCR1> bschaefer: yes, exactly - I just wanted to guide you along the way (many folks do not like CCSM it seems)
[22:27] <MCR1> :)
[22:27] <bschaefer> yeeah CCSM can cause 'problems'
[22:28] <bschaefer> MCR1, /home/bschaefer/src/unity.merge.fix-hardcoded-keys-part1/shortcuts/StandaloneShortcuts.cpp:77:202: error: expected ‘)’ before ‘;’ token
[22:28] <bschaefer> you forgot a ')' :)
[22:29] <MCR1> ups
[22:29] <MCR1> it is 0:29 here ;)
[22:29] <bschaefer> no problem, I did that when I was fixing the conflict on all of them haha
[22:29] <bschaefer> oo that is a bit late!
[22:30] <MCR1> I will fix it in the branch
[22:31] <bschaefer> MCR1, hmm I wonder if that was from my branch haha
[22:31] <bschaefer> it couldn't be though as it was compiling...
[22:31] <bschaefer> o well it's an easy fix :)
[22:31] <MCR1> no, I think it was my fault during copypaste
[22:32] <bschaefer> oo yeah, that'll happen. I don't like how we even generate all those shortcuts...
[22:32] <bschaefer> I want to get it into a header in a const structure...
[22:32] <MCR1> Compiz is great at shortcut handling imho
[22:33] <bschaefer> yeah, compiz does shortcuts well...I just don't like:
[22:33] <bschaefer> hints.push_back(std::shared_ptr<shortcut::AbstractHint>(new shortcut::MockHint(_("Menu Bar"), "", "", _("Reveals application menu."), shortcut::COMPIZ_KEY_OPTION, "unityshell", "show_hud")));
[22:33] <bschaefer> 50 times...
[22:33] <bschaefer> we should be able to loop over a structure that will do that haha
[22:33] <bschaefer> plus we have duplication in unityshell.cpp and that Standalone one...
[22:34] <MCR1> hehe
[22:34] <MCR1> yes the duplication is stupid
[22:34] <MCR1> pushed
[22:34] <bschaefer> MCR1, yeah. Hmm you're branch didn't seem to fix it :(
[22:34] <MCR1> noooooooooooooooooooo
[22:35] <bschaefer> MCR1, I think this is a problem somewhere else, possibly in compiz or in unity.xml thingy hmm
[22:35] <MCR1> then I have to dig further into the code - planned to find some time for that on the weekend...
[22:35] <MCR1> thanks a lot for testing - does it still jump back to Alt+Space ?
[22:35] <bschaefer> MCR1, you're branch is still good though. As we don't want that hardcoded stuff in there...
[22:35] <bschaefer> yeah
[22:35] <MCR1> grmmpf
[22:35] <bschaefer> so you're branch will still get merged :)
[22:36] <MCR1> but should be easy to find the problem... but not today
[22:36] <bschaefer> yeah haha
[22:36] <MCR1> ok, thx a lot for the help
[22:36] <bschaefer> MCR1, np! Go get some sleep :)
[22:36] <bschaefer> thanks for digging into that problem :)
[22:37] <MCR1> yeah, I guess we will fix for 12.10 ;)
[22:37] <MCR1> gn
[22:37] <bschaefer> yup. good night!