[08:33] <thostr_> sil2100: can you give me a silo for line 39?
[08:42] <sil2100> thostr_: one moment ;)
[08:44] <sil2100> Good thing that the spreadsheet seems in a better state today
[08:44] <sil2100> thostr_: done
[08:48] <sil2100> didrocks: morning! Do you have a moment for some packaging ACKs?
[08:48] <sil2100> didrocks: these are for the unity7 stack
[08:51] <didrocks> sil2100: sure
[08:55] <sil2100> didrocks: http://<IP_ADDRESS>/job/landing-003-2-publish/15/artifact/packaging_changes_unity_7.1.2+14.04.20140214.1-0ubuntu1.diff http://<IP_ADDRESS>/job/landing-003-2-publish/15/artifact/packaging_changes_unity-scopes-shell_0.3.1+14.04.20140214-0ubuntu1.diff and http://<IP_ADDRESS>/job/landing-003-2-publish/15/artifact/packaging_changes_bamf_0.5.1+14.04.20140214.1-0ubuntu1.diff for starters
[08:55] <sil2100> didrocks: there's also compiz: http://<IP_ADDRESS>/job/landing-003-2-publish/15/artifact/packaging_changes_compiz_1%3A0.9.11+14.04.20140214-0ubuntu1.diff <- there are some migrations there as well
[08:56] <sil2100> Reminds me of the 'good' old times
[08:56] <didrocks> sil2100: hum, have you checked that we actually want to remove the decoration? I remember that seb128 was seeing the new decorations as regressions
[08:56] <didrocks> no right click on the title bar and so on
[08:57] <didrocks> +1 on bamf and u-s-c
[08:57] <seb128> hey there
[08:57] <didrocks> salut seb128 !
[08:58] <seb128> didrocks, trevinho got a branch to fix the lack of menu, not sure if they included in that landing, but I see that as an ok tradeoff to get things moving, there has been no landing for those components in years so the first one is going to be a little bumpy
[08:58] <didrocks> seb128: ok then, as long as you are happy :)
[08:58] <didrocks> sil2100: I think you checked that unity-autopilot was in universe, and so, it's ok to have it depending on mesa-utils :)
[08:58] <sil2100> seb128, didrocks: there were some branches I added to this landing on Friday morning, so it's in most probably
[08:59] <seb128> oh right, they are there
[08:59] <didrocks> sil2100: +1 on unity
[08:59] <didrocks> remains compiz to check
[09:00] <seb128> not that robert_ancell did some manual uploads meanwhile
[09:00] <seb128> I would say to override those
[09:00] <vila> didrocks, sil2100, Mirv (vacations ?): qa-intel-4000 was out-of-disk ( fginther fixed that on Friday but it happened again last night), fixed now but some jobs may have failed because of that
[09:00] <sil2100> hmmm... I see one problem though!
[09:01] <didrocks> vila: thanks !
[09:01] <sil2100> didrocks: I don't see nux in the landing ;/
[09:01] <sil2100> Craaaap
[09:01] <didrocks> sil2100: no nux or no nux packaging change?
[09:02] <seb128> https://launchpad.net/~ci-train-ppa-service/+archive/landing-003/ has it
[09:02] <sil2100> didrocks: wait, I'm blind, I see it now
[09:02] <sil2100> didrocks: thought it got reverted during the spreadsheet problems, phew
[09:02]  * sil2100 is blind
[09:03] <didrocks> sil2100: packaging changes for it or none?
[09:03] <sil2100> didrocks: none
[09:03] <vila> didrocks, sil2100: Indeed http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000/1556/console, http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000/1557/console and http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-intel-4000/1558/console failed because they couldn't even create the script containing the commands to execute...
[09:04] <sil2100> vila: huh, out of disk space so frequently?
[09:05] <vila> sil2100: under investigation but it seems that one container was consuming ~500M for raring, ~1G for saucy and ~3G for trusty
[09:05]  * sil2100 hopes bregma tested the migration script for compiz
[09:05] <vila> sil2100: so either it's "normal" and we need a bigger disk or something wrong is going on
[09:08] <didrocks> sil2100: all migrations scripts for compiz: + 1
[09:10] <didrocks> so all ok for me
[09:10] <sil2100> \o/
[09:11] <sil2100> Then publishing!
[09:11] <sil2100> bregma will be happy ;)
[09:12] <sil2100> didrocks: thanks!
[09:13] <sil2100> eeek
[09:17] <sil2100> didrocks: so, publishing failed since 5 hours ago there has been a direct upload of compiz and unity - now, the directly uploaded versions deal with the unity-control-center and similar dependencies
[09:18] <didrocks> sil2100: this is what seb128 told above
[09:18] <didrocks> 10:00:01   seb128 | not that robert_ancell did some manual uploads meanwhile
[09:18] <didrocks> 10:00:08   seb128 | I would say to override those
[09:18] <didrocks> sil2100: did you miss that? ^
[09:18] <sil2100> didrocks: hah! Yes ;)
[09:19] <mhr3> sil2100, silo for #40 pls?
[09:19] <sil2100> mhr3: will do in a moment :)
[09:19] <sil2100> didrocks: so hm, override? People are going to yell at me again for 'removing changelog history' ;D
[09:19] <didrocks> sil2100: ignore or direct those to seb128 or I
[09:19] <mhr3> also, you evil people deleting lots of landing requests :P
[09:20] <didrocks> mhr3: look at the ubuntu-touch ML, google issue
[09:20] <sil2100> mhr3: it was the spreadsheet!
[09:20] <mhr3> yea, right :P
[09:20] <didrocks> everything is explained dude :p
[09:20] <seb128> didrocks, sil2100: don't worry, robert_ancell is not like that ;-) (and I'm going to email him about those)
[09:20] <mhr3> i know it is, i read it, still evil :P
[09:20] <didrocks> ahah
[09:21] <sil2100> ;)
[09:21] <didrocks> mhr3: TBH, I would prefer not having that, we had to reconciliate the state which was totally out of sync with jenkins
[09:21] <didrocks> one by one
[09:22] <sil2100> I wonder if those problems will be back again
[09:22]  * didrocks hopes not
[09:23] <sil2100> mhr3: ok, so please wait until the unity7 landing arrives in the archive, since right now it's blocking assignment of 40
[09:23] <mhr3> do we know why did it even happen?
[09:23] <sil2100> mhr3: since we had to bump a build-dep there
[09:23] <mhr3> sil2100, how long is that going to take?
[09:24] <sil2100> mhr3: they're migrating now, not sure how long it usually takes for unity7 to migrate, but I wouldn't assume anything longer than like 2 hours max?
[09:25] <mhr3> sil2100, could you ping me once you assign it?
[09:25] <sil2100> mhr3: sure
[09:28] <seb128> sil2100, didrocks: I promoted libunity-core-6.0-9 for you, should avoid hitting component mismatch and having to wait some extra publisher runs later on
[09:28]  * seb128 is used by now at the new binaries being copied to universe
[09:28] <didrocks> seb128: thanks
[09:28] <sil2100> seb128: thanks!
[09:28] <seb128> yw ;-)
[09:29] <vila> didrocks, sil2100: I got my numbers wrong, it's 30G to 3G, apparently record-my-desktop accumulate sessions under /tmp but only on qa-intel-4000
[09:29] <vila> s/to 3G/not 3G/
[09:29] <sil2100> oh shit
[09:30] <vila> sil2100: s/oh/of/ ? :-D
[09:31] <sil2100> ;D
[09:31] <sil2100> No no no
[09:31]  * ogra_ has some browser issues ... might be late
[09:31] <didrocks> ogra_: should we start without you?
[09:32] <ogra_> there we go
[09:33] <popey> bug 1281026
[09:34] <seb128> popey, is you "screen turn off when using power settings" happening with the indicator as well?
[09:42] <popey> seb128: having troublr reproducing that now ⍨
[09:49] <popey> ApplicationManager: application 'webbrowser-app' died unexpectedly!
[09:50] <popey> is it normal to see that in unity8.log?
[09:53] <didrocks> Saviq: ^
[09:53] <didrocks> I would have said we use upstart, so should be in the log
[09:54] <didrocks> but the application manager (in unity-mir) is running in the unity8 process?
[09:54] <didrocks> (IIRC)
[09:54] <Saviq> didrocks, popey, yes, that basically means upstart "lost" the app instance
[09:54] <popey> seeing that a lot
[09:54] <ogra_> it is loosing a lot lately
[10:02] <popey> any way to debug why the welcome screen isn't appearing for me when I lock the phone?
[10:02] <popey> by "lock" I mean "press the power button"
[10:11] <didrocks> Saviq: any idea on that one? Seems it's from some images ago ^
[10:11] <didrocks> popey: you don't have any reliable reproducer, right ?
[10:12] <Saviq> popey, didrocks, nope, only thing I saw is sometimes it won't wake up on first power press, but lock screen's always there
[10:15] <seb128> didrocks, sil2100, mhr3: just as a fyi, compiz/unity migration is going to take some extra hours, they stopped the ppc64el builders to change configs, it's going to need to build there before migrating (which means waiting for builders to be back, then build compiz, they building unity once it's published)
[10:16] <didrocks> thanks for keeping us posted seb128
[10:16] <seb128> yw!
[10:17] <mhr3> sigh, hate when things take so long
[10:17] <mhr3> but yea, thx for update
[10:17] <seb128> you got unlucky, they are reboostrapping that new arch, which is a one time thing
[10:18] <popey> didrocks: Saviq seems wedged in some kind of phone call mode. The "near my ear sensor" is active, if I wave my hand over the phone it blanks the screen.
[10:18] <Saviq> popey, sounds like ofono / powerd got stuck indeed
[10:20] <didrocks> yeah, can be powerd, will need a good and detailed bug report I guess
[10:23] <sil2100> seb128: thanks
[10:27] <ogra_> didrocks, maguro looks okayish
[10:27] <didrocks> ogra_: excellent, let's promote then!
[10:27] <sil2100> \o/
[10:28] <popey> Saviq: didrocks initctl is spinning 100%
[10:28] <popey> and my phone will die as a result, battery level 1%
[10:29] <popey> which app should I file a bug against while I can
[10:30] <ogra_> [10:30] <ogra_> popey, upstart-app-launch i guess
[10:30] <didrocks> popey: hum, noy sure filing a bug will give us more infos. It's a one time thing again?
[10:30] <didrocks> upstart-app-launch changed a lot recently
[10:30] <didrocks> maybe thostr_ can help you with that ^
[10:30] <popey> didrocks: no, it's not the first time this has happened
[10:30] <didrocks> so you can't even bisect the image :/
[10:31] <popey> root       598 16.2  4.5  88792 86892 ?        R    Feb15 431:02 initctl emit boot-hooks WHEN=new-version OLD_BUILD=176 NEW_BUILD=181
[10:31] <popey> thats what's eating the cpu
[10:32] <Saviq> no idea what triggers that :/
[10:32] <Saviq> sounds like upgrade mechanism
[10:32] <didrocks> yeah
[10:33] <didrocks> popey: can you try flashing an older image like 181, and see if we get that event again? (if it's an upgrade?)
[10:33] <popey> that _is_ 181
[10:33] <popey>   PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
[10:33] <popey>  1981 phablet   20   0<PHONE_NUMBER>44   1160 S   0.3 34.7  33:23.17 init
[10:34] <popey> http://paste.ubuntu.com/6948119/
[10:38] <ogra_> popey, i think mhall opened a bug for that quite a while ago ...
[10:38] <ogra_> havent seen it in a long time
[10:38] <popey> thanks.
[10:39] <popey> I'm guessing many people here don't see it because they're always rebooting their phones. these things come out for me during the weekend when it's left on
[10:40] <ogra_> mine runs all the time
[10:40] <ogra_> popey, do you notice weird battery behavior when the battery is low (around and below 20%) ?
[10:41] <ogra_> mine gets very jumpy ... hops around between 12 and 20 then, with the indicator going red when it drops to 12
[10:41] <popey> not noticed
[10:42] <popey> my dmesg is spammed with battery notifications though - filed that bug
[10:42] <popey> bug 1280124
[10:43] <ogra_> popey, duplicate of bug 1270248
[10:52] <popey> i think ofono getting wedged might be related to me running out of phone credit and trying to make a call
[10:58] <popey> damnit, phone died before I could get bug data out of it.
[12:18] <sil2100> didrocks: I'm afraid the spreadsheet problems are starting to appear again
[12:22] <popey> bug 1281082
[12:26] <sil2100> hmmm
[12:28] <sil2100> thostr_: I'll try assigning you a silo now, but it's all very risky as the spreadsheet is b0rken again and I'm doing it manually
[12:29] <thostr_> sil2100: ok
[12:31] <sil2100> thostr_: ok, silo assigned
[12:32] <sil2100> thostr_: be advised that google might say 'f**k it' and simply revert my changes now, so just give me a sign if by any chance your landing assignment gets erased
[12:33] <sil2100> didrocks: it seems some parts work correctly and some don't - the Oops error pops up again and assigning silos doesn't work - it generates the UID but doesn't do the assignment in metadata
[12:33] <sil2100> didrocks: I was doing it manually
[12:33] <sil2100> didrocks: the rest seems to work though
[12:33] <sil2100> (like the syncstatus bits)
[12:39] <didrocks> sil2100: not sure what to say but "ggg" :/
[12:39] <didrocks> I guess the unassignement won't work
[12:40] <thostr_> anybody has a clue what "jettisoned without merging" means?
[12:41] <thostr_> ci sheet line 32
[12:42] <didrocks> not sure as well
[12:45] <boiko> hi guys, one question: I had one MR in the spreadsheet that had a conflict, and it now got updated, do I need to do anything, or will the silo build be triggered automatically again?
[12:46] <didrocks> boiko: you  pushed to the same MP?
[12:46] <didrocks> (or rather, branch)
[12:46] <boiko> didrocks: yep
[12:47] <didrocks> boiko: so, you need to rerun the build job yourself to take into account
[12:47] <didrocks> boiko: if you have more than one component, you can just ask to rebuild one with the build only parameter
[12:47] <didrocks> tell me if there is anything unclear to you
[12:50] <boiko> didrocks: nice! let me try that
[12:52] <boiko> didrocks: so, I think I need to build two of the MRs from the branch, what separator should I use? spaces?
[12:54] <didrocks> boiko: it's not per MP, it's per component
[12:54] <didrocks> boiko: so, for instance, if you set "dialer-app messaging-app
[12:54] <didrocks> "
[12:54] <didrocks> it will rebuild all MPs for dialer-app and messaging-app
[12:54] <didrocks> that are part of the list
[12:55] <boiko> didrocks: ah yes, sorry, I didn't write it correctly, that's what I need, rebuild telephony-service and messaging-app, thanks
[12:55] <didrocks> (and not, let's say indicator-session if it was in the same request)
[12:55] <didrocks> ok, so just put telephony-service messaging-app"
[12:55] <didrocks> boiko: space to separate those :)
[12:55] <boiko> didrocks: yep, thanks
[12:55] <boiko> didrocks: "boiko is missing the Job/Build permission"
[12:56] <didrocks> oh
[12:56] <didrocks> I thought I added you to the team
[12:56] <didrocks> boiko: when you logged in, have you checked the ci-train-users" checkbox in launchpad sso?
[12:56] <didrocks> (you need to do that the first time)
[12:57] <boiko> didrocks: hmm, I didn't have that option there
[12:58] <didrocks> ah, yeah, I didn't add you, one sec
[12:58] <didrocks> boiko: you should see the option now
[12:58] <sil2100> didrocks: after lunch, around 15 of our time, I'll have to drive with my rat to the vet - depending on the diagnosis it might take more or less time
[12:58] <didrocks> boiko: btw, please come to the bootcamp now :)
[12:58] <didrocks> sil2100: oki, you should you will be back before the meeting,
[12:59] <boiko> didrocks: it's tomorrow, right?
[12:59] <didrocks> yeah
[12:59] <sil2100> didrocks: I'm sure I will, unless they decide to operate her like NOW ;) Which is highly improbable
[12:59] <didrocks> sil2100: oki, ttyl!
[12:59] <boiko> didrocks: now it works, thanks
[13:00] <didrocks> boiko: yw ;)
[13:23] <mhr3> sil2100, can we add 2 pkgs to the seed?
[13:23] <mhr3> sil2100, those being unity-scope-mediascanner2 and unity-scope-scopes
[13:26] <bregma> didrocks, once my ci-train stuff has landed completely does the line in the spreadsheet disappear automagically?
[13:26] <didrocks> bregma: it will become "landed" once you merge and clean
[13:26] <didrocks> (if sil2100 hasn't done it)
[13:27] <didrocks> it's up to you to do it, as you will see in tomorrow's bootcamp
[13:28] <bregma> didrocks, everything's merged and the silo has been cleaned and repurposed but the line in Pending is still there,  perhaps there was a burp somewhere
[13:29] <didrocks> bregma: ah, we keep them for some days
[13:29] <didrocks> bregma: so that you can see it was landed
[13:29] <didrocks> then, it's moved to the archive one
[13:29] <bregma> so I can just start adding new landings then?
[13:30] <sergiusens> didrocks, hey; going to need some hand holding for landing 33 (as it requires a seed change); when can we get that done
[13:30] <didrocks> bregma: see #ubuntu-desktop, there is one landing we need for one MP that was incorrect (missing -0ubuntu4), we are going to quickly land that
[13:31] <didrocks> sergiusens: we need to have "ready" set to yes first
[13:31] <didrocks> sergiusens: do you know why ubuntu-settings doesn't have MP? I would prefer we use a branch
[13:31] <didrocks> (of course, not for ubuntu-touch metapackage)
[13:32] <sergiusens> didrocks, https://code.launchpad.net/~bfiller/ubuntu/trusty/ubuntu-settings/touch-settings-click/+merge/206530
[13:32] <didrocks> sergiusens: it's not a branch as the others
[13:32] <didrocks> sergiusens: the bot has no access to it
[13:32] <sergiusens> didrocks, that situation is very ugly, we will most likely need to change it as the version won't be that; but until I get a lock on camera && gallery, I won't know what version it will be
[13:33] <sergiusens> didrocks, where does system settings live, I'll move the mr to there; just noticingit's against an ubuntu branch
[13:33] <sergiusens> *noticing
[13:33] <didrocks> sergiusens: I don't know, if there is no lp:ubuntu-settings, I would prefer we setup one
[13:33] <didrocks> that can bzr bd and build the package
[13:36] <sergiusens> ogra_, do you know if we have one?
[13:37] <sergiusens> didrocks, there is no lp:ubuntu-settings at least
[13:37]  * ogra_ reads backlog
[13:38] <ogra_> sergiusens, ask seb128 or Laney
[13:38] <sergiusens> forward ^
[13:38] <seb128> bregma, didrocks: I need https://code.launchpad.net/~seb128/unity/restore-gsd-override/+merge/206714 to land, fine if the landing includes other fixes
[13:38] <seb128> sergiusens, ogra_: what?
[13:39] <ogra_> seb128, the branch for touch-settings
[13:39] <sergiusens> seb128, do we have a regular lp branch for lp:ubuntu/ubuntu-settings
[13:39] <mhr3> sil2100, #40 rdy to publish
[13:39] <mhr3> or didrocks ^
[13:39] <sergiusens> seb128, as didrocks wants it under citrain
[13:39] <seb128> sergiusens, ogra_: hum, 'application://com.ubuntu.camera_camera_<IP_ADDRESS>.desktop' ... is that version? please tell me we are not going to need to update the key every time the click is updated?
[13:40] <ogra_> seb128, i think we do
[13:40] <seb128> no way
[13:40] <sergiusens> seb128, that seems to be, unity can't do matching yet
[13:40] <ogra_> well, upstart-app-launch does it for you
[13:40] <seb128> that's crazyness
[13:40] <ogra_> that logic needs to be moved into unity too i think
[13:40] <didrocks> mhr3: doesn't seem to be ready, see the comment
[13:40] <sergiusens> seb128, talk to ted or ken about it
[13:40] <ogra_> seb128, complain to ted
[13:41] <rsalveti> sergiusens: haha, didrocks published the qtubuntu one already
[13:41] <mhr3> seb128, does the comment in 003 still apply?
[13:41] <rsalveti> right before
[13:41] <bregma> seb128, didrocks I have 3 other small MPs for unity I want to land, shall I set one up?
[13:41] <seb128> mhr3, no
[13:41] <sergiusens> rsalveti, that means the sheet is outdated... didrocks can you check landing 007?
[13:41] <mhr3> didrocks, ^
[13:42] <seb128> bregma, yes please, as long as you include https://code.launchpad.net/~seb128/unity/restore-gsd-override/+merge/206715 and that we get that assigned soon
[13:42] <bregma> ASAP
[13:42] <seb128> bregma, current landing made g-s-d not run in trusty
[13:42] <didrocks> sergiusens: is it outdated? not for me
[13:42] <seb128> e.g no theme, no appmenu, no multimedia key
[13:42] <seb128> bregma, it makes me wonder how you guys tested the landing btw...
[13:43] <didrocks> bregma: seb128: just decide between you too what you want to include, but it needs to be quickly released, so don't take risks
[13:43] <sergiusens> didrocks, it says packages built and rsalveti tells me you already published... going to manually refresh sheet
[13:43] <seb128> didrocks, +1, thanks
[13:43] <didrocks> sergiusens: it says migrating as expected to me
[13:44] <sergiusens> didrocks, yeah, just refresh manually; wasn't getting the update
[13:44] <didrocks> mhr3: ok, publishing
[13:44] <didrocks> sergiusens: yeah, google backend is really flaky since last week
[13:45] <seb128> sergiusens, ogra_: ubuntu-settings is on https://code.launchpad.net/~ubuntu-desktop/+junk/ubuntu-settings atm, we should move that to a proper project indeed
[13:45] <mhr3> didrocks, ty
[13:45] <didrocks> mhr3: done
[13:45] <seb128> sergiusens, ogra_: I'm going to talk to ted/ken about the versionning
[13:46] <ogra_> seb128, i think you also need to involve jamie ... iirc there are security reqs as well wrt keeping the versiooning in the names
[13:49] <bregma> didrocks, I have line 44 ready
[13:49] <didrocks> bregma: assigning
[13:49] <ogra_> didrocks, can we let ubuntu-themes in soon ? i would like to be able to read email again :P
[13:50] <bregma> sweet
[13:50] <didrocks> ogra_: is there anything in ci train? I don't see it
[13:50] <ogra_> (evo has black bg without the new themes package)
[13:50] <didrocks> ogra_: or we'll need a lander
[13:50]  * sil2100 hates that his google spreadsheet is out of sync
[13:50] <ogra_> didrocks, i think seb128 has added it to the old spreadsheet
[13:50] <ogra_> manual upload etc
[13:50] <sil2100> ogra_: when did he add it?
[13:50] <ogra_> just needs approval
[13:50] <sil2100> Oh, he added it today
[13:50] <sil2100> ogra_: I can do it soon
[13:51] <seb128> didrocks, it has proven difficult to find somebody wanting to own that one
[13:51] <ogra_> no idea ... he just told me in -desktop
[13:51] <seb128> sil2100, thanks
[13:51]  * ogra_ hugs sil2100
[13:51] <didrocks> seb128: well, we'll need to find someone, we'll shutdown the daily release at some point
[13:52] <ogra_> luckily the font isnt black too ... so with a lot of patience i can read the dark grey on black :)
[13:52] <seb128> didrocks, right, working on it, but you know how it goes with the italian mafia, not easy to convince :p
[13:52] <didrocks> heh, yeah ;)
[13:52] <didrocks> thanks
[13:52] <ogra_> seb128, pasta helps !
[13:52] <didrocks> seb128: you can run the build job on landing-006
[13:52] <didrocks> even if you don't see it associated
[13:52]  * didrocks grrr at the timeouts of the spreadsheet
[13:52] <seb128> didrocks, thanks
[13:53] <seb128> bregma, didrocks: unity build started on http://<IP_ADDRESS>/job/landing-006-1-build/25/console
[13:54] <didrocks> great
[13:54]  * didrocks continues to try to assign manually
[13:56] <didrocks> ah, good news, IS opened a request at google
[14:04] <sil2100> \o/
[14:05] <sil2100> ogra_, seb128: I'm building new packages of ubuntu-themes right now
[14:06] <seb128> sil2100, thanks
[14:07] <ogra_> yay, thanks !
[14:23] <didrocks> psivaa: do you have the link for the camera-app failing tests on public jenkins?
[14:33] <mhr3> didrocks, how is the upcoming distro freeze going to affect our landings?
[14:33] <didrocks> mhr3: everything that's on desktop will be impacted
[14:33] <didrocks> mhr3: things are touch only are not discussed yet
[14:34]  * ogra_ would assume we do the same as last release for touch ...
[14:34] <mhr3> didrocks, i meant there's a real freeze period for the archive, right? if we try to land something touch-only during that time, will it actually land?
[14:35] <ogra_> general exception for all touch only stuff ... FFE for stuff in touch that touches other areas too
[14:37] <didrocks> mhr3: right now, the first freeze is feature freeze one
[14:37] <didrocks> nothing enforced
[14:37] <didrocks> just that things that will land on the destkop shouldn't change features
[14:37] <mhr3> didrocks, ah, ok, then all is cool :)
[14:41] <didrocks> and the spreadsheet reverted again :/
[14:42] <sil2100> THe fuuck...
[14:42] <didrocks> sil2100: do you have time to try to reconcialiate?
[14:42] <didrocks> like I'm sure the unity7 one is landed
[14:42] <didrocks> and we miss the additional bregma's/seb128 unity7 one
[14:43] <didrocks> I wonder if we don't have a client opened which is going crazy
[14:44] <didrocks> I can't even get the revision history…
[14:44] <seb128> didrocks, sil2100: the indicator-datetime one is missing as well
[14:44] <seb128> didrocks, the gdoc says "last edit 3 hours ago", that sounds wrong
[14:44] <mhr3> eh, how do i get to my merge&clean link now?
[14:44] <seb128> mhr3, what was your silo?
[14:45] <mhr3> seb128, 3
[14:45] <seb128> mhr3, http://<IP_ADDRESS>/job/landing-003-3-merge-clean/
[14:45] <didrocks> seb128: it is wrong
[14:45] <mhr3> seb128, not all is migrated yet though
[14:45] <mhr3> seb128, but thx :)
[14:45] <seb128> yw
[14:45] <didrocks> mhr3: you still have the link, just not the icon
[14:46] <sil2100> didrocks: I need to jump out to that vet now, but when I'm back then will try to fix up all which I remember ;/
[14:46] <didrocks> ok
[14:46]  * didrocks changes the status refresh to 5 minutes to see if this changes
[14:47] <didrocks> What do you think if I try to copy and paste this spreadsheet to another one?
[14:48] <didrocks> send an email to everyone to use the new one instead
[14:48] <didrocks> and see how it goes
[14:48] <didrocks> seb128: mhr3: thostr_: thoughts? ^
[14:48] <seb128> didrocks, wfm
[14:49] <didrocks> maybe let's give a day for google to look at it
[14:49] <didrocks> and move to that tomorrow
[14:50] <mhr3> didrocks, fine with me
[15:10] <psivaa> didrocks: https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job/trusty-touch-mako-smoke-daily/45/ has camera app failures. with image 184
[15:11] <didrocks> psivaa: thanks a lot!
[15:12]  * didrocks goes for a run
[16:00] <ogra_> didrocks, on my way to the bootcamp but will be a min late or two
[16:05] <ogra_> ah, bah
[16:05] <ogra_> totally mixed up the days
[16:06] <sil2100> ;
[16:06] <sil2100> ;)
[16:16]  * sil2100 tries fixing the spreadsheet contents
[16:16] <sil2100> I feel it will be pointless, since google will revert anyway
[16:24] <sil2100> Damn, it's all so broken
[16:39] <asac> cyphermox_: will you be around for CITrain support today?
[16:40] <didrocks> asac: robru will probably be late FYI, so cyphermox_ is our only hope
[16:40] <cyphermox_> asac: you mean the usual meeting in 30?
[16:40] <asac> yeah
[16:40] <cyphermox_> yes
[16:40] <cyphermox_> 20 minutes actually I guess
[16:40] <didrocks> shower + 10 minutes for me :)
[16:41] <asac> cyphermox_: thanks! you are THE man tonight
[16:41] <asac> thostr_ will need you later
[16:41] <sil2100> didrocks: ok, I restored what I could from the backend to the spreadsheet
[16:41] <didrocks> sil2100: thanks dude
[16:41] <didrocks> we should do a walkthrough with cyphermox_ as well
[16:42] <didrocks> if this happens again
[16:42] <sil2100> didrocks: I still get the Oops'es though ;/
[16:42] <didrocks> "last edit was 5 hours ago"
[16:42] <didrocks> it's so so so wrong
[16:42] <didrocks> asac: we'll really need some google support…
[16:42] <asac> didrocks: you wont get that
[16:43] <sil2100> Then yeah, it will be reverted again I guess, just a matter of time
[16:43] <asac> didrocks: even the most influential person wont be able to get you more than filing a ticket
[16:43] <sil2100> I think we'll have to find another backend :<
[16:43] <asac> didrocks: check with #is etc. ... they can file you a ticket
[16:43] <cyphermox_> didrocks: bugs...
[16:43] <didrocks> asac: they did that (after 3 days)
[16:44] <didrocks> asac: I thought we got some contract support as being a customer
[16:46] <asac> didrocks: google apps is a mass user product
[16:46] <asac> didrocks: your tickets might get looked at at some point
[16:46] <asac> thats afaik the only support you get
[16:46] <didrocks> asac: ok, I thought we got more support contract by buying google apps product license for company
[16:46] <asac> didrocks: https://support.google.com/a/answer/1047213?hl=en
[16:46] <didrocks> was so optimistic for once :)
[16:47] <didrocks> ok, it's like opening a bug then
[16:47] <asac> didrocks: yeah sorry. i really have never heard about anyone ever getting "real" support
[16:47] <asac> there is a phone number, but they wil just open a ticket for yo
[16:48] <didrocks> yeah, seeing that
[16:49] <asac> didrocks: so maybe think bout how to write the ticket so that you as a dev would look at it
[16:49] <asac> :)
[16:50] <asac> but thats the only way you can probably influence it
[16:50] <asac> call out REGRESSION :)
[16:50] <asac> in bold letters
[16:50] <asac> in subject
[16:50] <asac> and name a regression window
[16:56] <didrocks> asac: IS already opened it earlier today
[16:56] <didrocks> so I guess too late
[16:56] <asac> right
[16:56] <asac> didrocks: guess we could file duplicates :)
[16:56] <asac> doubt google cares
[16:56] <asac> just make it unobvious
[16:56] <didrocks> asac: do we have a special account to open a case?
[16:56] <popey> rewrite it in go
[16:56] <didrocks> popey: tsssssssss :)
[16:57] <popey> :D
[16:57] <asac> didrocks: check with the guy who opened the ticket i would think
[16:57] <popey> I love triggering your "tsssssssss"
[16:57] <asac> who was that
[16:57] <asac> didrocks: ?
[16:57] <didrocks> asac: I'll do that, finishing prepping the meeting
[16:57] <didrocks> popey: I'm expecting you are giving such argument at next Linux Unplugged :)
[17:03] <popey> hah
[17:11] <bregma> sil2100, is it OK to re-add stuff to ci-train that disappeared this morning in the kerfuffle (I had a compiz landing disappear before being allocated)
[17:15] <sil2100> bregma: yes, we're sadly still cursed by spreadsheet problems and entries get reverted ;/
[17:20] <popey> ☻  didrocks
[17:34] <sil2100> robru: I'll try publishing silo 004 if anything
[17:35] <sil2100> robru: ok?
[17:35] <robru> sil2100, sure...
[17:38] <elopio> ping cihelp, have any of you seen this error in other apps? http://<IP_ADDRESS>:8080/job/generic-mediumtests-trusty/1332/artifact/ubuntu_clock_app.tests.test_stopwatch.TestStopwatch.test_create_lap.ogv
[17:39] <elopio> qmlscene doesn't seem to be properly loading the qml.
[17:42] <sil2100> didrocks: ok, it seems to have finished
[17:43] <sil2100> didrocks: now it's waiting for stuff to build
[17:44] <vila> elopio: that rings no bells sorry, US guys are on holiday, try again tomorrow ? But I don't think they look at a lot of videos either
[17:48] <didrocks> sil2100: yeah, all .project files are here
[17:48] <didrocks> sil2100: oh no sorry
[17:48] <didrocks> sil2100: only 2
[17:48] <didrocks> dbus-test-runner.project
[17:49] <didrocks> libdbusmenu.project
[17:49] <thomi> fginther: if you have a moment - how often are the medium test runner machines (or VMs or whatever) dist-upgraded?
[17:49] <didrocks> sil2100: oh, I know why it's looking at the others, because they are on the ppa
[17:49] <didrocks> hum no
[17:49] <didrocks> that doesn't make any sense :/
[17:50] <didrocks> sil2100: oh, found the bug
[17:50] <sil2100> wtf
[17:50] <sil2100> Oh?
[17:50] <didrocks> ./indicator-network/unity-greeter-session-broadcast.project
[17:50] <didrocks> ./indicator-network/libdbusmenu-qt.project
[17:50] <didrocks> ./indicator-network/url-dispatcher.project
[17:50] <didrocks> I guess when there is no packaging diff, I don't come back to root
[17:50] <didrocks> sil2100: ok, let's kill the build and cook a quick fix
[17:51] <sil2100> hah! In the wrong directory!
[17:51] <sil2100> didrocks: good catch ;)
[17:51] <sil2100> Cancelling
[17:52] <didrocks> sil2100: pushed, mind deploying in production? and rerun :)
[17:56] <sil2100> Sure ;)
[17:56] <didrocks> hum
[17:56] <didrocks> you rerun the build job?
[17:56] <didrocks> ah no :)
[17:56] <didrocks> it's landing-001 :p
[17:56] <didrocks> ignore me
[17:57] <sil2100> didrocks: re-runing the build job now ;p
[18:03] <mandel> didrocks, sil2100 do you have any feedback about udm?
[18:03] <didrocks> sil2100: ok, it works now
[18:03] <sil2100> \o/
[18:03] <didrocks> mandel: you mean, new bugs are anything?
[18:03] <didrocks> or*
[18:04] <didrocks> sil2100: I'll let you handle that one and get that published?
[18:04] <mandel> didrocks, as in, did we add it to the new img? (188)
[18:04] <mandel> didrocks, the branches we talked about last friday (maybe it was with sil2100 and not you)
[18:05] <sil2100> didrocks: sure ;)
[18:05] <didrocks> mandel: is it merged in your trunk?
[18:05] <sil2100> mandel: I guess all landed from Friday that was tested, and it seems to be in the image since the weekend already
[18:05] <sil2100> No noticible regressions ;)
[18:06] <didrocks> 239. By PS Jenkins bot on 2014-02-14
[18:06] <didrocks> Releasing 0.3+14.04.20140214.1-0ubuntu1
[18:06] <didrocks> mandel: it's in your trunk, so it's in ubuntu :)
[18:06] <didrocks> as easy! :)
[18:06] <mandel> didrocks, sil2100 superb, so know we have the following => lp:~ps-jenkins/ubuntu-download-manager/trusty-proposed
[18:06] <didrocks> (also, you have the email I sent few minutes ago)
[18:06] <mandel> didrocks, sil2100 any idea of that branch?
[18:06] <didrocks> mandel: it's a transit branch
[18:06] <didrocks> while it's published, but not yet in the release pocket
[18:07] <didrocks> you can ignore it, it will push it everytime to there
[18:07] <mandel> didrocks, I was asking 'cause I saw the email and I was wondering about that branch
[18:07] <mandel> didrocks, ah, ok, so I can tell my brain no to read that, awesome
[18:07] <didrocks> mandel: exactly ;)
[18:07] <didrocks> if that annoys you, I can delete it once it's merged on the release pocket
[18:07] <mandel> didrocks, other question, know when we approve a branch they do not get merged to trunk and we have to do the ci train is that correct?
[18:08] <didrocks> mandel: exactly
[18:08] <mandel> didrocks, I want to make sure that we do not approve anything without doing it correctly
[18:08] <mandel> didrocks, awesome, no need to delete it, I was just curious :)
[18:08] <didrocks> mandel: no, everything's good :) ralsina will be bootstrapped tomorrow on the whole process for your team
[18:08] <didrocks> that should help spreading the info on how that works
[18:09] <didrocks> (we just did it in advance for you last week, before you are bootstrapped)
[18:09] <mandel> didrocks, ok, sounds great, I wanted to really understand the process
[18:12] <didrocks> yeah, I prefer people trying to understand that acking without getting a clue, that always helps :)
[18:39] <dobey> fginther: for https://bugs.launchpad.net/tarmac/+bug/1253770 is just printing the MP URL to STDOUT what you want?
[19:03] <sil2100> ogra_: hi! I need two packaging ACKs before going EOD ;) You around?
[19:05] <sil2100> cyphermox_: ^ maybe you? :)
[19:05] <cyphermox_> sure
[19:06] <ogra_> ah, thanks
[19:06] <ogra_> :)
[19:07] <sil2100> cyphermox_, ogra_: http://<IP_ADDRESS>/job/landing-005-2-publish/lastSuccessfulBuild/artifact/packaging_changes_libdbusmenu-qt_0.9.2+14.04.20140217.1-0ubuntu1.diff and http://<IP_ADDRESS>/job/landing-005-2-publish/lastSuccessfulBuild/artifact/packaging_changes_libdbusmenu-qt_0.9.2+14.04.20140217.1-0ubuntu1.diff
[19:10] <cyphermox_> sil2100: isn't that just one?
[19:10] <sil2100> Argh
[19:10] <sil2100> http://<IP_ADDRESS>/job/landing-005-2-publish/lastSuccessfulBuild/artifact/packaging_changes_url-dispatcher_0.1+14.04.20140217.1-0ubuntu1.diff
[19:10] <sil2100> cyphermox_: sorry about that, didn't copy what I wanted ;)
[19:12] <cyphermox_> sil2100: libdbusmenu-qt is ok
[19:18] <cyphermox_> sil2100: go for url-dispatcher
[19:20] <sil2100> cyphermox_: thanks!
[19:27] <robru> sweet, internet is officially connected at my new place ;-)
[19:27] <cyphermox_> nice robru
[19:28] <robru> cyphermox_, I'm going to assign silos for 45 and 46
[19:28] <cyphermox_> alright!
[19:30] <robru> thostr_, ping
[19:31] <thostr_> robru: pong
[19:31] <robru> thostr_, landing 45 got silo 3. landing 46 failed to get a silo due to conflicts with silo 5...
[19:31] <robru> silo 5 has a big error, trying to figure out whats gone wrong there...
[19:32] <thostr_> robru: landing 46???
[19:33] <robru> yeah, libdbusmenu-qt appears in both landings. silo 5 needs to get merged & cleaned before landing 46 can be assigned a new silo, but there's some problem.
[19:33] <thostr_> robru: could you check line 42 in the sheet? sheet says nothing but this should have landed by now???
[19:34] <thostr_> robru: line 42 was in silo 4
[19:34] <robru> thostr_, ok checking...
[19:36] <robru> thostr_, looks like that's taken care of. the spreadsheet is in an inconsistent state, but silo 4 has been freed, and I see there's an upload of unity-scope-click from an hour ago
[19:36] <thostr_> robru: perfect. could you quickly reconfig silo 3
[19:36] <robru> thostr_, why, did you change the MPs?
[19:37] <thostr_> because one we figure had a conflict
[19:38] <robru> thostr_, ok
[19:39] <thostr_> robru: was that ok meaning configured or you'll configure?
[19:39] <robru> thostr_, heh. meant "i'll configure" at the time, but it's done now.
[19:39] <thostr_> robru: ok :)
[19:41] <robru> cyphermox_, do you have any idea what's going on in silo 5?
[19:43] <thostr_> robru: cyphermox_: i guess I figured the problem with silo5
[19:44] <thostr_> we did a null merge to get network indicator into ci
[19:44] <robru> thostr_, null merges should be find
[19:44] <robru> fine
[19:44] <thostr_> ah, ok
[19:44] <thostr_> never mind then
[19:44] <robru> thostr_, i'm just checking the archive... looks like *some* of the projects from silo5 are in -proposed as of 20 minutes ago, but not all of them.
[20:06] <bregma> robru, could I get a silo assigned for line 48?
[20:06] <robru> bregma, sure
[20:08] <robru> bregma, silo 4 is yours
[20:08] <bregma> sweet, thanks
[20:17] <robru> i'm stepping out for lunch but feel free to ping me with landing requests and i'll get to them later
[21:02] <robru> back
[21:25] <bregma> robru, until I earn my big-boy pants could you please press the build button for me in silo 4?
[21:26] <robru> bregma, oh sure. have you heard yet when they're training you?
[21:26] <bregma> tomorrow
[21:27] <robru> sweet
[21:27] <bregma> evidently it involves paddles to the britches, I look forward to it
[21:27] <robru> bregma, heh. ok it's building
[21:27] <bregma> thanks
[21:28] <bregma> with FF in a couple days we're going to be landing a lot of stuff
[21:36] <robru> bregma, text conflict in debian/changelog.
[21:37] <robru> bregma, http://<IP_ADDRESS>/job/landing-004-1-build/25/console
[21:37] <bregma> urgh
[21:38] <bregma> ah, OK, we landed other stuff today, he's going to have to merge trunk
[21:38] <bregma> lesson learned
[21:45] <bregma> robru, the MP has been updated to fix the conflicts, could be so kind as to restart silo 4 build for me?
[21:45] <robru> sure
[21:48] <robru> bregma, http://<IP_ADDRESS>/job/landing-004-1-build/26/console if you enjoy watching paint dry
[23:06] <balloons> ping cihelp
[23:06] <balloons> bah, timezones suck


