[02:06] <bregma> robert_ancell, your unity-session-compositor LightDM branch is working really well for me, but is there any way to configure environment variables to pass to unity-system-compositor before starting it?
[02:07] <robert_ancell> bregma, not that I can think of, what sort of variables?
[02:07] <bregma> ANDROID_ROOT in particular, used to find device configuration files (instead of /system)
[02:08] <robert_ancell> bregma, you can make a shell script for the compositor and set the name of that in lightdm.conf
[02:08] <robert_ancell> if that's something more permanent, we could look into options
[02:08] <bregma> yeah, that was my next plan, assuming even using device files will solve my problem
[02:09] <robert_ancell> I'm not sure off hand if the global env variables make it through to the compositor or we have a clean environment
[02:10] <bregma> well, it's probably a sort of last-resort solution anyway, since going that route woukld require shipping device configuration for pretty much every known device
[02:10] <bregma> but if that's what it takes....
[02:12] <robert_ancell> yeah, shell script time for you :)
[03:26] <robru> cyphermox, hey i installed urfkill... how will i know it's working? what steps should I take o test it?
[05:49] <pitti> Good morning
[06:16] <TheMuso> pitti: Thanks for chacing down that espeak issue. That really was a weird one.
[06:17] <TheMuso> Well... Working around the dpkg issue that is.
[06:25] <pitti> TheMuso: well, it's not dpkg, it's overlayfs/aufs
[06:25] <pitti> TheMuso: and I'm far from proud about that workaround, but I didn't find a better one
[08:02] <pitti> Laney: do you know what holds glib 2.38 back from unstable?
[09:02] <Laney> morning
[09:02] <Laney> pitti: the ftbfs
[09:02] <seb128> hey laney
[09:02] <seb128> good morning desktopers
[09:03] <Laney> hey seb128
[09:03] <Laney> how's it going?
[09:04] <pitti> bonjour seb128
[09:04] <pitti> hey Laney
[09:04] <Laney> hola
[09:04] <seb128> pitti, guten tag! wie gehts?
[09:04] <seb128> Laney, good! you?
[09:04] <pitti> Laney: ah, of course
[09:04] <Laney> bigon was looking at the build failures a bit but I don't think he got anywhere
[09:04] <pitti> seb128: gut, danke!
[09:05] <Laney> good thanks seb128!
[09:05] <Laney> pub quiz last night ;-)
[09:07] <Laney> seb128: seen https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1260473 ?
[09:07] <ubot2`> Launchpad bug 1260473 in Ubuntu Kylin "The slide bar that allow to rezise the partition does not appear" [Medium,Triaged]
[09:11] <seb128> Laney, now I did ... that seems similar to https://code.launchpad.net/~larsu/ubiquity/lp1260396
[09:11] <seb128> that fix landed right? (I didn't follow up, that was during my holidays, just saw it mentioned when looking to what happened while I was not there)
[09:12] <seb128> Laney, the mp got approved only on monday and we didn't have an ubiquity upload since
[09:12] <Laney> not sure that's the same
[09:13] <seb128> yeah, me neither
[09:14] <seb128> it would be good to land an update with the fix from Lars though
[09:15] <seb128> would it only be to avoid debugging something that's already fixed (if that turns out to be the same issue)
[09:15] <seb128> xnox, hey, do you plan to do an ubiquity update in trusty?
[09:22] <seb128> didrocks, hey, do you have any opinion on what integration tests we should have before merging https://code.launchpad.net/~diegosarmentero/ubuntu-system-settings/click-updates/+merge/195729 in?
[09:23] <seb128> didrocks, there is some pushback in recent comment saying it makes the review longer and should be in another merge later on, I'm just unsure that they are going to care once that one land so I'm tempted to ask for the branch with tests to be ready before we merge that one
[09:23] <didrocks> seb128: for system image update, it would be nice to use barry's mock and that the mock so that we ensure we receive the right signals
[09:23] <didrocks> seb128: well, if I were you, I would really bind the 2 merges (tests and code) together, otherwise, you know how it goes
[09:24] <seb128> didrocks, I guess they are going to argue that the system image is your code and that they didn't change/don't own it :p
[09:24] <seb128> right
[09:24] <didrocks> seb128: they did change it, right?
[09:24] <seb128> they changed the UI and refactored
[09:24] <didrocks> yeah, both the UI and backend
[09:25] <seb128> didrocks, well, it looks like they kept most of your updates.cpp, just did s/updates/systemupdate
[09:26] <seb128> in any case, let's me try to get them to add some more testing there
[09:26] <didrocks> seb128: there are some new objects retaining all states, not sure the signaling is still working
[09:26] <seb128> ok
[09:26] <didrocks> seb128: and yeah, you know how QML can be, when changing it :p
[09:36] <seb128> didrocks, so, can I try to land the u-s-s update we put in CI train yesterday or is the system down due to the canonistack issues?
[09:36] <didrocks> seb128: you can try, there are a lot of network issues
[09:37] <didrocks> so be prepare to run and rerun
[09:37] <seb128> didrocks, is #is looking at those?
[09:37] <didrocks> seb128: not sure, asked twice yesteday
[09:37] <didrocks> nothing happened
[09:37] <seb128> did you get anyone responding?
[09:37] <didrocks> in meeting…
[09:37] <didrocks> well, everyone using canonistack
[09:37] <didrocks> so yeah
[10:08] <xnox> seb128: after bug #1260473 is fixed, ubiquity will be uploaded.
[10:08] <ubot2`> Launchpad bug 1260473 in Ubuntu Kylin "The slide bar that allow to rezise the partition does not appear" [Medium,Triaged] https://launchpad.net/bugs/1260473
[10:08] <seb128> xnox, so it's a different issue than the one larsu fixed?
[10:08] <xnox> which also appears to be a gtk+ / themeing bug.
[10:08] <seb128> xnox, do you need help debugging it? is it easy to reproduce?
[10:09] <xnox> seb128: yeah, larsu's fixed is good. the installer is no 3X width the monitor screen.
[10:09] <xnox> seb128: well... we have a custom widget that is using deprecated gtkwidget themeing.... what could go wrong?! =)
[10:10]  * xnox needs to do a minimal example. As going from start to "dual-boot install" takes some time.
[10:13] <seb128> xnox, yeah, having a small example code would be nice
[10:23] <didrocks> seb128: ok, seems we are going to redeploy another instance in lcy01
[10:23] <didrocks> seb128: as I can't get any instance up on lcy02, it means I can't rsync the filesystem :/
[10:23] <didrocks> so, I'll have to rerun your build job with the same parameters
[10:24] <didrocks> (and reconfigure the silos)
[10:24] <didrocks> mind if I do that? So that you are unblocked ASAP
[10:25] <czajkowski> Laney: which train are you on to FOSDEM ?
[10:25] <Laney> 1532 or so
[10:25] <czajkowski> :(
[10:25] <seb128> didrocks, whatever unblocks the upload wfm
[10:25] <didrocks> seb128: ok ;)
[10:25] <Laney> y u sad
[10:25] <didrocks> asac: FYI, applying the band-aid version (I'll rerun the stuff for seb128 to not have to redo it himself) ^
[10:25] <seb128> didrocks, I've other changes to land today btw, not sure if we want to batch those or just redo a landing
[10:26] <czajkowski> Laney: I'm on the 12
[10:26] <ochosi> seb128: thanks for checking my merge-request on indicator-power and spotting the obvious whoopsie. anyway, i was also wondering whether this patch doesn't introduce problems for ubuntu-gnome, or are they not using indicators at all?
[10:26] <didrocks> seb128: as you prefer, we can do that, sure
[10:26] <Laney> czajkowski: the other uk-ers too?
[10:26] <czajkowski> yp about 10 going from our LUG
[10:26] <czajkowski> :D
[10:27] <czajkowski> Laney: stop by the NoSQL room on sunday will be there all day for a cupcake!
[10:27] <Laney> ^_^
[10:27] <mlankhorst> ;D
[10:29] <seb128> ochosi, yw, larsu said he's going to tweak it and land it I think
[10:29] <asac> didrocks: what is the bandaid version?
[10:30] <asac> is that the bandaid of the bandaid :P
[10:30] <seb128> ochosi, well, Ubuntu GNOME doesn't use indicators so they shouldn't be impacted by whatever the indicator code is doing
[10:30] <didrocks> asac: redeploying somewhere else and rerunning myself the job so that seb128 is in the same state
[10:30] <ochosi> seb128: ah, nice!
[10:30] <ochosi> seb128: ok, that's good to hear, cause i was afraid that the gnome-control-center call was for them...
[10:30] <asac> didrocks: yeah. unfortunate, but this exercise of redeploying etc. is probably worth it
[10:31] <asac> didrocks: how would the system behave if we just deploy it 2-3 times (e.g. on different regions)
[10:31] <asac> and the switch to whereever we get what we want?
[10:31] <seb128> ochosi, I think the g-c-c call was more "we didn't think much about the different usecase and let the old command as default"
[10:31] <didrocks> asac: not possible accross regions
[10:31] <didrocks> asac: the rules for having something quick were clear: one instance, one filesystem
[10:32] <asac> didrocks: sure, but we could have one spare?
[10:32] <didrocks> asac: well, you have to rsync the filesystem between the 2
[10:32]  * asac guesses that causs races etc.
[10:32] <didrocks> which isn't possible here
[10:32] <didrocks> as we even can't brought up an instance on lcy02 to attach to filesystem
[10:32] <ochosi> seb128: i see. well i'm sure ubuntu-studio will also be greatful for this getting in, as it'll make it very easy for them to also use -power if they want to, so thanks for the quick review!
[10:32] <seb128> ochosi, yw ;-)
[10:36] <ochosi> larsu: let me know if you want me to update the MR or if you're just going to throw the "gchar *path;" and "g_free (path);" into the Unity-if yourself
[10:37] <asac> didrocks: that is only if you dont want to risk loosing progress on active landings/silos?
[10:37] <asac> e.g. what will we loose if we redo the filesystem?
[10:37] <didrocks> asac: right
[10:37] <asac> ok thats fine
[10:37] <didrocks> all progress
[10:37] <didrocks> all silo attributions
[10:37] <asac> for a moment i was scared that we need to backup filesystem
[10:37] <larsu> ochosi: I'm doing it right now. Thanks!
[10:38] <didrocks> asac: and changing instance means changing some metadata on the spreadsheet, meaning if people keep IP directly, they won't work
[10:38] <asac> didrocks: the IP is recorded in the spreadsheet for the silo? what else?
[10:38] <didrocks> well, here, we need to have new public IP
[10:38] <asac> e.g. what else is instance specific
[10:39] <didrocks> and new firewall rules
[10:39] <didrocks> but that's only one time, we'll keep both opened then
[10:39] <asac> ok. we cant reassign the IP:)
[10:39] <asac> like elastic ips?
[10:39] <asac> maybe we have something like that?
[10:39] <asac> note: this is just theory talk so i understand better
[10:39] <didrocks> I don't think they have this notion accross instances
[10:42] <ochosi> larsu: ok, thank *you* in fact :)
[11:13] <Laney> bah
[11:13] <Laney> webkit ooming on the porterbox
[11:16] <seb128> Laney, well, does it mean that it went far enough that it should build?
[11:16] <Laney> not quite ...
[11:16] <seb128> :-(
[11:18] <Laney> -Wl,--reduce-memory-overheads HEAR MY CALL
[11:18] <mitya57> Didn't Debian fix the FTBFS on i386 recently?
[11:20] <Laney> I'm not looking at that
[11:21] <Laney> (ppc)
[11:21] <mitya57> Ah, yes, ppc
[11:22] <mitya57> Then I am waiting for your fix to apply it to qtwebkit :)
[11:22] <Laney> does that track webkit 2.3.x?
[11:23] <mitya57> 2.3 is webkitgtk numeration, not upstream one
[11:23] <Laney> you know what I mean
[11:24] <Laney> I'm trying something quite similar to http://pkgs.fedoraproject.org/cgit/webkitgtk3.git/tree/webkitgtk-1.11.5-libatomic.patch?id=2d4347bc2e76a07a8a0d6e8260730dfc91b0410e
[11:24] <mitya57> qtwebkit 5.2.0 is webkit 538.1, don't know about the gtk one
[11:25] <Laney> trying one more time with --reduce-memory-overheads
[11:25] <Laney> otherwise I'll just take the chance probably
[11:29] <didrocks> seb128: sil2100: can you check that you can login in and have enough rights on http://162.213.34.102/ ? (to run some jobs)
[11:31] <seb128> didrocks, what job can I try on?
[11:32] <didrocks> seb128: just check if you have the "build" button
[11:32] <seb128> didrocks, I don't
[11:32] <seb128> didrocks, on what job should I have one?
[11:32] <didrocks> hum
[11:32] <didrocks> everyone but deploy
[11:32] <seb128> I tried http://162.213.34.102/job/landing-001-1-build/
[11:32] <didrocks> and configure silo
[11:32] <didrocks> ok, let me check
[11:33] <didrocks> seb128: when you logged in, you have tick the teams you are in, right?
[11:33] <sil2100> hmm, I have some problems logging in
[11:33] <seb128> didrocks, yes, u-c-d
[11:33] <seb128> didrocks, but even without that, before I had a build button even when not logged in
[11:33] <seb128> clicking on the button would send me to the auth page
[11:33] <seb128> didrocks, http://ubuntuone.com/3X3SNx74hOelkX9J5kuZDE
[11:34] <didrocks> seb128: I don't see a build button here, you meant, you had one when not logged in?
[11:34] <sil2100> didrocks: do I have to create a new ubuntu one account here? Since it seems I cannot get my existing credentials to work
[11:35] <seb128> didrocks, yes, remember the discussion the other time? I had the "build" button even when not logged in before
[11:35] <didrocks> sil2100: yeah, it's using staging sso
[11:35] <seb128> didrocks, I first though it was a bug, but clicking on it was sending to a login page
[11:35] <didrocks> seb128: it's when you go to the build page directly
[11:35] <didrocks> (this isn't the build page)
[11:35] <seb128> oh
[11:35] <seb128> I got confused by jenkins UI again
[11:36] <seb128> well, anyway, I'm logged in and checked the u-c-d team (which was the only listed)
[11:36] <didrocks> ok
[11:36] <didrocks> let me check why
[11:36] <seb128> didrocks, is the canonical team supposed to be in the list?
[11:36] <didrocks> seb128: no, is it?
[11:36] <seb128> (it's not)
[11:36] <didrocks> ok ;)
[11:36] <didrocks> we can't
[11:36] <seb128> no, but I though it was before
[11:36] <didrocks> as we are not whitelisted
[11:36] <seb128> ok
[11:37] <didrocks> there was a canonica-ci
[11:37] <didrocks> canonical-ci*
[11:37]  * didrocks finished to resetup the rsync
[11:37] <didrocks> ok, now let's see those creds
[11:43] <didrocks> seb128: better now?
[11:44] <seb128> didrocks, yes
[11:44] <seb128> didrocks, http://ubuntuone.com/3X3SNx74hOelkX9J5kuZDE
[11:44] <seb128> ups
[11:44] <seb128> didrocks, http://162.213.34.102/job/landing-001-1-build/1/
[11:44] <seb128> "/tmp/hudson1182320129477473757.sh: line 5: cd: /var/lib/jenkins/silos/landing-001: No such file or directory"
[11:44] <seb128> didrocks, :-(
[11:44] <didrocks> seb128: yeah, I didn't assign you the silo yet
[11:45] <didrocks> and the firewall for rsync isn't opened by IS
[11:45] <didrocks> (as the IP changed)
[11:45] <didrocks> seb128: want me to attribute the silo so that you can build?
[11:45] <didrocks> or you want to add more components first?
[11:53] <didrocks> sil2100: in addition to seb128's right, you should be able to see the build button for deploy-jenkins
[11:54] <seb128> didrocks, let's attribute the silo, we can do another landing later
[11:56] <didrocks> ok :)
[11:56] <didrocks> launchpad authorization done
[11:56] <didrocks> let's attribute
[11:57] <didrocks> seb128: ok, you can try to run a build
[11:58] <didrocks> seb128: sil2100: I'm reverting to login.ubuntu instead of staging
[11:59] <sil2100> \o/
[12:00] <didrocks> sil2100: mind testing and so answering if the creds are fine?
[12:00]  * didrocks pushed his changes to prod
[12:00] <sil2100> didrocks: ok, so I'm logged in now and I had ubuntu-unity team in it
[12:00] <didrocks> sil2100: so, do you see the build button to the deploy-jenkibs job?
[12:01] <sil2100> didrocks: and I see build with parameters on landing-001-1-build
[12:01] <sil2100> didrocks: yes
[12:01] <didrocks> great!
[12:01] <sil2100> :)
[12:03] <didrocks> sil2100: can you try to reassign the second silo? would be a good exercise :)
[12:04] <didrocks> sil2100: only the jenkins job is needed, not the spreadsheet part
[12:04] <didrocks> asac: so, we're back on shape, I just rebuilt an instance and improved the install rules
[12:05] <didrocks> asac: just the status isn't synced back to the spreadsheet and we can't copy packages to distro until rsync from the new IP address is allowed
[12:05] <didrocks> asac: ev will work on that once he's back
[12:05] <seb128> didrocks, build running (sorry, was have lunch, I'm back now)
[12:05] <didrocks> seb128: let's look if it's starting fine
[12:05] <sil2100> didrocks: how can I do a reassign by using only jenkins? Which job to use?
[12:05] <seb128> didrocks, it is, it's installing packages
[12:06] <didrocks> seb128: sweet!
[12:06] <didrocks> sil2100: you have the link in the assign silo menu
[12:07]  * didrocks now praises that there is just one call to change to update all links :p
[12:07] <didrocks> seb128: great, uploaded to the ppa it seems
[12:08] <seb128> nice
[12:08] <didrocks> let's hope the gpg is rightly setup
[12:08] <didrocks> we'll see it soon :)
[12:08] <didrocks> seems it signed successfully at least
[12:08] <sil2100> didrocks: destination is Ubuntu archive, yes? ;)
[12:08] <didrocks> launchpadlib creds matches
[12:08] <didrocks> sil2100: yeah, so keep it empty
[12:09] <didrocks> seb128: https://launchpad.net/~ci-train-ppa-service/+archive/landing-001/+builds?build_state=building
[12:09] <sil2100> didrocks: reconfigure_silo set to landing-002 (just confirming if doing it irght)
[12:09] <didrocks> ok, now, I can work on what I planned at 10am :p
[12:09] <seb128> didrocks, great
[12:09] <didrocks> sil2100: you can try this ;) (it's a special case, as we don't really have a config file)
[12:09] <didrocks> sil2100: let's see ;)
[12:10] <didrocks> sil2100: if you don't set anything, it will take next available silo anyway
[12:10] <didrocks> which is landing-002 :p
[12:10] <sil2100> didrocks: oh noes... sil2100 is missing the Job/Build permission
[12:10] <sil2100> ;_;
[12:10] <didrocks> sil2100: hum… you checked ubuntu-unity, right?
[12:10] <didrocks> oh
[12:10] <didrocks> I redeployed all jobs
[12:10] <sil2100> Yes
[12:10] <didrocks> not that one
[12:10] <didrocks> uno momento
[12:11] <didrocks> sil2100: retry
[12:12] <sil2100> didrocks: yay, seems to work!
[12:12] <didrocks> great!
[12:12] <sil2100> Finished: SUCCESS
[12:12] <didrocks> sweet, all good then :)
[12:12] <asac> didrocks: ok thanks. i hope it takes not too long
[12:12] <sil2100> Assigned to landing-002
[12:12] <didrocks> asac: let's see…
[12:12] <sil2100> SO all is cool
[12:12] <didrocks> sil2100: thanks :)
[12:12] <didrocks> sil2100: back to landing -> did yu publish the keyboard?
[12:12] <sil2100> didrocks: thank *you* ;)
[12:13] <didrocks> (I don't see it in -changes)
[12:13] <sil2100> didrocks: yes, I pressed the button at least
[12:13] <didrocks> as I'll need that to update the seeds
[12:13] <didrocks> hum, and the artefacts were created?
[12:13] <sil2100> Let me check
[12:14] <didrocks> I have an idea what can happen
[12:14] <sil2100> http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Services/job/cu2d-services-head-3.0publish/127/console <- hum
[12:14] <sil2100> So not good...
[12:14] <didrocks> ok
[12:14] <didrocks> I guess the rsync on snakefruit doesn't happen
[12:14] <didrocks> as the script is set -e
[12:14] <didrocks> and now that the jenkins other node isn't reachable…
[12:16] <didrocks> sil2100: yeah, that was it, unblocked
[12:16] <didrocks> and added || true to first request
[12:16] <sil2100> didrocks: thanks ;)
[12:16] <didrocks> sil2100: yw! think about looking at -changes please :)
[12:16] <sil2100> didrocks: there is this as well -> https://code.launchpad.net/~sil2100/ubuntu-keyboard/some_packaging_changes/+merge/202654 (not top priority)
[12:17] <sil2100> didrocks: it's still not lintian-free, but well...
[12:17] <sil2100> didrocks: will do :)!
[12:17] <didrocks> sil2100: approved
[12:22] <didrocks> sil2100: I don't see hub and libcolumbus though
[12:48] <didrocks> seb128: hum, do you see deja-dup, wasn't it in g-c-c? (or visible in the dash)
[12:48] <didrocks> I may have remove the g-c-c plugin part, just checking
[12:49] <seb128> shrug
[12:49] <didrocks> hum, deja-dup binary package has the plugin normally
[12:49] <seb128> 3 person to ask the question this week :p
[12:49] <didrocks> ahah :)
[12:49] <seb128> didrocks, it's showing in unity-control-center and not gnome-control-center
[12:49] <seb128> mterry knows about it
[12:50] <seb128> (it's supposed to show in both)
[12:50] <seb128> we didn't switch defaults yet because everything didn't get transitionned for u-c-c
[12:50] <seb128> but that's ongoing work
[12:50] <didrocks> seb128: ok, as we are still shipping g-c-c by default… :p
[12:50] <didrocks> yeah
[12:50] <seb128> well, the intend was to have it in both
[12:50] <seb128> there is a bug, we discussed with mterry on monday
[12:50] <didrocks> I can see that as /usr/lib/x86_64-linux-gnu/control-center-1/panels/libdeja-dup.so
[12:50] <seb128> I guess he's going to fix it
[12:50] <didrocks> ok ;)
[12:51]  * didrocks install u-c-c
[12:51] <seb128> that's likely a key in the .desktop issue
[12:51] <seb128> you can run the standalone deja-dup UI otherwise
[12:51] <didrocks> probably, yeah
[12:51] <didrocks> I never know how to get the main panel
[12:51] <seb128> would give you an idea of how client side decoration don't work on Unity ;-)
[12:51] <didrocks> it's only restore or save
[12:52] <seb128> didrocks, run "deja-dup-preferences"?
[12:52] <didrocks> ah -preferences
[12:52] <didrocks> seb128: come on, there is a beautiful decoration there!
[12:53] <didrocks> invisible, but I'm sure, beautiful :)
[12:54] <seb128> ;-)
[13:33] <Laney> happyaron: are kylin doing some alpha 2 testing?
[14:04] <happyaron> Laney: I think they are mainly busy working on those third party cooperation projects
[14:21] <xnox> seb128: thanks for the new glade! so much better.
[14:22] <xnox> seb128: i'm however, loading ubiquity custom python widgets catalog, and it appears to be marking one of my widgets as "deprecated" (but no other), not sure why
[14:26] <seb128> xnox, yw!
[14:27] <seb128> I don't know about the deprecation either
[14:29] <Laney> happyaron: would be good to have some if there's to be a release
[14:45] <seb128> Laney, hum, would it make sense to override the fileselector setting in ubuntu-settings rather than in the gtk source?
[14:46] <Laney> hmm
[14:47] <seb128> Laney, that's where we moved the Ubuntu overrides for other sources, it makes easier for other flavors to make different decisions than us
[14:48] <seb128> to take*
[14:48] <seb128> on that note, I'm away for some exercice, be back in ~1h
[14:48] <Laney> I was thinking of it as a "gtk" choice rather than an "ubuntu desktop" one
[14:48] <Laney> don't really mind
[14:50] <seb128> Laney, that works for me, especially if we patch gtk2 we sort of enforce that as a gtk choice
[14:50] <seb128> or we would just give others the flexibility to make gtk2/3 softwares inconsistant
[15:02] <tedg> seb128, Looking at your comment: https://code.launchpad.net/~robert-ancell/indicator-power/ucc-only-in-unity/+merge/202559/comments/472287
[15:03] <tedg> seb128, What do you think we should be checking?  I thought we only wanted u-c-c for Unity so that GNOME could be "vanilla"?
[15:03] <mdeslaur> seb128: for some reason, I'm getting a race at boot with trusty where gnome-keyring doesn't end up as the ssh agent...have you seen that?
[15:03] <mdeslaur> about half the time
[15:10] <happyaron> Laney: I see, will check with our PM how to talk about it with them.
[15:10] <Laney> mdeslaur: I think it races with the upstart job
[15:10] <Laney> happyaron: cool, thanks
[15:11] <happyaron> :)
[15:14] <mdeslaur> Laney: hrm, ok, I'll file a bug. thanks
[15:35] <seb128> mdeslaur, what Laney said, and yes sometime the agent is not working for me either (wrong env, because if I run gnome-keyring-daemon and export the env it prints things works)
[15:36] <mdeslaur> seb128: I filed 1271591
[15:36] <seb128> tedg, right, GNOME doesn't use indicators (there is no way to use them under gnome-shell and the UI wouldn't fit the shell anyway)
[15:37] <tedg> seb128, So what's the issue of checking for the Unity desktop?
[15:37] <seb128> tedg, GNOME is going to be vanilla by not using indicator and using g-c-c
[15:37] <seb128> tedg, xfce use indicators, gnome-panel session use indicators
[15:37] <tedg> I'm more worried about folks like Xubuntu
[15:38] <tedg> Don't they want g-c-c ?
[15:38] <seb128> tedg, did you see https://code.launchpad.net/~larsu/indicator-power/xfce-control-center/+merge/202641
[15:38] <seb128> tedg, I think those desktops want, in priority order, their-own-tool, u-c-c, g-c-c
[15:39] <tedg> seb128, Oh, okay, I thought they'd want g-c-c before u-c-c.
[15:39] <seb128> tedg, g-c-c is not going to include indicator settings, so better to call u-c-c which does
[15:39] <seb128> tedg, I'm also unsure that stuff like CSD is going to work well on those desktops
[15:39] <tedg> Seems weird that the behavior could change based on what is installed though.
[15:39] <seb128> tedg, I think they are closer from Unity than from shell
[15:40] <tedg> i.e. if you had Xubuntu and Ubuntu Desktop you'd get one, but not if you didn't.
[15:40] <seb128> you mean?
[15:40] <seb128> xfce would always have their own tool called
[15:40] <seb128> Ubuntu Desktop installed or not
[15:40] <tedg> I guess Xubuntu is a bad example as they have their own.  But just saying because we're checking for the existence of the utility, we could behave differently.
[15:41] <tedg> Seems we should decide and error.
[15:41] <seb128> I would be fine with that
[15:41] <seb128> I don't care enough to spend time on it though
[15:41] <seb128> if somebody files a bug or some other desktops have concerns they can file a bug/send a patch
[15:41] <tedg> Is there any reason an indicator would want to call g-c-c?
[15:42] <seb128> better than erroring out I guess?
[15:42] <seb128> but yeah, at this point g-c-c seems a random choice
[15:42] <seb128> we could as well call kdeconfig
[15:42] <tedg> Yeah
[15:42] <seb128> we should maybe just hide the entry if u-c-c is not installed
[15:43] <seb128> though having the g-c-c case makes it easier for e.g Debian to keep packaging indicators
[15:43] <seb128> or at least having them working as designed
[15:44] <tedg> It also makes the migration story easier.
[15:44] <seb128> tedg, I think we should claim the current code as good enough and not spend more effort on it until somebody comes with a valid concern/bug/reason to change
[15:44] <tedg> So my thought is: keep the patches like they are today.  But when we get to a stable point we can start dropping g-c-c.
[15:44] <seb128> +1
[15:45] <tedg> K, will review as such.
[15:45] <seb128> thanks
[15:47] <xnox> seb128: my custom do_draw() is borked. All it does is request the current split between pack1 & pack2 of a Gtk.Paned widget and updates labels appropriately with the split.
[15:47] <xnox> seb128: upon resizing, does Gtk.Paned emit any singnal that I can key on?
[15:48] <seb128> xnox, do you have code to share/a small testcase showing what you do/the issue?
[15:48] <xnox> seb128: yeah, one sec.
[16:04] <xnox> seb128: awwwwww!
[16:04] <seb128> xnox, works now or what?
[16:04] <xnox> seb128: so my do_draw() method ( a derived / subclassed Gtk.Paned)
[16:05] <xnox> seb128: did not have "Gtk.Paned.do_draw(self, cr)" as first thing
[16:05] <xnox> seb128: so nothing was drawn!
[16:05] <xnox> seb128: now it all works!
[16:05] <seb128> great!
[16:15] <xnox> seb128: do you know if I can increase the corner radius of the ShadowType.ETCHED_IN ?
[16:15] <xnox> of a Gtk.Frame
[16:16] <xnox> seb128: \o/ OMG, migrating away from HPaned to Paned, made that custom widget render in the new glade! #firstinhistory
[16:20] <seb128> haha
[16:20] <seb128> dunno for the corner
[16:20] <seb128> but larsu might
[16:20] <seb128> or Cimi
[16:21] <Cimi> xnox, it's static IIRC
[16:21] <xnox> Cimi: fair enough =) it looks miles better now, so it's all good.
[16:21] <Cimi> xnox, because at that time there were child windows and we couldn't play much with those
[16:21] <Laney> pix
[16:22] <xnox> Laney: we are not past UIF yet, are we?! =)
[16:23] <Laney> depends on whether you're going to give me chocolate / beer as a bribe :-)
[16:23] <seb128> what do I need to do to get chocolate / beer as well? ;-)
[16:26] <Laney> I'm after ui-toolkit in trusty with the listview emulator
[16:26] <Laney> will share my chocolate with you if you do that :P
[16:26] <seb128> hum
[16:26] <seb128> not sure I'm that hungry in fact :p
[16:26] <seb128> but it reminds me I wanted to test your autopilot fixes branch
[16:26]  * seb128 goes to do that
[16:26] <Laney> om nom nom
[16:26] <seb128> ;-)
[16:33] <xnox> Laney: sbuild-build-depends-ubiquity-dummy : Depends: gir1.2-webkit-3.0 but it is not going to be installed
[16:34] <xnox> Laney: how can I build a ubiquity update?! =)
[16:34] <Laney> there's skew atm
[16:34] <seb128> you might want to delete the proposed version
[16:34] <seb128> to unblock ubiquity
[16:34] <Laney> do it
[16:34] <seb128> where is my chocolate? ;-)
[16:35] <Laney> xnox has it
[16:35] <Laney> it's posh belgian stuff
[16:36] <ogra_> i thought she is english
[16:36] <xnox> Laney: i'm still pondering about going to Fosdem to replenish my backup stores.
[16:36] <xnox> ogra_: posh - adj, not Posh - name.
[16:36] <Laney> neat, see you there
[16:36] <ogra_> :)
[16:36] <Laney> everyone's going
[16:37] <xnox> Laney: hm. I have a volleyball match on sunday =/
[16:37] <xnox> Laney: yeah, FTBFS on i386 is not good =)
[16:37] <Laney> heh
[16:37] <Laney> trying to get a ppc fix before uploading
[16:38] <Laney> speaking of which
[16:38] <Laney> collect2: error: ld terminated with signal 9 [Killed]
[16:41] <seb128> Laney, xnox: deleted from proposed, that should unblock other things until Laney uploads a version that builds
[16:41] <Laney> ta
[16:41] <xnox> seb128: thanks!
[16:41] <seb128> yw!
[17:17] <Laney> aha, I think it got past the failing stage
[17:23] <Laney> yup
[18:26] <seb128> sil2100, hey, can you give me a landing slot for ubuntu-system-settings? (l10 on the CI train list)
[18:29] <sil2100> seb128: sure! (I think ;p) Let me take a look, will be my first real time
[18:32] <sil2100> seb128: hmmm
[18:33] <sil2100> seb128: there seems to be a problem, as the previous request still didn't get cleaned up
[18:33] <sil2100> seb128: landing from l7 is still in state 'Cleaning silo', and it's blocking further ubuntu-system-settings landings
[18:33] <sil2100> didrocks: ^
[18:34] <seb128> sil2100, try again, it just finished cleaning it ;-)
[18:34] <sil2100> didrocks: how long does it usually take to clean up a silo ?
[18:34] <sil2100> Ah!
[18:34] <sil2100> Ok ;)
[18:34] <sil2100> didrocks: nevermind!
[18:34] <seb128> didrocks, sil2100: btw I saw it was still running, but that was making a good test of that scenario
[18:34] <seb128> sil2100, http://162.213.34.102/job/landing-001-3-merge-clean/1/console
[18:34] <sil2100> \o/
[18:34] <seb128> sil2100,  seems like the ppa took ~10 min from the delete request to be empty
[18:36] <sil2100> seb128: indeed - ok, assigning silo now
[18:36] <seb128> sil2100, thanks
[18:37] <sil2100> hmmm
[18:38] <sil2100> didrocks, seb128: I'm trying to press the 'Submit' button to assign a silo, but it does not work sadly?
[18:38] <didrocks> sil2100: hum
[18:38] <didrocks> sil2100: the job or the spreadsheet?
[18:39] <sil2100> didrocks: on the spreadsheet
[18:39] <didrocks> have you set the silo naming?
[18:39] <sil2100> didrocks: the jenkins job was ok, but now when I selected the silo it doesn't work
[18:39] <sil2100> I set landing-001 there
[18:39] <didrocks> which silo was assigned?
[18:39] <didrocks> ok
[18:40] <didrocks> sil2100: worked here
[18:40] <sil2100> didrocks: does it have some permissions on submit, or would the script not start even if I wouldn't have the permissions?
[18:41] <didrocks> sil2100: not sure, we need to look together, you should have all needed permissions
[18:42] <sil2100> didrocks: let's look at it tomorrow, not to waste your time anymore for today :)
[18:43] <didrocks> yeah, finishing a hangout and done
[18:43] <jasoncwarner> hey seb128 or laney (or anyone). I seem to have a broken package on upgrade. gyp? anyone know anything about that? seems to be broken for a few days now.
[18:43] <seb128> not know no, which one?
[18:43] <seb128> "gyp" is that the name?
[18:44] <jasoncwarner> seb128: yeah.
[18:44] <seb128> https://bugs.launchpad.net/ubuntu/+source/gyp/+bug/1246730 ?
[18:44] <ubot2`> Launchpad bug 1246730 in gyp (Ubuntu) "dependency_links.txt.dpkg-new': No such file or directory" [Undecided,Confirmed]
[18:45] <jasoncwarner> seb128: that's teh one
[18:45] <seb128> hum
[18:45] <seb128> that's a build tool from the chromium stack it seems, first time I read about it
[18:46] <seb128> qengho, ^ do you know about that source or bug?
[18:46] <qengho> Generate your Project.  Yes, I know of it.
[18:46] <seb128> jasoncwarner, you are building your own chromium packages then? ;-)
[18:46] <jasoncwarner> seb128: didn't think I was ;)
[18:46] <jasoncwarner> seb128: though, I might have installed something along the way. perhaps I have a ppa (checking)
[18:47] <seb128> jasoncwarner, you can probably safely uninstall that package then, still a bug that should be fixed though ... but an universe one
[18:47] <qengho> jasoncwarner, seb128, I don't think we got it from chromium, though.  Even an old one.
[18:47] <seb128> qengho, I'm just saying that because it has "maintainer: Debian Chromium Maintainers"
[18:48] <jasoncwarner> ah, it seems it is probably nodejs
[18:48] <jasoncwarner> when I go to uninstall it, all my node modules get uninstalled
[18:48] <seb128> oh, ok
[18:48] <qengho> seb128: I think GYP is one of those projects that was split off to be standalone, but few other projects took it up.
[18:48] <seb128> seems so
[18:48] <qengho> Nodejs isn't small, though.  That's nice.
[18:52] <jasoncwarner> I removed nodejs for now. not like I have time to work on that project anyway atm ;)
[20:07] <robert_ancell> tedg, are you OK with https://code.launchpad.net/~robert-ancell/indicator-power/ucc-only-in-unity/+merge/202559 being rejected? It means indicator-power runs u-c-c if it is installed, where the other indicators only do that if in Unity. I don't think it's a problem in practise but just inconsistent with the changes you requested
[20:08] <robert_ancell> seb128, ^ if still online
[20:08] <tedg> robert_ancell, Yeah, so seb128 and I had a conversation about it.  Long term we're just not going to call g-c-c at all.
[20:08] <robert_ancell> yep
[20:08] <tedg> robert_ancell, But for the migration and everything else, we're being simple.
[20:08] <tedg> i.e. not worth another round of back-and-forth
[20:08] <seb128> robert_ancell, hey
[20:08] <robert_ancell> ack
[20:09] <seb128> robert_ancell, do you look at the commit I pointed?
[20:09] <robert_ancell> yes
[20:12] <seb128> what's wrong with it?
[20:13] <seb128> robert_ancell, what do you want changed compared to the code that got commited?
[20:14] <robert_ancell> seb128, all the indicators have a g_strcmp0 (g_getenv ("XDG_CURRENT_DESKTOP"), "Unity") == 0 (on tedgs request) except for indicator-power
[20:14] <robert_ancell> but it's not that important
[20:14] <robert_ancell> so running the indicators say from lxde will bring up g-c-c for everything except indicator-power which will bring up u-c-c
[20:14] <seb128> robert_ancell, right, that's from the time where GNOME was gnome-panel and using indicators, I don't think that makes sense anymore with GNOME = gnome-shell and not using indicators
[20:15] <robert_ancell> yeah, it all goes away if we don't support g-c-c anymore
[20:15] <seb128> robert_ancell, I would argue that other indicators should favor u-c-c over g-c-c as well (that's basically what I did today for -power and why we landed that code)
[20:15] <seb128> g-c-c doesn't have indicator options to start with
[20:15] <robert_ancell> that was my original branches :)
[20:16] <seb128> you were right then ;-)
[20:16] <seb128> we just didn't have discussions about the topic before
[20:16] <seb128> and reviews are probably not the best venue to decide on such changes
[20:17] <robert_ancell> anyways, when do these new versions hit the archive?
[20:18] <robert_ancell> tedg, you can treat utf-8 as ASCII. Since all multibyte characters have the first bit set to 1 you will never get a valid ascii character in a multibyte sequence
[20:18] <robert_ancell> utf-8 is surprisingly clever
[20:18] <seb128> robert_ancell, I'm going to do a landing ask tomorrow, I already talked to didrocks about it todauy
[20:18] <tedg> Ha, I didn't realize.
[20:21] <seb128> robert_ancell, btw, for some reason the unity/compiz keybinding are not showing in the keyboard section of u-c-c, do we need to make compiz install its .xml in a new location?
[20:21] <seb128> e.g the hud key is not there
[20:21] <seb128> but other sections are missing as well
[20:21] <robert_ancell> seb128, oh, I hadn't noticed that
[20:21] <robert_ancell> is there a bug open?
[20:22] <seb128> robert_ancell, no, I just noticed today, I can open one if you want
[20:22] <robert_ancell> please do
[20:22] <robert_ancell> yeah, looks like it needs to
[20:22] <robert_ancell> /usr/share/gnome-control-center/keybindings - move/copy to /usr/share/unity-control-center/keybindings
[20:23] <seb128> shrug
[20:24] <seb128> robert_ancell, I don't know why you insist on migrating those locations ;-)
[20:24] <seb128> robert_ancell, https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1271710
[20:24] <ubot2`> Launchpad bug 1271710 in unity-control-center (Ubuntu) "doesn't list compiz/unity keybindings" [Undecided,New]
[20:24] <robert_ancell> seb128, because we're not g-c-c anymore and who knows what changes will come in new versions of g-c-c
[20:25] <seb128> robert_ancell, we are going to need landing of compiz and unity to complete that migration then, let's see how many weeks that takes
[20:25] <seb128> :/
[20:25] <robert_ancell> we need to sort that out
[20:25] <robert_ancell> our velocity has got even slower
[20:26] <seb128> indeed
[20:26] <seb128> well, the landing team is really focussed on touch
[20:26] <robert_ancell> seb128, did you see I uploaded that nautilus patch
[20:26] <seb128> yes
[20:26] <seb128> thanks for that
[20:26] <seb128> did you code review it or just went "oh, it builds, it seems to work, let's upload"?
[20:27] <robert_ancell> I reviewed it, but not in depth. It seems independent enough that we can maintain it into newer versions
[20:27] <seb128> I was sort of going to do that and figured out I would try to ping you in case you had the motivation to do a proper review ;-)
[20:27] <seb128> we already received a bug report about it btw
[20:27] <robert_ancell> it does logical stuff
[20:27] <seb128> the guy who wrote the patch is going to look at it
[20:27] <robert_ancell> yeah, he seems onto it
[20:28] <seb128> Sweetshark, https://launchpadlibrarian.net/163120675/buildlog_ubuntu-trusty-powerpc.libreoffice_1%3A4.2.0~rc2-0ubuntu1_FAILEDTOBUILD.txt.gzhttps://launchpadlibrarian.net/163120675/buildlog_ubuntu-trusty-powerpc.libreoffice_1%3A4.2.0~rc2-0ubuntu1_FAILEDTOBUILD.txt.gz :-(
[20:29] <seb128> shrug, sorry for the double copy, firefox was hanging while loading the page and I though it didn't get the copy
[20:29] <seb128> https://launchpadlibrarian.net/163120675/buildlog_ubuntu-trusty-powerpc.libreoffice_1%3A4.2.0~rc2-0ubuntu1_FAILEDTOBUILD.txt.gzhttps://launchpadlibrarian.net/163120675/buildlog_ubuntu-trusty-powerpc.libreoffice_1%3A4.2.0~rc2-0ubuntu1_FAILEDTOBUILD.txt.gz
[20:29] <seb128> https://launchpadlibrarian.net/163120675/buildlog_ubuntu-trusty-powerpc.libreoffice_1%3A4.2.0~rc2-0ubuntu1_FAILEDTOBUILD.txt.gz
[20:29] <seb128> (grrrr)
[20:29] <seb128> robert_ancell, you are going to be in London, right?
[20:29] <robert_ancell> seb128, yep
[20:29] <seb128> great
[20:30] <seb128> I hope we can finish those transitions there
[20:30] <seb128> robert_ancell, do you need help from me before that?
[20:30] <robert_ancell> seb128, just help to keep things moving
[20:30] <robert_ancell> i.e. annoying people until they take the changes / get them into the archive :)
[20:31] <robert_ancell> and finding any bugs
[20:31] <seb128> right, I'm on that already
[20:31] <seb128> how is u-s-s going?
[20:31] <seb128> btw, are you bored/looking for things to do? ;-)
[20:33] <robert_ancell> ha, I wish
[20:33] <seb128> :-(
[20:33] <robert_ancell> I'm leaving u-s-s until u-c-c is out of the way
[20:33] <robert_ancell> Don't want to land both at once
[20:33] <seb128> you are still fulltime on u-c-c?
[20:33]  * seb128 has work for you :p
[20:34]  * robert_ancell hides
[20:34] <robert_ancell> doing lightdm stuff and general fixing
[20:34] <robert_ancell> sure, propose it to me
[20:34] <robert_ancell> I want to hear a great sell
[20:34] <seb128> robert_ancell, joke aside I think most of our changes for the LTS are going to be done after u-c-c/u-s-d
[20:35] <seb128> robert_ancell, it's an old sell, but I think you did some work on gnome-screensaver some cycles ago to give it an unity-greeter like UI (or at least a less-win-95-like-UI)
[20:35] <seb128> do you still have that somewhere?
[20:35] <robert_ancell> yeah, somewhere
[20:35] <robert_ancell> I can do some work there
[20:36] <robert_ancell> it will be hacky, but I guess it's better than nothing
[20:37] <seb128> how much work would it be to bring it back? ;-)
[20:37] <seb128> that would be nice
[20:37] <seb128> thanks
[20:38] <seb128> yeah
[20:38] <seb128> in fact I don't even care much if it's the same as the login screen (that would be nice though)
[20:38] <robert_ancell> seb128, do you know if it needs to be conditional on running in Unity, i.e. is anyone else still using gnome-screensaver?
[20:38] <seb128> but at least something which is not that grey rectangle
[20:38] <seb128> I wouldn't bother
[20:39] <robert_ancell> we'll see if anyone shouts
[20:39] <seb128> gnome-shell doesn't use gnome-screensaver
[20:39] <seb128> and xfce went for light-locker
[20:39] <seb128> yeah
[20:39] <seb128> if anyone complains we can rename "fork" gnome-screensaver as well :p
[20:39] <seb128> that one would be an easy rename
[21:17] <TheMuso> pitti: Fair enough, thanks again.
[21:58] <seb128> shrug, why is dch setting my distro serie to "the"?!
[21:58] <kenvandine> seb128, cool... "the"
[21:58] <kenvandine> it starts with a T
[21:58] <kenvandine> :-D
[21:58] <Laney> The next release
[21:59] <seb128> kenvandine, did you hack into my computer? ;-)
[21:59] <kenvandine> yup :)
[21:59] <seb128> damnit!
[21:59] <Laney> panel still uses gnome-screensaver
[21:59] <Laney> fallback
[21:59] <seb128> Laney, what greeter do they use?
[21:59] <Laney> and random people might, of course
[21:59] <seb128> well
[22:00] <seb128> the question is "would they be annoyed if the lock screen was looking unity-greeter like, rather than win95 like"
[22:00] <seb128> ?
[22:00] <Laney> I think it'd be good for it to look better
[22:00] <Laney> but "nobody other than us uses this" isn't a good metric to make decisions on
[22:00] <kenvandine> you know someone will complain
[22:00]  * Laney wouldn't mind
[22:00] <kenvandine> the only thing worse is xscreensave
[22:00] <kenvandine> +r
[22:01] <seb128> well, it's rather "is anyone attached to the current look"?
[22:01] <seb128> I would think not
[22:01] <seb128> but you never know
[22:01] <kenvandine> fork it!
[22:01]  * kenvandine ducks
[22:01] <seb128> lol
[22:01] <Laney> heh
[22:01] <seb128> kenvandine, read the backlog, I suggested it ;o
[22:01] <Laney> I'd change it and then see who complains
[22:01] <seb128> right
[22:01] <kenvandine> feeling a little punchy after a couple hours debugging the keyboard
[22:01] <kenvandine> ha... you did :)
[22:01] <seb128> that's what are going to do I think
[22:01] <Laney> I doubt a fork is required as it'd probably be easy to have both looks if necessary
[22:02] <seb128> well, fork might be better than a stack of if statements in the code
[22:02] <Laney> shrug
[22:02] <seb128> but let's see if anyone complains first
[22:02] <seb128> well, first let's refresh the UI
[22:02] <seb128> then let's see if anyone complains
[22:03] <seb128> if they do, then let's decide on what to do ;-)
[22:03] <seb128> soooo
[22:03] <seb128> where is dch getting the current distro serie from?
[22:03] <seb128> is anyone else getting "the" on "dch -r"?
[22:03] <seb128> kenvandine, WHAT DID YOU DO
[22:04]  * kenvandine tries
[22:04] <Laney> there's a mode where it copies the previous one
[22:04] <kenvandine> nope... i'm getting trusty
[22:04] <seb128> I'm not using any mode
[22:04] <seb128> or said differently, I've no custom config
[22:04] <seb128> shrug
[22:05] <Laney> well... is it getting it from the previous entry?
[22:05] <seb128> I doubt it, just got that on 6 different sources
[22:06] <Laney> otherwise I think it gets it from distro-info
[22:06] <Laney> ubuntu-distro-info --devel --codename
[22:07] <seb128> $ distro-info --devel --codename
[22:07] <seb128> trusty
[22:07] <Laney> outta ideas
[22:08] <seb128> shrug
[22:08] <Laney> now you get to use the source :P
[22:08] <seb128> so in fact my issue is
[22:08] <seb128> $ dch -i "Rebuild for the new poppler soname"
[22:08] <seb128> $ dch -r
[22:08] <seb128> it has to do with the dch -i message
[22:08] <seb128> wth?
[22:09] <seb128> if I "dch -i "Rebuild"" it works
[22:09] <Laney> oh yeah, I see that
[22:09] <Laney> that's funny
[22:09] <Laney> I always do dch -D trusty -r "" so I'd never see that
[22:10] <seb128> I usually do it in those steps for the vcs commits
[22:10] <seb128> you get the commit with the change
[22:10] <seb128> then the release one
[22:11] <seb128> but wth is wrong with that changelog entry?
[22:12] <Laney> bug
[22:12] <Laney> debug it!
[22:13] <seb128> :-(
[22:13] <seb128> that doesn't seem like the sort of bug I'm wanting to debug
[22:13] <seb128> that seems like a bug infinity would enjoy :p
[22:13] <seb128> or slangasek
[22:15] <seb128> ok, let me open a bug and assign it to kenvandine
[22:16] <seb128> he mentioned earlier that he has something to do with that issue
[22:16] <seb128> ;-)
[22:16] <seb128> kenvandine, debugging dch should be good for you, that's going to be a change of all the touch work
[22:17] <seb128> of->from
[22:38] <Sweetshark> seb128: *urgh*
[22:38] <seb128> Sweetshark, indeed... :/
[22:39] <seb128> cyphermox, hey, did you see https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1197854 ?
[22:39] <ubot2`> Launchpad bug 1197854 in network-manager (Ubuntu) "NetworkManager crashed with SIGABRT in g_assertion_message()" [High,Confirmed]
[22:39] <cyphermox> I did
[22:39] <seb128> ok, you never commented/acted on it, so I'm checking
[22:39] <cyphermox> yeah
[22:39] <cyphermox> I think it's already been applied though
[22:39] <seb128> it seems a simple commit, can we get it in trusty?
[22:39] <cyphermox> yeah
[22:40] <seb128> thanks
[22:40] <cyphermox> we'll get it via 0.9.8.8 on friday though
[22:40] <cyphermox> I'm updating NM and MM
[22:40] <seb128> ok, good
[22:41] <seb128> (you are right, looking to the current source it seems the source has it)
[22:43] <Sweetshark> seb128: so the good thing is that it is a casting error in a function called 'convertLittleEndian', so a/ it will likely only fail on PPC and b/ its at least a decent hint of what is going wrong (unlike e.g. stumbling over itself somehow) ...
[22:52] <seb128> Sweetshark, "good" I guess, still not debugging/work/another upload :/
[22:54] <Sweetshark> seb128: yup
[22:54] <seb128> not->need
[22:55] <Sweetshark> seb128: git blame suggests I might was just out at a bar with the guy who broke it ;)
[22:55] <seb128> Sweetshark, well, the good news is that the l10n package built :-)
[22:55] <seb128> haha
[22:56] <seb128> you just missed an opportunity to bribe him in fixing it then!
[22:59] <seb128> on that note, enough for today, night everyone