[00:42] <bfiller> robru: hmn, no idea
[00:43] <kenvandine> bfiller, rogue robots proposing branches? :-D
[00:44] <bfiller> robru: those MR's have already been merged from the ubuntu release
[00:45] <robru> bfiller: great
[00:45] <robru> bfiller: did you test it in rtm?
[00:46] <bfiller> robru: yes I tested the click package in both ubuntu and rtm
[00:46] <bfiller> works fine
[01:08] <kenvandine> it's pretty amazing... the here location service stuff is working really well on my mako!
[01:09] <kenvandine> totally not working on my krillin...
[01:09] <kenvandine> but... it gets a location amazingly fast on mako :-D
[01:09] <kenvandine> and it's nice to see the apps listed on location access in system-settings :)
[01:15] <ToyKeeper> bzoltan: Not sure if you're around, but the uitk silo appears to introduce at least six new test failures in ubuntu-system-settings.  :(
[01:15] <kenvandine> ToyKeeper, that makes me sad :(
[01:15] <kenvandine> ToyKeeper, bug i'm am really thankful you are catching them :)
[01:15] <kenvandine> s/bug/but
[01:16] <ToyKeeper> ... should have found it earlier, but it sounded like brendand had another issue blocking it so I was waiting on him.
[01:23] <jdstrand> hmmm
[01:24] <robru> jdstrand: citrain woes? I broke everything, working on it though
[01:24] <jdstrand> robru: I needed to copy in a new version of apparmor to utopic silo 014
[01:24] <jdstrand> ok
[01:25] <jdstrand> yeah I tried a reconfigure, had an error so I did a prepare. the prepare had an import error
[01:25] <jdstrand> so, I leave you to it
[01:25] <jdstrand> I'll*
[01:25] <jdstrand> (this was utopic silo 014 if you wanted something to look at)
[01:25] <robru> jdstrand: nope I got it, thanks
[01:26] <jdstrand> cool. I'll keep an eye out here for when things are fixed again
[01:26] <jdstrand> thanks
[01:26] <robru> jdstrand: ok it should be working right now, please try again ;-)
[01:27] <jdstrand> oh, that was fast :)
[01:27] <robru> jdstrand: yeah it was a silly mistake, fixed it easily ;-)
[01:27] <jdstrand> ok, the reconfigure worked
[01:34] <kgunn> robru: hesitant to ask you in the midst of ci-woes, but any ideas or help on stuck unity8 migration? silo19
[01:35] <jdstrand> robru: all seems fine, thanks!
[01:37] <robru> jdstrand: you're welcome!
[01:37] <robru> kgunn: not sure, retrying the adt runs for you
[01:37] <robru> (apparently I can do that...)
[01:38] <kgunn> thanks...
[01:38] <robru> kgunn: but otherwise you should ping an #ubuntu-release person for -proposed migration issues, like infinity or cjwatson
[01:39] <kgunn> i see in ubuntu-release some discussion about it...and it being complex and may need a
[01:39] <kgunn> a pitti to look at it
[02:04] <imgbot> [02:06] <robru> https://ci-train.ubuntu.com/job/deploy-citrain/250/console God. Fucking. Damnit.
[02:06] <robru> I want that hour of my life back.
[02:07] <robru> http://bazaar.launchpad.net/+branch/cupstream2distro/revision/721#citrain/manual/jenkins-templates/prepare-silo-manual.xml.tmpl
[03:04] <imgbot> [03:41] <bzoltan> robru:  are you still around?
[03:41] <bzoltan> I do not get what the problem is here: https://ci-train.ubuntu.com/job/ubuntu-landing-010-1-build/52/console
[03:49] <imgbot> [03:50] <imgbot> [04:11] <Mirv> bzoltan: the gles upload probably gets rejected for some reason or another. as you can see, ppa doesn't have it despite multiple builds
[04:12] <bzoltan> Mirv:  I see that. What i do not see is why it happens
[04:12] <bzoltan> Mirv: "Some source packages were never published in the ppa" No shit, Sherlock ... that is a new package I just added to the sheet.
[04:13] <bzoltan> Mirv: and the QtC pugin package gets rejected too in the same PPA.
[04:16] <Mirv> I don't see anything wrong with the mp :(
[04:19] <bzoltan> Mirv:  Me neither. Maybe a reconf helps
[04:19] <imgbot> [04:20] <imgbot> [04:21] <bzoltan> Mirv:  the good thing is that I managed to pull off the test plan for the UITK. It is all good. All the tests are at east as green as the RTM is. Only the camera app is freezing, but that is not UITK related.
[04:24] <bzoltan> Mirv:  and the other proble is that the cick+qtc-plugin-ubuntu is blocked http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[04:24] <bzoltan> Mirv:  and so that blocks the next landing :(
[04:25] <bzoltan> Mirv:  What the hack? "dpkg-source: error: cannot fstat file ./ubuntu-ui-toolkit-gles_1.1.1239+14.10.20140908.orig.tar.gz: No such file or directory"
[04:28] <ToyKeeper> bzoltan: Not sure if you saw it earlier, but the uitk silo appears to introduce at least half a dozen new test failures into ubuntu-system-settings.
[04:29] <bzoltan> ToyKeeper: I have logs from the 128 AP tests of the ubuntu_system_settings. Al OK
[04:29] <bzoltan> All
[04:29] <ToyKeeper> bzoltan: I got 6-7 failures out of 128.  The base image was 122/122 pass.
[04:30] <bzoltan> ToyKeeper: I was running during my night against the  image #233
[04:31] <bzoltan> ToyKeeper:  here are the logs ->  http://paste.ubuntu.com/8296368/
[04:31] <ToyKeeper> The base image I used was krillin rtm 23.  I don't really care much what the results were on a non-krillin non-rtm image.
[04:32] <ToyKeeper> At least, for a rtm landing anyway.
[04:32] <bzoltan> ToyKeeper:  I have run 17 times the  ubuntu_system_settings tests during the last 7 days. Never seen  a single faiure.
[04:33] <bzoltan> ToyKeeper:  I can take a look.
[04:34] <bzoltan> ToyKeeper:  do you have the logs?
[04:35] <ToyKeeper> bzoltan: Yes, I just pastebinned it...  looks like it exceeded the scrollback though, so I'd need to re-run to get anything before the beginning of the log.  https://pastebin.canonical.com/116558/
[04:35] <bzoltan> ToyKeeper:  The lanidg process of the UITK is that first I test the silo against the Ubuntu image. If that is OK then we land on Ubuntu. After that I test the RTM sio against the latest RTM image. So double testing... now I am working with the Ubuntu  image.
[04:36] <Mirv> bzoltan: right, that migration needs resolving first. I tried reconfiguring the new silo but I think it's probably something else. very weird errors.
[04:37] <ToyKeeper> bzoltan: FWIW, on two successive test runs, I got 6 failures the first time, 7 failures the second.  What changed between was I moved a bunch of stuff out of ~/ on my notebook, since the first logs seemed to include a 'cd ; echo *' and I wanted to rule out weird file names as a cause of errors.
[04:38] <bzoltan> ToyKeeper: What image do you test agains?
[04:39] <ToyKeeper> bzoltan: Latest krillin rtm image, whatever it is.  Today it was #23.
[04:39] <bzoltan> ToyKeeper:  The first few faiures are "autopilot.exceptions.StateNotFoundError: Object not found with name '*' and properties {'objectName': 'dialpadSounds'}." That is a classic flakiness
[04:40] <ToyKeeper> I saw some other failures, but those were all present in the base image too.  Only ubuntu-system-settings changed after adding the silo, though I didn't make it all the way through all the components so there could be others.
[04:40] <bzoltan> ToyKeeper:  who is developing the AP tests for that app?
[04:41] <ToyKeeper> bzoltan: Flakiness?  Not sure who wrote those bits of code.
[04:42] <bzoltan> ToyKeeper: Few question ... have you checked the version of the UITK before and after adding the silo? Was the ~phablet/autopilot/ubuntuuitoolkit diectory removed?
[04:42] <ToyKeeper> bzoltan: In any case, it seemed curious that 6 tests were added and 6-7 tests failed.
[04:42] <ToyKeeper> At the moment I don't have the silo installed.
[04:43] <bzoltan> ToyKeeper:  I do not know what causes the problem there :( But the logs do not point  to the UITK
[04:44] <ToyKeeper> bzoltan: In any case, I add the PPA, disable all other package sources, apt-get dist-upgrade, re-add the basic package sources, then run the autopilot tests.  In this case it failed to run at all the first time due to a gpg error, but after overriding that I was able to get test results.
[04:44] <ToyKeeper> (overriding == manually apt-get install the two packages apt complained about, then re-run phablet-test-run)
[04:45] <bzoltan> ToyKeeper:  I do not like to run apt-get dist-upgrade because it brings other packages too
[04:45] <ToyKeeper> bzoltan: That's why I disable all other package sources first... so that it can *only* get packages from the silo.
[04:45] <bzoltan> ToyKeeper:  I see
[04:46] <ToyKeeper> It seems like there are probably process differences to explain the different test results...  but I'm not sure what the process differences are.
[04:46] <bzoltan> ToyKeeper:  I am struggling a lot with the AP tests.. and when I say a lot I do mean it :) let me show how I do it.
[04:47] <ToyKeeper> For me, I flash fresh and wipe, then manually get online via nmcli, install the silo as described earlier, reboot, then go through the welcome wizard, set a time zone, disable automatic updates, reboot to work around the current OSK bug, then remount / rw and start on the AP tests.
[04:48] <bzoltan> ToyKeeper: http://paste.ubuntu.com/8296476/  `./uitk_test_plan.sh -c -p ppa:ci-train-ppa-service/landing-010 -f system_settings`
[04:48] <ToyKeeper> Er, re-adding regular package sources before starting on the AP tests since otherwise they can't even install.  And sometimes I have to manually install a couple packages from the silo first to work around missing gpg keys.
[04:49] <ToyKeeper> bzoltan: I do not have uitk_test_plan.sh...  I have only https://wiki.ubuntu.com/Process/Merges/TestPlan/ui-toolkit
[04:49] <bzoltan> ToyKeeper:  That script is in the UITK source tree tests/ and this version is in the actual release candidate.
[04:49] <bzoltan> ToyKeeper: that script executes the UITK tesp plan.
[04:50] <bzoltan> ToyKeeper: It is a lot help ...
[04:50] <ToyKeeper> If the test plan is a shell script, the documentation needs to point to that instead of what it says now.
[04:50] <bzoltan> ToyKeeper: I need to update the test plan
[04:51] <ToyKeeper> QA is executing the test plan in the wiki, because that's what's linked to from the landing spreadsheet.
[04:51] <ToyKeeper> If the test plan is wrong, it's kind of an automatic fail.
[04:51] <bzoltan> ToyKeeper: That script is a new development. I made it to make my life less miserable.
[04:52] <bzoltan> ToyKeeper: I do not think QA would ever run my script :)
[04:52] <bzoltan> ToyKeeper:  that script is for local validation
[04:53] <ToyKeeper> I was very tempted to make a script like that earlier today, since uitk tests are almost entirely automated anyway.
[04:54] <ToyKeeper> I'm happy to see there is one, but we need to get you and QA testing the same things or we'll end up with failed landings like today.
[04:55] <ToyKeeper> I'm of the opinion that anything which can be automated should be.
[05:33] <Mirv> hmmh
[05:34] <Mirv> robru: I've a weird problem where even after manual prepare-silo reconfig (https://ci-train.ubuntu.com/job/prepare-silo/1897/console) watch_only build gives nothing (https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-020-1-build/5/console). not sure if it could be related to your latest batch of changes.
[06:05] <bzoltan> mvo_: the cick and qtc plugin landing is stuck. Do you know how to make it move?
[06:05] <bzoltan> mvo_:  http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html  -> autopkgtest for click 0.4.29.1build1: Regression
[06:06] <robru> bzoltan: that looks like a failure to upload, id guess you should rebuild but it seems that hadn't worked for you. Not sure what else to try. Can Mirv do a manual upload for you?
[06:06] <robru> I mean the one you pinged me about
[06:07] <bzoltan> robru:  I have tried all combination of rebuilds... it seems that the silo is busted
[06:07] <robru> bzoltan: I'm afk but Mirv should be able to free and reassign
[06:08] <Mirv> robru: I think manual upload might be the only option, or indeed freeing and reassigning
[06:08] <Mirv> robru: that gallery-app rtm-020 silo is really weird
[06:09] <robru> Mirv: yeah i have no idea what happened there. If it's a problem just free it and resynchronize utopic
[06:10] <robru> Brb
[06:10] <Mirv> I'll do that
[06:10] <Mirv> or hmm, I could take someone to simply publish it manually
[06:16] <mvo_> bzoltan: yeah, we are waiting for the ubuntu-rtm QA verification
[06:16] <mvo_> bzoltan: the click/packagekit changes need to land there as well
[06:17] <mvo_> bzoltan: I should have waited with the publishing to -proposed even until it lands in ubuntu-rtm, but I made a mistake here
[06:19] <Mirv> bzoltan: ok I was able to upload the -gles package there manually now. the qtcreator plugin will succeed once the previous landing has properly finished.
[06:20] <bzoltan> mvo_: Is not that regression mark a problem?
[06:20] <mvo_> bzoltan: that too, there is also a explicit bugreport to prevent it from leaving utopic-proposed
[06:20] <mvo_> bzoltan: I look at the test failure right now
[06:21] <bzoltan> mvo_:  thanks. I totally forget about that landing. Because it actually blocks the next landing.
[06:22] <Mirv> mvo_: is the click transition also breaking the unity8 migration to release pocket? http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html - regressions in qtcreator-plugin-ubuntu/unity-scope-click
[06:24] <Mirv> mvo_: hmm, is the rtm 003 really going forward since it's not marked as having been tested by upstream? ie is it on QA team's radar?
[06:24] <Mirv> it was not even marked as "Ready", but I changed that to Yes now that it had a silo and had built already
[06:28] <mvo_> Mirv: oh? well I tested it yesterday and it should be good on utopic
[06:28] <mvo_> Mirv: its waiting for QA for the ubuntu-rtm landing
[06:28] <mvo_> Mirv: or am I missing something?
[06:37] <Mirv> mvo_: the line 39 says "Packages built", it's not "QA needs to sign off"
[06:37] <Mirv> mvo_: there's no "Testing pass?" set to "Yes" together with the rtm image number it was tested by upstream
[06:38] <Mirv> so upstream tests first, only after that QA will start testing
[06:38] <mvo_> Mirv: sorry for that, let me fix it
[06:40] <mvo_> Mirv: I did test this in the line before for the normal ubuntu utopic archive, pardon my ignorance about the workflow, I will retest this with the ubuntu-rtm channel image now (that is correct?)
[06:41] <Mirv> mvo_: ok! yes, the rtm landing should be tested separately on the rtm image, and even noticing that apt-add-repository doesn't work correctly (unless it got fixed) so you need to edit sources.list manually to add that rtm-003 silo
[06:42] <mvo_> Mirv: thanks, download is now running
[06:59] <Mirv> cjwatson: if you don't mind, we've a very problematic silo and would need ./copy-package -d ubuntu-rtm -s 14.09 --ppa=ci-train-ppa-service --ppa-name=landing-020 --to-primary --to-distribution=ubuntu-rtm --to-suite=14.09-proposed gallery-app
[07:00] <Mirv> cjwatson: it's cosmetics mostly, since it's not installed from archives anyhow and is already in the store, but just so I can mark that problematic rtm silo as "done" at some point.
[07:00] <Mirv> the silo just doesn't want to recognize there's something in it...
[07:19] <didrocks> cihelp: ps-trusty-desktop-amd64-1 is down, can you turn it back up, please?
[07:27] <Mirv> thanks mvo!
[07:28] <Mirv> brendand: we'd have rtm-003 (signature checking etc) as a priority one landing to QA, since it's blocking next landings in both utopic and rtm (interestingly)
[07:28] <Mirv> since the utopic + rtm landings need to go hand in hand, and now the utopic landing is stuck in proposed and probably also the reason why unity8 is in utopic proposed still
[07:31] <brendand> Mirv, i guess that's my next port of call then
[07:32] <vila> didrocks: there is a migration going on from the lab to the cloud and given the number of ps-* slaves offline I suspect they are involved. You want to check with ev/fginther (I've been in vacations then ill so I don't know the details)
[07:33] <didrocks> vila: he told me that for now we keep that machine until the migration is complete
[07:33] <didrocks> vila: and he rebooted it yesterday as well, due to the same issue
[07:33] <didrocks> so, if you can reboot it, that would be appreciated so that the daily tests can run :)
[07:33] <vila> didrocks: urgh, ok, let me see if those beasts are documented
[07:34]  * didrocks crosses fingers :)
[07:34] <didrocks> vila: it's a vm AFAIK
[07:34] <Mirv> brendand: that's a bit what I was thinking, thanks :)
[07:36] <brendand> except my krillin is not charged - hmmm.
[07:36]  * brendand waits a few minutes
[07:38] <vila> didrocks: the server is running but I can't connect via ssh (no credentials for me there), do you know where the VM is hosted ?
[07:39] <didrocks> vila: I guess on the same that the i386, I can connect on that one, but unsure how to know where the host is?
[07:40] <vila> hehe
[07:40] <didrocks> vila: the IP of the i386 vm is 10.98.2.79, if that can help
[07:40] <vila> no idea
[07:41] <didrocks> vila: s-jenkins is the jenkins connected to it
[07:41] <vila> that was my guess, I'm there and searching
[07:42] <didrocks> vila: http://s-jenkins.ubuntu-ci:8080/computer/ps-trusty-desktop-amd64-1/
[07:42] <vila> didrocks: that doesn't tell us much does it ?
[07:42] <vila> didrocks: that's where the vm connect to but it can be anywhere
[07:43] <didrocks> yeah…
[07:44] <vila> no /var/lib/libvirt on s-jenkins, probably not there
[07:45] <didrocks> vila: ssh naartjie /usr/bin/sudo virsh snapshot-revert ps-trusty-desktop-amd64-1 1410056823
[07:45] <didrocks> naartjie maybe?
[07:46] <didrocks> vila: it's back online, calling the snapshot revert virsh command
[07:47] <vila> didrocks: looks more promising
[07:48] <didrocks> vila: so yeah, it's up now thanks to that, don't bother more! Thanks for looking :)
[07:48] <vila> ack
[08:02] <brendand> ogra_`, what's the new option i need to specify to get developer mode enabled after flashing?
[08:02] <brendand> ogra_`, apart from --developer-mode of course
[08:05] <ogra_`> pren--password=
[08:05] <ogra_`> err
[08:05] <ogra_`> brendand, --password= ... with a password supplied
[08:07] <ogra_`> robru, no landing mail ?
[08:13] <Mirv> I more or less know the situation, but maybe robru will write a belated landing mail in his morning :)
[08:15] <ogra_`> Mirv, yeah, its not for me, i have some followers on G+ that read my re-post of them every day though
[08:15] <ogra_`> whats that dirt on my nick ?
[08:15] <ogra_> wiped away :)
[08:16] <Mirv> :)
[08:16] <ogra_> pete-woods, hmm, did you do the seed meger yourself ?
[08:16] <ogra_> *merge
[08:17] <ogra_> (the commit message looks like ...)
[08:18] <pete-woods> ogra_: I have no idea how I'd even do that
[08:18] <ogra_> funny ...
[08:20]  * ogra_ just wanted to merge but notices that someone else did already ... and bzr log only has your name 
[08:20] <ogra_> (whoever did it forgot to re-generate the metapackage)
[08:29] <ogra_> Saviq, whats up with https://code.launchpad.net/~unity-team/unity8/new-adbd/+merge/233684 ? greyback set it to "needs fixing" at 19:30 with some serious error message and 30min later he set it to approved without explanation
[08:30] <Saviq> ogra_, the error was only for our run-on-device script, so no impact on anything
[08:30] <Saviq> ogra_, it's currently stuck in proposed due to oxide-qt fiasco
[08:30] <Saviq> dbarth_, you around?
[08:31] <ogra_> Saviq, ah, ok
[08:34] <dbarth_> Saviq: yes
[08:35] <Saviq> dbarth_, we have a problem with the oxide-qt 1.2 landing, they got stuck in proposed because oxide-qt is 1.2~, which is lower than 1.2
[08:35] <dbarth_> uh
[08:35] <Saviq> dbarth_, is there an actual oxide-qt 1.2 coming somewhere, or should the dependencies be >= 1.2~?
[08:35] <Mirv> Saviq: I thought unity8 is stuck because of the click landings in -proposed?
[08:36] <Saviq> Mirv, no, it's because ↑
[08:36] <dbarth_> Saviq: we should adjust dependencies
[08:36] <dbarth_> or rather
[08:36] <dbarth_> 1.2 official should be in 1-2 weeks max.
[08:37] <Mirv> Saviq: ok, just looking at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html autopkgtests failed for unity-scope-click and qtcreator-plugin-ubuntu, but do those fail because of oxide and not click?
[08:37] <dbarth_> i don't have the schedule in mind, but we get a stable evey 6 weeks; and we just branched off 1.3 so 1.2 should be declared stable official soon
[08:37] <Saviq> Mirv, that's what jibel_ found, yes
[08:37] <Mirv> ok
[08:37] <dbarth_> that won't help fo today, so the easiest is to adjust deps i think
[08:38] <Saviq> dbarth_, yeah, Mirv, can you please upload webbrowser-app and ubuntu-system-settings-online-accounts with the deps adjusted?
[08:39] <Mirv> I'll help with silos when just told so
[08:39] <dbarth_> do you want me to upload a new set of packages to fix that?
[08:40] <davmor2> tvoss, thostr_: RTM silo004 we are finally able to test it.  I wanted to know though how quick should I get a fix?  With it in place though location service stops crashing, but trust store is still crashing
[08:41] <tvoss> davmor2, sorry, gimme 10 to context switch
[08:42] <Saviq> Mirv, I thought you could upload directly to proposed to not wait for silo?
[08:44] <Mirv> Saviq: no, I can't. in two weeks possibly for some packages.
[08:45] <Mirv> and Qt I can upload
[08:45] <thostr_> davmor2: that tvoss to answer. however, I'm wondering whether the packages can - after successful testing - be published or just manually as we did with utopic. lool?
[08:45] <Saviq> Mirv, oh ok, can dbarth_ use the same silo then? can it be un-published?
[08:46] <dbarth_> ok, so i just rebuild in silo 2 and ping you back once done
[08:46] <dbarth_> Mirv: i'll double check deps with you in a minute
[08:50] <dbarth_> Saviq: actually there is an oxide-qt-1.2!
[08:50] <dbarth_> https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages
[08:50] <dbarth_> we prepared it last friday and i thought this was the one stuck
[08:51] <popey> Mirv: when you get a moment could you push http://s-jenkins.ubuntu-ci:8080/job/terminal-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.terminal_0.5.141_armhf.click to the store?
[08:51] <dbarth_> so the webbrowse-app dependency is correct
[08:52] <popey> Mirv: also http://s-jenkins.ubuntu-ci:8080/job/filemanager-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.filemanager_0.3.275_armhf.click  please
[08:53] <Saviq> dbarth_, when will it reach proposed at least then?
[08:54] <Saviq> dbarth_, because until it's in https://launchpad.net/ubuntu/+source/oxide-qt, stuff's broken
[08:54] <Saviq> dbarth_, so you know the fallout, even unity8 is blocked in proposed currently
[08:54] <brendand> mvo_, hello - i am testing silo 3
[08:55] <Saviq> dbarth_, because UITK and click scope tests can't run due to the unsatisfiable dependency
[08:55] <Saviq> and that's what unity8 is gated on
[08:57] <dbarth_> Saviq: let me ask for the proposed copy; either its that, or a larger revert for silo 2, because the silo does *not* work with the older oxide build
[08:58] <brendand> seb128, i'm hitting some problems with the reset device option on image 24 (which has the updated system settings)
[08:58] <Mirv> Saviq: sorry still in meeting. same silo can probably be used in this case.
[08:58] <brendand> seb128, i recall kenvandine mentioned last week that he saw the same thing (before landing it)
[08:58] <seb128> brendand, what sort of reset?
[08:59] <seb128> brendand, the factory reset?
[08:59] <brendand> seb128, yeah erase and reset everything
[08:59] <davmor2> seb128: reset launcher is that meant to clear off any pinned apps if so it doesn't
[08:59] <dbarth_> Saviq: who has permissions to binary copy stuff to -proposed?
[08:59] <brendand> seb128, after pressing the button nothing happens
[08:59] <seb128> brendand, no idea about that, I never tried it and didn't work on it
[08:59] <seb128> davmor2, it's meant to reset the launcher as the title suggest
[08:59] <dbarth_> Saviq: from a test pov, i have checked that new build of oxide with webbrowser + core webapps, so it's good to go
[08:59] <seb128> davmor2, it only apply after restart, the dialog tell you about that no?
[09:00] <brendand> seb128, ok. is there anyone else around who might know about it or i suppose i need to wait for kenvandine?
[09:00] <seb128> brendand, jgdx but he might not be on yet
[09:00] <davmor2> seb128: no just a push button that says reset launcher there is no text anywhere
[09:01] <Saviq> dbarth_, archive admins at the moment probably, the correct thing to do would be to dput it in a silo (even the same silo as the webbrowser and settings)
[09:01] <davmor2> seb128: oh no it thows up a popup
[09:01] <Saviq> dbarth_, that Mirv can help you with (right Mirv?)
[09:01] <davmor2> that didn't happen before
[09:01] <Mirv> Saviq: dbarth_: no I can't, you'll need a core-dev to copy to archives
[09:01] <brendand> cjwatson, is mvo_ around today?
[09:01] <seb128> davmor2, :-)
[09:01] <Mirv> like ogra_ (in the same meeting)
[09:02] <seb128> brendand, he is, he said he had to be away from some minutes, a bit earlier on #distro
[09:02] <Mirv> brendand: he was in the morning
[09:02] <davmor2> seb128: by before I mean like 2 minutes ago when I tried it
[09:02] <Mirv> where I got him to test the rtm silo
[09:02] <seb128> davmor2, weird, I can't confirm that, wfm
[09:02] <davmor2> seb128: might just of been a glitch
[09:02] <seb128> could be
[09:04] <Mirv> dbarth_: can you reiterate to ogra_ what needs to be copied from where to utopic-proposed to fix oxide, and why doe it fix that?
[09:05] <Mirv> I understood so far as some apps depend on oxide (>=1.2), while it should be (>=1.2~)
[09:05] <Mirv> and that problem blocks unity8 from migrating among else
[09:06] <dbarth_> Mirv: no, i got i wrong initially; i thought the new oxide upload was stuck in proposed, but actually it's not there yet
[09:06] <dbarth_> Mirv: silo 2 rquires that 1.2 oxide, not the previous ~bzr releases
[09:07] <dbarth_> ogra_: so jdstrand uploaded that new build to the security proposed ppa on friday in prep for that landing
[09:07] <ogra_> so we just have to wait ?
[09:07] <Mirv> popey: filemanager and terminal done
[09:08] <dbarth_> ogra_: the oxide-qt-1.2 in the security proposed ppa should be migrated to utopic proposed now, to unblock silo 2
[09:08] <ogra_> well, i guess we need someone from the security team for that copy, right ?
[09:09] <dbarth_> ogra_: we can wait for jdstrand to double check, yes
[09:09] <ogra_> ok
[09:09] <ogra_> Saviq, we have quite some errors in unity8 tests on both images, is someone looking into that ?
[09:10] <Saviq> ogra_, silo 19
[09:10] <ogra_> ok
[09:10] <Saviq> ogra_, adb fallout, or rather password-required fallout
[09:10] <ogra_> Saviq, cant be ... rtm has the same errors and still the old adb
[09:10] <Saviq> we didn't support password-protected unity8 tests
[09:10] <Saviq> ogra_, but it's probably flashed with passwords now
[09:10] <ogra_> utopic has 12 failures, rtm 9
[09:11] <ogra_> i dont think rtm is yet ...
[09:11]  * ogra_ chacks
[09:11] <ogra_> *checks
[09:11] <Saviq> ogra_, in any case, utopic silo 19, rtm silo 10, tested yesterday with 100% success rate
[09:11] <Saviq> it'd be in already if not for the oxide-qt problem
[09:11] <ogra_> export IMAGE_OPT=--device=krillin --developer-mode --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --wipe
[09:11] <ogra_> not with --password yet
[09:13] <ogra_> so it shouldnt behave any different than before yet
[09:18] <davmor2> asac: rtm silo 004 is granted
[09:18] <asac> ogra_: Mirv: ^
[09:19] <ogra_> oops
[09:19] <ogra_> yes i see it ... silly focus
[09:20] <ogra_> publishing
[09:21] <ogra_> why is thostr_ suddenly owning all the HERE stuff ? :)
[09:21] <thostr_> ogra_: it's lool!!! ;)
[09:22] <ogra_> haha
[09:22] <ogra_> i thought so :)
[09:22] <ogra_> he just doesnt want to be held responsible if it fails
[09:22] <ogra_> ugh
[09:23] <ogra_> Mirv, any ide what that means ? (rtm 004) ^^^
[09:23] <ogra_> *idea
[09:24] <ogra_> does it check against utopic instead of rtm
[09:24] <brendand> mvo_, cjwatson - after installing silo 3 packages won't install from the store
[09:24] <ogra_> lool, !
[09:24] <ogra_> lool, you messed up the version !
[09:24] <ogra_> 0.1+14.10.20140829~rtm-0ubuntu1~usilo10~1 (Newer version available)
[09:25] <ogra_> asac, that will need a re-upload or some such
[09:25] <ogra_> with proper versioning
[09:26] <Saviq> Mirv, did you finish your meeting? could we add source-only oxide-qt to utopic silo 2, or how do we do this?
[09:28] <kalikiana> Mirv: the ubuntu-rtm/landing-008 seems to work nicely
[09:28] <bzoltan> ogra_: Mirv tried to figure out already but we still do not know what is wrong with the silo10, it does not accept any packages. Would you please take a look at it?
[09:28] <kalikiana> Mirv: I disabled network to see that the cache actually works
[09:29] <Saviq> kalikiana, I think you mean utopic silo 8?
[09:30] <Saviq> not rtm
[09:31] <Mirv> ogra_: probably justlacking watch_only build
[09:32]  * Mirv runs
[09:32] <ogra_> Mirv, with that versioning ?
[09:32] <Mirv> Saviq: can you please give exact instructions what needs to be done? copy/upload what from where to where?
[09:32] <asac> ogra_: hmm
[09:33] <asac> ogra_: whats the problem with that version?
[09:33] <Mirv> Saviq: I can oxide-qt to silo2 nd reconfigure
[09:33] <bzoltan> mvo_: is there any news about the click+qtc plugin landing?
[09:33] <asac> ogra_: will it break the world if we pump it in like that?
[09:33] <ogra_> the last bit with tildes i think
[09:33] <Mirv> ogra_: hmm, let's see
[09:33] <ogra_> right, let Mirv do his magic ...
[09:33] <asac> ogra_: what does it mean?
[09:33] <asac> i ma not sure
[09:33] <asac> lool: ^^
[09:33] <Mirv> ogra_: it probably needs to be changed to be manually configured. the sync process is really botched up. but it just needs a few extra clicks.
[09:33] <Saviq> Mirv, https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+sourcepub/4393535/+listing-archive-extra to utopic silo 2 please
[09:34] <asac> ogra_: can you reupload withright version?
[09:34] <ogra_> asac, but that would mean re-testing too, no ?
[09:34] <asac> ogra_: so what can we do?
[09:34] <ogra_> lets see if Mirv can somehow massage it through
[09:34] <asac> thanks
[09:34] <asac> i think that would be best
[09:34] <ogra_> if not, yes, we might need to re-uplaod
[09:35] <ogra_> the questio then is, do we need re-signoff from QA or do we just trust  the rebuild
[09:35] <mvo_> bzoltan: ubuntu-rtm is verified by me now, so the next step is QA
[09:35] <asac> ogra_: i think just doing a quick smoke run to see that it is not completely busted is fine if its source identical
[09:35] <ogra_> k
[09:36] <ogra_> yeah, i doubt it would introduce any issues
[09:36] <Saviq> dbarth_, ok, so Mirv will upload oxide-qt from your PPA to silo 2, it could probably use some testing to confirm and will need to be published again
[09:36] <Mirv> mvo_: brendand has some issues to represent, or potential issues
[09:37] <mvo_> brendand: did you install click, packagekit, packagekit-tools ? i.e. all the stuff from the silo?
[09:37] <mvo_> brendand: the updated packagekit/packagekit-tools is crucial
[09:37] <brendand> mvo_, yes - i have everything i'm sure. i can double check
[09:37] <mvo_> Mirv: aha, just saw it, thanks!
[09:38] <mvo_> brendand: could you please kill packagekitd too? or reboot?
[09:38] <brendand> mvo_, several times :)
[09:38] <mvo_> brendand: :(
[09:38]  * Mirv starts copy-pasting higlights to emacs... I'll respond to each at some point :)
[09:39] <Mirv> Saviq: srccopy fine?
[09:39] <Saviq> Mirv, yeah
[09:40] <bzoltan> mvo_: is not that "regression" https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-click/lastBuild a problem?
[09:40] <cjwatson> Mirv: are you sure you don't want the -b option for that copy from ubuntu-rtm/landing-020?
[09:41] <mvo_> brendand: so if all the packages from the ppa are installed, the output of /usr/lib/packagekit/packagekitd -v would be nice, ie. start that on a terminal and then run a install via the store. but I can also try to reproduce it again, I was using ubuntu-rtm/devel-proposed image #30 for my tests. do you have the same
[09:41] <Mirv> cjwatson: no, sorry, -b yes please :)
[09:41] <cjwatson> bzoltan: yes it is a problem, that's one reason this is blocked
[09:41] <mvo_> bzoltan: yes, sorry, this issue is fixed with a branch I prepared
[09:41] <Mirv> Saviq: dbarth_ oxide copied to landing-002
[09:42] <brendand> mvo_, i have the latest image for krillin
[09:42] <Saviq> Mirv, thanks a bunch
[09:42] <bzoltan> cjwatson: mvo_: OK, I just want to make sure that the process is not stalled. I have an other set of MP in queue already.
[09:42] <Mirv> asac: ogra_: HERE published
[09:42] <cjwatson> Mirv: done, using new preferred syntax: copy-package --from=~ci-train-ppa-service/ubuntu-rtm/landing-020 -s 14.09 --to=ubuntu-rtm --to-suite=14.09-proposed -b gallery-app
[09:43] <mvo_> brendand: I only have a n4, so not sure if/what the differences are, but it should not matter, unless there is no debsig-verify installed or something like this
[09:43] <Mirv> cjwatson: oh! thanks for that, good toknow that syntax
[09:43] <Mirv> kalikiana: so no regressions in location related apps, but the bug is fixed?
[09:43] <Saviq> Mirv, I've added oxide-qt to the sources, can you please reconfigure silo 2?
[09:44] <brendand> mvo_, http://paste.ubuntu.com/8298378/
[09:44] <dbarth_> Mirv: ok; do you need something more to unblock that landing at this stage?
[09:44] <ogra_> Mirv, yay
[09:44] <asac> Mirv: yay :)
[09:45]  * asac waits for a new image
[09:45] <asac> ogra_: Mirv: how are our regressions going on rtm?
[09:45] <asac> i think unity made it with the input fix?
[09:45] <mvo_> brendand: uh, thats confusing, hold on a sec, let me try that on my n4 - there are no changes in this area at all. and thanks for the pastebin :)
[09:45] <Mirv> dbarth_: hmm, I think se Tested to No and retest after oxide has built?
[09:46] <Mirv> asac: unity8 is stuck in proposed because of this oxide problem being resolved with dbarth_ and ogra_
[09:46] <Mirv> and Saviq
[09:46] <Mirv> asac: otherwise it would be resolved, and we could move to publishing it to rtm
[09:46] <dbarth_> Mirv: ok, i can redo some smoke testing yes
[09:46] <asac> Mirv: ok. thanks
[09:46] <asac> Mirv: do we know if there are any other bad regressions taht slipped into rtm?
[09:46] <Mirv> Saviq: done and running watch_only build
[09:46] <asac> ogra_: when was last rtm image kicked?
[09:47] <asac> i didnt get a notifcation for ages here
[09:47] <kalikiana> Mirv: basically that means osm touch - all the others are web apps
[09:47] <Mirv> asac: davmor2 is of the general opinion that let's see after the current blockers are fixed, whether there's something hiding behind those fixes. currently no big marked-as-blockers.
[09:47] <cjwatson> brendand: packagekitd must be run as root
[09:47] <cjwatson> mvo_: ^-
[09:47] <Mirv> kalikiana: right
[09:48] <asac> Mirv: hidden behind which?
[09:48] <asac> behind the input prblem?
[09:48] <asac> but yeah. lets see
[09:48] <ogra_> asac, by cron, tonight
[09:49] <ogra_> around 5am european time
[09:49] <mvo_> brendand: what cjwatson said, sorry that I did not mention the sudo - I'm keen to learn what it outputs :)
[09:49] <brendand> cjwatson, mvo_ - this is more helpful - http://paste.ubuntu.com/8298416/
[09:50] <brendand> oh it failed because it's not signed :)
[09:50] <brendand> i guess that's supposed to happen :P
[09:50] <mvo_> brendand: it needs a new debsig-verify
[09:50] <Mirv> asac: yes, let's see after the fixes are in
[09:50] <mvo_> brendand: thanks! let me update the landing, it needs 0.10ubuntu2 from utopic
[09:50] <brendand> mvo_, no problem
[09:51] <Mirv> kalikiana: which image you used to run the tests? latest from this morning?
[09:52] <cjwatson> mvo_: aha, good catch, I'll copy that in now
[09:53] <kalikiana> Mirv: ah damn, I didn't update since yesterday :-/
[09:53] <kalikiana> I thought I had
[09:53] <mvo_> cjwatson: oh, thanks! thats even better, I was about to trigger a build with jenkins
[09:53] <cjwatson> yeah don't do that
[09:53] <Mirv> kalikiana: not a problem, but did you use utopic image anyhow? if you apt dist-upgraded from PPA you essentially got the latest image too..
[09:54] <kalikiana> Mirv: I only installed the ppa packages as we do usually in the uitk
[09:54] <kalikiana> I'm using ubuntu-touch/ubuntu-rtm/14.09-proposed
[09:55] <cjwatson> mvo_: guess we'll want to land the click fix before re-QAing though
[09:55] <cjwatson> mvo_: um you need to be more careful than that about ubuntu/landing-003
[09:56] <Mirv> kalikiana: ah, but that's a utopic landing, so it should be tested on utopic too
[09:56] <mvo_> cjwatson: oh, what did I do wrong?
[09:56] <cjwatson> mvo_: we need to first merge in wherever the commit is that "released" click 0.4.32, then merge your branch, then try again
[09:56] <cjwatson> mvo_: I was in the middle of trying to sort that ...
[09:57] <kalikiana> Mirv: please tell me exactly how you would prefer me to test
[09:57] <cjwatson> ah, the branch is called lp:~ps-jenkins/click/ubuntu-utopic-proposed now
[09:57] <mvo_> cjwatson: ok, I will leave my hands from jenkins for now then
[09:57] <mvo_> cjwatson: aha, thanks, that is good to know
[09:58] <mvo_> cjwatson: so it will be 0.4.32 too? not 0.4.32.1?
[09:58] <ogra_> asac, i didnt get any notification either btw ... not sure if there is something wrong, but i expect to have at least one more rtm image during the day (more likely two) so we can check it
[09:59] <cjwatson> mvo_: no, it will be 0.4.32.1
[09:59] <cjwatson> mvo_: argh, I think your force rebuild has busted things
[09:59] <cjwatson> oh, maybe not ... qtcreator-plugin-ubuntu is still at least in the PPA
[10:00] <cjwatson> let's see
[10:01] <lool> ogra_: hey, the version was just temporary
[10:01] <mvo_> cjwatson: I just used "ignore steps", did not force-rebuild (fortunately you stopped me before)
[10:01] <lool> I think I had copied the source version verbatim already
[10:01] <ogra_> lool, to late now
[10:01] <lool> so the older version didn't matter
[10:01] <ogra_> lool, seems Mirv managed to push it through
[10:01] <ogra_> looks a bit ugly though
[10:01] <ogra_> :)
[10:01] <lool> the only thing there was to push was ubuntu-system-settings and indicator-location
[10:02] <ogra_> lool, why was it in the silo then ?
[10:02] <lool> ogra_: it had to  :-(   first, because there was a package in NEW and second because of the meta changes
[10:02] <lool> ogra_: because it was sitting in NEW
[10:02] <lool> at the time
[10:02] <cjwatson> mvo_: once lp:click/devel has been updated as described above, the thing to do is just a new build specifying "click" in the box for the list of source packages, and no other options
[10:02] <ogra_> ah
[10:02] <cjwatson> mvo_: (which I've just done)
[10:03] <lool> there was really nothing crazy here; just the minimum I had to workaround to get it pulled when testing the silos
[10:03] <ogra_> lool, next time just put that info in the comments column on the spreadsheet
[10:03] <mvo_> cjwatson: thanks, the PACKAGES_TO_REBUILD on top? I will remember that
[10:03] <lool> ogra_: fair enough; I've described this at length here, but should have documented in the spreadshhet
[10:03] <brendand> ogra_, where's the krillin dashboard again? (i should really bookmark it)
[10:03] <mvo_> (hopefully )
[10:03] <cjwatson> mvo_: yep
[10:03] <ogra_> lool, yeah, not everyone is around and not everyone reads all backlog :)
[10:04] <cjwatson> mvo_: (only necessary because this is a landing of multiple packages)
[10:04]  * mvo_ nods
[10:06] <cjwatson> mvo_: I've copied the source to the ubuntu-rtm silo as well, so it can build in parallel
[10:07] <mvo_> cjwatson: cool, once its build I will re-test on my n4
[10:11] <Mirv> kalikiana: sorry for the delay again. so, flash --channel=ubuntu-touch/utopic-proposed , add the PPA with apt-add-repository, apt dist-upgrade (should be fine, but you could also list the qtlocation binary packages by hand), test
[10:12] <Mirv> "usilo10" :)
[10:12] <ogra_> haha
[10:13] <Mirv> we should have named the distro usilo instead of ubuntu-rtm
[10:13] <ogra_> lol
[10:13] <davmor2> asac: I've been thinking about the emergency number?  Is there a way we can add a test number that is dialable?  I'm assuming that there is a list or db of numbers that are dialable in emergency mode.  We could then ring a land line number to test that the feature works
[10:13] <ogra_> Mirv, then we could have a "wheat" release and a "corn" one :)
[10:14] <asac> davmor2: well. this is not only software
[10:14] <asac> davmor2: its also the provider that allows you to call a numer without sim
[10:15] <asac> davmor2: not sure if there is a test number for providers
[10:15] <asac> that is also whitelisted
[10:15] <lool> Mirv, ogra_: I hav to upload meta in rtm to drop the hardcoded dep
[10:16] <ogra_> lool, there is one other change in the seeds, please pick that up alongside
[10:16] <ogra_> davmor2, i think the numbers come from your SIM and are hardcoded ...
[10:17] <davmor2> ogra_: :(
[10:18] <davmor2> ogra_: hang on it can't we are on about the test with no sim to emergency services
[10:18] <ogra_> (or from the network, not sure ... but we dont have any influence)
[10:19] <lool> ogra_, Mirv: 1.184 copied over
[10:19] <ogra_> davmor2, ask tony once he is up ... he could probably hack some intercepting test stuff in there that mangles the number or so
[10:19] <ogra_> oh, i see, didrocks uploaded it already
[10:19] <ogra_> great
[10:19] <davmor2> ogra_: yeah I will
[10:25] <Mirv> mvo_: cjwatson: are you handling also the click (re)publishing?
[10:25] <cjwatson> yes
[10:25] <cjwatson> the train is wrong, that hasn't been retested
[10:25] <Saviq> dbarth_, fwiw it could make sense to make oxide-qt "Architecture: i386 amd64 armhf" to not waste other arches builders' time
[10:25] <Mirv> ok, marking it so
[10:26] <cjwatson> done for ubuntu-rtm too
[10:26] <Saviq> oh wow, it's a 5h build time for armhf ;(
[10:27] <cjwatson> Saviq: don't optimise for other arches' builder time please
[10:27] <Saviq> cjwatson, ok
[10:28] <cjwatson> Saviq: well, unless that's genuinely intrinsically never going to build elsewhere, which seems like a poor long-term assumption
[10:28] <cjwatson> Saviq: it fails quickly enough on the other arches so isn't really a problem, and generally we'd rather have failures visible
[10:29] <Saviq> cjwatson, ok understood
[10:31] <cjwatson> brendand: ubuntu-rtm/landing-003 hasn't been dev-tested unless mvo_ is even quicker than usual, but if you happen to have a bit of time then it should be ready ...
[10:31] <cjwatson> (again)
[10:32] <brendand> cjwatson, sure i can check that it fixes the problem i saw and then continue with the rest of the testing
[10:32] <mvo_> cjwatson: I did a quick test already with debsig-verify 0.10ubuntu2 on ubuntu-rtm and ro filesystem I can install clicks again (couldn't with 0.10)
[10:32] <mvo_> brendand: ---^
[10:33] <cjwatson> see "even quicker than usual"
[10:33] <mvo_> but of course, given my failure to spot the initial error a proper QA person needs to test this :)
[10:33] <dbarth_> Saviq: it's almost a faq but i stick to what cjwatson says
[10:33] <mvo_> cjwatson: :)
[10:33] <Saviq> dbarth_, yeah, makes sense
[10:34] <cjwatson> the only other arch with slow builders now is arm64, and we'll probably want oxide-qt for that in the not too distant future
[10:35] <ogra_> cant be slow, there is a 64 in the name :P
[10:46] <ogra_> psivaa, i just looked at krillin utopic ... seems there is also a device missing
[10:46] <psivaa> ogra_: i missed that combi. let me take a look
[10:47] <ogra_> yeah, me too ... just struck me to take a look at that :)
[10:52] <zbenjamin> ogra_: is there a problem with the current image? i get a reconnect loop after i enabled developer mode
[10:53] <ogra_> zbenjamin, hmm, weird, dbarth_ reports the same ... i cant reproduce it at all here
[10:53] <psivaa> ogra_: the device was available, it failed in this step:
[10:53] <psivaa> hablet-config writable-image
[10:53] <psivaa> error: protocol fault (no status)
[10:53] <psivaa> error: device not found
[10:54] <ogra_> psivaa, gah
[10:54] <psivaa> ogra_: rerunning it whilst watching :)
[10:54] <ogra_> thanks
[10:54] <ogra_> seems some people see adb disconnects ...
[10:54] <ogra_> could be the same ...
[10:54] <ogra_> (why cant i reproduce that, damned)
[10:54] <psivaa> yea, looks like the same
[10:55] <zbenjamin> ogra_: is it possible that by not wiping the device that problems could come up?
[10:55] <ogra_> zbenjamin, well, what worked in 232 should still work
[10:55] <ogra_> or 233
[10:56] <zbenjamin> i did not upgrade since last week
[10:56] <ogra_> hmm
[10:56] <zbenjamin> i wonder how i do the wipe now , with that reconnect problem
[10:56] <ogra_> from recovery
[10:56]  * zbenjamin does a bootstrap
[10:57] <ogra_> or that, yeah
[11:03] <brendand> ogra_, i suppose there's a known problem with pull-lp-source?
[11:03] <ogra_> brendand, on rtm, yes
[11:03] <ogra_> it doesnt know about the distro
[11:03] <brendand> ogra_, ah ok - so how can we run click tests?
[11:03] <ogra_> with phablet-tools, as usual
[11:03] <ogra_> it was adjusted for this
[11:04] <brendand> ogra_, ah probably i need to update phablet-tools again then
[11:05] <brendand> i'm getting a different error now - odd
[11:05] <brendand> IndexError from resource.py
[11:08] <ogra_> zbenjamin, would you mind downgrading your install to https://launchpad.net/ubuntu/+source/android-tools/4.2.2+git20130218-3ubuntu31/+build/6326142/+files/android-tools-adbd_4.2.2%2Bgit20130218-3ubuntu31_armhf.deb ?
[11:09] <ogra_> zbenjamin, call pahblet-shell once to get your key copied (that should work even with conection dropping), then adb shell "android-gadget-service enable ssh" and from there you should be able to install the package via ssh
[11:09] <ogra_> i cant reproduce it at all here :(
[11:10] <zbenjamin> ogra_: i probably would if the keyboard on the login screen would come up
[11:10] <ogra_> zbenjamin, oh, old bug, reboot
[11:10] <ogra_> the wizard doesnt properly restart the OSK after it ran
[11:11] <ogra_> on a new boot all should be fine
[11:11] <ogra_> zbenjamin, so you are seeing that issue before you have a password set up ?
[11:11] <ogra_> (or a pin)
[11:11] <zbenjamin> ogra_: no i did set up a pw in the wizard
[11:12] <ogra_> ok
[11:13] <davmor2> ogra_: on 24 I have a working keyboard on first boot
[11:14] <ogra_> zbenjamin, if you could somehow capture /var/log/upstart/android-tools-adbd.log that would also be helpful i think
[11:14] <davmor2> ogra_: there is however an issue triggering the sim unlock
[11:14] <ogra_> davmor2, funny, i didnt have any issue aftet OTA here today
[11:15] <davmor2> ogra_: this is a fresh install
[11:15] <ogra_> davmor2, yeah, there seems to be some difference here
[11:16] <Mirv> bzoltan: https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/landing_05.09/+merge/233459 not approved
[11:18] <kalikiana> Mirv: updated result: all works fine with unicorns and rainbows and even without ever turning on the network the cache works
[11:18] <kalikiana> which is reaaaally nice :-D
[11:21] <Mirv> kalikiana: thanks for the testing!!
[11:21] <zbenjamin> ogra_: phablet-shell does not work, can i somehow enable SSH from the terminal on the device?
[11:24] <kalikiana> ogra_: unlock the phone first
[11:24] <kalikiana> er
[11:24] <kalikiana> sorry
[11:24] <kalikiana> zbenjamin: unlock the phone first
[11:25] <zbenjamin> kalikiana: developer mode is on, but my adbd does not work
[11:25] <kalikiana> zbenjamin: and you did unlock?
[11:25] <zbenjamin> kalikiana: yes
[11:25] <kalikiana> here I get "Connection closed" if it's locked - otherwise phablet-shell is fine
[11:26] <zbenjamin> kalikiana: do you have the reconnect loop too?
[11:26] <kalikiana> no adb is all fine
[11:27] <kalikiana> adb shell doesn't even seem to mind the screen lock
[11:27] <kalikiana> (maybe that is by design?)
[11:35] <ogra_> zbenjamin, android-gadget-service enable ssh ...
[11:35] <ogra_> (in terminal-app)
[11:36] <zbenjamin> ogra_: i have a gazillion "stdin: is not a tty" in the log file
[11:36] <ogra_> zbenjamin, but you need your key on the device
[11:36] <ogra_> zbenjamin, thats fine
[11:36] <ogra_> (shouldnt cause issues)
[11:37] <ogra_> anything else in there ?
[11:37] <zbenjamin> i just have the small terminal on the phone, didn't see anything else
[11:38] <ogra_> zbenjamin, well, if you have the terminal you can also use passwd to set a password ;)
[11:38] <zbenjamin> ogra_: no, i just tail -f the file but i only get this line
[11:38] <ogra_> kalikiana, thats just not there yet :)
[11:39] <ogra_> zbenjamin, right, but that message is harmless
[11:39] <zbenjamin> ogra_: i have a pw set but i have no key, and pw connection is disabled it seems
[11:39] <ogra_> i was hoping for some more usefull errors alongisde
[11:39] <ogra_> yeah, it is
[11:39] <ogra_> on security req.
[11:40] <zbenjamin> ogra_: can i somehow get on the filesystem from bootloader or recovery?
[11:41] <ogra_> zbenjamin, pretty tricky on mako ... you need to create a mountpoint and loop mount the rootf img file
[11:41] <ogra_> *rootfs
[11:42] <ogra_> kalikiana, are you on 234 too ?
[11:43]  * ogra_ wonders why some people see it and others dont
[11:43] <zbenjamin> ogra_: what is the command for the mount?
[11:43] <lool> cjwatson: hmm I don't get how this is possible:
[11:43] <lool>  ubuntu-location-provider-here | 0.1+14.10.20140829~rtm-0ubuntu1~usilo10~1 | ubuntu-rtm/14.09-proposed/universe | source, amd64, armhf, i386
[11:43] <lool>  ubuntu-location-provider-here | 0.1+14.10.20140829-0ubuntu1               | utopic/universe                    | source, amd64, arm64, armhf, i386, powerpc, ppc64el
[11:43] <lool>  ubuntu-location-provider-here | 0.1+14.10.20140829-0ubuntu1               | ubuntu-rtm/14.09/universe          | source, amd64, armhf, i386
[11:44] <kalikiana> ogra_: 26
[11:44] <lool> cjwatson: isn't 0.1+14.10.20140829~rtm-0ubuntu1~usilo10~1 a smaller version than 0.1+14.10.20140829-0ubuntu1?
[11:44] <kalikiana> don't ask me how the numbers map - it's the latest image from a few minutes ago
[11:44] <lool> cjwatson: should that not be refused from 14.09-proposed?
[11:45] <ogra_> kalikiana, ah, so you are on krillin and zbenjamin is on mako
[11:45] <kalikiana> yes
[11:45] <kalikiana> but the images are the same, right?
[11:46] <kalikiana> except for the drivers
[11:46] <ogra_> yeah
[11:46] <ogra_> well, its far more than "drivers", but the rootfs is identical
[11:47]  * ogra_ sighs about not having a spare device to do a proper bootstrap install 
[11:47] <kalikiana> ogra_: I can flash a mako
[11:47] <kalikiana> just I don't always update both since it's kinda time consuming
[11:48] <ogra_> kalikiana, that would be massively helpful (if you can capture some data)
[11:48] <lool> ogra_: there are a bunch of issues migrating touch-meta around  :-(
[11:48] <ogra_> lool, hmm ?
[11:48] <kalikiana> sure
[11:48] <lool> ogra_: in utopic, it's held by the click-scope tests being uninstallable
[11:48] <lool> ogra_: and in rtm, the langpacks are missing
[11:48] <ogra_> lool, you just did dput it directly to rtm, right ?
[11:48] <davmor2> ogra_: well you aren't using flo for anything important right ;)
[11:49] <lool> ogra_: to 14.09-proposed
[11:49] <lool> ogra_: I've copy-package-d it
[11:49] <ogra_> davmor2, no, but i dont care about flo either much ... the issue seems to be really mako specific
[11:49] <lool> see http://people.canonical.com/~ubuntu-archive/proposed-migration/ubuntu-rtm/update_excuses.html
[11:50] <ogra_> lool, do a binary copy ... we dont have desktop-next in rtm
[11:50] <Mirv> I need to afk for 1-2 hours, but I'll be back to check what's needed before robert is up
[11:50] <lool> ogra_: not sure why that'd help; the issue isn't with the new binaries; it's with proposed migration
[11:51] <cjwatson> lool: copies are allowed to go backwards; direct uploads aren't
[11:51] <ogra_> lool, the issue is with desktop-next and the SDK
[11:51] <ogra_> neither is in rtm
[11:51] <cjwatson> lool: this is occasionally actually useful :)
[11:51] <lool> cjwatson: can we kick it from -proposed?
[11:51] <cjwatson> lool: sure
[11:51] <lool> cjwatson: that'd be helpful for provider-here
[11:51] <lool> ogra_: I understand, but I dont know how we're supposed to force it in
[11:52] <ogra_> by directly copying it to rtm instead of -proposed
[11:52] <cjwatson> no!
[11:52] <ogra_> iirc we did that the last times
[11:52] <cjwatson> do not ever do that!
[11:52] <lool> cjwatson: ^ perhaps you know; ubuntu-touch-meta can't migrate from 14.09-proposed due to broken deps
[11:52] <lool> (apparently)
[11:52] <ogra_> lool, again, these are not broken deps but completely unavailable stacks in rtm
[11:53] <ogra_> and ignorable ...
[11:53] <lool> ogra_: generally I feel we should not copy binaries to RTM; and I dont think we can copy to 14.09 anyway
[11:53] <cjwatson> lool: IMO we should fork ubuntu-touch-meta for ubuntu-rtm and drop those binaries
[11:53] <ogra_> hmpf
[11:53] <cjwatson> lool: ubuntu-location-provider-here/0.1+14.10.20140829~rtm-0ubuntu1~usilo10~1 removed; https://launchpad.net/ubuntu-rtm/+source/ubuntu-location-provider-here/+publishinghistory
[11:54] <lool> thanks
[11:54] <ogra_> cjwatson, cant we just set up a general pass-through for it in rtm proposed migration instead
[11:54] <ogra_> rather than having to keep to metas in sync
[11:54] <ogra_> *two
[11:54] <cjwatson> ogra_: while I could override it, that runs the risk of it allowing other things to break
[11:55] <cjwatson> ogra_: do you take responsibility for that?
[11:55] <popey> Mirv: could you please upload http://s-jenkins.ubuntu-ci:8080/job/calendar-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.calendar_0.4.440_all.click ?
[11:55] <ogra_> cjwatson, for a general pass-thrugh and possible fallout ? ... what could that fallout be ?
[11:55] <ogra_> (and yes, if it isnt to heavyweight)
[11:55] <cjwatson> ogra_: proposed-migration might decide to trade off some other uninstallable you actually care about if it happens to make ubuntu-desktop-next or ubuntu-sdk installable somehow
[11:56] <ogra_> well, i should see them in the image changes
[11:56] <cjwatson> 14.09 seems to have a fair few uninstallables already :-/
[11:56] <ogra_> so yeah, go ahead
[11:56] <ogra_> they would be removed/added then and should become visible in the manifest diff
[11:57] <cjwatson> only if they show up on images
[11:57] <ogra_> well, for rtm we dont really care if they dont ... people using the SDK get sdk-libs from utopic
[11:58] <cjwatson> heh, I don't actually have a hints branch for RTM yet
[11:58] <cjwatson> guess I'd better create one
[11:58] <lool> cjwatson: http://paste.ubuntu.com/8299266/ ?
[11:59] <cjwatson> lool: that's what I'd do, but it appears that ogra_ disagrees
[11:59] <lool> cjwatson: didn't update meta map; seems to be fine to keep it; I assume we keep the seeds and germinate output from utopic
[11:59] <cjwatson> shouldn't matter very deeply for metapackages
[11:59] <ogra_> lool, i really dont want to have to keep two distinct metas in sync all the time
[12:00] <lool> ogra_: the thing is that meta contains desktop-next and sdk which we haven't copied to 14.09
[12:00] <lool> ogra_: so we could split these in utopic
[12:00] <ogra_> since not everyone uploading to ubuntu might notify us etc
[12:00] <lool> but that's painful too
[12:00] <cjwatson> lool: well, I agreed above to force those uninstallables
[12:00] <cjwatson> so let's just do that and move on
[12:00] <ogra_> yeah
[12:00] <lool> cjwatson: so ignore just ubuntu-sdk and ubuntu-touch-desktop-next?  fine with me
[12:01] <ogra_> neither of them are any relevant for rtm
[12:01] <lool> cjwatson: ah and that's when you realized you needed a dedicated branch because you dont want to ignore them on utopic-proposed migration; ok
[12:01] <ogra_> we should file a bug to solve this properly for next rtm ;)
[12:02] <ogra_> cjwatson, why would a binary copy be so bad btw ? the package version as well as its deps would be indentical anyway, no ?
[12:03] <cjwatson> ogra_: I don't have a problem with binary copies of ubuntu-touch-meta
[12:03] <ogra_> or would that confuse any archive tools ?
[12:03] <cjwatson> that was lool :)
[12:03] <cjwatson> lool: right
[12:03] <cjwatson> http://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu-rtm/revision/1
 by directly copying it to rtm instead of -proposed
 no!
 iirc we did that the last times
 do not ever do that!