[07:10] <Kilos> morning all
[11:01] <Kilos> how do i get to see all the files in my home on maverick please
[11:01] <Kilos> i got a remastersys file there i cant find
[11:02] <Kilos> iso file i hope
[11:03] <Kilos> home folder
[11:03] <Kilos> i only see the basic 9 that come with installation
[11:05] <Kilos> i mean /home/miles
[11:06] <Kilos> the basic 9 in miles
[11:06] <Kilos> dunno how to open home to find the iso file
[12:42] <Kilos> if i cd /home it is there
[12:43] <Kilos> is this a chown time again
[12:49] <Kilos> got it
[12:49] <Kilos> hehe
[12:49] <Kilos> aw
[12:49] <Kilos> remastersys still missing
[15:37] <Kilos> hi guys. i got probs. used gparted to wipe an external now my xchat lost all its channels and wants to go to new channel/6667 which doesnt exist
[15:38] <Kilos> i have tried a complete removal with synaptic and then reinstalled but it members that there are no channel list
[15:40] <Kilos> oh its looking up new server all the time
[15:40] <Kilos> lost freenode and all the others
[15:42] <superfly> Kilos: all your settings are stored in your home directory. reinstalling xchat won't help
[15:44] <Kilos> eish
[15:45] <Kilos> under .xchat 2 superfly ?
[15:46] <Kilos> can i just delete that and try again
[15:46] <superfly> Kilos: I don't run XChat, so I don't know
[15:46] <Kilos> i stay here, maybe an xchat user comes on
[15:47] <Kilos> ty superfly
[15:47] <superfly> Kilos: at a guess, yes
[16:05] <drubin> Kilos: it shoudl work close xchat and do  mv ~/.xchat2/ ~/xchat2.bak
[16:05] <drubin> and then start it again
[16:07] <Kilos> ty drubin will try that
[16:17] <Kilos> looks its working. ty drubin
[16:18] <Kilos-> w00t
[16:45] <Kilos> hehe i be a dodo
[16:46] <Kilos> had to go read my blog to find how to recover partitions
[16:48] <Kilos> hi lengau how do you do
[19:59] <nlsthzn> feeling all retro... using mIRC
[20:00] <superfly> eww :-P
[20:02] <nlsthzn> superfly something like that... stuck in the 90's for sure
[21:22] <Kilos> night all sleep tight


