[00:37] plars: bfiller_afk: tomorrow I will investigate those crashes [03:03] t1mp: I made one minor but important change to that branch, so you might want to repull it. I've proposed a merge for it, and it ought to land in trunk of lp:ubuntu-test-cases/touch tomorow [03:05] === trainguard: IMAGE 262 building (started: 20140326-03:05) === [04:25] === trainguard: IMAGE 262 DONE (finished: 20140326-04:25) === [04:25] === changelog: http://people.canonical.com/~ogra/touch-image-stats/262.changes === [05:13] good morning [05:58] now I realize I forgot to ask sergiusens for click credentials yesterday, after ball_oons taught me how to publish click packages. on the other hand, I'd like to go through the first time by double-checking the steps anyway. [05:58] (regarding the gallery-app) [06:07] nice to see 100% green again http://ci.ubuntu.com/smokeng/trusty/touch/mako/261:20140325.3:20140304/7375/ [07:39] tvoss: were you planning to test+land dbus-cpp ppc64el fix before the process-cpp one? I mean, you are not having a problem of not having a silo for process-cpp yet? [07:39] nope [07:40] Mirv, coming back to you in ~30 [07:40] I take that as a positive answer to my triple negations etc ;) [07:40] cool [07:42] Mirv: 3rd day of the week, triple negations… Tomorrow, four? :) [07:44] :) [07:55] Morning! [07:56] didrocks: so, I checked the dch parameters, and found the difference between precise and now - in precise we need to use "--release-heuristic changelog", as by default it uses 'log' [07:56] didrocks: it works differently as the default heiristics looks for dput upload files, not the changelog contents ;/ [07:56] sil2100: oh, I was overleading that in the directory [07:56] but as we moved CI Train, I guess we missed that [07:56] yeah [07:56] you're more than right [07:57] so the fix is easy! [07:57] morning sil2100 :) [07:57] sil2100: want to propose a branch? ;) [07:57] didrocks: ok ;) [07:57] sil2100: with some unit tests will be bonus! [07:57] Mirv, hey, I'm confused :) https://code.launchpad.net/~thomas-voss/dbus-cpp/fix-ppc64-el/+merge/211894 [07:57] says that it is merged [07:57] Will try, guess it won't be that hard ;p [07:58] sil2100: shouldn't, thanks! [07:59] tvoss: err. let's see.. it seems to have been published by robru (somehow) https://lists.ubuntu.com/archives/trusty-changes/2014-March/013069.html [08:00] Mirv, it used to be in silo 001 before [08:02] tvoss: it looks to me that sil2100 published it on Monday http://162.213.34.102/job/landing-001-2-publish/59/ :D maybe he can explain something to this confusion [08:02] I'm not seeing a line in CI Train where it got published [08:02] hmm, I remember publishing that in CI train [08:03] tvoss: and yes it build for ppc64el, and we got 100% pass on CI Train too from image #261 so I guess that counts as tested.. https://launchpad.net/ubuntu/+source/dbus-cpp/2.0.0+14.04.20140322-0ubuntu1 === vila changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: vila | CI Train support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: - [08:03] Mirv, so you don't need me to do anything, correct? :) [08:03] Mirv: I guess something racy happened, let's set it to landed I guess ;) [08:04] tvoss: yeah no need, let's get that silo to your newest process-cpp line then :) [08:04] sil2100: only free silo? [08:05] Mirv: yes, only free silo in the m&c, and then let's set it to Landed manually :) [08:05] running [08:05] Thanks o/ [08:05] Mirv, hang on, I need to bump build deps before we can do that [08:05] Mirv, give me ~15 [08:05] tvoss: ok [08:07] FYI we'd have the gallery-app click package built too, if we'd just have someone to push it to the store together with publishing landing-009 [08:18] cjwatson, for https://code.launchpad.net/~thomas-voss/process-cpp/fix-death-observer/+merge/211996 and your comment on build deps: Do I have to bump the build deps and make them versioned? [08:20] cjwatson, as in: requiring libprocess-cpp-dev (>= 1.0.0) in dbus-cpp for example [08:22] thomas has a silo now, so he can click build when the brances are double-checked to be ready [08:23] Oi, it has been a long day. I just realized I marked all my test results with image 261, but it was really image 262. [08:26] ToyKeeper: just update on the spreadsheet, thanks for the testing! [08:26] I already did. [08:26] Mirv, can I just add trunk branches to the silo as well? To check that everything still works together? [08:26] sil2100: hi [08:27] sil2100: there seems to be an issue with landing silo 002 [08:27] a message about a package in the unapproved queue [08:28] dbarth: let me take a look [08:28] dbarth: ah, might be due to the freeze [08:29] didrocks: btw. looking at the unit tests ;p When and where do we run those unit tests? As I already see a zillion unit tests that should fail in our case! ;) [08:29] tvoss: if you're not planning to publish those trunks, maybe just build the silo and then update to the silo locally and to the test builds? I mean, it becomes slightly tricky if there are "just out of interest" builds/branches in the PPA which need to be cleaned before publishing. [08:30] sil2100: hum, are you sure they are failing? I run them recently and they don't [08:30] tvoss: if you want non-x86 PPA builds, I can help by building in another PPA against the landing PPA after it has built [08:30] sil2100: nosetests tests/unit/ [08:30] sil2100: Ran 190 tests in 18.055s [08:31] didrocks: they wouldn't fail for me here, would have to modify it to 'do the wrong thing' - but looking code wise they should just fail, as all the test_refresh_symbols_files_* compare the resulting changelog with the 'right' one, and this should fail - let me experiment ;) [08:31] Mirv, alternatively, I could setup MPs for the packages that have a build and runtime dep on process-cpp, bumping the build-dep to libprocess-cpp-dev (>= 1.0.0) [08:31] Mirv, does that make sense? [08:32] sil2100: I don't use a mock dch, but let me check [08:33] sil2100: ah, so what's the way forward? [08:33] sil2100: yeah, only bzr, dput and sudo are mocked [08:33] tvoss: do they need the rebuild and the bumping of build-dep? if so, yes it makes sense, but if there is no need other than testing that they WOULD build against the new process-cpp, again I'd use another PPA that builds against that landing PPA [08:33] Mirv, I think I'm a fan of versioned build-deps here, so I would prefer bumping them [08:34] dbarth: I think we'll have to poke the release team and try to convince them that it's something we need to get pushed through [08:35] tvoss: if you can get approvals for the version bump MP:s similar to the other MP:s, sure I don't object :) [08:35] Mirv, ack :) [08:37] Mirv, could you have a look at http://162.213.34.102/job/landing-014-1-build/40/console [08:37] didrocks: so, when running the unit tests locally by emulating what's going on on the citrain device (i.e. a precise system with heuristics default to log), then I get all the test_refresh_symbols_* tests failing [08:37] didrocks: so on the citrain machine it has to be failing as well! [08:37] sil2100: ah, so making sense! [08:38] sil2100: let me see if I can install nosetest on the machine [08:40] didrocks: anyway, I was shocked on how many tests you wrote for this :o There's like almost every case supported :o [08:40] sil2100: I told you it's not some small scripts :) [08:40] ;) [08:40] Ran 190 tests in 21.974s [08:40] FAILED (failures=7) [08:40] sil2100: confirmed! [08:40] and the diff contains this :p [08:41] http://paste.ubuntu.com/7155572/ [08:41] which confirms the theory [08:41] sil2100: so yeah, my fault was to only run the test on my machine :p [08:41] didrocks: \o/ the branch for a quick-fix is here: https://code.launchpad.net/~sil2100/cupstream2distro/dch_heuristics/+merge/212788 [08:41] not a precise one [08:42] didrocks: yeah, who would have guessed there would be these subtle differences ;p [08:42] sil2100: excellent :) [08:42] sil2100: well, TBH, I've seen it while putting the train in production [08:42] and you can see I changed that when generating the changelog [08:42] didn't thought about the symbols file [08:42] though [08:42] tvoss: I checked them out and it looks like lp:~marcustomlinson/unity-scopes-api/scope_process_lifetime would need another sync with the trunk to have the latest changelog entry included too before bumping the version [08:43] sil2100: so approved! [08:43] tvoss: there was a release on Monday of it [08:43] sil2100: we'll put that in prod at the same time than the other changes (continuing on the spreadsheet refactoring for the request id support) [08:43] sil2100: feel free to merge manually to cu2d [08:44] didrocks: ah, we don't have an auto-merger? [08:44] sil2100: unfortunately, not [08:44] Ok :) [08:53] Mirv: are you handling Bill's gallery-app landing, or can I pick it up and publish? === tvoss is now known as tvoss|afk [08:59] sil2100: it needs the simultaneous click publishing, so we need someone that can push the (already built) click package too [08:59] sil2100: and I can't do that even though I was taught how to, since I forgot to ask sergiusens for crendentials yesterday [08:59] additionally, the Python publishing thing fails to run for me for some reason (it downloads random modules from the internet so maybe that's why) [09:02] seb128: morning! sorry to grab you as you arrive [09:02] but what you were worried about with the HUD sync has happened [09:02] seems my boss was immediate in following my instructions to clean the PPA [09:03] do you have any advice about what I should do? [09:03] hey pete-woods, I guess you need to put a new landing ask for the same vcs-es and do a new landing :/ [09:04] infinity, slangasek, ^ (silo cleaned while the copy was in trusty unapproved queue, is there any way around redoing a build/upload)? [09:06] I do actually have another MR I'd have liked to add, so I can just request another silo (and not clean this time) if that would work [09:06] then maybe just reject the sync? [09:06] sil2100: should i just go here on the channel and ask the release tema? [09:08] pete-woods, yes, rejecting the sync is fine [09:09] pete-woods, if you need a landing feel free to give me the merge requests urls, I can put one for you (I think thostr is off today) [09:09] seb128: the silo's in a weird state now, though, the branches have been merged, but the spreadsheet doesn't know it's clean [09:10] seb128: https://code.launchpad.net/~unity-api-team/hud/dbusmenu-safety-valve/+merge/212668 is the one [09:10] that branch is based on top of the merged trunk, though.. [09:10] sil2100: i'd like to flush the siloi to get started with the more important oxide branches for webbrowser-app [09:11] pete-woods, the weird state is because thostr stopped the clean job [09:11] pete-woods, but the ppa was already cleared [09:11] seb128: ah, he must have got my "wait, don't clean the PPA" ping too late [09:12] sil2100, Mirv, didrocks: what's the proper way to deal with that ^? [09:12] dbarth: yeah, sorry, let's try doing that - was busy with something [09:13] seb128: so, something was cleared, but the job was stopped? [09:13] seb128: and so unassignement didn't work? [09:13] pete-woods, seb128: so, branches are merged but packages still not released? [09:13] Or is everything in the archive and merged in properly, just the silo is still there? [09:13] didrocks, sil2100: right, the clean job was started, it merged back and send the clean ppa order, then the job was stopped [09:13] sil2100: yes, the packages ended up in the unapproved list [09:13] so things are merged&cleaned [09:14] seb128: wonder why people are doing that [09:14] hum [09:14] which silo #? [09:14] didrocks, because we overlooked that "sync to unapproved" are not copies [09:14] 11 [09:14] didrocks: silo 11 [09:14] seb128: what the link with sync to unapproved? [09:14] didrocks, those syncs are links to the ppa, so when you clean the ppa the item in the unapproved queue becomes void/can't be accepted [09:14] merge and clean will have failed with that [09:15] telling don't merge, things are in unapproved [09:15] didrocks, well, we didn't want to block the silo until beta freeze [09:15] otherwise we are going to be out of silo and locked down today [09:15] so override? [09:15] that's what happened [09:15] nice… :/ [09:15] until we realized that cleaned the ppa makes the upload unvalid [09:15] since the queue doesn't have a copy [09:16] just a pointer to the ppa librarian [09:16] everything was blocked or some components passed? [09:16] you mean? [09:16] didrocks: hud didn't make it, the other package did [09:16] ok [09:16] (libqtdbustest) [09:16] oh, right [09:16] I suggest that you bzr push --overwrite HUD trunk to the previous status [09:17] to reconcile with what's in the distro [09:17] then, we force m&c [09:17] and redo a landing [09:17] didrocks: should I go and reopen the MRs then? [09:18] pete-woods: yeah, rewrite history basically! :) [09:18] okay, cool, I'll do that then [09:18] pete-woods: seb128: if that request is set to landed, that's fine? [09:18] didrocks, can't we just add a landing for a new mp? [09:18] (that's what will happen) [09:18] that would do trunk + that new change [09:18] seb128: depends, is there any? [09:18] yes [09:18] ok, that can work as well [09:18] https://code.launchpad.net/~unity-api-team/hud/dbusmenu-safety-valve/+merge/212668 [09:18] if you don't let the ball dropping and we are not in a middle-state [09:18] pete-woods: ^ [09:19] * didrocks runs m&c with "only free silo" [09:19] didrocks: I'm happy with whichever way you guys think will work [09:19] let put a landing ask for ^ [09:19] * seb128 does that [09:19] pete-woods: yeah, so just file a new request with that branch, but please mention that the rest in the decription will land as well [09:20] it's just frustrating being "unapproved" for bug fixes while if I had a phone FFE I could land anything [09:20] anyway, I'm not interested in moaning, I will get that landing request in [09:20] pete-woods: we are in beta freeze, that's why desktop updates are blocked [09:20] I think the release team is making that more difficult that it should [09:20] they should let stuff in proposed and britney block [09:20] yep [09:22] and then people complain about Touch process ;) [09:24] didrocks, pete-woods, sil2100: l48 [09:24] sil2100: letting you assigned once the current silo is freed? [09:24] (should be refreshed in less than a minute) [09:25] sil2100: done, please assign [09:26] pete-woods: seb128: set manually the previous status to "Landed but HUD" [09:26] didrocks: should I explicitly specify that silo, or just leave citrain to decide which silo to use? [09:26] sil2100: let CI Train deciding [09:27] nothing remained in the silo [09:27] it's really freed and gone [09:29] dbarth: hmmm... [09:29] dbarth: actually, give me some time to think about how to proceed ;/ [09:30] sil2100: sure [09:30] sil2100: i just want to clear decks as much as you do i guess [09:30] Yeah, it's a sticky situation [09:30] seb128, didrocks, sil2100: thanks for sorting me out here , guys :) [09:31] |HELP [09:31] pete-woods: yw :) [09:32] ah interesting [09:32] So deletion and queues don't interact very well [09:32] popey: coming? [09:32] sorry, yeah [09:33] |HELP [09:33] I am the firendly image watchbot [09:33] :) [09:33] Laney, no they don't, pocket copies are not actual copies, they are pointers to the librarian [09:33] Laney, so when you clean the source you loose the data and the unapproved entry becomes invalid [09:33] firendly indeed [09:33] ogra_: I don't believe you [09:33] seb128: I see [09:33] heh [09:34] Not sure if that would be fixable in LP [09:34] but you could use an intermediate PPA [09:34] lol [09:34] more crazyness isn't the answer :p [09:34] just let thing in proposed and review there? [09:35] This argument is already hitting a wall, so I'll go and do something more useful [09:35] yeah, same here [09:35] I guess I don't care enough [09:36] let's hit the silos lockdown situation [09:36] I do, but if there is no option to change anything CI is doing then it's pointless even talking about it [09:36] but I guess that's going to come down back from management on why we lock everything then [09:36] Laney, I guess there is the option, but why isn't release open to consider changes as well? [09:39] Essentially I think that any process designed to work with the archive has to be able to deal with what it does, and that includes freezes sometimes [09:39] It could just be that LP can actually be fixed to work how we want it to here, but I don't know enough to say that [09:39] * Laney EOD :-) [09:39] * wgrant wakes up [09:40] o hai [09:40] Haven't ready all of scrollback, but is the problem that a copy sitting in the queue will fail if the source PPA has the source removed? [09:40] That should work if it's accepted within a week or so [09:41] Yeah [09:41] I assume there was an actual incident, but ... [09:41] infinity warned that if we clean the ppa we screw the items in the queue [09:41] we just took his words on it [09:42] Well [09:42] That was a problem back when stuff would sit in unapproved for weeks [09:42] But stuff is copiable until at least seven days after it was deleted from the origin. [09:42] Would it be possible to notice the reference made by a copy record? [09:43] Not in the current model. [09:44] Fair enough [09:44] There's a redesign in progress, but it's currently blocked on a couple of other big projects. [09:44] Well anyway, I think 7 days should actually be alright for our purposes [09:44] People start pinging after 7 hours, anyway. ;-) [09:44] right [09:50] sil2100: ^^^ you should be alright === tvoss|afk is now known as tvoss [09:53] didrocks: ^ [09:55] ok, then, just m&c with "ignore package in dest" [09:56] tvoss: I would tend not to unless the changes require the new APIs [09:57] cjwatson, yup, same here. But with that, we cannot easily add trunk for the build deps to the silo as per what Mirv said [09:57] dbarth: we might have a solution! [09:57] tvoss: or just wait until the new process-cpp is in trusty and then it won't matter [09:58] dbarth: let me get back to you in a some minutes [09:58] tvoss: bumping the build-deps isn't *wrong*, I wouldn't spend much time agonising about it, but it does impede situations where you might otherwise be reasonably able to backport things [09:58] cjohnston, ack and thanks [10:00] sil2100: ok [10:00] sil2100: Mirv: FYI, when I'll be in a little bit of a quieter place, I'll be able to finish the spreadsheet part and then switch to the new assignement silo/reconfiguration process [10:00] I'll keep you posted [10:03] ok [10:13] davmor2: can you give me the new bug # ref? [10:13] so that I can +1, set the appropriate priority as well [10:14] didrocks: ok ;) [10:17] didrocks: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1297770 [10:17] Ubuntu bug 1297770 in unity8 (Ubuntu) "Scopes scroll down till header goes seems to lock the scope in place" [Undecided,New] [10:19] didrocks: I added the secondary icons visible in header as I assume the two are linked [10:22] davmor2: yeah, I think they are [10:22] sil2100: this is the bug to give to the unity8 team as well ^ [10:23] davmor2: please mention it's a regression from latest promoted image and the image # [10:39] dbarth: ok, so, what we'll do - I'll merge and clean your silo (as we need to do some special handling) and then I can assign a new silo for your features [10:39] dbarth: it seems that we can do it now even [10:49] Mirv, Marcus and me are testing silo 14, would be great if you could setup a ppa for testing the process-cpp build-deps [10:51] sil2100: perfect [10:52] sil2100: need me to push some buttons? [10:52] dbarth: no no, all is handled from our side ;) [10:52] dbarth: which landing from your list is now the highest priority? [10:55] Mirv: so, you're going to publishin landing-002 as we discussde? [10:55] seb128: hi, the HUD silo has been tested (and succeeded) now, would you be able to mark it as such for me? [10:56] Mirv: I'll publish the gallery-app silo in the meantime [10:56] tvoss: you can set one at https://launchpad.net/~thomas-voss/ or I can push builds to some PPA when you give me a list of packages to build against the landing PPA [10:56] sil2100: thanks [10:57] Mirv, ack [10:58] seb128: thanks :) [10:59] pete-woods, yw ;-) publishing as well (just not cleaning this time) [10:59] :) [11:00] tvoss: so which way, your PPA or my PPA? :) [11:00] sil2100: uh sorry; it's line 18 [11:00] Mirv, your PPA :) [11:01] tvoss: does this happen to be the correct set: connectivity-api dbus-cpp platform-api platform-api unity-mir unity-scopes-api ? (reverse-depends -b libprocess-cpp-dev) [11:01] dbus-cpp unity-mir and unity-scopes-api are sufficient [11:03] didrocks: so it looks like the header in it's current format will be removed so what do you want to do about it? [11:03] davmor2: I won't take any decision, I guess it's your/QA decision to take [11:04] for it being a promotion blocker or not [11:04] like, are we happy to have users with such bugs on their phone [11:04] Oh I wouldn't block on it [11:09] tvoss: rebuilds of those against landing-014 visible now at https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta-proper/+packages?field.name_filter=&field.status_filter=published&field.series_filter=trusty [11:09] Mirv, thank you [11:20] dbarth: oh, but line 18 is still not set to ready - is it ready? [11:24] Mirv, what's up? How were you shown the process? [11:31] sergiusens: morning! Could you release a new gallery-app to the click store? :) [11:31] sil2100: ah wait, yes i was putting on hold [11:31] sil2100: just re-checking the branches real quick [11:32] sil2100, yeah [11:32] sil2100: oh and they're stacked on each other, so i need to flatten that first [11:33] dbarth: ok, just give me a poke once it's ready and I'll assign a silo then :) [11:33] sergiusens: thanks [11:40] sergiusens: the gallery-app would need publishing as sil2100 said. balloons showed me the jenkins job(s) that can be used to build click packages, and explained lp:click-toolbelt having a tool to push those packages [11:44] Mirv, yeah, can you install click-toolbelt into a vitualenv? [11:45] sergiusens: nope, since the install fails at some point to "TypeError: dist must be a Distribution instance" [11:46] Mirv, yeah, make the virtualenv python2 [11:46] Mirv, we need to tell pindonga about that py3 bug === vila changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: - [12:21] sergiusens: (first time using virtualenv) even if I use virtualenv --python=python2.7 I get the same error. installing python-stevedore from archives instead of fetching it via the easy_install resolves that problem at install time, but I still get some DistributionNotFound error when trying to execute the resulting bin/click-toolbelt [12:21] hm, I don't have that error [12:22] some pastebin instructions on how you install lp:click-toolbelt could be enlightening [12:23] Mirv, all I did from trusty was; virtualenv [path]; [path]/bin/activate; bzr branch lp:click-toolbelt; cd click-toolbelt; python setup.py install [12:25] Mirv, anyways, direct uploads is broken... talking to pindonga about it and he confirmed... http://paste.ubuntu.com/7156378/ [12:26] manual uploads seem broken too :-/ [12:27] sergiusens: tried http://pastebin.ubuntu.com/7156410/ [12:27] sergiusens: right [12:28] Mirv, try installing oauthlib locally [12:28] popey: are you getting the welcome screen locking for a while most times you wake the device? [12:28] yes [12:28] suspected it's the queuing issue [12:29] yeah [12:29] it seems to take longer the longer it was suspended [12:29] which kind of points to the queue issue [12:29] sergiusens: both python-oauthlib and python3-oauthlib seem already installed, or do you mean locally as in force its installation to the virtual env too? can try. [12:29] takes nearly 30sec in the morning for me [12:30] that's the answer I was hoping for atleast :) [12:30] sergiusens: thanks for the e-mail anyway, in case I'm required to do some publishing at some point [12:30] i guess there is a lot of sensor events and such that pile up [12:31] * davmor2 must remember to try ringing his phone after it has been off for a while, now where did I put that pad [12:31] heh, did anyone try the new scopes on flo already ? [12:32] the font in my Apps header is slightly moved to the center after boot [12:32] only moves to the left once i switched back and forth between scopes [12:32] Mirv, sure, just copy that into~/.config/click-toolbelt/click_toolbelt.cfg [12:34] Mirv, ok, with python3 (and yes this feels broken), just do python setup.py install in a loop until it works (just tried myself) [12:36] sergiusens: ... [12:36] sergiusens: works :S [12:36] ;) [12:37] Mirv, ugly; but the dev told me to do this; it's one of the reasons I asked for proper packaging on the list... [12:37] this fits well in my (granted, very limited) experience of "easy" install, ruby gems and so on [12:38] sergiusens: ok, I'm set up then, in case the uploads start working at some point and something in addition to the currently pending gallery app is needed during EU timezones [12:39] * davmor2 has poached popey 's excellent idea of a pad for quick notes/bugs you need to file :) [12:40] unfortunately it's now filling up :) [12:40] geez, just dont add stuff then ! [12:42] Mirv, sil2100 so I can't upload the new gallery until the store gets fixed [12:42] popey: erm what. On the desktop pull down the system inidcator what is lock now called :) [12:44] sergiusens: ok... any ETA on that? [12:46] davmor2, not sure what you describe, the indicator-session items didn't change [12:47] sil2100, I don't have one [12:50] Mirv, I would like to the unity-scopes-api branch out of the silo [12:50] sergiusens: Mirv: ok, the spreadsheet is ready… I'm going for a run now. However, we'll see depending on ping crazyness if I deploy it today or tomorrow [12:50] Mirv, take it out [12:50] tvoss: you can do that yourself [12:50] tvoss: just reconfigure with the list of MP and remove the unity-scopes-api from it [12:51] (but we need to remove the package if there is no more MP associated to it) [12:51] didrocks, in the silo tab? [12:51] tvoss: yeah, if unity-scopes-api has been built from a MP [12:52] tvoss: if you do that ^ I can remove the package fro the PPA [12:53] didrocks, Mirv when I try to alter in the silo tab, I only get a formula [12:53] * tvoss is scared [12:53] tvoss: hum, see the "reconfigure" button? [12:53] seb128: in the live session it's called start screensaver I'm assuming because there is no password for lock. I was just double checking that it was lock on a real desktop rather than rebooting [12:54] davmor2, real desktop is fine [12:55] seb128: okay cool [12:58] didrocks, Mirv I reconfigured here: http://162.213.34.102/job/landing-014-0-reconfigure/9/ [12:58] great :) [12:59] tvoss: looks good :) I removed the unity-scopes-api from the PPA now [13:00] Mirv, thanks [13:02] sil2100, seems the bug is soon to be solved; given it's backened it might take a bit to propagate === alan_g is now known as alan_g|lunch [13:04] sergiusens: excellent! [13:08] didrocks: hello, we are discussing adding a staging branch for the ubuntu-ui-toolkit [13:08] didrocks: I have a proposal here https://docs.google.com/a/canonical.com/document/d/1rgXqqCeGg9JjHEHmDHOfhBJOGTgk7luBuBbpzNTMMLk/edit# [13:08] didrocks: it would be good to get your feedback/approval on that :) [13:09] * sil2100 goes for a longer lunch [13:21] Mirv, okay, with silo 14 reconfigured, and the rebuild packages from your ppa, things still work. Could you give it a quick spin, too? [13:31] didrocks: hello there. How can I become a lander for ubuntu-push? :) [13:32] tvoss: ok I updated my phone with those two PPA:s and even removed the libprocess-cpp0, indeed I don't notice anything different [13:33] Mirv, okay, that's good in this case, so I will set the silo to tested [13:33] Mirv, thanks for the help :) [13:33] Mirv, done [13:34] is there an easy way to point at a /usr/lib/{multiarch}/yadda/yadda from an upstart script? [13:38] tvoss: ok. I'm going to run "watch only" build job now first since it seems the spreadsheet doesn't update correctly. [13:38] oh, right there's an eternal build job running already [13:39] so, let's see if watch only correctly notices just the process-cpp [13:40] tvoss: darn, you've a small ppc64el problem that would prevent the package from migrating to release pocket since it built there before: https://launchpadlibrarian.net/170746201/buildlog_ubuntu-trusty-ppc64el.process-cpp_1.0.0%2B14.04.20140326.1-0ubuntu1_FAILEDTOBUILD.txt.gz [13:41] why that is only on ppc64el I don't know [13:44] tvoss: and the build problem wasn't visible on the dashboard since there was a stalled build job running for the silo that waited eternally for unity-scopes-api [13:44] should be trivial to change anyway [13:53] Mirv, cjwatson updated the symbols file [13:53] sergiusens: are you able to find time to drive (test) your landings in silos 010 (phablet-tools) and 005 (usensord, platform-api) soon? just wondering since they've been built for quite some time now. [13:53] still weird ... [13:53] tvoss: ok! kick a rebuild then. now it shouldn't stall on unity-scopes-api anymore. [13:54] sil2100: silo-13 ready to be released [13:54] Mirv, I thought usensord and platform api were unassigned already two weeks ago+ [13:55] Mirv, for silo 10; I can deal with that today if doanac has a minute to spare [13:55] Mirv, kicked [13:55]