[12:03] <ogra_> i was referring to that reaction :)
[12:03] <cjwatson> ogra_: where did you get from that that I'm objecting to a binary copy? :)
[12:04] <cjwatson> ogra_: my objection is to directly copying to 14.09, bypassing -proposed
[12:04] <ogra_> ah
[12:04] <ogra_> sorry, mis-read my own sentence :)
[12:04] <cjwatson> heh
[12:04] <lool> cjwatson: seems it's safer to default to not copying binaries; would you suggest most of the time we can opt to copy the binaries?
[12:04] <lool> sounds error-prone to me
[12:05] <ogra_> well, for meta it doesnt make any difference
[12:05] <lool> I guess proposed migration woudl catch error if deps/shlibs are right
[12:05] <cjwatson> lool: well, I had this conversation with sil but it was while I was at debconf so was pretty on and off the net
[12:05] <ogra_> utopic and rtm will be 100% identical
[12:05] <cjwatson> lool: IMO proposed-migration should catch any significant problems and silo QA will catch the rest, so binaryful copies should generally be safe
[12:05] <cjwatson> and would be less confusion over different binaries with same version
[12:05] <lool> ok; I'll try to default to that then
[12:06] <cjwatson> lool: but apparently landing team folks disagreed, or else I misremember what I said to sil
[12:06] <ogra_> we have binaries with same versions all over the place for all initially synced stuff anyway
[12:07] <ogra_> at least if it didnt get updated in utopic
[12:07] <jdstrand> dbarth_, ogra_: hey, I'm here. what do you need me to do?
[12:07]  * ogra_ thinks thats a moot point
[12:07] <lool> ogra_: when we branched the archive, we knew they were built right
[12:07] <cjwatson> ogra_: all the initially-synced stuff was copied with binaries
[12:07] <ogra_> jdstrand, i think it was solved differently ...
[12:07] <cjwatson> ogra_: and copied from utopic, not from utopic-proposed, so should all have been fully built
[12:08] <ogra_> cjwatson, right, i just mean the version argument doesnt really matter
[12:08] <cjwatson> afaik the only different-binary-same-version cases are things uploaded/copied after the branch
[12:08] <lool> ogra_: now imagine we update a base lib in utopic and dont bump shlibs right, or there's some other hidden behavior/ABI change (same for any dep really), it works in utopic and we copy it over where it doesn't work with old lib
[12:08] <lool> it's a bug in our deps, but we might only discover it too late
[12:08] <lool> tests should catch it, but we dont test everything
[12:09] <cjwatson> lool: personally I don't think that's worth the effort of worrying about
[12:09] <ogra_> lool, oh, indeed, i agree we shouldnt binary copy libs that could have rdeps :)
[12:09] <lool> cjwatson: I heard you; just explaining the potential issue to ogra_
[12:09] <ogra_> but thats very unlikely to happen anyway
[12:09] <lool> well cjwatson argues that almost all the time it should be ok
[12:09] <lool> anyway
[12:09] <ogra_> we didnt have many packages that bypassed the silos ... and definitely not a lib among them
[12:10] <cjwatson> right, my general opinion is that spending hours of build time on low-probability events is a misallocation of resources, but whatever
[12:11] <kalikiana> ogra_: hm something's odd with the unlock setting, didn't have any lock on that one, tried to input, now it asks me for something it didn't actually save O_o
[12:11] <kalikiana> can I reset it?
[12:13] <ogra_> kalikiana, hmm, that sounds like another mterry bug ... (developer mode has nothing to do with passwords, apart from the fact that it shecks if one exists)
[12:13] <ogra_> *checks
[12:13] <mterry> ogra_, I missed the question?
[12:14] <ogra_> <kalikiana> ogra_: hm something's odd with the unlock setting, didn't have any lock on that one, tried to input, now it asks me for something it didn't actually save O_o
[12:14] <ogra_> <kalikiana> can I reset it?
[12:14] <ogra_> mterry, ^^
[12:15] <davmor2> mterry: with all the new things that have landed in RTM we now have the issue that appear in utopic where you get the Hello login prompt for password rather than pin and number pad :(
[12:16] <ogra_> davmor2, does that happen on a flash without --developer-mode and --password ?
[12:16] <mterry> davmor2, bug 1363405, has an MP
[12:16] <mterry> ogra_, yeah separately, I'm wondering if the wizard shouldn't show some warning on the password page if you already have a password set
[12:16] <davmor2> mterry: I thought it might be covered already from utopic so yay \o/
[12:16] <ogra_> davmor2, if so that would be the bug that mterry pointed to ... if it happens with these options in u-d-f then there is a u-d-f bug
[12:17] <ogra_> (we need to somehow set the mode which doesnt happen yet)
[12:17] <davmor2> ogra_: I didn't have --password only --developer-mode
[12:17] <ogra_> mterry, i really wonder how we should do that btw ... we wont have any dbus from recovery
[12:18]  * ogra_ will wait for sergiusens and discuss with him if he has any idea
[12:18] <mterry> ogra_, ah interesting
[12:18] <mterry> ogra_, you can edit the /var/lib/AccountsService/users/phablet file
[12:18] <mterry> (or some such path like that)
[12:18] <ogra_> ah, perfect
[12:19] <mterry> ogra_, it's just a keyfile, should be easy to pipe some text into
[12:19] <ogra_> right
[12:19] <davmor2> ogra_: the other bug is the sim lock pin keyboard not appearing on first boot, if you reboot it acts as expected, so I'm assuming it might be a similar issue to the main keyboard not appearing, but for the number pad.
[12:19] <ogra_> we will need detection logic too ... or a switch for --password-mode or so
[12:19] <ogra_> davmor2, yeah, smells like it
[12:20] <mterry> ogra_, yeah, but the number of developers that put in a 4-digit PIN but actually want a passphrase has to be small
[12:20] <mterry> ogra_, but might as well allow a switch I suppose
[12:20] <mterry> ogra_, though design was talking about allowing a 4-8 digit PIN.  but anyway
[12:21] <ogra_> mterry, i personally expect to get a numberpad when doing something like --password=0000
[12:21] <ogra_> and currently it would just give you a password prompt by default
[12:21] <ogra_> i think
[12:22] <mterry> ogra_, right -- I think autodetection could work just fine
[12:22] <ogra_> mterry, oh, on the booted image later you mean ?
[12:23] <ogra_> that would indeed be more awesome than adding a hack to recovery
[12:23] <mterry> ogra_, no I had meant in recovery but was just brainstorming
[12:24] <ogra_> ah, yeah
[12:24] <ogra_> well, lets see if sergiusens has an idea once he gets up
[12:24] <mterry> ogra_, for us to do it on booted image later, we'd need to keep password in plaintext on disk
[12:24] <ogra_> oh, right ... nota good idea
[12:25] <sergiusens> ogra_: mterry wrt to password and recovery, I only did exactly what I was told to
[12:25] <sergiusens> I don't mind plain text in recovery
[12:25] <ogra_> sergiusens, yes, and thats fine
[12:25] <sergiusens> it's a ci tool
[12:25] <sergiusens> if you use, you probably can care less about your password
[12:25] <ogra_> sergiusens, but the password mode for the UI doesnt get set the way we do it today
[12:25] <ogra_> we need an idea how to set it alongside
[12:26] <sergiusens> mterry: ogra_ if we drop a plaintext file somewhere, will the wizard be able to pick it up?
[12:26] <ogra_> sergiusens, as much as you call it a CI tool, you wont prevent people from using the switches :)
[12:26] <sergiusens> ogra_: fine, but I'll add a note saying that the password is going to be saved in plain text
[12:26] <mterry> sergiusens, ogra_: I'd rather we keep the developer hacks in the developer tools
[12:26] <sergiusens> ogra_: and just don't promote it!
[12:27] <ogra_> sergiusens, thats what i thought too, but it sounds hackish ... having an upstart lxc-android-boot hook that checks for it and sets the right dbus call
[12:27] <sergiusens> ogra_: mterry if you look at https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1365990
[12:27] <sergiusens> I would just say we need "developer mode" inhibit switch and forget about this problem
[12:28] <kalikiana> ogra_: mterry so… I can't even flash anymore since adb doesn't work… and I don't know whatever password may have been set
[12:28] <sergiusens> as in --developer-mode from u-d-f makes adb enabled always, pasword or no password
[12:28] <ogra_> kalikiana, flash from recovery (and use --device= there)
[12:28] <ogra_> sergiusens, i agree that we should just set a default PW in the emulator
[12:29] <ogra_> sergiusens, there is an upstart job that checks for the PW and disables it ... with a start on starting android-tools-adbd stanza
[12:29] <mterry> kalikiana, so you tried to set a password, it failed to, but now you have a password anyway and you aren't sure what it is?
[12:30] <ogra_> sergiusens, it = adbd
[12:32] <kalikiana> mterry: it complained the passwords didn't match, I had to cancel, next attempt it asks for the "existing passphrase"
[12:32] <kalikiana> btw I treid to add a PIN
[12:33] <mterry> kalikiana, aha!  You are hitting bug 1366814 it sounds like -- someone else reported that phrase "didn't match"
[12:33] <mterry> kalikiana, I haven't been able to reproduce
[12:37] <kalikiana> mterry: mmmm just noticed the PIN I set and "did not work" actually works as a passphrase at the lock now
[12:37]  * kalikiana confused
[12:37] <mterry> kalikiana, ah... then you must be experiencing the fixed (but not released) bug 1363405
[12:37] <cjwatson> lool,ogra_: ubuntu-touch-meta/1.184 should be migrating soonish
[12:38] <ogra_> cjwatson, great ... i just need to clearify some device tarball stuff, please dont kick an image or anything yet
[12:38] <lool> cjwatson: thansk
[12:39] <lool> I see valid candidate, great
[12:39] <cjwatson> ogra_: wasn't planning to, enjoy
[12:39] <cjwatson> mvo__,brendand: any luck with click testing?
[12:39] <kalikiana> mterry: seems to work now, I disabled and re-entered the PIN and it works normally
[12:40] <brendand> cjwatson, mostly. i had a strange problem with running some click package autopilot tests, which i doubt has anything to do with the silo. just retesting and then i'll sign it off if everything is well
[12:40] <mterry> kalikiana, yup, I believe it based on the way that bug works
[12:42] <kalikiana> mterry: cool, thanks a lot!
[12:42] <ogra_> kalikiana, what about adb ? do you see the reconnects ?
[12:42] <cjwatson> brendand: great, thanks
[12:42] <ogra_> now that your system is set up properly
[12:42] <cjwatson> [lunchtime, off out for an hour or so]
[12:42] <kalikiana> ogra_: adb shell, phablet-shell work fine… no loop
[12:42] <ogra_> lol
[12:42] <ogra_> heisenbug
[12:43] <kalikiana> anything in particular I could try that would help?
[12:43] <ogra_> i wish i knew whats going on for the people that see it
[12:43] <ogra_> kalikiana, no, i think my mako is in the same state as yours
[12:43] <ogra_> so that one i can reproduce ...
[12:43] <john-mcaleely> ogra_, per your request, new device image pushed
[12:43] <ogra_> yay
[12:47] <brendand> mvo__, can you set the 'Tested' column for silo 3? I won't sign it off until it's in the 'Needs QA sign-off' state
[12:49] <dbarth_> jdstrand: we copid the oxide binary to silo 2
[12:49] <dbarth_> i think we're good at this stage, but i still need to finish smoke testing
[12:50] <jdstrand> ok, cool
[12:50] <mvo__> brendand: done
[12:51] <mvo__> brendand: thanks a bunch for your testing
[12:52] <brendand> ogra_, ah didn't #24 get systemd-shim?
[12:53] <ogra_> rtm or utopic ?
[12:53] <ogra_> brendand, yeah, rtm 24 did
[12:54] <brendand> hmmm
[12:54] <brendand> why does sim unlock still be borked....?
[12:54] <ogra_> brendand, why ? any issues with that ?
[12:55] <ogra_> brendand, thats because robru landed unapproved stuff last night ... there should have been a new blocker bug for it in the landing mail (which wasnt sent)
[12:55] <zbenjamin> ogra_: weird i managed to create the .ssh/authorized_keys file but i still get access denied(publickey)
[12:56] <ogra_> zbenjamin, and you still have the loop too ?
[12:56] <zbenjamin> yes
[12:56] <brendand> ogra_, oh
[12:56] <ogra_> brendand, at least i assume thats thereason
[12:57] <ogra_> we know that some breakage slipped through
[12:57] <brendand> ogra_, could be. once that's sorted out we'll see
[12:58] <ogra_> john-mcaleely, looks like #25 is done, happy OTAing :)
[12:59] <john-mcaleely> ogra_, thank you!
[13:00] <ogra_> well, thank *you* :)
[13:13] <ogra_> cjwatson, wjat is the trick to get rmadison output for rtm btw ?
[13:14]  * ogra_ just wanted to check for -meta and noticed he doesnt know how :P
[13:15] <davmor2> ogra_: well it's like checking for -dev only not ;)
[13:19] <davmor2> kenvandine: hey dude did you fix the keyboard appearing after the wizard on first boot?
[13:20] <kenvandine> davmor2, not me personally, but yes that should be fixed
[13:20] <kenvandine> davmor2, for rtm, that was probably part of the sync in silo 15 you tested yesterday
[13:20] <kenvandine> which included lots of fixes :)
[13:20] <davmor2> kenvandine: it is however the sim unlock number pad now isn't appearing after first boot :)
[13:20] <Mirv> popey: calendar uploaded
[13:21] <kenvandine> davmor2, where?  in the shell or in settings?
[13:21] <kenvandine> davmor2, i guess it must be shell
[13:21] <davmor2> kenvandine: shell as it is the unlock request
[13:21] <camako> landing-019
[13:21] <kenvandine> davmor2, that doesn't use the OSK
[13:21] <kenvandine> it's a dialpad thing
[13:22] <davmor2> kenvandine: it's the dialpad thing
[13:22] <brendand> kenvandine, i just flashed 24 which has the new system-settings
[13:22] <Mirv> cjwatson: mvo__: how are the click landings?
[13:22] <brendand> kenvandine, good news - the keyboard does work now
[13:22] <kenvandine> davmor2, so if that isn't showing, it is a different bug
[13:22] <brendand> kenvandine, bad news, sim unlock is broken
[13:22] <kenvandine> since it's not the osk
[13:22] <kenvandine> brendand, good... is there a "but" ?
[13:22] <kenvandine> brendand, is there a changelog for image 24?
[13:23] <brendand> kenvandine, from what ogra_ told me the systemd-shim change landed, but there might have been some mistake with an ofono landing that broke it again
[13:23] <davmor2> brendand: reboot and try again I think this is what I've just been talking about
[13:23] <kenvandine> there was some regressions that got published by mistake, in ofono
[13:23] <jdstrand> so, I am looking at rtm silo 002. is the process I test it, then I update 'Testing pass' accordingly, then QA comes along and marks 'QA Signoff needed' to 'Granted' and then it lands?
[13:23] <kenvandine> brendand, what sim unlock?  talking about from in the shell?
[13:23] <brendand> kenvandine, same thing as i reported yesterday
[13:24] <ogra_> jdstrand, yeah, like magic
[13:24] <mvo__> Mirv: it seems like all looks good now, so unless I miss something we can publish - cjwatson anything else that I might have overlooked before hitting publish for the click/sdk landing
[13:24] <brendand> kenvandine, clicking on the button from indicator-network
[13:24] <kenvandine> ok... that isn't related to system-settings
[13:24] <jdstrand> ogra_: do I need to coordinate with QA or they are monitoring it?
[13:24] <davmor2> brendand: yes and nothing appears right?
[13:24] <kenvandine> brendand, probably the same thing davmor2 just noted
[13:24] <Mirv> mvo__: ok, let's wait for ack from him still
[13:25] <davmor2> brendand: reboot it works,  I think it has a similar issue to the keyboard that after the first boot the wizard still owns the keypad for the sim unlock
[13:25] <kenvandine> davmor2, can't be that...
[13:25] <kenvandine> davmor2, that unlock isn't using the keyboard
[13:26] <kenvandine> mterry, ^^^ what could keep the dialpad from showing to unlock the pin after first boot?
[13:26] <brendand> davmor2, well yesterday it was supposedly to do with systemd-shim
[13:26] <brendand> davmor2, but that got updated with a 'fix' so i was told
[13:26] <kenvandine> brendand, that shim problem caused many things to fail...
[13:26] <kenvandine> but that is fixed
[13:27]  * kenvandine updates to image 25
[13:27] <mterry> kenvandine, davmor2, is this when you press the "Unlock SIM" button nothing happens?
[13:27] <mterry> that was supposed to be fixed by the shim yes
[13:27] <davmor2> mterry: yes
[13:27] <brendand> mterry, yes in image #24
[13:27] <davmor2> mterry: if I reboot though it works fine
[13:27] <kenvandine> mterry, i  tested that yesterday, but not right after the wizard
[13:27] <brendand> mterry, actually #25 too
[13:27] <kenvandine> i locked the pin after first boot... and rebooted
[13:27] <kenvandine> not locked the pin then rebooted into the wizard to test
[13:28] <mterry> brendand, and those have version 7-3 for systemd-shim?
[13:28] <kenvandine> i'll test that scenario now once 25 finishes installing
[13:28] <popey> Mirv: thanks
[13:29] <brendand> mterry, yes i do
[13:29] <kenvandine> doesn't sound like systemd-shim since it works after a reboot
[13:29] <davmor2> mterry: ditto http://paste.ubuntu.com/8299904/
[13:29] <kenvandine> does regular pin unlock from the greeter work?
[13:29] <kenvandine> i think that's basically the same UI... not sure if it's the same code though :)
[13:30] <mterry> kenvandine, yeah... but that was a race so I could believe timing would matter.  But I guess not by that point in the boot process
[13:30] <kenvandine> but i doubt any of that uses malit
[13:30] <davmor2> kenvandine: no it only displays the password line mterry has an mp for that already though
[13:30] <kenvandine> mterry, sounds like it's only failing after the wizard run
[13:30] <mterry> kenvandine, yeah that's not maliit
[13:34] <kenvandine> mterry, i've reproduced it... after the wizard run clicking unlocking sim in indicator-network just seems to do nothing
[13:35] <kenvandine> mterry, this is all i have in the indicator-network.log
[13:35] <kenvandine> http://pastebin.ubuntu.com/8299938/
[13:36] <kenvandine> a timeout
[13:36] <mterry> kenvandine, the indicator exits on a dbus timeout?
[13:37] <kenvandine> i don't think so
[13:37] <kenvandine> it was still running
[13:37] <mterry> kenvandine, I reproduced the bug yesterday after the wizard, upgraded my shim package, rebooted and didn't get it and declared victory.  :-/  Didn't re-enable wizard because didn't realize that was part of it
[13:37] <mterry> kenvandine, ah OK, I saw "terminate called"
[13:37] <kenvandine> not sure what the wizard could have to do with it
[13:37] <kenvandine> yeah... not a good error message :)
[13:38] <kenvandine> and indeed unlock works after another reboot
[13:39] <davmor2> kenvandine: the wizzard takes the control of the keypad when you setup the pin initially, I don't know if it releases it.
[13:39] <kenvandine> doesn't sound like that could be it... it looks like it can't talk to ofono ?
[13:39] <mterry> davmor2, but this isn't a keyboard thing -- those PIN screens aren't using maliit
[13:42] <davmor2> mterry: indeed, and the keyboard now works fine with the fix in place.  Which is what made me wonder if it was a similar issue for the keypad tool?  As that code wouldn't be effected by the fix to the keyboard right?
[13:43] <mterry> davmor2, I don't know what this issue is yet, but it's not likely to be that same cause
[13:43] <mterry> davmor2, is there a bug yet?
[13:44] <davmor2> mterry: I haven't written one yet, brendand did you?
[13:45] <brendand> davmor2, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1366745, but mterry duped it
[13:46] <mterry> brendand, ah yes after my test that didn't realize the wizard was crucial to reproducing
[13:46] <mterry> brendand, can undup
[13:47] <mterry> Only happens on krillin too...  Just like the shim issue.  Man, what's the deal with krillin
[13:48] <brendand> mterry, well if it's a timing issue
[13:48] <brendand> mterry, krillin is a bit slower
[13:48] <brendand> i think
[13:48] <kenvandine> mterry, any hints at where the bug is?  ofono? indicator-network?
[13:48] <davmor2> mterry: it hates you ;)
[13:48] <mterry> kenvandine, "instead nothing happens for a bit and then the indicator seems to reload" -- sounds like the indicator did crash
[13:49] <kenvandine> mterry, i just ran list-modems a few times after the wizard run and before trying to unlock
[13:49] <kenvandine> looks fine...
[13:49] <brendand> mterry, i thought so too but there is nothing in /var/crash
[13:49] <mterry> humph
[13:50] <mterry> kenvandine, I'd start with the indicator but could be anywhere
[13:50] <kenvandine> mterry, i think you're right
[13:50] <kenvandine> looking at the process time on the network indicator
[13:51] <kenvandine> it has been runing 4 minutes shorter than my device has been up
[13:51] <kenvandine> but not crash file
[13:51] <kenvandine> note the longer delay is because i was running list-modems commands in between the wizard and trying to unlock
[13:51] <davmor2> mterry: setup wizard crash, mtp crash, and network indicator here,  That could of been from stabbing the button multiple times it seemed to refresh the indicator then http://paste.ubuntu.com/8300029/
[13:51] <kenvandine> took a couple minutes
[13:52] <davmor2> kenvandine: ^
[13:52] <kenvandine> bingo.. you have a crash file for the indicator :)
[13:52] <kenvandine> is the wizard crash file current?
[13:52] <kenvandine> or maybe from yesterday when we knew it was crashing?
[13:52] <davmor2> kenvandine: fresh install
[13:53] <kenvandine> so it was wiped?
[13:53] <davmor2> kenvandine: yeap
[13:53] <kenvandine> ok... what version of ubuntu-system-settings?
[13:53] <kenvandine> oh... the wizard crash fix isn't in the image yet
[13:54] <kenvandine> it's in the archive though
[13:54] <davmor2> kenvandine: indeed
[13:54] <kenvandine> i don't have the crash for that because i have the fixed version from the silo installed :)
[13:54] <kenvandine> i also don't have a crash file for indicator-network though... and still seeing the unlock problem
[13:55] <kenvandine> davmor2, so link your indicator crash from errors.ubuntu.com to the bug report please
[13:55] <davmor2> kenvandine: if you want the indicator crash just keep hitting the sim unlock button
[13:55] <davmor2> kenvandine: eventually you'll see the indicator restart
[13:56] <kenvandine> davmor2, i know mine restarted... but no crash file
[13:57] <brendand> davmor2, can you play music from the scope on #25?
[13:58] <kenvandine> https://errors.ubuntu.com/oops/4aba9212-3824-11e4-9fdb-fa163e4ccdf2
[13:58] <kenvandine> i bet that's it
[13:58] <mterry> kenvandine, should we assign to indicator people?
[13:59] <kenvandine> mterry, i think so... seems like a safe assumption
[14:03] <kenvandine> mterry, davmor2: ok... scratch all of that
[14:03] <kenvandine> i just did a dist-upgrade without any silos enabled
[14:04] <kenvandine> and i can no longer reproduce it
[14:04] <kenvandine> maybe it was all triggered by the wizard crashing?
[14:04] <kenvandine> my dist-upgrade included:
[14:04] <mterry> kenvandine, the report did note that it started happening with an upgraded USS
[14:04] <kenvandine>   indicator-location libsystemsettings1 qtdeclarative5-ubuntu-syncmonitor0.1 sync-monitor sync-monitor-uoa ubuntu-sdk-libs ubuntu-system-settings
[14:04] <kenvandine>   ubuntu-system-settings-wizard
[14:04] <kenvandine> which included the fix for the wizard crash
[14:05] <mterry> kenvandine, I don't know why the crash would trigger that behavior on the indicator side thoug
[14:05] <cjwatson> ogra_: just use rmadison, it works automatically
[14:05] <kenvandine> maybe the session was in some weird state?
[14:05]  * kenvandine tries again
[14:06] <cjwatson> mvo__: should be fine, go ahead and publish
[14:07] <ogra_> cjwatson, bah, i swear it didnt when i tried last week
[14:08] <kenvandine> mterry, any chance after the wizard runs something restarts the indicator upstart job?
[14:08] <Mirv> mvo__: I'm trying to do that ^
[14:08] <cjwatson> ogra_: that's because I only fixed that on Thursday afternoon :)
[14:08] <mterry> kenvandine, we do do something like that, but I didn't think it was in the post-crash code, let me check
[14:08] <kenvandine> mterry, when it wasn't working, i noticed the upstart log file didn't exist even though the service process was running..
[14:08] <kenvandine> and it got created when i opened the indicator
[14:09] <ogra_> cjwatson, lol, ok :)
[14:09] <ogra_> anyway, looks like we could have another RTM image now ...
[14:09]  * ogra_ starts a build 
[14:09] <kenvandine> mterry, but now i that is working, i see the upstart log file is there and being written too right after the shell starts
[14:09] <mterry> kenvandine, yeah we do that in the cleanup job: "initctl emit indicator-services-end" but that's pre-crash
[14:09] <davmor2> jhodapp: you about yet dude I'm blaming you for this completely ;)
[14:09] <kenvandine> mterry, so i'm confident the wizard crash fix fixed this
[14:09] <ogra_> oops
[14:09] <kenvandine> davmor2, ^^
[14:09] <mterry> kenvandine, yay...?
[14:09] <ogra_> new artwork on nusakan
[14:09] <jhodapp> davmor2, I'm innocent!
[14:10] <ogra_> jhodapp, nobody belives you !
[14:10] <kenvandine> mterry, davmor2: i've gone through the wizard 3 times and works fine after :)
[14:10] <mterry> kenvandine, was there a bug for that wizard crash?  (for dup purposes)
[14:10] <jhodapp> :)
[14:10] <jhodapp> davmor2, what's up?
[14:10] <ogra_> rtm build triggered
[14:10] <davmor2> jhodapp: ha blagged now I know you're here ;)  in scope if you click on play in music nothing it happening
[14:11] <jhodapp> davmor2, url-dispatcher broken?
[14:11] <ahayzen_> davmor2, which image?
[14:11] <kenvandine> mterry, not sure if there was a bug, do you know davmor2?
[14:11] <davmor2> jhodapp: however if I click on the play button in the scope it works fine,  and if I open the music player and play music it is fine
[14:11] <davmor2> ahayzen_: 24/25
[14:12] <mterry> kenvandine, no doesn't seem to be one (none listed in MP at least)
[14:12] <davmor2> jhodapp: hmm could be let's have a look and see if there is a crash
[14:12] <kenvandine> ok... i'm happy all seems good :)
[14:12] <kenvandine> just need a new rtm image :-D
[14:12] <jhodapp> davmor2, yeah that's not anything my code is in charge of handling
[14:13] <davmor2> jhodapp: okay in that case for a change it might not be your fault ;)
[14:13] <jhodapp> told yah! :)
[14:13] <jhodapp> haha
[14:14] <kenvandine> mterry, i'll work on getting your branches in a landing today
[14:14] <imgbot> [14:15] <mvo__> Mirv: hm, not known in space or time always sounds bad :/
[14:15] <Mirv> mvo__: yes, but give it time, I think the reason to worry is that if it's like that after 30 mins :)
[14:15] <ahayzen_> davmor2, so your saying if the music-app is closed nothing happens, but if it is open then it works? or have i missunderstood?
[14:15] <mvo__> Mirv: heh :)
[14:15] <Mirv> mvo__: seems appearing now
[14:15] <mterry> kenvandine, thank you!  (by just syncing utopic, right?)
[14:16] <kenvandine> mterry, you're recent MPs
[14:16] <kenvandine> not in utopic yet
[14:16] <mterry> kenvandine, ah I see!  Yes, thanks
[14:16] <kenvandine> np... thanks for the fixes
[14:16] <mterry> kenvandine, that password setting page has been a bear
[14:16] <kenvandine> yeah
[14:16] <mterry> all sorts of corner cases
[14:16] <kenvandine> seems in good shape now though :)
[14:16] <davmor2> ahayzen_: so if I hit the play in music from the scope nothing happens,  if I open music and select the track in music it plays, So I think jhodapp hit the nail on the head and it is the url-handler at fault
[14:16] <kenvandine> takes a few iterations :)
[14:16] <mterry> kenvandine, you shut your jinxing mouth  :)
[14:16] <kenvandine> haha
[14:16]  * kenvandine zips it
[14:17] <Mirv> mvo__: was it correct that qtcreator-plugin-ubuntu did not get republished, ie the current one stuck in proposed was fine and utopic only needed the new click?
[14:17] <ahayzen_> davmor2, hmmm i'm on devel-proposed and i was writing url-dispatcher tests last night for music and it was working then
[14:18] <ahayzen_> davmor2, on #234 i just did 'Play in music app' on an album in the scope and it worked
[14:19] <Mirv> mvo__: to answer to myself, yes it seems correct, the same version is already in utopic-proposed
[14:19] <ahayzen_> davmor2, and playing a single track works as well so maybe it is just rtm that is broken?
[14:19] <Mirv> so now we just cross fingers that everything gets fixed by those uploads
[14:19] <mvo__> Mirv: yes, thats correct, only click needed the update
[14:19] <Mirv> except, hmm, the problems coming from the oxide problem...
[14:19] <mvo__> Mirv: yeah, my fingers are crossed too
[14:19] <davmor2> ahayzen_: could be
[14:20] <ahayzen_> davmor2, do any of the other url-handler calls work for other apps?
[14:20] <kenvandine> davmor2, hey... btw  you were testing the location stuff yesterday
[14:20] <davmor2> kenvandine: I was
[14:21] <kenvandine> it wasn't working for me on krillin, but works GREAT on mako
[14:21] <kenvandine> did it work for you on krillin?
[14:21] <davmor2> kenvandine: it worked fine on krillin for me
[14:21] <davmor2> kenvandine: 20-30 secs to get a fix
[14:21] <kenvandine> it seemed faster than that for me on mako
[14:22] <kenvandine> but it never gets a fix on krillin...
[14:22]  * kenvandine tries again with all the updates
[14:22] <ogra_> still doesnt work on mako for me :(
[14:22] <ogra_> nor on krillin
[14:22] <davmor2> ogra_: you need to leave the concrete bunker and see daylight ;)
[14:22] <ogra_> i only get "no location found" in here maps all the time
[14:22] <ogra_> davmor2, i thought it should work indoors too !
[14:23] <kenvandine> davmor2, i tested it with a sim in slot 2 and a sim in both slots... not just a sim in the first slot... i wonder if there's any chance that confuses it?
[14:23] <ogra_> i also dont get any trust store questions for any app
[14:23] <kenvandine> ogra_, i didn't at first...
[14:23] <ogra_> is that because i confirmed them in tsh past already ?
[14:24] <kenvandine> rebooting fixed that
[14:24] <kenvandine> which seemed odd
[14:24] <davmor2> ogra_: you haven't got silo 004 yet though right so you won't have the fix yet
[14:24] <kenvandine> still no location fix..
[14:24] <ogra_> kenvandine, i havent gotten any since several images
[14:24] <ogra_> no matter how often i reboot
[14:24] <ogra_> davmor2, my mako has utopic
[14:24] <kenvandine> davmor2, silo 4 landed
[14:24] <ogra_> that should have all bits and pieces, no ?
[14:24] <kenvandine> so was in my updates
[14:25] <davmor2> kenvandine: image 26 that is building now
[14:25] <kenvandine> my mako was utopic-proposed, worked there
[14:25] <kenvandine> davmor2, yeah... anyway i have all those packages that landed in silo 4
[14:25] <kenvandine> i don't see how to debug this...
[14:25] <davmor2> kenvandine: :(
[14:26] <ogra_> tvoss, am i supposed to get any trust store popups at all ?
[14:26] <kenvandine> i even tried outside with gps enabled
[14:26]  * ogra_ hasnt seen any in his -proposed install in two weeks or so 
[14:26] <tvoss> ogra_, n4?
[14:26] <ogra_> tvoss, yep
[14:26] <tvoss> ogra_, known bug, working on it
[14:26] <ogra_> N4 utopic-proposed
[14:26] <ogra_> ok
[14:27] <ogra_> tvoss, the conversation of the others sounded like it would be an ogra-issue :)
[14:27] <ogra_> since it seems to work for them
[14:27] <davmor2> ogra_: open setting, click on security and then on location is here maps listed if it is that'll be why you don't see trust requests
[14:27] <tvoss> ogra_, well, it is racy. Might well work for others
[14:27] <kenvandine> tvoss, what logs should i look at to get an idea why location isn't working on my krillin?
[14:28] <kenvandine> tvoss, i do see the app listed in location access in settings, and is enabled
[14:28] <ogra_> davmor2, only camer and mic ... both greyed out showing 0
[14:28] <kenvandine> so sounds like it should be trusted
[14:28] <tvoss> kenvandine, syslog and you can add a GLOG_v=100 to the upstart job for the location service, which then gives you quite some logs in /var/log/ubuntu-location-service
[14:28] <kenvandine> ok
[14:28] <ogra_> oh, wait
[14:28] <davmor2> ogra_: that's other apps not location
[14:28] <kenvandine> ogra_, location access
[14:28] <ogra_> there is a new item in system-settings :P
[14:28] <kenvandine> not other apps
[14:28] <kenvandine> yeah :)
[14:28] <ogra_> confusing
[14:28] <davmor2> ogra_: hahaha
[14:29] <davmor2> ogra_: in location is here maps listed?
[14:29] <ogra_> still ... apps just tell me there is no location service available
[14:29] <ogra_> davmor2, indeed
[14:29] <ogra_> osmtouch, gmaps and here
[14:30] <davmor2> ogra_: so that is why you don't see trust popups then they are already trusted :)
[14:30] <ogra_> do i need a SIM ?
[14:30] <ogra_> my mako doesnt have one
[14:31] <kenvandine> E0908 17:07:32.856950  3970 skeleton.cpp:177] Error creating session: Client lacks permissions to access the service with the given criteria
[14:32] <kenvandine> tvoss, ^^ is that a problem?
[14:32] <tvoss> kenvandine, yeah ... that's basically a denial
[14:32] <tvoss> kenvandine, mind checking ps -ef | grep trust
[14:32] <tvoss> kenvandine, n4?
[14:33] <kenvandine> krillin
[14:33] <kenvandine> actually... those logs are from yesterday :)
[14:33] <kenvandine> maybe i need to restart more than ubuntu-location-service
[14:33] <rhuddie> does anyone know about using phablet-click-test-setup (from https://wiki.ubuntu.com/Touch/Testing#Running_Click_tests). I keep getting this error: http://pastebin.ubuntu.com/8300260/
[14:34] <kenvandine> tvoss, all the logs in /var/log/ubuntu-location-service/ are dated yesterday... but i've rebooted my phone a bunch of times today...
[14:34] <ogra_> davmor2, ha !
[14:34] <ogra_> works now ... i actually had t go in the garden even though i'm sitting next to a giant window
[14:34] <kenvandine> phablet   3617  1762  0 10:06 ?        00:00:00 /usr/bin/trust-stored-skeleton --remote-agent DBusRemoteAgent --bus=system --local-agent MirAgent --trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service UbuntuLocationService --store-bus session
[14:34] <kenvandine> tvoss, ^^
[14:35] <tvoss> kenvandine, okay, that looks good
[14:35]  * kenvandine rebooted with GLOG _v set
[14:35] <tvoss> kenvandine, thank you
[14:36] <kenvandine> I0909 10:35:48.042486  3485 ofono_nm_connectivity_manager.cpp:171] Exception while creating connected radio cell: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.ofono.NetworkRegistration" doesn't exist
[14:36] <kenvandine> tvoss, ^^
[14:36] <kenvandine> tvoss, so right now i have a sim in slot 2
[14:37] <kenvandine> and nothing in slot 1
[14:37] <tvoss> kenvandine, hmmm, that exception is gracefully handled, though
[14:37] <davmor2> ogra_: told you you need to leave the concrete bunker and get into the sunlight ;)
[14:37] <tvoss> ogra_, mind wanna check that the window is not only painted on the wall!? :)
[14:37] <ogra_> davmor2, then i need to travle ... no sunlight here
[14:37] <kenvandine> tvoss, ok
[14:38] <ogra_> (thats why i had the balls to go outside without being molten :P )
[14:38] <davmor2> ogra_: if you can see there is sunlight :P
[14:38] <kenvandine> tvoss, wow... lots of logging now that the HERE app is trying to get a fix :)
[14:39] <brendand> ogra_, i seem to not be the only one who has hit a problem running click tests, rhuddie got the same error
[14:39] <tvoss> kenvandine, yup :) GLOG_v=100 is like "log the world"
[14:39] <brendand> ogra_, could it be anything related to the developer-mode changes?
[14:39] <tvoss> kenvandine, still got an item on my list to allow for enabling it at runtime
[14:39] <ogra_> brendand, perhaps ... though the smoke tests run fine
[14:40] <kenvandine> tvoss, ok... no fix and only logs are written to the INFO file
[14:40] <ogra_> brendand, you are on utopic, right ?
[14:40] <kenvandine> tvoss, should i pastebinit?
[14:40] <tvoss> kenvandine, please, yes
[14:40] <ogra_> brendand, rtm didnt have the dev mode changes
[14:40] <ogra_> (yet)
[14:40] <brendand> ogra_, could that upset phablet-tools?
[14:40] <ogra_> shoudlnt
[14:41] <ogra_> sergiusens, do you see any possible issue with using the new phablet tools with old adb mode ? i think everything is backwards compatible
[14:42] <brendand> ogra_, sergiusens - http://pastebin.ubuntu.com/8300260/ is what we're seeing
[14:43] <tedg> Are there any traingaurds right now, or are we waiting for robru to finish breakfast?
[14:43] <tedg> Also, qagaurds
[14:43] <cjwatson> ogra_,sergiusens: hm, speaking of phablet-tools, don't we need to make click-buddy's provision mode use pkcon --allow-untrusted now
[14:43] <ogra_> tedg, cyphermox_ should be able to help you
[14:43] <cjwatson> ?
[14:43] <cjwatson> mvo__: cc ^?
[14:43] <cjwatson> ^-
[14:43] <tedg> ogra_, Ah, cool.
[14:44] <tedg> cyphermox_, Can I get an rtm silo for line 55 please?
[14:44] <ogra_> cjwatson, did that land in any rtm image yet ?
[14:44] <tedg> cyphermox_, And can you please publish line 54?
[14:44] <cjwatson> ogra_: it's on its way, not actually in an image yet
[14:44] <ogra_> well, then we should indeed land the phablet-tools fix alongside
[14:45] <cjwatson> sorry I only just noticed this
[14:45] <bzoltan> ogra_:  I have heard from zbenjamin that some devs have problems with the SDK.
[14:45] <ogra_> bzoltan, yeah, you have a hardcoded "adb root" in one of your scripts
[14:46] <bzoltan> ogra_:  nopez
[14:46] <mvo__> ogra_: is that lp:phablet-tools ? let me check
[14:46] <sergiusens> cjwatson: yeah, I need to add that
[14:46] <ogra_> bzoltan, that needs to go (alongside with a change in adbd to ignore that call)
[14:46] <Mirv> FYI we're still completely out of RTM silos, but QA has 5 silos under testing
[14:46] <ogra_> bzoltan, ?
[14:46] <ogra_> bzoltan, i have the paste hre
[14:46] <sergiusens> ogra_: brendand if you are on rtm you need to specify --distro and --series
[14:46] <bzoltan> ogra_: http://bazaar.launchpad.net/~ubuntu-sdk-team/qtcreator-plugin-ubuntu/trunk/revision/251
[14:46] <ogra_> http://pastebin.ubuntu.com/8300137/
[14:46] <bzoltan> ogra_:  what version of the qtc plugin?
[14:47] <ogra_> bzoltan, no idea, ask dbarth_ or zbenjamin :)
[14:47] <ogra_> bzoltan, they both had the issue
[14:47] <bzoltan> ogra_:  that is the old version
[14:47] <mvo__> cjwatson, ogra_: sorry I was not aware of this script lp:~mvo/phablet-tools/pkcon-allow-untrusted
[14:47] <bzoltan> ogra_:  they both should upgrade :)
[14:47] <ogra_> bzoltan, ah, good to knwo
[14:48] <ogra_> bzoltan, anyway it exposed a bug in adbd, zbenjamin helped a lot to find it :)
[14:48] <bzoltan> ogra_: cool :)
[14:48] <brendand> sergiusens, ah ok
[14:48] <tedg> Mirv, I have two rtm silos that can be free'd with QA sign off :-)
[14:49] <dbarth_> bzoltan: wassup?
[14:49] <brendand> tedg, indicator-display?
[14:49] <tedg> brendand, Yes, and indicator-datetime
[14:49] <sergiusens> brendand: there isn't any reliable auto magic hints we can use on the image yet, or it would of been automatic
[14:50] <brendand> tedg, what's indicator-display meant to do?
[14:50] <brendand> tedg, it doesn't seem to add any new indicator
[14:50] <Mirv> tedg: yeah, the 016 of them is being tested by... right, brendan
[14:50] <sergiusens> brendand: this is one of the pains of the ~rtm renaming, would of been mostly transparent otherwise
[14:50] <bzoltan> dbarth_:  I have heard that you have problem with the adbd
[14:50] <tedg> brendand, So an indicator on the panel when rotation lock is enabled.
[14:50] <tedg> brendand, Show
[14:50] <bzoltan> dbarth_:  what version of qtcreator-plugin-ubuntu do you have installed?
[14:50] <tedg> brendand, Look at the test plan, it talks about how to enable rotation lock, it doesn't work in system settings right now.
[14:50] <dbarth_> bzoltan: ah, indeed
[14:51] <dbarth_> bzoltan: on #ubuntu-touch maybe
[14:53] <brendand> tedg, thanks
[14:59]  * ogra_ wonders why the bot didnt pick up the running build 
[15:09] <brendand> pete-woods, jamesh - i'm testing the scopes silo
[15:11] <brendand> pete-woods, jamesh - it seems to break playback from the scope
[15:12] <pete-woods> brendand: sorry, which silo? I didn't realise I had any
[15:15] <ogra_> sergiusens, there is another phablet tools MP we need from pitti, i would like to get it into the same silo if possible
[15:16] <brendand> pete-woods, silo 14 in RTM
[15:16] <brendand> pete-woods, jamesh and Satoris are also mentioned as landers
[15:18] <pete-woods> brendand: it breaks the little preview widgets?
[15:18] <brendand> pete-woods, yeah the play button
[15:20] <pete-woods> brendand: is it broken for grooveshark / 7digital / local music / everything?
[15:21] <brendand> pete-woods, i haven't checked the remote stuff
[15:21] <brendand> pete-woods, i'm otp right now but as soon as i'm done we can talk through it
[15:21] <pete-woods> okay
[15:25] <pete-woods> brendand: I have the same. local music previews seem to be broken
[15:25] <brendand> pete-woods, i hate to say it, but it seems like the test plan wasn't followed :/
[15:25] <pete-woods> brendand: seems like it. unfortunately I'm just the guy pushing the "tested" button
[15:26] <Mirv> could a core-dev ack Unity team's SRU micro version bump? https://ci-train.ubuntu.com/job/ubuntu-landing-005-2-publish/lastSuccessfulBuild/artifact/packaging_changes_unity_7.2.3+14.04.20140826-0ubuntu1.diff
[15:27] <pete-woods> I guess I should be less trusting..
[15:29] <sergiusens> ogra_: I'm in no hurry
[15:29] <sergiusens> let it be queued
[15:29] <sergiusens> ogra_: it's not in the spreadsheet though...
[15:29] <ogra_> sergiusens, can i add it to your line ?
[15:29] <imgbot> [15:30] <imgbot> [15:30] <sergiusens> ogra_: depends, if it's qa like and requires too much testing, I don't want to land it
[15:30] <sergiusens> ogra_: this one requires like zero testing
[15:30] <ogra_> https://code.launchpad.net/~pitti/phablet-tools/network/+merge/231761
[15:30] <sergiusens> ogra_: as in, if affects phablet-click-test-setup or phablet-test-run I don't want it
[15:30] <sergiusens> ogra_: as the testplan for those takes 6 to 8 hours
[15:30] <ogra_> i think it doesnt require more than storing/restoring the network config once to test
[15:31] <ogra_> its a change to phablet-config ... not for any test setup stuff
[15:32] <sergiusens> ogra_: if it's properly reviewed/tested, I'll add ;-)
[15:32] <ogra_> sergiusens, i tested and pitt  did too
[15:39] <cyphermox_> tedg: you should finish testing on your landings first...
[15:39] <tedg> cyphermox_, Which one? The rtm ones are tested.
[15:40] <cyphermox_> tedg: my bad, I wasn't up to date
[15:41] <cyphermox_> tedg: there are no rtm silos available right now, you'll get one as soon as possible
[15:42]  * Mirv sees rsalveti battling with Train awesomeness
[15:42] <rsalveti> Mirv: lool: do you know what happened with silo 4 (rtm)?
[15:43] <rsalveti> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-004
[15:43] <rsalveti> two packages seems to be outdated comparing to the archive version of the same packages
[15:43] <rsalveti> and publishing seems to be waiting for them to be available in the destination, but that will for sure fail
[15:44] <tedg> cyphermox_, Cool, thanks!
[15:44] <Mirv> rsalveti: lool: it got QA approved and published, but something is amiss, you're right.  ubuntu-touch-meta already got another update, so the ubuntu-location-provider-here is the question mark.
[15:45] <rsalveti> the version string in there is a bit confusing
[15:46] <cjwatson> I had to remove ubuntu-location-provider-here from 14.09-proposed because the version copied in there was older than that already in 14.09
[15:46] <cjwatson> see scrollback from a few hours ago ...
[15:46] <cjwatson> needs a build with a newer version number :)
[15:46] <Mirv> rsalveti: it seems the ubuntu-location-provider-here already in rtm is identical to the tried-to-be-published one, except the funny (and lower) version number
[15:47] <Mirv> the HERE landing was a bit manual operation in both utopic and 14.09
[15:47] <rsalveti> Mirv: yeah
[15:47] <Mirv> so from what I see it's all ok except that the silo is wrong status
[15:47] <rsalveti> lool: can you confirm that?
[15:47] <rsalveti> if so, we can probably clean that silo
[15:47] <Mirv> rsalveti: so, your 011 publishing...
[15:47] <rsalveti> Mirv: what's up?
[15:48] <Mirv> rsalveti: it failed. possibly because of robru's continous code cleanup, the sync publishing is quite bollocks at the moment, often.
[15:48] <rsalveti> argh, just noticed =\
[15:48] <Mirv> rsalveti: my trick has been to change the sync:N to package name, reconfigure, build with watch_only and then publish
[15:48] <rsalveti> right
[15:48] <rsalveti> let me try that
[15:49] <lool> Mirv: I think we can flush it now
[15:49] <lool> Mirv: I had copied touch-meta and location-provider-here from ubuntu to ubuntu-rtm already
[15:50] <lool> Mirv: touch-meta publishing was actually not needed BTW, but I should have noted that in the comments -- not just the changelog
[15:50] <rsalveti> Mirv: it seems I can't reconfigure the rtm silo for some weird reason
[15:50] <Mirv> lool: ok, thanks
[15:50] <rsalveti> got the link, but went nowhere
[15:50] <Mirv> rsalveti: I do the "real" reconfigure via prepare-silo always
[15:50] <Mirv> with the request ID
[15:50] <rsalveti> hm, ok
[15:50] <ogra_> lool, Mirv, it all landed http://people.canonical.com/~ogra/touch-image-stats/rtm/26.changes
[15:50] <ogra_> flush away :)
[15:51] <rsalveti> Mirv: same thing, jenkins ignored me
[15:51] <lool> we should get a pull chain image to flush silos
[15:51] <lool> like in world of goo
[15:51] <ogra_> heh
[15:52] <rsalveti> Oops!
[15:52] <Mirv> rsalveti: jenkins just started totally ignoring my actions too...
[15:52] <rsalveti> when trying to log-in
[15:52] <rsalveti> seems jenkins is busted
[15:52] <ogra_> rsalveti, thats by design i thought
[15:52] <rsalveti> seems to be more broken than the usual
[15:52] <rsalveti> vanguard? fginther I guess
[15:53] <rsalveti> it seems ci-train.ubuntu.com is not behaving properly
[15:53] <rsalveti> can't log-in anymore
[15:54] <rsalveti> IOError: [Errno 28] No space left on device
[15:54] <ogra_> lovely
[15:54] <rsalveti> Mirv: fginther: Ursinha: ^
[15:54] <rsalveti> that seems to be why
[15:54] <fginther> yuck
[15:54] <Ursinha> oops
[15:54] <rsalveti> https://ci-train.ubuntu.com/job/prepare-silo/1924/console
[15:54] <Ursinha> rsalveti: citrain is trainguards, but let me have a look
[15:54] <ogra_> i have some TB spare space on my desktop machine, you can NFS mount it ;)
[15:54] <Ursinha> ogra_: lol
[15:55] <rsalveti> Ursinha: thought infra stuff like that was more for vanguard
[15:55] <Ursinha> robru: halp
[15:55] <fginther> rsalveti, Ursinha, we've run into this before. We may have some control over this without going to IS
[15:55] <Ursinha> fginther: what is that?
[15:56] <fginther> Ursinha, the last time this happened, the disk was full of defunct pbuilder chroots, we can remove those if that is the case
[15:56] <fginther> but the problems appear to run deeper then that :-(, I can't even login
[15:56] <Ursinha> fginther: what machine is that
[15:56] <fginther> https://ci-train.ubuntu.com/
[15:57] <rsalveti> Ursinha: http://community.sephora.com/t5/image/serverpage/image-id/116046i2AF73FFDE6096D06/image-size/original?v=mpbl-1&px=-1
[15:57] <Ursinha> LOL
[15:59] <fginther> Ursinha, despite the ugly stack trace, I was able to login and run some test jobs. Looks like several defunct chroots are still there: https://ci-train.ubuntu.com/job/fginther-test/15/console
[15:59] <Ursinha> fginther: I like the way you cheated jenkins
[15:59] <fginther> Ursinha, anything over a day old under /var/cache/pbuilder/build can be removed
[16:00] <Ursinha> fginther: can we create a job to remove them or we need IS help?
[16:00] <Ursinha> I can't seem to be able to login to that machine
[16:01] <fginther> Ursinha, I think the jenkins user has sufficient rights to clean things up, let me check on that
[16:01] <ogra_> brendand, meeting ?
[16:02] <ogra_> popey, and you ? (or do you just skip the evening meetings)
[16:03] <Ursinha> fginther: am I supposed to be able to login to that machine with my regular user? or you're talking about logging into jenkins?
[16:04] <fginther> Ursinha, I login to the jenkins UI
[16:04] <fginther> we don't have ssh access
[16:04] <Ursinha> fginther: ah, the UI, not the machine :)
[16:05] <Mirv> Ursinha: rsalveti: jenkins started working again for me
[16:06] <Ursinha> Mirv: I just saw a new job here
[16:06] <Ursinha> fginther: did you remove the chroots already?
[16:06] <fginther> Ursinha, not yet, there's a job created to do it, but it needed a little work
[16:06] <fginther> pbuilder-clean
[16:08] <fginther> Ursinha, running it now
[16:10] <fginther> rsalveti, can you please retry that job?
[16:10] <Mirv> rsalveti: I did already for you, seems to work
[16:11] <rsalveti> fginther: Mirv: will retry
[16:11] <Ursinha> that would be my next question, Mirv, fginther, can we just retry such jobs manually or should we use citrain tools for that?
[16:13] <ev> can someone explain to me why silos.previous exists?
[16:13] <Mirv> rsalveti: fginther: so, the retries worked.
[16:13] <ev> why it needs this backup
[16:13] <Mirv> robru: ^ see ev's question, you might have better idea than I do
[16:13] <Mirv> Ursinha: the citrain tools are just wrappers around running the jobs
[16:14] <ev> we already do daily backups of /var/lib/jenkins, so I'm confused as to why we'd have an extra layer of backups
[16:14] <Mirv> so with the same parameters it should work
[16:15] <Mirv> something weird with rtm 008 still though, retrying again
[16:16] <Mirv> and the queuebot seems gone
[16:17] <brendand> tedg, so the rotation lock is not supposed to work at all right now - this landing purely provides the indicator?
[16:17] <tedg> brendand, Correct
[16:17] <tedg> brendand, The indicator is supposed to work, but not rotation lock itself. :-)
[16:17] <brendand> tedg, would be kind of good if the indicator closes after unsetting the lock
[16:18] <brendand> tedg, otherwise you get thrown to the location indicator - it's a bit jarring
[16:18] <tedg> brendand, Yes, I think there needs to be some design back and forth there, but bug fixes vs. feature. Trying to get the feature in (with FFe of course).
[16:18] <tedg> brendand, I imagine it'll get refined.
[16:19] <brendand> tedg, ok seems fine then
[16:20] <brendand> tedg, -datetime next
[16:20] <tedg> brendand, Woot! Thanks!
[16:23] <brendand> robru, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1366745
[16:25] <kenvandine> brendand, that should be in image 26
[16:26] <brendand> kenvandine, did it land already?
[16:26] <kenvandine> yes
[16:27] <kenvandine> it was in the HERE silo
[16:27] <kenvandine> 4 i think
[16:27] <Mirv> rsalveti: the train is a really train wreck atm, I'll salvage the rtm-008 still for publishing and then I'll let robru take over
[16:28] <kenvandine> brendand, yes, it landed with rtm silo 4 this morning
[16:28] <brendand> kenvandine, ok. that's confusing - but we'll see i guess
[16:28] <kenvandine> where can i find changes for rtm images?
[16:29] <Mirv> note to self: do no trust any "sync:N"
[16:30] <brendand> kenvandine, http://people.canonical.com/~ogra/touch-image-stats/rtm/
[16:30] <kenvandine> brendand, thanks!
[16:30] <brendand> kenvandine, the build number corresponds to krillin
[16:30] <kenvandine> ubuntu-system-settings-wizard from 0.3+14.10.20140904.2~rtm-0ubuntu1 to 0.3+14.10.20140908-0ubuntu1
[16:30] <brendand> kenvandine, you asked earlier and i forgot to reply :/
[16:30] <kenvandine> brendand, that had the fix
[16:30] <brendand> kenvandine, ok good
[16:37] <rsalveti> Mirv: thanks
[16:41] <brendand> tedg, datetime looks good
[16:46] <brendand> tedg, how do i test the fix for https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1350544
[16:54] <Mirv> rsalveti: 008 published, although spreadsheet seems broken
[16:54] <awe_> robru, it's come to my attention that the ofono rtm silo never actually published yesterday, so no we're out of sync between utopic & rtm
[16:54] <Mirv> robru: the jenkins problem probably broke spreadsheet updating somehow
[16:54] <awe_> please advise on how we can fix this
[16:55] <Mirv> robru: I get "SyntaxError: Empty JSON strings" when trying to refreshSilosStatus
[16:58] <rsalveti> Mirv: great, thanks!
[17:01] <robru> Mirv: ugh, what now?? OK i need to eat breakfast but I'll look at it soon
[17:02] <Mirv> robru: yeah, no idea. jenkins now works, but the connection between spreadsheet and jenkins does not.
[17:02] <Mirv> robru: have a fun day, I know I had...
[17:05] <Mirv> the spreadsheet updating worked 1h ago, and broke at the same point we noticed jenkins had run out of space
[17:18] <awe_> robru, did you seem my question re: ofono/rtm?
[17:18] <boiko> Mirv: is the jenkins out of space problem fixed already? (I have a silo that needs building)
[17:20] <Mirv> boiko: that's fixed, only jenkins <-> spreadsheet updating is broken
[17:20] <Mirv> so use http://people.canonical.com/~platform/citrain_dashboard/#?q= as much as possible
[17:20] <boiko> Mirv: so I can trigger a build already? (silo 008)
[17:20] <Mirv> boiko: should be
[17:21] <boiko> Mirv: thanks, let me try
[17:21]  * Mirv redirects further questions towards Robert, I really need to start preparing for sleeping activities :)
[17:21] <robru> awe_: well, fix whatever regression you had found, then do a new landing for both utopic and rtm
[17:21] <robru> Mirv: thanks for staying so late, I'm not feeling well today and only just starting to wake up
[17:22] <ogra_> robru, so did you find out why we have landings vanishing
[17:22] <awe_> robru, dude...the silo for utopic landed, the silo for rtm didn't land
[17:22] <awe_> so now we're out of sync
[17:22] <robru> ogra_: I have a hunch but haven't been able to confirm it yet.
[17:22] <Mirv> robru: no problem, take care
[17:22] <awe_> I have no idea how to fix this
[17:22] <robru> awe_: dude, I just told you, if you do a new landing to both, it'll be back in sync.
[17:24] <robru> awe_: considering that the last release had some big regression that everybody was mad at me for publishing, i think it's good that it didn't get into rtm. so no real point to sync the distros, just fix the problem and make a new release.
[17:25] <ogra_> robru, but you are aware that this was part of the location landing and due to it not landing there might be issues in location ?
[17:25] <awe_> first, the big regression was marked invalid this morning, and now we're out of sync
[17:25] <awe_> robru, if a new landing is the only way to get things back in sync
[17:26] <awe_> then c'est la vie
[17:26] <awe_> if we'd had better communication between the lander (me), QA (davmor2) and CI, we wouldn't be in this position
[17:26] <robru> ogra_: awe_: so what do you guys want? do you want the utopic version in rtm? we can make a sync silo for that, it's easy. but we just finished having a landing meeting where people were saying "wow, it's so lucky that that bug stopped this awful package from making it into rtm"
[17:27] <awe_> robru, we were mad that it was published because the testing pass hadn't been approved, nor had the MR
[17:27] <ogra_> robru, i didnt say we're lucky
[17:28] <ogra_> robru, i said we might have been lucky to not have to have another regression bug, i hve no clue about the impact on the landing it had to get in with
[17:28] <awe_> robru, I'm surprised as we discussed the regression and how it had been marked invalid during out standup
[17:29] <awe_> needless to say, all I want now is for utopic and rtm to be in sync;  if it requires a silo, then so be it.
[17:30] <sergiusens> copy-package and done
[17:30] <infinity> cjwatson: What's the process (or do we have one) for syncing back from utopic to RTM for things that we know don't break ABI and don't need rebuilds?  Should I JFDI and copy?
[17:30] <infinity> cjwatson: (Specifically thinking of glibc and its recent security updates, as prompted by the security team)
[17:31] <awe_> cjwatson, is it possible to create sbuild chroots based on rtm?
[17:31] <robru> awe_: yeah there is a large failure of communication here. I have no idea why you want to put your broken package in rtm. how far away are you from a real fix that we can just land in both?
[17:31] <awe_> robru, didn't I just say, it's *not* broken?????
[17:31] <ogra_> infinity, technically it  needs to go through a silo and QA signoff ... with the exception of meta and langpacks (not sure who could decide on an exception for glibc security fixes)
[17:32] <robru> awe_: what are you talking about? everybody was mad at me for publishing such a broken package, and then everybody breathed a sigh of relief when they saw it didn't really publish at all
[17:32] <awe_> https://code.launchpad.net/~phablet-team/ofono/lp1363413/+merge/233434
[17:32] <awe_> the merge proposal has the original testing details
[17:33] <awe_> the critical regression was: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1366231
[17:33] <infinity> ogra_: So, rebuilding it would be a silly waste of time, I assume one can just do a copy-with-binaries to a silo PPA and then land?
[17:33] <robru> awe_: https://code.launchpad.net/~phablet-team/ofono/lp1363413/+merge/233434/comments/570911 so I'm proposing that you fix that critical bug, and come back with a totally new landing. don't be bothered by the fact that they're out of sync, a new landing will re-sync thme
[17:33] <awe_> and again, it was found to be Invalid earlier today
[17:34] <ogra_> infinity, i'll leave the binary decision to colin :)
[17:34] <robru> ogra_: is it ok with you if we sync ofono from utopic to rtm?
[17:35] <ogra_> robru, ask QA, not me ... with me thats indeed ok (not a binary sync indeed)
[17:35] <robru> ogra_: isn't that the whole problem? davmor2 toldme to sync it prematurely
[17:35] <infinity> If it's not a binary sync, it's not a sync.  Please tell me we're not doing source syncs with the same version numbers. :/
[17:36] <robru> infinity: get out of here with your debian terminology, we're too good for that crap! This. Is. Sparta!
[17:36] <robru> I mean, This. Is. CI Train!
[17:37] <infinity> robru: "sync" is Ubuntu terminology. :P
[17:37] <robru> infinity: anyway the people who birthed citrain invented all new terminology. sync doesn't mean what you think it means
[17:38] <infinity> *sigh*
[17:38] <infinity> Why? :(
[17:38] <infinity> And what does it mean, then?
[17:39] <robru> infinity: I don't know why, just like I don't know why citrain does half of the things that it does. But sync means something like "get the source package, mangle it's version number for rtm, upload to RTM PPA, pray that somebody bothers to test it, then publish."
[17:39] <robru> and pray that it gets anywhere
[17:40] <infinity> Kay.  The "mangle the version numbers" part of that implies "backport", not "sync", but whatever.  I guess learning distro terminology when people work on the distro is hard. :P
[17:40] <robru> infinity: I don't work on the distro, I work on ci train ;-)
[17:40] <infinity> ...
[17:40] <robru> infinity: I know, it's a mess.
[17:41] <infinity> "I don't work on Linux, I work on the SCSI subsystem."
[17:41] <davmor2> ogra_, robru: so if this it the version blessed by awe_ then by all means sync it to a silo I can run quick tests on it and then land it.
[17:41] <robru> davmor2: ok
[17:42] <robru> davmor2: ogra_ awe_: what packages are affected? just ofono?
[17:42] <infinity> Anyhow, I have to go play cat chauffeur.
[17:42] <awe_> robru, correct, just ofono
[17:42] <davmor2> robru: there was only ofono in the silo but that isn't to say that is all that was meant to be in there by the sound of it
[17:44] <robru> awe_: what's going on in silo rtm19? there's an ofono there
[17:44] <awe_> I have *no* idea
[17:45] <awe_> rsalveti, did you create this ^^
[17:46] <awe_> robru, looks like Mirv created it to fix the missed landing from yesterday
[17:47] <robru> awe_: davmor2: ok silo rtm19 has the utopic version of ofono in it, and it even already says QA:granted, so that can just be published whenever anybody feels like it
[17:47] <awe_> ok
[17:47] <robru> well, I mean, maybe a double-check is in order then I'll publish it
[17:47] <awe_> yes, I will do so
[17:48] <davmor2> robru: yeah I'll hit it in a minute
[17:56] <brendand> tedg, an answer appreciated about verifying the bug - then i can sign silo 001 off hopefully
[17:59] <rsalveti> I have nothing to do with rtm19 :-)
[18:01] <Saviq> dbarth_, what's the status of the oxide-qt landing?
[18:03] <robru> rsalveti: your name is on it!
[18:07] <rsalveti> robru: haha, I created the utopic one
[18:07] <rsalveti> the rest was just automatic
[18:09] <bfiller> robru: any idea while silo 12 for ubuntu not showing up correctly in the webview? line 56 on sheet
[18:13] <robru> bfiller: uh
[18:16] <robru> bfiller: yeah because http://people.canonical.com/~platform/citrain/ubuntu/landing-012 got truncated somehow
[18:17] <robru> oh it's truncated in the backend, too
[18:17] <robru> bfiller: I guess only a reconfigure can save it
[18:17] <bfiller> robru: I will reconfigure it
[18:17] <robru> bfiller: no no
[18:18] <robru> bfiller: needs super admin reconfigure
[18:18] <bfiller> ok
[18:22] <robru> bfiller: ok, silo 12 should be ready for a fresh build here.
[18:23] <bfiller> robru: thank you
[18:23] <robru> bfiller: you're welcome!
[18:24] <robru> tvoss: around? your silo utopic 4 got itself into an inconsistent state somehow, I need to nuke it
[18:24] <tvoss> robru, how would that work?
[18:25] <tvoss> robru, how would that happen?
[18:25] <robru> tvoss: not sure how it got this way, but the silo state file is just missing, which means citrain doesn't have a clue what's going on there (also if you check the dashboard, silo 4 is blank). I can nuke it and reassign and it should work
[18:26] <robru> tvoss: we had ENOSPACE issues this morning, so I guess the files got truncated as a side effect
[18:26] <tvoss> robru, ack, let's do it then
[18:27] <robru> tvoss: ok silo 4 is ready for a fresh build if you wanna kick it off
[18:27] <tvoss> robru, still nothing in the silo for me
[18:28] <robru> tvoss: dashboard should update soon
[18:28] <tvoss> robru, ack
[18:28] <robru> tvoss: looks good to me
[18:31] <balloons> plars, are the devices being run with a pin set now?
[18:31] <robru> queuebot: haha, welcome back!
[18:31] <balloons> I'm asking because the failures in terminal and file manager are quite clearly due to PAM, which only appears if a pin or password is set
[18:32] <ogra_> balloons, indeed, we have to, else adb wont work
[18:32] <balloons> ogra_, I knew that was going to happen, I just didn't think you landed it yet
[18:32] <balloons> I wanted to be prepared, heh
[18:32] <ogra_> balloons, it is only in utopic
[18:32] <ogra_> not in rtm
[18:32] <balloons> OHH, gotcha
[18:33] <balloons> that makes sense
[18:33] <ogra_> (but due tomorrow)
[18:33] <balloons> lol
[18:41] <plars> balloons: do you mean the libcogl one we set as a test a while back?
[18:41] <plars> balloons: or are you talking about something else?
[18:41] <plars> balloons: oh, sorry I'm catching up
[18:42] <plars> balloons: yes, we certainly set the password on devices now. Otherwise we have no adb
[18:42] <balloons> plars, yea, I'm all covered ;-) I didn't think that landed yet.. and indeed it hasn't in rtm, but has in utopic
[18:42] <plars> balloons: yes, but it should go into rtm soon enough
[18:43] <balloons> yep, so anyways, we'll update tests accordingly to account for this
[18:43] <balloons> I just wanted to do it BEFORE those changes landed not after
[18:48] <davmor2> ogra_: https://bugs.launchpad.net/url-dispatcher/+bug/1367400 can't launch local music from the scope  I'm assuming url dispatcher is to blame after chatting to jhodapp
[18:49] <ogra_> davmor2, blocker ?
[18:49] <davmor2> ogra_: certainly annoying and user facing and a regression so yes.
[18:50] <jhodapp> I agree
[18:50] <ogra_> davmor2, can you tag it the right way ?
[18:50] <ogra_> so it lands on sils list
[18:50] <davmor2> ogra_: sure let me figure it out
[18:50] <ogra_> thx
[18:50] <jhodapp> davmor2, did you assign it to tedg?
[18:50] <davmor2> jhodapp: no feel free though
[18:51] <jhodapp> done
[18:52] <awe_> davmor2, sanity check of ofono silo looks good on my end.  Did you get a chance to kick the tires?
[18:52] <awe_> if so, I'll click publish and cross my fingers
[18:52] <davmor2> awe_: rebooting now
[18:52] <awe_> k
[18:54] <davmor2> ogra_: let me know if that shows up please
[18:55] <ogra_> davmor2, will do
[18:56] <davmor2> ogra_: yay it did ;)
[18:56] <ogra_> awesome !
[18:56] <tedg> davmor2, Are there any recoverable errors from that?
[18:57] <davmor2> tedg: I can have a look in a bit just reflashed to get the ofono stuff tested quickly
[18:57] <tedg> brendand, You can't really unfortunately, it's an issue between LP and the package. It's before it gets on the device.
[18:57] <tedg> davmor2, Okay, they should be still there if you didn't wipe.
[18:58] <dbarth_> Saviq: not been able to smoke test things this afternoon btween meetings and dev. mode; re-trying now
[18:58] <Saviq> dbarth_, I'll set it to not tested then
[18:58] <brendand> tedg, so what's the effect? the string should be translatable now?
[18:58] <davmor2> tedg: I always wipe, it gives me a clean image to test against
[19:00] <Saviq> dbarth_, FWIW it only built like an hour and a half ago... it takes 5½h to build on armhf...
[19:00] <Saviq> ok finished 3h ago
[19:00] <Saviq> still
[19:00] <tedg> brendand, Not translatable, that the character when imported into launchpad should be readable in the webui.
[19:03] <davmor2> brendand, ogra_: confirming what kenvandine spotted that his fix which is in image 26 fixes the sim unlock issue on first boot
[19:04] <kenvandine> davmor2, thx
[19:04] <ogra_> yay
[19:04] <ogra_> so no extra blocker for that one ... good :)
[19:04] <davmor2> ogra_: also I think the location blocker can be killed now
[19:04] <dbarth_> Saviq: uh, i thought this was a binary copy in that case
[19:05] <dbarth_> Saviq: building oxide indeed takes a looong time
[19:05] <ogra_> davmor2, great ... sad that none f the changelogs did auto-close it though :)
[19:05] <ogra_> davmor2, i'll mark it fix released when assembling the mail later
[19:05] <Saviq> dbarth_, yeah, not safe, silo ppas use proposed and stuff, I don't think they'd like bincopy to archive from a PPA other than the silos
[19:09] <davmor2> tedg: so I just repeated the test on this fresh install where will any issues show up?  .cache/url-dispatcher or elsewhere
[19:11] <tedg> davmor2, /var/crash
[19:11] <tedg> davmor2, They should show up as recoverable errors.
[19:11] <davmor2> tedg: nope I only see trust-store-skeleton and unity8
[19:15] <tedg> davmor2, Hmm, that's odd.
[19:15] <lool> trainguards, the testplan proposed for silo 6 RTM wasn't working and needs to be updated (completely unrelated to the changes), can we keep the silo for a bit longer while we update the testplan (tomorrow UTC morning I guess)
[19:15] <tedg> Not sure they're getting to URL dispatcher then.
[19:20] <davmor2> tedg: ouch that could be much worse then
[19:20] <tedg> davmor2, Yeah, let me look into it some.
[19:20] <tedg> davmor2, This is off an image, right?
[19:20] <davmor2> tedg: thanks
[19:20] <tedg> davmor2, Or do I need a silo?
[19:21] <davmor2> tedg: no image 25/26
[19:21] <tedg> davmor2, Same on utopic?
[19:21] <davmor2> tedg: I don't have a utopic device currently both on rtm
[19:22] <tedg> davmor2, Okay, I'll switch mine over to be sure.
[19:25] <cyphermox_> robru: around?
[19:29] <pmcgowan> is anyone messing with launchpad team membership?
[19:29] <pmcgowan> I seem to have lost my powers
[19:29] <awe_> davmor2, can I publish?
[19:30] <davmor2> pmcgowan: are you logged in, I discovered that if there is  a db update you are logged out sometimes
[19:30] <pmcgowan> seb128, you know anything? I cant manage system settings anymore
[19:30] <pmcgowan> davmor2, yes logged in
[19:30] <seb128> pmcgowan, did you expire from any team?
[19:31] <pmcgowan> seb128, no email I saw
[19:31] <pmcgowan> let me check junk
[19:31] <davmor2> pmcgowan: click on you personal tab and see if you have all team memberships
[19:32] <pmcgowan> lp keeps timing out
[19:32] <dbarth_> Saviq: ok, works as expected; i think we can re-try to land silo 2 now
[19:32] <pmcgowan> one of those days
[19:32] <davmor2> awe_: sim unlock is working consistently, sim selection works, second sim seems more stable (no guarantee on that ), sms works, calls in an out work
[19:33] <awe_> it's exactly what we landed in utopic
[19:33] <awe_> just needed a sanity check
[19:33] <awe_> and it was fully tested yesterday by me, the landing just vanished
[19:33] <pmcgowan> seb128, which team is bug maintainer or whatever for system settings?
[19:33] <awe_> so I think we're good to go
[19:33] <davmor2> awe_: yeap it is looking good here
[19:33] <seb128> pmcgowan, you triage the ubuntu package bugs right?
[19:34] <pmcgowan> seb128, right
[19:34] <davmor2> awe_: I see no crashes
[19:34] <dbarth_> seb128: did silo 15 land to get my location stuff next?
[19:34] <awe_> davmor2, ok... then I'll go ahead an publish
[19:34] <pmcgowan> seb128, but suddenly I cant set importance and assignment
[19:34] <awe_> your bug-control membership probably expired
[19:34] <seb128> pmcgowan, can you check if you are in https://launchpad.net/~ubuntu-bugcontrol ?
[19:35] <awe_> ;)
[19:35] <pmcgowan> seb128, trying, p not answering my partiticpation
[19:35] <seb128> just open this page
[19:35] <seb128> it should write your status
[19:35] <seb128> it write that here " You are an indirect member of this team: "
[19:36] <pmcgowan> seb128, says I am not a member
[19:36] <seb128> there you go
[19:36] <davmor2> Right I'm outta here night all
[19:36] <pmcgowan> seb128, how'd that happen I wonder
[19:37] <seb128> pmcgowan, get mhall119 or bdmurray to add you back
[19:37] <kenvandine> seb128, can you test silo 14?
[19:37] <seb128> pmcgowan, default membership expire after 1 year I think
[19:37] <seb128> kenvandine, sure
[19:37] <kenvandine> seb128, specifically updates, with the system-image-dbus problem i'm seeing, i want someone else to verify :)
[19:38] <seb128> pmcgowan, you should have received emails about the expiration though ... do you ignore launchpad emails? ;-)
[19:38] <pmcgowan> seb128, uh oh
[19:38] <pmcgowan> ;)
[19:38] <pmcgowan> I may have a filter thats a tad too aggressive
[19:38] <mhall119> pmcgowan: what do you need adding to?
[19:38] <seb128> hehe
[19:38] <pmcgowan> lol
[19:38] <pmcgowan> mhall119, ubuntu-bug-control
[19:38] <seb128> ~ubuntu-bugcontrol he means
[19:38] <robru> cyphermox_: nah I'm off sick
[19:39] <pmcgowan> yeah that
[19:39] <robru> lool: feel free to keep it
[19:39] <cyphermox_> robru: who's looking after things? should I pay more attention to the landings?
[19:39] <mhall119> pmcgowan: what's your LP id?
[19:39] <pmcgowan> seb128, thanks, I will make a NEW filter for those
[19:39] <robru> cyphermox_: yeah if you don't mind, sorry i should have pinged you
[19:39] <pmcgowan> mhall119, pat-mcgowan
[19:40] <seb128> pmcgowan, yw! did you find the emails?
[19:40] <cyphermox_> robru: depends if there was someone from your team or something already meant to be handling this
[19:40] <pmcgowan> seb128, yes, sigh
[19:40] <mhall119> pmcgowan: added you
[19:40] <pmcgowan> mhall119, ty
[19:40] <mhall119> np
[19:40] <seb128> pmcgowan, well, at least it explains the issue ;-)
[19:40] <pmcgowan> indeed
[19:40] <robru> cyphermox_: it should be in a reasonable state, ping me if anything really horrible comes up (like tracebacks in the logs)
[19:40] <cyphermox_> ack
[19:40] <barry> robru: i guess i can help with landings, if i can remember how to do it and can muddle through whatever new rules there are for rtm
[19:41] <robru> barry: haha, best bet is just let other people tell you what to do.
[19:41] <barry> robru: i am a good monkey, as you know
[19:41] <cyphermox_> barry: we can look at things
[19:42] <barry> cyphermox_: cool, thanks.  do ping me if you need a hand
[19:42] <dbarth_> hey guys, so i re-verified silo 2 now
[19:42] <cyphermox_> yeah
[19:42] <dbarth_> with the included oxide-qt packags to fix the dep problem
[19:42] <cyphermox_> ok
[19:43] <dbarth_> you should be able to clean th situation there, to let unity8 and Saviq land his work
[19:44] <cyphermox_> omg
[19:46] <cyphermox_> davmor2: still around?
[19:50] <jdstrand> elopio, ToyKeeper: fyi, rtm silo 002 is ready for QA signoff
[19:51] <cyphermox_> dbarth_: so what did you change, basically just copying oxide-qt to the silo, re-testing?
[19:52] <dbarth_> cyphermox_: yes
[19:52] <dbarth_> cyphermox_: to resolve the dependency in webbrowser-app
[19:52] <cyphermox_> no code changes?
[19:53] <dbarth_> nope
[19:53] <dbarth_> just smoke testing once oxide was part of the silo
[19:53] <cyphermox_> ok
[19:53] <dbarth_> i did a clean flash to r234, devmode
[19:53] <dbarth_> then apt-add-repo
[19:55] <cyphermox_> right
[19:56] <cyphermox_> so oxide-qt is already in utopic, it's just that u-s-s-o-a is blocked because of architectures for which oxide-qt isn't available, and webbrowser-app regressed a test because of oxide, and probably needs that test to be re-run
[20:01] <dbarth_> cyphermox_: oxide-qt 1.2~bzr was in utopic this morning, not 1.2 final
[20:01] <dbarth_> cyphermox_: this is what i understood blockd the whole landing
[20:01] <cyphermox_> yes
[20:01] <cyphermox_> just a minute :)
[20:01] <dbarth_> nw
[20:06] <tedg> davmor2, https://bugs.launchpad.net/url-dispatcher/+bug/1367400/comments/2
[20:06] <tedg> davmor2, What did I do different there?
[20:06] <elopio> jdstrand: I hope ToyKeeper can take that one. I'll check back later if it's still pending.
[20:07] <elopio> tedg: davmor2 is gone for today.
[20:07] <cyphermox_> dbarth_: what is ubuntu-system-settings-online-accounts using oxide-qt for? does it totally fail if oxide-qt is unavailable?
[20:07] <jdstrand> elopio, ToyKeeper: ack, I'll be stepping away for a bit, but read backscroll.
[20:07] <cyphermox_> dbarth_: I think the depends should be adjusted to not require oxide-qt on powerpc/ppc64/arm64, where it's not available.
[20:08] <tedg> elopio, Ah, okay. I'll just mark it "incomplete" then.
[20:08] <dbarth_> cyphermox_: it's using its webview and captures cookies
[20:08] <cyphermox_> so very crippling? ;)
[20:08] <dbarth_> cyphermox_: the cookie API changed between oxide 1.2~bzr, and 1.2 final
[20:09] <dbarth_> cyphermox_: yes, that's why they are in the same silo
[20:09] <cyphermox_> hm
[20:09] <cyphermox_> the thing is, oxide-qt never built on these arches, or at least 1.2~bzr doesn't seem to have
[20:09] <dbarth_> cyphermox_: but i checked that use case as well, ie create an account, enable the webapp, and autologin in twitter
[20:09] <dbarth_> yeah!
[20:09] <cyphermox_> so the depends was added?
[20:09] <dbarth_> hmm, not sure for ussoa
[20:10] <dbarth_> cyphermox_: yes, it was added as well:
[20:10] <dbarth_> +         liboxideqt-qmlplugin (>= 1.2.0),
[20:10] <cyphermox_> I see that
[20:11] <cyphermox_> yuck
[20:13] <cyphermox_> so it seems to me like the correct fix would be to limit which architectures ussoa builds on, but it's kind of awkward to do while it's half-landed as far as citrain is concerned
[20:14] <cyphermox_> rsalveti: awe_: btw, I would like to land your ofono landing as requested, but the spreadsheet line isn't set to testing pass; could you adjust that if it really was tested and good?
[20:14] <dbarth_> long thread, but cjwatson essentially recommends not to put any arch-specific constraints here
[20:14] <cyphermox_> rsalveti: ^since you can confirm, this was requested by awe_
[20:14] <cyphermox_> oh
[20:15] <cyphermox_> dbarth_: could you point me to the thread?
[20:16] <dbarth_> cyphermox_: scroll back to this morning here, between Saviq and cjwatson
[20:16] <rsalveti> cyphermox_: awe_ was testing that one, let's wait his feedback
[20:16] <dbarth_> but the qustion was raised on a couple of occasions already
[20:17] <cyphermox_> rsalveti: well, he asked me a few minutes ago before leaving to the gym
[20:17] <cyphermox_> rsalveti: but the spreadsheet state doesn't match :)
[20:17] <cyphermox_> dbarth_: ok, let me read it and get it back up to speed on this, to really understand what to do
[20:19] <Saviq> dbarth_, thanks, cyphermox_, it's basically about publishing oxide-qt from silo 2 and once in proposed retrying the failed adt runs for ussoa, unity-scope-click etc.
[20:19] <cyphermox_> yes
[20:19] <balloons> plars, re: fm and terminal failures. Are we ok with letting those ride for the moment as they are only on utopic?
[20:20] <plars> balloons: that's a question for sil2100, but iirc they are also failing on rtm
[20:21] <plars> yeah, there's quite a few failures on rtm for them also. Either way, I'd suggest looking at those
[20:22] <cyphermox_> dbarth_: Saviq: as I understand it, cjwatson was fine with uninstallables for this kind of case. I hope I'm reading this right
[20:22] <balloons> plars, can you provide a complete link? I see very small runs for those on rtm
[20:22] <balloons> plars, mm.. touch-stable I guess has the full runs
[20:23] <Saviq> cyphermox_, you mean that on some arches you won't be able to install? I believe so, that was the case before already
[20:23] <cyphermox_> yes
[20:24] <Saviq> cyphermox_, our discussion was really about whether packages that only build on certain arches should be limited, and Colin said that shouldn't be the case except when it's known that it will basically never be possible to build, otherwise we want the failures to be visible
[20:24] <Saviq> cyphermox_, as for uninstallables, it's probably best to make such a dependency optional if at all possible
[20:24] <cyphermox_> yeah
[20:25] <cyphermox_> Saviq: this case doesn't seem to be
[20:25] <cyphermox_> tedg: charles: I'm looking into the failure above
[20:26] <charles> cyphermox_, ty
[20:26] <cyphermox_> dbarth_: Saviq: I asked on #u-release to have the proper steps taken, but it seems like there is nothing needed at the citrain level
[20:26] <cyphermox_> once things transition from proposed it will get cleared up
[20:26] <Saviq> cyphermox_, one thing at least is needed, is to publish oxide-qt, is it in proposed already?
[20:26] <cyphermox_> it's already in the archive
[20:27] <Saviq> ah
[20:27] <Saviq> cyphermox_, then yeah, adt just needs reruns then
[20:28] <cyphermox_> yes, and ussoa forced in
[20:28] <Saviq> right
[20:28] <cyphermox_> as per my last messages in #ubuntu-release
[20:28] <tedg> cyphermox_, Sorry, confused, which one?
[20:29] <infinity> Saviq: The simple way to satisfy both the "don't build on arches where it can't install" and "make the failure visible" cases are to build-dep on the thing you depend on.
[20:30] <cyphermox_> rtm silo 1
[20:30] <Saviq> infinity, right, makes sense
[20:30] <infinity> ie: if ubuntu-system-settings-online-accounts had a build-dep on liboxideqt-qmlplugin, it would dep-wait on all those arches instead of building a useless binary.
[20:31] <tedg> cyphermox_, Ah, I see. Thanks!
[20:31] <infinity> cyphermox_ / Saviq: You can read the above as "no, I won't force in ussoa and raise the uninstallable count".
[20:32] <cyphermox_> I did read it that way
[20:32] <cyphermox_> I was just thinking "why didn't I think of it"
[20:32] <Saviq> infinity, well, the count is already there
[20:32] <balloons> plars, right.. since pin/pass is set on phones, rtm is affected too. I don't see an open bug for it, I will file one if you confirm there isn't one
[20:32] <cyphermox_> now, the problem is also how to fix this in citrain with the least amount of pain
[20:32] <cyphermox_> ie. on a half-done landing
[20:32] <Saviq> infinity, that situation is already there in the archive, I'd say we need a bug against ussoa instead
[20:33] <infinity> Saviq: Err, no.
[20:33] <infinity> Saviq: The "situation" is in proposed, which is exactly what proposed is there for.  TO prevent the situation migrating to release.
[20:33] <infinity> Saviq: "It's broken in proposed, may as well call it a wash" would be ignoring the whole point of porposed. :P
[20:33] <Saviq> infinity, ah, I thought that was just a bumped dep, not a completely new one
[20:34] <infinity> Saviq: It's a new dep.
[20:34] <Saviq> infinity, no no, I thought it wasn't a new dep
[20:34] <Saviq> right
[20:34] <cyphermox_> itś a new dep
[20:34]  * Saviq wonders if it was just a missing dep before, i.e. it didn't work anyway...
[20:35] <infinity> Whee, and it has rdeps too, of course.
[20:35] <infinity> So glad we keep picking technologies that aren't actually ported.
[20:36] <dbarth_> cyphermox_: ok, so i guess all good for today
[20:36] <dbarth_> see you
[20:36] <cyphermox_> dbarth_: sorry, just trying to pick this up and piece the information back together
[20:36] <Saviq> infinity, could you upload a fixed packaging version to proposed directly and we'll resync trunks as needed?
[20:37] <infinity> Saviq: I could, but I'm taking a sick day and not actually home.
[20:37] <cyphermox_> Saviq: I can do that, it was mostly just a matter of figuring out *what* to do
[20:37] <Saviq> infinity, ah sorry, take care then
[20:37] <infinity> I wonder how painful it would be to port oxide to the 3 arches where it's FTBFS.
[20:38] <Saviq> infinity, it was missing "gyp" which IIUC is some google built-time tool thingy
[20:38] <infinity> Saviq: No, no, gyp isn't missing, it's just missing platform definitions.
[20:38] <Spads> also a racial slur
[20:39] <infinity> That bit is easy, what's not is that it might explode later. :P
[20:39] <Saviq> infinity, right
[20:39] <Saviq> Spads, ;)
[20:39] <infinity> I could probably convince IBM to fix it on ppc/ppc64el, but not sure who I'd talk into fixing arm64.
[20:40] <infinity> And arm64 is something we should really deeply care about, since phones are going that route.
[20:40] <infinity> We won't be armhf forever.
[20:41] <Saviq> +1
[20:42] <infinity> cyphermox_: That'll still need some archive admin massaging once it stops building on those arches, so give me a ping when it's all built and stuck.
[20:43] <cyphermox_> ok
[20:43] <cyphermox_> thanks
[20:43] <Saviq> cyphermox_, ok, so to resolve this I believe we need just a bit of packaging changes (build-dep on liboxideq-qmlplugin) and the rdep infinity mentioned
[20:43]  * cyphermox_ stabs iwldvm
[20:43] <Saviq> cyphermox_, so I'd vote for uploading a fixed version directly and we'll handle the resync tomorrow
[20:43] <cyphermox_> brb; I first need to fix my wifi if I want to be ableto upload anything at all
[20:44] <Saviq> sure
[20:46] <infinity> It would probably be nice to make ubuntuone-credentials build-dep on ubuntu-system-settings-online-accounts to give the same hackish workaround.
[20:46] <infinity> All the other rdeps are arch:all and thus not a big deal.
[20:52] <infinity> Argh.
[20:52] <infinity> cyphermox_: Hold the phone.
[20:52] <cyphermox_> aye
[20:52] <infinity> cyphermox_: The second level of rdeps has a ton of arch-specific stuff. :/
[20:53] <cyphermox_> where are you looking so that I can look at the same place?
[20:53] <infinity> cyphermox_: reverse-depends ubuntu-system-settings-online-accounts, and then drill down.
[20:53] <infinity> So, removing this will break severl other bits (singon stuff, sync-monitor, etc)
[20:54] <infinity> OOI, why was the new dep needed? :P
[20:56] <infinity> Still not happy about forcing it in, mind you.  But not keen on rebuilding the whole rdep stack just to perpetuate the build-dep hacks and remove a bunch more binaries.
[20:56] <cyphermox_> I can file a bug about how damanged the situation is
[20:57] <infinity> "Use new Oxide cookie API"
[20:57] <infinity> Oh.
[20:57] <infinity> Are we pulling in a whole web rendering engine just for cookies? :)
[20:58] <cyphermox_> why not? :)
[21:05] <cjwatson> infinity: there's no reason why we can't do a binaryful copy into a silo.  citrain doesn't support it but you can do copy-package -b.
[21:06] <cjwatson> infinity: people seem to be paranoid and want rebuilds for some reason but if anyone thinks that's reasonable for glibc I will be happy to challenge them to explain why
[21:07] <cjwatson> awe_: fiddly I'm afraid because you have to do amusing things to debootstrap - for the time being it's probably best to grab the one linked from https://api.launchpad.net/devel/ubuntu-rtm/14.09/amd64 or similar
[21:15] <infinity> cjwatson: So, thoughts on ubuntu-system-settings-online-accounts?
[21:16] <infinity> cjwatson: New dep on oxide makes it uninstallable on 3 arches, the naive fix would be to build-dep on oxide and stop building it,but that has rdep fallout that cascades anyway, so we either propagate the same hack to N packages, where N is approaching 10, or just force the count up. :/
[21:16] <cyphermox_> jhodapp: could you check what's up with your package in rtm silo 5?
[21:16] <cjwatson> infinity: Ugh.  Might be worth sucking it up for now; online-accounts is always tricky
[21:16] <infinity> cjwatson: I'm leaning to the latter for now, after evangelising the former.
[21:16] <cjwatson> I suspect it will need something more involved
[21:17] <cjwatson> infinity: You'll want both force and force-hint IIRC
[21:17] <infinity> cjwatson: Well, what it really wants is oxide ported (or, hey, Canonical stopping this "it exists on an arch and a half, sweet, let's standardise on it" trend), but meh.
[21:19] <cjwatson> Agreed
[21:20] <infinity> cjwatson: And yeah, I know I *can* do a binary copy to a silo (well, since I'm in a group that can upload to them anyway), I was just arguing with people who seem rebuild happy. ;)
[21:21] <infinity> cjwatson: And I think when I initially asked "how do we do this", I was assuming a copy straight to RTM, bypassing CI.
[21:22] <cjwatson> I think you should ignore the rebuild bit and JFDI.  Going through a silo for QA is sane; rebuilding glibc because the copied binaries might depend on some incompatible ABI (in, er, what exactly?) isn't.
[21:22] <cjwatson> It would be helpful for reduction in later panic if you could get QA signoff on the silo though.
[21:22] <balloons> plars, I filed https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1367453, just fyi for the failures
[21:22] <cjwatson> Otherwise we'll spend ages with people wanting to ascribe whatever's broken tomorrow to glibc ...
[21:23] <plars> balloons: ack
[21:37] <Saviq> infinity, so, FWIW, the dependency is not new (except it is new in debian/control), online accounts actually render web pages to log into services
[21:38] <Saviq> infinity, so it basically should've been there already months ago, and now only bumped to use the new API calls
[21:50] <cjwatson> qtcreator-plugin-ubuntu autopkgtest worked on retry; should clear some things out, including ubuntu/landing-003
[21:51] <cjwatson> Retrying unity-scope-click autopkgtest too on the off-chance
[21:53] <infinity> cjwatson: Heh.  Well, I'll dance through the paperwork and hoops tomorrow for glibc, then.
[22:10] <cjwatson> unity-scope-click passed too.
[22:15]  * cjwatson squints at citrain
[22:15] <cjwatson> In what sense is ubuntu-rtm/landing-001 "All packages are in destination"?
[22:16] <cjwatson> The PPA has 13.10.0+14.10.20140908.1~rtm-0ubuntu1, but no sign of that in https://launchpad.net/ubuntu-rtm/+source/indicator-datetime/+publishinghistory
[22:16] <cjwatson> robru,cyphermox_,rsalveti: I'm probably not the first to notice this, but don't believe citrain's lies for merge-and-cleanliness of sync silos
[22:16] <cjwatson> tedg: cc ^-
[22:17] <cyphermox_> yeah, it happened to me before
[22:17] <cyphermox_> it´s early enough that it´ s easier to fix
[22:22] <infinity> cyphermox_: For better or worse, ubuntu-system-settings-online-accounts is migrated now.
[22:30] <cyphermox_> infinity: thanks
[22:36] <robru> cjwatson: yeah i know, it fails on sync silos when the package names are implicit (eg sync:n silos). The other symptom of this issue is the lack of package names appearing in the dashboard. I was hoping to fix it bit I'm sick :-(
[22:42] <cjwatson> robru: ok, just wanted to make sure you knew about it, thanks, GWS
[22:43] <cyphermox_> cjwatson: so I guess it´s time to copy-package
[22:44] <cjwatson> ah yes, it's tested
[22:44] <cyphermox_> how can I specify ubuntu-rtm proposed?
[22:44] <cjwatson> $ copy-package --from=~ci-train-ppa-service/ubuntu-rtm/landing-001 --from-suite=14.09 --to=ubuntu-rtm --to-suite=14.09-proposed -b indicator-datetime
[22:44] <cyphermox_> ah!
[22:44] <cjwatson> I have it queued up here if you want ...
[22:44] <cyphermox_> feel free
[22:45] <cjwatson> done
[22:45] <cyphermox_> I'm trying to follow a discrete math class :)
[22:45] <cjwatson> you'll have to watch rmadison or something for when it's actually M&Cable
[22:45] <cyphermox_> sure
[22:45] <cjwatson> or I guess https://launchpad.net/ubuntu-rtm/+source/indicator-datetime/+publishinghistory
[22:45] <cjwatson> damn that hit Published quick :)
[22:45] <cjwatson> (in -proposed)
[22:45] <cyphermox_> woo
[22:51] <cjwatson> ok, published for real in 14.09 now; ubuntu-rtm runs quickly when it feels like it
[22:51] <cjwatson> cleaning
[22:53] <cyphermox_> ah, yeah you want to tick the ignore project checkbox
[22:53] <cjwatson> had to ... that
[22:53] <cyphermox_> dah
[22:54] <cyphermox_> hmm, means I'll go merge the branch in manually
[22:54] <cjwatson> there's no 14.09 branch anyway
[22:54] <cjwatson> which is reasonable since it's a sync
[22:54] <cyphermox_> oh, true
[22:54] <cjwatson> well, except a pseudo-sync with a different version number, but anyway
[22:55] <cyphermox_> ah, I meant to ask about this
[22:56] <cyphermox_> why are these syncs with ~rtm- ..., a version number lower than what's in utopic?
[22:57] <cjwatson> I haven't the faintest idea
[22:57] <cyphermox_> ah, I thought it was somehow done on purpose, for some reason I didn't think of
[22:57] <cjwatson> well, I mean in general it's probably to reduce the incidence of different binaries with the same version number
[22:58] <cjwatson> but I don't think I agree with the practice of rebuilding
[22:58] <cjwatson> lower than utopic will be because these are morally sort of backports - we want utopic to supersede eventually
[22:58] <cyphermox_> I was really expecting ubuntu -> ubuntu-rtm  transitioning to work much the same as debian -> ubuntu
[22:59] <cjwatson> the problem with that is that we're going to want to bulk-copy utopic (or v) over the top for the next time round
[22:59] <cjwatson> we might have a problem with mismatching binaries with the same version when we get there
[22:59] <cyphermox_> ok
[23:00] <cjwatson> anyway, tired, ICBW, night
[23:00] <cyphermox_> good night, and thanks again!
[23:03] <cyphermox_> lies
[23:09] <Saviq> cyphermox_, thanks!
[23:10] <cyphermox_> Saviq: np
[23:17] <ToyKeeper> Is it a known, expected thing that 'phablet-click-test-setup' by itself fails on a rtm image?  (fails while trying to get a unity8 package from LP)
[23:20] <cyphermox_> what's the error message?
[23:20] <cyphermox_> I guess it could well not work
[23:21] <ToyKeeper> cyphermox_: pull-lp-source: Error: Failed to download: https://launchpad.net/ubuntu/+archive/primary/+files/unity8_8.00+14.10.20140903.1~rtm-0ubuntu1.dsc: 404 Not Found
[23:22] <cyphermox_> yeah, that's broken alright
[23:22] <cjwatson> --distribution=ubuntu-rtm
[23:22] <cjwatson> oh and probably --series=14.09
[23:23] <cyphermox_> cjwatson: are those parameters that can be passed to phablet-click-test-setup?
[23:23] <ToyKeeper> Nope.
[23:26] <cyphermox_> ToyKeeper: update your phablet-tools maybe?
[23:26] <cyphermox_> seems to be in lp:phablet-tools
[23:28] <ToyKeeper> cyphermox_: *facepalm* ...  thanks.  :)
[23:32] <ToyKeeper> ... and now it's failing on UITK.  I get the feeling I might need to bug bzoltan about this though.
[23:32] <ToyKeeper> (because I think I found the reason why he's getting different test results than QA)