[00:24] <jMCg> Keybuk: how does it work? Why does it work? And: Even if it makes automake obsolete, it doesn't really make for understandable code :-/
[00:25] <Keybuk> jMCg: $@ is the make variable for "the target"
[00:25] <Keybuk> so $@_SOURCES for init expands to init_SOURCES
[00:25] <Keybuk> $($@_SOURCES) is thus "the contents of $(init_SOURCES)"
[00:25] <Keybuk> the .SECONDEXPANSION bit tells automake to expand the objects of a target twice, and in the second time variables like $@ are set
[00:25] <jMCg> Keybuk: unintentionally, I use that...
[00:26] <jMCg> see: https://scm.brainsware.org/svn/webstack/linux/Makefile
[00:27] <jMCg> Keybuk: ah.. my innitial understanding was that you didn't use automake.
[00:27] <Keybuk> that isn't automake
[00:27] <Keybuk> sorry
[00:27] <Keybuk> "tells MAKE to expand"
[00:28]  * jMCg tries to reparse.
[00:29] <jMCg> Ah, okay, that explains the escaping of the $.
[00:38] <Keybuk> now for the advanced class
[00:38] <Keybuk> http://paste.ubuntu.com/597191/
[00:38] <Keybuk> work out what *that* does
[00:38] <Keybuk> and why it's awesome :D
[00:50] <jMCg> Keybuk: what's $1?
[00:50] <jMCg> Oh.
[00:50] <Keybuk> so:
[00:50] <jMCg> It's Whatever $$@ gets expanded to.
[00:50] <Keybuk> dep_dir turns src/foo.c into src/.deps/
[00:50] <Keybuk> and dep_file turns src/foo.c into src/.deps/foo.mk
[00:51] <jMCg> Why do you have an .mk file for each .c file?
[00:51] <Keybuk> both are written using Make functions so they work if you pass them multiple arguments
[00:51] <jMCg> GNU Make, anyway.
[00:52] <Keybuk> so $(call dep_file,src/foo.c tests/bar.c baz.c) returns src/.deps/foo.mk tests/.deps/bar.mk ./.deps/baz.mk
[00:52] <Keybuk> the next bit is the implicit compile rule
[00:52] <Keybuk> it says any .c file can be turned into a .o file using CC (gcc, clang)
[00:52] <Keybuk> -MMD -MT $@ -MT src/.deps/foo.mk -MP
[00:52] <Keybuk> is an operative bit there
[00:53] <Keybuk> it means: AS WELL AS compiling the .o file, generate src/.deps/foo.mk
[00:53] <Keybuk> that is a Makefile snippet that lists all of the .h files that gcc found
[00:53] <Keybuk> so it might look like:
[00:53] <Keybuk> src/foo.o: src/foo.c src/common.h src/log.h
[00:54] <jMCg> ACK.
[00:54] <Keybuk> and then
[00:54] <Keybuk> -include $(call dep_file,$(SOURCES))
[00:54] <Keybuk> means include every .mk file for every defined file in $(SOURCES)
[00:54] <jMCg> What's -include?
[00:54] <Keybuk> -include means "ignore error due to not existing"
[00:54] <Keybuk> so the first time you type "make" none of these .deps files exist
[00:54] <Keybuk> so make doesn't know which headers are deps
[00:54] <Keybuk> but that's ok
[00:54] <Keybuk> none of the .o files exist either ;-)
[00:54] <jMCg> I suppse you define $(SOURCES) somewhere above.
[00:55] <Keybuk> so the first time you compile, make's brain is populated with all of the .h deps
[00:55] <Keybuk> so the next time, it rebuilds based on what you changed
[00:55] <Keybuk> yeah, $(SOURCES) is put together elsewhere using $(foreach ...)
[00:55] <Keybuk> the one other strange bit is the stamp madness
[00:55] <jMCg> That's bordering insane -- but then, so is autocrap.
[00:55] <Keybuk> each .o file depends on the equivalent src/.deps/stamp file
[00:56] <Keybuk> and that rule is simple, it makes the .deps directory and touches the stamp file in it
[00:56] <Keybuk> this means there's only one mkdir call for each .deps directory
[00:56] <Keybuk> rather than one for each C file
[00:56] <Keybuk> not strictly necessary, but it looks better in the make V=1 output :p
[00:58] <jMCg> Keybuk: how long did you work on upstart's Makefile?
[00:59] <Keybuk> oh, that stuff?
[00:59] <Keybuk> on the shuttle this morning
[00:59] <Keybuk> so about an hour
[01:00] <jMCg> I hereby declare you my personal hero of the hour.
[01:00] <jMCg> Would you very much mind removing all the autocrap from trafficserver: https://svn.apache.org/repos/asf/trafficserver/traffic/trunk/ - please?
[01:02] <jMCg> Instead of reading the GNU m4 handbook and subscribing to the libtool-users mailinglist, maybe I should have read the GNU make handbook instead.
[01:03] <Keybuk> heh, I don't hate autotools
[01:03] <Keybuk> I'm listed in AUTHORS after all
[01:03] <Keybuk> but Upstart simply doesn't need any of the portability stuff
[01:03] <Keybuk> we can assume GNU make and GCC or clang
[01:03] <Keybuk> and Linux
[01:03] <Keybuk> and Automake's requirements to list every single binary was *really* causing me problems with maintaining the ever-growing test suite
[01:04] <Keybuk> by switching to GNU Make turned up to 11, I can just have a single TESTS = ... that lists every binary
[01:04] <Keybuk> and where I need it linked to .o files from the source, add
[01:04] <Keybuk> tests/blah: src/blah.o src/foo.c
[01:04] <Keybuk> and everything else is automatic
[01:05] <jMCg> http://www.varnish-cache.org/docs/trunk/phk/autocrap.html << regarding portability: we're down to a handful of unices anyway, so portability isn't that much of an issue.
[01:06] <Keybuk> agree
[01:06] <Keybuk> Linux + OS X
[01:06] <Keybuk> and those are largely GNU Toolchain
[01:06] <Keybuk> hell, I build Upstart on OS X on my MBP half the time when testing random bits
[01:07] <jMCg> Solaris 11 will be moving to gmake and much of the GNU Tool chain - well, I suppose they will keep their compiler.
[01:07] <jMCg> And maybe, one day, FreeBSD will have moved to clang -- but they will still have the rest of the GNU chain.
[01:08] <Keybuk> Solwhatnow?
[01:08] <jMCg> The thing we use at $work.
[01:08] <Keybuk> oh, that Oracle thing
[01:08] <Keybuk> I thought they were pushing Red Hat ;-)
[01:08] <Keybuk> well, Oracle Ripped Off Linux
[01:09] <jMCg> Well, there's a couple of things in Solaris I'd really love to see in Linux.
[01:09] <ion> I want a good port of zfs on Linux or the 2018 release of btrfs.
[01:09] <jMCg> SMF is, by now, I believe, suprior to upstart.
[01:09] <jMCg> ion: +1
[01:10] <ion> (Also, i want it now.)
[01:11] <jMCg> Well, actually there's only two things missing: switching users/groups without using *ugly* "hacks" - and reducing privileges(5) (on Linux: Capabilities(7)) so you don't have to start a daemon as root.
[01:11] <jMCg> That really rocks.
[01:11] <jMCg> I can run Tomcat on port 80 without feeling dirty.
[01:12] <JanC> wasn't there some talk about some BSDs switching to PCC ?  ;)
[01:12] <Keybuk> jMCg: really? what do you think SMF does better than Upstart?
[01:12] <jMCg> JanC: long, long time ago. I think they've hopped on the LLVM bandwagon, because that one's actually moving.
[01:12] <Keybuk> SMF was pretty basic last time I looked
[01:13] <jMCg> Keybuk: 02:18:46 < jMCg> Well, actually there's only two things missing: switching users/groups without using *ugly* "hacks" - and reducing privileges(5) (on Linux: Capabilities(7)) so you don't have to start a daemon as root.
[01:13] <Keybuk> jMCg: yeah, just got that
[01:13] <Keybuk> +1 then ;-)
[01:13] <Keybuk> that's coming in one week
[01:13] <jMCg> About a year ago, I asked you if there's a chance these will get into upstart and you gave an ~18 month estimate :)
[01:13] <jMCg> whoa.
[01:13] <Keybuk> I have a patch from someone that adds all the useful bits
[01:13] <Keybuk> but that person refused to sign the CLA
[01:14] <jMCg> Pity.
[01:14] <Keybuk> and I promised the Canonical CTO that I would continue those negotiations until the end of April
[01:14] <Keybuk> so 1st May, bzr merge ... ;-)
[01:14] <JanC> lol
[01:15] <Keybuk> I've suggested what I think is a sensible compromise between the positions
[01:15] <Keybuk> it's up to them
[01:15] <jMCg> When someone gives you code - on the ML or via launchpad, don't they basically automatically give up all rights?
[01:15] <Keybuk> jMCg: no, Geneva Convention means they still own copyright
[01:15] <jMCg> I kinda figured that was the position with apache, but I try not to care too much about CLAs.
[01:19] <JanC> the Geneva convention doesn't say anything about copyright really  ;)
[01:19] <Keybuk> err
[01:19] <Keybuk> Berne
[01:19] <JanC> it's an international treaty about the treatment of war victims
[01:19] <JanC> ;)
[01:20] <Keybuk> to be fair, Berne and Geneva are both cities in Switzerland
[01:20] <Keybuk> and you can see how I got there
[01:20] <jMCg> By air plane?
[01:20] <Keybuk> haha, yes, train no more
[01:22] <jMCg> hmm.. any chances that new patchset will make it into Natty? :O
[01:22] <JanC> jMCg: natty releases before the 1st of May  ;)
[01:23] <jMCg> And 10.10 comes with: ii  upstart                                               0.6.6-4                                               event-based init daemon
[01:23] <jMCg> That's sad :-/
[01:27] <Keybuk> aye
[01:27] <Keybuk> it could be worse
[01:27] <Keybuk> 11.04 could come with a version of Upstart that was invented by Ubuntu, and doesn't match any upstream release at all ;-)
[01:28] <jMCg> ugh.
[01:35] <jMCg> Keybuk: can you link the bzr branch that contains your Makefile?
[01:44] <Keybuk> it's not in a branch, it's just on my laptop at the moment
[01:50] <Keybuk> on the shuttle trip home, I shall make po/pot generation work
[01:51] <Keybuk> and then maybe tomorrow morning, "make dist"
[12:04] <bencc> when removing and purging a package I still have processes running so I think I don't stop it correctly in my upstart script
[12:04] <bencc> http://dpaste.com/534618/
[12:05] <bencc> why doesn't my server being stopped?
[16:11] <JanC> I'd say it's more likely something is wrong in the packaging...
[16:33] <hallyn> When I have something wiating on 'mounted MOUNTPOINT=/', then mountall stops after emitting that signal, until the wiating job has finished.  I'm just curious - is that done by upstart, for any job which says 'emit X', or is mountall doing that specially?
[16:50] <JanC> hallyn: is that job a task ?
[16:54] <JanC> the DBus method EmitEvent has a Boolean 'wait' parameter, and if the waiting job is a task, waiting will wait until the task is run
[16:55] <JanC> "initctl emit" also has an option --no-wait that you can use
[16:56] <hallyn> ah, i see.
[16:56] <hallyn> yeah it's a task
[16:56] <hallyn> so mountall must do a --wait
[16:57] <hallyn> JanC: thanks
[16:57] <JanC> well, mountall probably uses the DBus API directly, but yeah  ☺
[17:22] <hallyn> so is there any way, from an upstart job, to say 'start on x and y' where only the later one of x and y will be waited upon?


[00:58] <TheLordOfTime> hggdh, got the latest message?
[00:58] <TheLordOfTime> on the mailing list
[00:58] <TheLordOfTime> bdmurray, same question ^
[19:12] <hggdh> TheLordOfTime: from balloons? Yes, will answer as soon as possible. I think it is a good idea
[19:12] <TheLordOfTime> hggdh, yeah there's continued discussion on it, i put in my two cents, but i've lurked the QA team's area for a while now, since occasionally bug triage questions come out outside the scope of ISOtesting
[19:13] <TheLordOfTime> of course i put in my two-cents in #ubuntu-quality since GMail's not sending my emails today for some reason
[19:13] <TheLordOfTime> but meh
[20:44] <asd> hi i would like to assign a bug to a particular package but am not able to find which package the bug belongs too
[20:44] <asd> can someone please help
[20:44] <TheLordOfTime> asd, which bug
[20:45] <asd> TheLordOfTimes it is Bug #1242907
[20:45] <ubot2> Launchpad bug 1242907 in Ubuntu "The Shutdown button does not work" [Undecided,Confirmed] https://launchpad.net/bugs/1242907
[20:45] <asd> this bug also affects me
[20:47] <penguin42> fun - I'd file that against pm-utils or linux
[20:47] <penguin42> asd: So it stops working but doesn't actually turn the power off ?
[20:47] <TheLordOfTime> asd, ^
[20:48] <asd> for me the case is when i press the top right button and shutdown a window pops up with two huge buttons restart and shutdown
[20:48] <asd> clicking on wither does nothing
[20:49] <asd> and clicking on some where else in the screen dismisses the window
[20:49] <TheLordOfTime> asd, do me a favor and test this in the command line: `sudo shutdown -r now`  (tests restart)   or  `sudo shutdown -h now`  (tests full shutdown and halt)
[20:50] <TheLordOfTime> of course, assuming you aren't on your system right now :)
[20:50] <TheLordOfTime> but if you are just test
[20:50] <TheLordOfTime> (because if it's just those buttons not working that might be a more specific issue)
[20:50] <asd> TheLordOfTime: I have tested these two commands and they work from a user who is sudoers list
[20:51] <asimionov> asd: have you checked the logs? do you have something in the system log?
[20:52] <asd> asimionov: could you please direct me to where I can find the logs, sry but I am new to ubuntu
[20:53] <asimionov> do this: open a new console, type: tail -f /var/log/syslog
[20:53] <asimionov> asd: and type some ENTERs
[20:53] <asimionov> asd: then do you stuff and see what you get in the logs
[20:53] <asimionov> asd: *your
[20:55] <asd> asimionov: Oct 24 22:54:58 c490100005 gnome-session[1984]: WARNING: Unable to inhibit system: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted
[20:57] <asd> TheLordOfTime: it seems to be the buttons, i did what asimionov asked and in the logs i see ^
[20:57] <TheLordOfTime> wait, wasn't this a bug in 13.04?  And 12.10, too?
[20:57] <TheLordOfTime> i could've sworn i've seen this crop up in **every single release*
[20:59] <asd> I have not used 13.04 or 12.10, I was using 12.04 and i updated to 13.10 a few days back
[20:59] <TheLordOfTime> i was addressing everyone else, not just you
[20:59] <TheLordOfTime> i've seen questions about this issue since 12.10
[20:59] <TheLordOfTime> on Ask Ubuntu and stuff
[21:00] <asd> oh ok
[21:00] <penguin42> TheLordOfTime: So this is a permission/session permission thing where it's not allowing the shutdown?
[21:01] <TheLordOfTime> penguin42, dunno, i've only seen the people complaining on Ask Ubuntu about it, i haven't seen any bug resolutions for it
[21:01] <TheLordOfTime> i mean, i could go digging, but... meh
[21:01] <TheLordOfTime> penguin42, i'm also not a dev, and I personally have never had the bug
[21:01] <penguin42> TheLordOfTime: Yeh I'm sure I hit it a few releases ago but can't remember how it resolved
[21:01] <TheLordOfTime> (it works fine in my systems xD)
[21:02] <penguin42> asd: The problem you are hitting sounds different to the bug you linked to - that bug sounds like it starts shutting down just never actually manages to turn the power off
[21:02] <TheLordOfTime> ... be right back, I need to wage war against sbuild right now... (it's FTBFSing only on my system)
[21:02] <penguin42> asd: But there again it's not too clear from the wording of that bug if it is that he's seeing
[21:03] <asd> penguin42: okay i searched for my issue and found this bug, should i create a new one instead, thanks
[21:03] <penguin42> asd: Yes, create a new one - if the shutdown -h now works then I suggest  filing the bug against either unity or pm-utils
[21:03] <penguin42> asd: (unity assuming you're running unity that is)
[21:04] <asd> penguin42: how do i find if i am running unity, thanks
[21:04] <penguin42> asd: Is it the 'normal' Ubuntu gui - with the ubuntu symbol at the top left that when you click it pops up a search box and buttons down the left side?
[21:05] <brainwash> could be gnome-session, systemd/logind or policykit
[21:05] <penguin42> brainwash: Indeed, but very non-trivial to track down
[21:06] <penguin42> certainly I wouldn't know where to go from that point - feel free to suggest
[21:06] <asd> penguin42: yes that is what I have.
[21:07] <penguin42> asd: OK, Unless brainwash has some better ideas of package to pick then I'd file against   pm-utils  and see what happens
[21:07] <penguin42> asd: AS long as you pick something reasonable then the guys who own it might be able to point in a better direction
[21:07] <asd> penguin42: ok thanks I will do so
[21:07] <brainwash> pm-utils is kinda wrong
[21:07] <TheLordOfTime> ... and I'm back, apparently sbuild didn't take into account the PPA i told its schroots to add into it for the nginx builds...
[21:08] <penguin42> brainwash: Ok, make a better suggestion
[21:08]  * penguin42 has to disappear for a while
[21:08] <asd> brainwash: shall i choose unity then, thank you
[21:09] <brainwash> well, gnome-session is throwing the waring
[21:09] <brainwash> warning
[21:10] <asd> well the thing is that is same warning being thrown every few seconds
[21:10] <asd> i just realized this
[21:11] <brainwash> what does "dbus-send --print-reply --system --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanPowerOff" return?
[21:12] <brainwash> yes, no or challenge
[21:12] <asd> brainwash: dbus-send --print-reply --system --dest=org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager.CanPowerOff
[21:12] <asd> returns method return sender=:1.3 -> dest=:1.77 reply_serial=2    string "challenge"
[21:13] <brainwash> that means that there is are other active user session running at the moment, right?
[21:13] <asd> yes i ran the command from a sudoer user
[21:13] <asd> from my user i see this method return sender=:1.3 -> dest=:1.78 reply_serial=2    string "challenge"
[21:14] <brainwash> mmh, how many sessions does "loginctl list-sessions" list?
[21:15] <asd> it says o sessions listed
[21:15] <asd> *0
[21:16] <brainwash> that is odd
[21:17] <asd> brainwash: the sudoer user I have logged in only from the terminal using su
[21:17] <asd> my user is the one currenty logged in physically
[21:17] <asd> dont know if that makes a difference
[21:18] <asd> again i am pretty new to ubuntu and linux in general so sry if it sounds silly :)
[21:18] <brainwash> using su?
[21:19] <brainwash> why that?
[21:19] <asd> yes from the terminal i say su <sudoerUserName>
[21:19] <TheLordOfTime> why would your user that you're logged in as not already be in sudoers?
[21:20] <asd> TheLordOfTime: that is the configuration from my office
[21:20] <asd> my user is not in the sudoers list
[21:21] <asd> i just know a user in the sudoers list that i am currently using to issue the shutdown command when i want to shutdown
[21:23] <brainwash> so did you run the mentioned commands as normal user (your user account)?
[21:25] <asd> yes the first one from my user account gives method return sender=:1.3 -> dest=:1.81 reply_serial=2    string "challenge"
[21:25] <asd> and the loginctl list gives 0 sessions also run from my user
[21:31] <brainwash> right, and that's a bit odd
[21:31] <brainwash> it should at least list your current session
[21:35] <brainwash> what does "cat /etc/pam.d/common-session | grep systemd" return?
[21:36] <asd> brainwash: it returns nothing
[21:36] <brainwash> oh
[21:36] <brainwash> mmmmmh
[21:36] <brainwash> it should return something
[21:38] <brainwash> I'm looking for an existing bug report
[21:38] <asd> it would maybe help to add that my user is linked to a kerberos account
[21:46] <brainwash> asd: so, the entry for systemd is missing in your pam conf file
[21:46] <asd> brainwash: yes it looks like that is the case
[21:47] <brainwash> it's "session optional        pam_systemd.so"
[21:48] <brainwash> there is pam-auth-update to manage the modules, well, but I'm not that familiar with pam
[21:48] <asd> brainwash: i have session optional with couple of other stuff
[21:49] <brainwash> add it below the the pam_unix.so line
[21:50] <asd> pam_unmask.so, pam_krb5.so minimum_uid=1000, pam_ldap.so and pam_ck_connector.so nox11 these are what i have
[21:51] <brainwash> so add "session optional        pam_systemd.so"
[21:52] <brainwash> the block on the bottom is called "Additional" block
[21:52] <brainwash> and the line belongs there
[21:53] <brainwash> It's the only hint we got so far, maybe it does solve your issue
[21:54] <brainwash> if no, you should file a bug report against gnome-session I guess and attach all the information we gathered
[21:55] <asd> ok will add and see what happens
[21:55] <asd> thank you for yout time
[21:55] <asd> *your
[21:57] <brainwash> hopefully the mystery gets solved now or soon :)
[22:00] <asd> brainwash: i have added the line i guess i will have to restart for the changes to take effect
[22:01] <brainwash> right, maybe a relog would be enough
[22:01] <brainwash> but a restart won't hurt
[22:03] <asd> ok doing a restart now
[22:13] <asd> brainwash: it worked
[22:13] <brainwash> great
[22:14] <asd> thank you, the results of the command now are, method return sender=:1.3 -> dest=:1.77 reply_serial=2    string "yes"
[22:15] <asd>    SESSION        UID USER             SEAT                     c2      20006 abduljabbar.gulam seat0             1 sessions listed.
[22:15] <brainwash> you should file a report, but against system and pam
[22:15] <asd> and i can do a restart and shutdown
[22:16] <asd> where can i do this report, thank you
[22:16] <brainwash> on launchpad
[22:17] <brainwash> to inform the devs about this issue, it might affect more people
[22:17] <brainwash> people who upgraded to 13.10
[22:18] <brainwash> https://bugs.launchpad.net/ubuntu/+source/systemd/+filebug
[22:18] <brainwash> afterwards you can also add pam to the list of affected packages
[22:21] <TheLordOfTime> brainwash, might be better for him to do `ubuntu-bug systemd` in the command line
[22:21] <TheLordOfTime> then apport grabs things about it
[22:21] <brainwash> right
[22:22] <brainwash> asd: use `ubuntu-bug systemd` in the command line
[22:23] <TheLordOfTime> without the ` characters
[22:23] <asd> TheLordOfTime and brainwash from command line i get a message saysing Package systemd does not exist
[22:23] <asd> a window pops up displaing this message
[22:23] <asd> displaying
[22:24] <TheLordOfTime> bleh
[22:24] <TheLordOfTime> hmm
[22:24] <TheLordOfTime> brainwash, systemd != in saucy
[22:26] <asd> from the link brainwash sent i find "libpam-systemd" shall i choose this
[22:26] <brainwash> yes
[22:27] <brainwash> systemd is the meta build package name I assume
[22:29] <asd> ok i did ubuntu-bug libpam-systemd
[22:30] <penguin42> brainwash: Nice bit of debug
[22:32] <asd> yes brainwash, thank you
[22:32] <brainwash> penguin42: thanks, sadly 13.10 isn't fully compatible with systemd/logind yet
[22:32] <brainwash> asd: you're welcome :)
[22:33] <brainwash> penguin42: and on top o that, not well tested regarding systemd/logind
[22:34] <penguin42> brainwash: But that is the default install isn't it?
[22:35] <brainwash> yes, logind is now the default, it replaced consolekit (deprecated)
[22:36] <brainwash> currently I'm trying to debug and understand bug 1184262
[22:36] <ubot2> Launchpad bug 1184262 in network-manager (Ubuntu) "[logind] stuck in PrepareForSleep, causing network and other services to not resume" [High,Confirmed] https://launchpad.net/bugs/1184262
[22:36] <penguin42> brainwash: OK, interesting - I hadn't noticed consolekit went away
[22:36] <TheLordOfTime> asd, what's the bug number on your bug that you filed (it should give you a link after its filed)
[22:37] <asd> TheLordOfTime it is Bug #1244463
[22:37] <ubot2> Launchpad bug 1244463 in systemd (Ubuntu) "session optional pam_systemd.so missing from /etc/pam.d common-session file" [Undecided,New] https://launchpad.net/bugs/1244463
[22:38] <penguin42> asd: Did you go straight from 12.04 to 13.10 ?
[22:39] <asd> penguin42: no i ran update-manager -d and it updated to 12.10, 13.04 and finally to 13.10
[22:39] <brainwash> o.o
[22:39] <asd> i did this however one after the other immediately without changing anything in betweem
[22:39] <asd> between
[22:39] <brainwash> clean install would have saved you some time
[22:41] <asd> well i did not want to lose my kerberos settings
[22:41] <asd> but it looks like a clean install would have been better :)
[22:42] <penguin42> asd: Hmm ok, that's interesting - could you add the detail about how you upgraded to your report please
[22:44] <asd> penguin42 yes sure
[22:50] <penguin42> brainwash: Really something somewhere should have done a lot of that session debug automagically rather than the thing just sulking
[22:51]  * penguin42 gulps at the loginctl kill-user  parameter
[22:53] <brainwash> I really dislike ubuntu's systemd abomination :/
[22:53] <penguin42> what have they done - picked just one part of it?
[22:54] <brainwash> the parts which are needed like logind, udev,..
[22:54] <brainwash> and we ship systemd-shim, a simple wrapper for dbus calls
[22:55] <penguin42> brainwash: In which direction do you dislike it, for going too far or not far enough?
[22:55] <brainwash> and the usual ubuntu custom patches :D
[22:55] <brainwash> going further would mean to replace upstart with systemd
[22:56] <penguin42> well you said you disliked it - but I wondered what your preferred route was
[22:57] <brainwash> the current one is the "right" one
[22:58] <brainwash> we had to replace consolekit
[23:49] <penguin42> brainwash: is this the same as bug 1243837 ?
[23:49] <ubot2> Launchpad bug 1243837 in xfce4 (Ubuntu) "Restart in the main menu does a logout instead" [Undecided,Confirmed] https://launchpad.net/bugs/1243837
[23:50] <TheLordOfTime> penguin42, i think this is a different bug, looks like the user here is hitting shutdown or restart but then nothing happens, at least by their description...
[23:51] <brainwash> it is related to bug 1184262
[23:51] <ubot2> Launchpad bug 1184262 in network-manager (Ubuntu) "[logind] stuck in PrepareForSleep, causing network and other services to not resume" [High,Confirmed] https://launchpad.net/bugs/1184262
[23:53] <penguin42> ok
[23:54] <brainwash> ^ this report is driving me mad anyway, people keep bumping it with "useless" comments or simply confirm the workaround over and over again
[23:54] <brainwash> still no real debugging information


[08:37] <fabbione> ok logging is on
[08:49] <jbailey> fabbione: Won't this just get too noisy
[08:49] <jbailey> ?
[08:49] <fabbione> jbailey: see the other chan
[08:49] <fabbione> it's ok to start with
[08:50] <fabbione> we will split if required
[08:50] <fabbione> i don't think it will get too noisy anyway
[09:00] <jbailey> Mmm, alright.
[09:00] <jbailey> Seems to be not much point to having something other than -devel, then.
[09:03] <fabbione> exactly
[09:03] <jbailey> Err.
[09:03] <jbailey> So why have -ports at all then?
[09:04] <fabbione> night jeff
[07:36] <lamont__> fabbione: upload party for hoary is over. you win
[07:40] <fabbione> lamont__: re
[07:40] <fabbione> ehehe
[07:40] <lamont__> er, breezy, even
[07:40] <lamont__> there are already uploads in at least -updates, though
[07:42] <fabbione> lamont: already processesed them :)
[07:42] <lamont__> feh
[07:45] <twysted> i didnt have a party :(
[07:46] <fabbione> lamont: so what are the official numbers?
[07:52] <lamont__> will get them after lunch - sorry
[07:52] <lamont__> ah.
[07:52] <lamont__> i386 95.39% 6290 of 6594
[07:52] <lamont__> powerpc 94.36% 6058 of 6420
[07:52] <lamont__> amd64 93.95% 5996 of 6382
[07:52] <lamont__> ia64 93.36% 5938 of 6360
[07:52] <lamont__> sparc 90.28% 5756 of 6376
[07:52] <lamont__> hppa 90.20% 5715 of 6336
[07:53] <lamont__> now fleeing to lunch
[07:53] <fabbione> eheh
[07:53] <fabbione> enjoy :)
[08:33] <jbailey> Are there really 300 packages that are not-for-i386 ?
[08:34] <fabbione> i have 80 in my list
[08:34] <fabbione> but i skip some stuff we really don't care about
[08:34] <fabbione> (and my wife is too busy watching tv)
[09:32] <lamont__> jbailey: is possible