/srv/irclogs.ubuntu.com/2014/09/09/#ubuntu-ci-eng.txt

bfillerrobru: hmn, no idea00:42
kenvandinebfiller, rogue robots proposing branches? :-D00:43
bfillerrobru: those MR's have already been merged from the ubuntu release00:44
robrubfiller: great00:45
robrubfiller: did you test it in rtm?00:45
bfillerrobru: yes I tested the click package in both ubuntu and rtm00:46
bfillerworks fine00:46
kenvandineit's pretty amazing... the here location service stuff is working really well on my mako!01:08
kenvandinetotally not working on my krillin...01:09
kenvandinebut... it gets a location amazingly fast on mako :-D01:09
kenvandineand it's nice to see the apps listed on location access in system-settings :)01:09
ToyKeeperbzoltan: 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
kenvandineToyKeeper, that makes me sad :(01:15
kenvandineToyKeeper, bug i'm am really thankful you are catching them :)01:15
kenvandines/bug/but01:15
ToyKeeper... should have found it earlier, but it sounded like brendand had another issue blocking it so I was waiting on him.01:16
jdstrandhmmm01:23
robrujdstrand: citrain woes? I broke everything, working on it though01:24
jdstrandrobru: I needed to copy in a new version of apparmor to utopic silo 01401:24
jdstrandok01:24
jdstrandyeah I tried a reconfigure, had an error so I did a prepare. the prepare had an import error01:25
jdstrandso, I leave you to it01:25
jdstrandI'll*01:25
jdstrand(this was utopic silo 014 if you wanted something to look at)01:25
robrujdstrand: nope I got it, thanks01:25
jdstrandcool. I'll keep an eye out here for when things are fixed again01:26
jdstrandthanks01:26
robrujdstrand: ok it should be working right now, please try again ;-)01:26
jdstrandoh, that was fast :)01:27
robrujdstrand: yeah it was a silly mistake, fixed it easily ;-)01:27
jdstrandok, the reconfigure worked01:27
kgunnrobru: hesitant to ask you in the midst of ci-woes, but any ideas or help on stuck unity8 migration? silo1901:34
jdstrandrobru: all seems fine, thanks!01:35
robrujdstrand: you're welcome!01:37
robrukgunn: not sure, retrying the adt runs for you01:37
robru(apparently I can do that...)01:37
kgunnthanks...01:38
robrukgunn: but otherwise you should ping an #ubuntu-release person for -proposed migration issues, like infinity or cjwatson01:38
kgunni see in ubuntu-release some discussion about it...and it being complex and may need a01:39
kgunna pitti to look at it01:39
imgbot=== trainguards: IMAGE 234 building (started: 20140909 02:05) ===02:04
robruhttps://ci-train.ubuntu.com/job/deploy-citrain/250/console God. Fucking. Damnit.02:06
robruI want that hour of my life back.02:06
robruhttp://bazaar.launchpad.net/+branch/cupstream2distro/revision/721#citrain/manual/jenkins-templates/prepare-silo-manual.xml.tmpl02:07
imgbot=== trainguards: RTM IMAGE 24 building (started: 20140909 03:05) ===03:04
=== cprov__ is now known as cprov
bzoltanrobru:  are you still around?03:41
bzoltanI do not get what the problem is here: https://ci-train.ubuntu.com/job/ubuntu-landing-010-1-build/52/console03:41
=== psivaa_ is now known as psivaa
imgbot=== trainguards: IMAGE 234 DONE (finished: 20140909 03:50) ===03:49
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/234.changes ===03:50
Mirvbzoltan: the gles upload probably gets rejected for some reason or another. as you can see, ppa doesn't have it despite multiple builds04:11
bzoltanMirv:  I see that. What i do not see is why it happens04:12
bzoltanMirv: "Some source packages were never published in the ppa" No shit, Sherlock ... that is a new package I just added to the sheet.04:12
bzoltanMirv: and the QtC pugin package gets rejected too in the same PPA.04:13
MirvI don't see anything wrong with the mp :(04:16
bzoltanMirv:  Me neither. Maybe a reconf helps04:19
imgbot=== trainguards: RTM IMAGE 24 DONE (finished: 20140909 04:20) ===04:19
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/24.changes ===04:20
bzoltanMirv:  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:21
bzoltanMirv:  and the other proble is that the cick+qtc-plugin-ubuntu is blocked http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html04:24
bzoltanMirv:  and so that blocks the next landing :(04:24
bzoltanMirv:  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:25
ToyKeeperbzoltan: 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:28
bzoltanToyKeeper: I have logs from the 128 AP tests of the ubuntu_system_settings. Al OK04:29
bzoltanAll04:29
ToyKeeperbzoltan: I got 6-7 failures out of 128.  The base image was 122/122 pass.04:29
bzoltanToyKeeper: I was running during my night against the  image #23304:30
bzoltanToyKeeper:  here are the logs ->  http://paste.ubuntu.com/8296368/04:31
ToyKeeperThe 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:31
ToyKeeperAt least, for a rtm landing anyway.04:32
bzoltanToyKeeper:  I have run 17 times the  ubuntu_system_settings tests during the last 7 days. Never seen  a single faiure.04:32
bzoltanToyKeeper:  I can take a look.04:33
bzoltanToyKeeper:  do you have the logs?04:34
ToyKeeperbzoltan: 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
bzoltanToyKeeper:  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:35
Mirvbzoltan: right, that migration needs resolving first. I tried reconfiguring the new silo but I think it's probably something else. very weird errors.04:36
ToyKeeperbzoltan: 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:37
bzoltanToyKeeper: What image do you test agains?04:38
ToyKeeperbzoltan: Latest krillin rtm image, whatever it is.  Today it was #23.04:39
bzoltanToyKeeper:  The first few faiures are "autopilot.exceptions.StateNotFoundError: Object not found with name '*' and properties {'objectName': 'dialpadSounds'}." That is a classic flakiness04:39
ToyKeeperI 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
bzoltanToyKeeper:  who is developing the AP tests for that app?04:40
ToyKeeperbzoltan: Flakiness?  Not sure who wrote those bits of code.04:41
bzoltanToyKeeper: 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
ToyKeeperbzoltan: In any case, it seemed curious that 6 tests were added and 6-7 tests failed.04:42
ToyKeeperAt the moment I don't have the silo installed.04:42
bzoltanToyKeeper:  I do not know what causes the problem there :( But the logs do not point  to the UITK04:43
ToyKeeperbzoltan: 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:44
bzoltanToyKeeper:  I do not like to run apt-get dist-upgrade because it brings other packages too04:45
ToyKeeperbzoltan: That's why I disable all other package sources first... so that it can *only* get packages from the silo.04:45
bzoltanToyKeeper:  I see04:45
ToyKeeperIt 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
bzoltanToyKeeper:  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:46
ToyKeeperFor 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:47
bzoltanToyKeeper: http://paste.ubuntu.com/8296476/  `./uitk_test_plan.sh -c -p ppa:ci-train-ppa-service/landing-010 -f system_settings`04:48
ToyKeeperEr, 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:48
ToyKeeperbzoltan: I do not have uitk_test_plan.sh...  I have only https://wiki.ubuntu.com/Process/Merges/TestPlan/ui-toolkit04:49
bzoltanToyKeeper:  That script is in the UITK source tree tests/ and this version is in the actual release candidate.04:49
bzoltanToyKeeper: that script executes the UITK tesp plan.04:49
bzoltanToyKeeper: It is a lot help ...04:50
ToyKeeperIf the test plan is a shell script, the documentation needs to point to that instead of what it says now.04:50
bzoltanToyKeeper: I need to update the test plan04:50
ToyKeeperQA is executing the test plan in the wiki, because that's what's linked to from the landing spreadsheet.04:51
ToyKeeperIf the test plan is wrong, it's kind of an automatic fail.04:51
bzoltanToyKeeper: That script is a new development. I made it to make my life less miserable.04:51
bzoltanToyKeeper: I do not think QA would ever run my script :)04:52
bzoltanToyKeeper:  that script is for local validation04:52
ToyKeeperI was very tempted to make a script like that earlier today, since uitk tests are almost entirely automated anyway.04:53
ToyKeeperI'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:54
ToyKeeperI'm of the opinion that anything which can be automated should be.04:55
Mirvhmmh05:33
Mirvrobru: 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.05:34
bzoltanmvo_: the cick and qtc plugin landing is stuck. Do you know how to make it move?06:05
bzoltanmvo_:  http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html  -> autopkgtest for click 0.4.29.1build1: Regression06:05
robrubzoltan: 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
robruI mean the one you pinged me about06:06
bzoltanrobru:  I have tried all combination of rebuilds... it seems that the silo is busted06:07
robrubzoltan: I'm afk but Mirv should be able to free and reassign06:07
Mirvrobru: I think manual upload might be the only option, or indeed freeing and reassigning06:08
Mirvrobru: that gallery-app rtm-020 silo is really weird06:08
robruMirv: yeah i have no idea what happened there. If it's a problem just free it and resynchronize utopic06:09
robruBrb06:10
MirvI'll do that06:10
Mirvor hmm, I could take someone to simply publish it manually06:10
mvo_bzoltan: yeah, we are waiting for the ubuntu-rtm QA verification06:16
mvo_bzoltan: the click/packagekit changes need to land there as well06:16
mvo_bzoltan: I should have waited with the publishing to -proposed even until it lands in ubuntu-rtm, but I made a mistake here06:17
Mirvbzoltan: 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:19
bzoltanmvo_: 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-proposed06:20
mvo_bzoltan: I look at the test failure right now06:20
bzoltanmvo_:  thanks. I totally forget about that landing. Because it actually blocks the next landing.06:21
Mirvmvo_: 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-click06:22
Mirvmvo_: 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
Mirvit was not even marked as "Ready", but I changed that to Yes now that it had a silo and had built already06:24
mvo_Mirv: oh? well I tested it yesterday and it should be good on utopic06:28
mvo_Mirv: its waiting for QA for the ubuntu-rtm landing06:28
mvo_Mirv: or am I missing something?06:28
Mirvmvo_: the line 39 says "Packages built", it's not "QA needs to sign off"06:37
Mirvmvo_: there's no "Testing pass?" set to "Yes" together with the rtm image number it was tested by upstream06:37
Mirvso upstream tests first, only after that QA will start testing06:38
mvo_Mirv: sorry for that, let me fix it06:38
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:40
Mirvmvo_: 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 silo06:41
mvo_Mirv: thanks, download is now running06:42
Mirvcjwatson: 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-app06:59
Mirvcjwatson: 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
Mirvthe silo just doesn't want to recognize there's something in it...07:00
didrockscihelp: ps-trusty-desktop-amd64-1 is down, can you turn it back up, please?07:19
Mirvthanks mvo!07:27
Mirvbrendand: 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
Mirvsince 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 still07:28
brendandMirv, i guess that's my next port of call then07:31
viladidrocks: 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:32
didrocksvila: he told me that for now we keep that machine until the migration is complete07:33
didrocksvila: and he rebooted it yesterday as well, due to the same issue07:33
didrocksso, if you can reboot it, that would be appreciated so that the daily tests can run :)07:33
viladidrocks: urgh, ok, let me see if those beasts are documented07:33
* didrocks crosses fingers :)07:34
didrocksvila: it's a vm AFAIK07:34
Mirvbrendand: that's a bit what I was thinking, thanks :)07:34
brendandexcept my krillin is not charged - hmmm.07:36
* brendand waits a few minutes07:36
viladidrocks: 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:38
didrocksvila: I guess on the same that the i386, I can connect on that one, but unsure how to know where the host is?07:39
vilahehe07:40
didrocksvila: the IP of the i386 vm is 10.98.2.79, if that can help07:40
vilano idea07:40
didrocksvila: s-jenkins is the jenkins connected to it07:41
vilathat was my guess, I'm there and searching07:41
didrocksvila: http://s-jenkins.ubuntu-ci:8080/computer/ps-trusty-desktop-amd64-1/07:42
viladidrocks: that doesn't tell us much does it ?07:42
viladidrocks: that's where the vm connect to but it can be anywhere07:42
didrocksyeah…07:43
vilano /var/lib/libvirt on s-jenkins, probably not there07:44
didrocksvila: ssh naartjie /usr/bin/sudo virsh snapshot-revert ps-trusty-desktop-amd64-1 141005682307:45
didrocksnaartjie maybe?07:45
didrocksvila: it's back online, calling the snapshot revert virsh command07:46
viladidrocks: looks more promising07:47
didrocksvila: so yeah, it's up now thanks to that, don't bother more! Thanks for looking :)07:48
vilaack07:48
brendandogra_`, what's the new option i need to specify to get developer mode enabled after flashing?08:02
brendandogra_`, apart from --developer-mode of course08:02
ogra_`pren--password=08:05
ogra_`err08:05
ogra_`brendand, --password= ... with a password supplied08:05
ogra_`robru, no landing mail ?08:07
MirvI more or less know the situation, but maybe robru will write a belated landing mail in his morning :)08:13
ogra_`Mirv, yeah, its not for me, i have some followers on G+ that read my re-post of them every day though08:15
ogra_`whats that dirt on my nick ?08:15
=== ogra_` is now known as ogra_
ogra_wiped away :)08:15
Mirv:)08:16
ogra_pete-woods, hmm, did you do the seed meger yourself ?08:16
ogra_*merge08:16
ogra_(the commit message looks like ...)08:17
pete-woodsogra_: I have no idea how I'd even do that08:18
ogra_funny ...08:18
* 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:20
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 explanation08:29
Saviqogra_, the error was only for our run-on-device script, so no impact on anything08:30
Saviqogra_, it's currently stuck in proposed due to oxide-qt fiasco08:30
Saviqdbarth_, you around?08:30
ogra_Saviq, ah, ok08:31
dbarth_Saviq: yes08:34
Saviqdbarth_, 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.208:35
dbarth_uh08:35
Saviqdbarth_, is there an actual oxide-qt 1.2 coming somewhere, or should the dependencies be >= 1.2~?08:35
MirvSaviq: I thought unity8 is stuck because of the click landings in -proposed?08:35
SaviqMirv, no, it's because ↑08:36
dbarth_Saviq: we should adjust dependencies08:36
dbarth_or rather08:36
dbarth_1.2 official should be in 1-2 weeks max.08:36
MirvSaviq: 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 soon08:37
SaviqMirv, that's what jibel_ found, yes08:37
Mirvok08:37
dbarth_that won't help fo today, so the easiest is to adjust deps i think08:37
=== jibel_ is now known as jibel
Saviqdbarth_, yeah, Mirv, can you please upload webbrowser-app and ubuntu-system-settings-online-accounts with the deps adjusted?08:38
MirvI'll help with silos when just told so08:39
dbarth_do you want me to upload a new set of packages to fix that?08:39
davmor2tvoss, 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 crashing08:40
tvossdavmor2, sorry, gimme 10 to context switch08:41
SaviqMirv, I thought you could upload directly to proposed to not wait for silo?08:42
MirvSaviq: no, I can't. in two weeks possibly for some packages.08:44
Mirvand Qt I can upload08: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
SaviqMirv, oh ok, can dbarth_ use the same silo then? can it be un-published?08:45
dbarth_ok, so i just rebuild in silo 2 and ping you back once done08:46
dbarth_Mirv: i'll double check deps with you in a minute08:46
dbarth_Saviq: actually there is an oxide-qt-1.2!08:50
dbarth_https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages08:50
dbarth_we prepared it last friday and i thought this was the one stuck08:50
popeyMirv: 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 correct08:51
popeyMirv: also http://s-jenkins.ubuntu-ci:8080/job/filemanager-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.filemanager_0.3.275_armhf.click  please08:52
Saviqdbarth_, when will it reach proposed at least then?08:53
Saviqdbarth_, because until it's in https://launchpad.net/ubuntu/+source/oxide-qt, stuff's broken08:54
Saviqdbarth_, so you know the fallout, even unity8 is blocked in proposed currently08:54
brendandmvo_, hello - i am testing silo 308:54
Saviqdbarth_, because UITK and click scope tests can't run due to the unsatisfiable dependency08:55
Saviqand that's what unity8 is gated on08:55
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 build08:57
brendandseb128, i'm hitting some problems with the reset device option on image 24 (which has the updated system settings)08:58
MirvSaviq: sorry still in meeting. same silo can probably be used in this case.08:58
brendandseb128, i recall kenvandine mentioned last week that he saw the same thing (before landing it)08:58
seb128brendand, what sort of reset?08:58
seb128brendand, the factory reset?08:59
brendandseb128, yeah erase and reset everything08:59
davmor2seb128: reset launcher is that meant to clear off any pinned apps if so it doesn't08:59
dbarth_Saviq: who has permissions to binary copy stuff to -proposed?08:59
brendandseb128, after pressing the button nothing happens08:59
seb128brendand, no idea about that, I never tried it and didn't work on it08:59
seb128davmor2, it's meant to reset the launcher as the title suggest08:59
dbarth_Saviq: from a test pov, i have checked that new build of oxide with webbrowser + core webapps, so it's good to go08:59
seb128davmor2, it only apply after restart, the dialog tell you about that no?08:59
brendandseb128, ok. is there anyone else around who might know about it or i suppose i need to wait for kenvandine?09:00
seb128brendand, jgdx but he might not be on yet09:00
davmor2seb128: no just a push button that says reset launcher there is no text anywhere09:00
Saviqdbarth_, 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
davmor2seb128: oh no it thows up a popup09:01
Saviqdbarth_, that Mirv can help you with (right Mirv?)09:01
davmor2that didn't happen before09:01
MirvSaviq: dbarth_: no I can't, you'll need a core-dev to copy to archives09:01
brendandcjwatson, is mvo_ around today?09:01
seb128davmor2, :-)09:01
Mirvlike ogra_ (in the same meeting)09:01
seb128brendand, he is, he said he had to be away from some minutes, a bit earlier on #distro09:02
Mirvbrendand: he was in the morning09:02
davmor2seb128: by before I mean like 2 minutes ago when I tried it09:02
Mirvwhere I got him to test the rtm silo09:02
seb128davmor2, weird, I can't confirm that, wfm09:02
davmor2seb128: might just of been a glitch09:02
seb128could be09:02
Mirvdbarth_: 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:04
MirvI understood so far as some apps depend on oxide (>=1.2), while it should be (>=1.2~)09:05
Mirvand that problem blocks unity8 from migrating among else09:05
dbarth_Mirv: no, i got i wrong initially; i thought the new oxide upload was stuck in proposed, but actually it's not there yet09:06
dbarth_Mirv: silo 2 rquires that 1.2 oxide, not the previous ~bzr releases09:06
dbarth_ogra_: so jdstrand uploaded that new build to the security proposed ppa on friday in prep for that landing09:07
ogra_so we just have to wait ?09:07
Mirvpopey: filemanager and terminal done09:07
dbarth_ogra_: the oxide-qt-1.2 in the security proposed ppa should be migrated to utopic proposed now, to unblock silo 209:08
ogra_well, i guess we need someone from the security team for that copy, right ?09:08
dbarth_ogra_: we can wait for jdstrand to double check, yes09:09
ogra_ok09:09
ogra_Saviq, we have quite some errors in unity8 tests on both images, is someone looking into that ?09:09
Saviqogra_, silo 1909:10
ogra_ok09:10
Saviqogra_, adb fallout, or rather password-required fallout09:10
ogra_Saviq, cant be ... rtm has the same errors and still the old adb09:10
Saviqwe didn't support password-protected unity8 tests09:10
Saviqogra_, but it's probably flashed with passwords now09:10
ogra_utopic has 12 failures, rtm 909:10
ogra_i dont think rtm is yet ...09:11
* ogra_ chacks09:11
ogra_*checks09:11
Saviqogra_, in any case, utopic silo 19, rtm silo 10, tested yesterday with 100% success rate09:11
Saviqit'd be in already if not for the oxide-qt problem09:11
ogra_export IMAGE_OPT=--device=krillin --developer-mode --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --wipe09:11
ogra_not with --password yet09:11
ogra_so it shouldnt behave any different than before yet09:13
davmor2asac: rtm silo 004 is granted09:18
asacogra_: Mirv: ^09:18
=== ogra_ changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS yes, i see it :)| QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Ping robru if any citrain jenkins jobs have unexpected results.
ogra_oops09:19
=== ogra_ changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Ping robru if any citrain jenkins jobs have unexpected results.
ogra_yes i see it ... silly focus09:19
ogra_publishing09:20
ogra_why is thostr_ suddenly owning all the HERE stuff ? :)09:21
thostr_ogra_: it's lool!!! ;)09:21
ogra_haha09:22
ogra_i thought so :)09:22
ogra_he just doesnt want to be held responsible if it fails09:22
ogra_ugh09:22
ogra_Mirv, any ide what that means ? (rtm 004) ^^^09:23
ogra_*idea09:23
ogra_does it check against utopic instead of rtm09:24
brendandmvo_, cjwatson - after installing silo 3 packages won't install from the store09: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:24
ogra_asac, that will need a re-upload or some such09:25
ogra_with proper versioning09:25
SaviqMirv, did you finish your meeting? could we add source-only oxide-qt to utopic silo 2, or how do we do this?09:26
kalikianaMirv: the ubuntu-rtm/landing-008 seems to work nicely09:28
bzoltanogra_: 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
kalikianaMirv: I disabled network to see that the cache actually works09:28
Saviqkalikiana, I think you mean utopic silo 8?09:29
Saviqnot rtm09:30
Mirvogra_: probably justlacking watch_only build09:31
* Mirv runs09:32
ogra_Mirv, with that versioning ?09:32
MirvSaviq: can you please give exact instructions what needs to be done? copy/upload what from where to where?09:32
asacogra_: hmm09:32
asacogra_: whats the problem with that version?09:33
MirvSaviq: I can oxide-qt to silo2 nd reconfigure09:33
bzoltanmvo_: is there any news about the click+qtc plugin landing?09:33
asacogra_: will it break the world if we pump it in like that?09:33
ogra_the last bit with tildes i think09:33
Mirvogra_: hmm, let's see09:33
ogra_right, let Mirv do his magic ...09:33
asacogra_: what does it mean?09:33
asaci ma not sure09:33
asaclool: ^^09:33
Mirvogra_: 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
SaviqMirv, https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+sourcepub/4393535/+listing-archive-extra to utopic silo 2 please09:33
asacogra_: can you reupload withright version?09:34
ogra_asac, but that would mean re-testing too, no ?09:34
asacogra_: so what can we do?09:34
ogra_lets see if Mirv can somehow massage it through09:34
asacthanks09:34
asaci think that would be best09:34
ogra_if not, yes, we might need to re-uplaod09:34
ogra_the questio then is, do we need re-signoff from QA or do we just trust  the rebuild09:35
mvo_bzoltan: ubuntu-rtm is verified by me now, so the next step is QA09:35
asacogra_: i think just doing a quick smoke run to see that it is not completely busted is fine if its source identical09:35
ogra_k09:35
ogra_yeah, i doubt it would introduce any issues09:36
Saviqdbarth_, 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 again09:36
Mirvmvo_: brendand has some issues to represent, or potential issues09:36
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 crucial09:37
brendandmvo_, yes - i have everything i'm sure. i can double check09:37
mvo_Mirv: aha, just saw it, thanks!09:37
mvo_brendand: could you please kill packagekitd too? or reboot?09:38
brendandmvo_, several times :)09:38
mvo_brendand: :(09:38
* Mirv starts copy-pasting higlights to emacs... I'll respond to each at some point :)09:38
MirvSaviq: srccopy fine?09:39
SaviqMirv, yeah09:39
bzoltanmvo_: is not that "regression" https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-click/lastBuild a problem?09:40
cjwatsonMirv: are you sure you don't want the -b option for that copy from ubuntu-rtm/landing-020?09:40
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 same09:41
Mirvcjwatson: no, sorry, -b yes please :)09:41
cjwatsonbzoltan: yes it is a problem, that's one reason this is blocked09:41
mvo_bzoltan: yes, sorry, this issue is fixed with a branch I prepared09:41
MirvSaviq: dbarth_ oxide copied to landing-00209:41
=== nik90_ is now known as nik90
brendandmvo_, i have the latest image for krillin09:42
SaviqMirv, thanks a bunch09:42
bzoltancjwatson: 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
Mirvasac: ogra_: HERE published09:42
cjwatsonMirv: 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-app09:42
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 this09:43
Mirvcjwatson: oh! thanks for that, good toknow that syntax09:43
Mirvkalikiana: so no regressions in location related apps, but the bug is fixed?09:43
SaviqMirv, I've added oxide-qt to the sources, can you please reconfigure silo 2?09:43
brendandmvo_, 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, yay09:44
asacMirv: yay :)09:44
* asac waits for a new image09:45
asacogra_: Mirv: how are our regressions going on rtm?09:45
asaci 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
Mirvdbarth_: hmm, I think se Tested to No and retest after oxide has built?09:45
Mirvasac: unity8 is stuck in proposed because of this oxide problem being resolved with dbarth_ and ogra_09:46
Mirvand Saviq09:46
Mirvasac: otherwise it would be resolved, and we could move to publishing it to rtm09:46
dbarth_Mirv: ok, i can redo some smoke testing yes09:46
asacMirv: ok. thanks09:46
asacMirv: do we know if there are any other bad regressions taht slipped into rtm?09:46
MirvSaviq: done and running watch_only build09:46
asacogra_: when was last rtm image kicked?09:46
asaci didnt get a notifcation for ages here09:47
kalikianaMirv: basically that means osm touch - all the others are web apps09:47
Mirvasac: 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
cjwatsonbrendand: packagekitd must be run as root09:47
cjwatsonmvo_: ^-09:47
Mirvkalikiana: right09:47
asacMirv: hidden behind which?09:48
=== tvoss is now known as tvoss|test
asacbehind the input prblem?09:48
asacbut yeah. lets see09:48
ogra_asac, by cron, tonight09:48
ogra_around 5am european time09:49
mvo_brendand: what cjwatson said, sorry that I did not mention the sudo - I'm keen to learn what it outputs :)09:49
brendandcjwatson, mvo_ - this is more helpful - http://paste.ubuntu.com/8298416/09:49
brendandoh it failed because it's not signed :)09:50
brendandi guess that's supposed to happen :P09:50
mvo_brendand: it needs a new debsig-verify09:50
Mirvasac: yes, let's see after the fixes are in09:50
mvo_brendand: thanks! let me update the landing, it needs 0.10ubuntu2 from utopic09:50
brendandmvo_, no problem09:50
Mirvkalikiana: which image you used to run the tests? latest from this morning?09:51
cjwatsonmvo_: aha, good catch, I'll copy that in now09:52
kalikianaMirv: ah damn, I didn't update since yesterday :-/09:53
kalikianaI thought I had09:53
mvo_cjwatson: oh, thanks! thats even better, I was about to trigger a build with jenkins09:53
cjwatsonyeah don't do that09:53
Mirvkalikiana: 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:53
kalikianaMirv: I only installed the ppa packages as we do usually in the uitk09:54
kalikianaI'm using ubuntu-touch/ubuntu-rtm/14.09-proposed09:54
cjwatsonmvo_: guess we'll want to land the click fix before re-QAing though09:55
cjwatsonmvo_: um you need to be more careful than that about ubuntu/landing-00309:55
Mirvkalikiana: ah, but that's a utopic landing, so it should be tested on utopic too09:56
mvo_cjwatson: oh, what did I do wrong?09:56
cjwatsonmvo_: we need to first merge in wherever the commit is that "released" click 0.4.32, then merge your branch, then try again09:56
cjwatsonmvo_: I was in the middle of trying to sort that ...09:56
kalikianaMirv: please tell me exactly how you would prefer me to test09:57
cjwatsonah, the branch is called lp:~ps-jenkins/click/ubuntu-utopic-proposed now09:57
mvo_cjwatson: ok, I will leave my hands from jenkins for now then09:57
mvo_cjwatson: aha, thanks, that is good to know09:57
mvo_cjwatson: so it will be 0.4.32 too? not 0.4.32.1?09:58
=== tvoss|test is now known as tvoss
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 it09:58
cjwatsonmvo_: no, it will be 0.4.32.109:59
cjwatsonmvo_: argh, I think your force rebuild has busted things09:59
cjwatsonoh, maybe not ... qtcreator-plugin-ubuntu is still at least in the PPA09:59
cjwatsonlet's see10:00
loologra_: hey, the version was just temporary10:01
mvo_cjwatson: I just used "ignore steps", did not force-rebuild (fortunately you stopped me before)10:01
loolI think I had copied the source version verbatim already10:01
ogra_lool, to late now10:01
loolso the older version didn't matter10:01
ogra_lool, seems Mirv managed to push it through10:01
ogra_looks a bit ugly though10:01
ogra_:)10:01
=== psivaa changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: psivaa | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Ping robru if any citrain jenkins jobs have unexpected results.
loolthe only thing there was to push was ubuntu-system-settings and indicator-location10:01
ogra_lool, why was it in the silo then ?10:02
loologra_: it had to  :-(   first, because there was a package in NEW and second because of the meta changes10:02
loologra_: because it was sitting in NEW10:02
loolat the time10:02
cjwatsonmvo_: 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 options10:02
ogra_ah10:02
cjwatsonmvo_: (which I've just done)10:02
loolthere was really nothing crazy here; just the minimum I had to workaround to get it pulled when testing the silos10:03
ogra_lool, next time just put that info in the comments column on the spreadsheet10:03
mvo_cjwatson: thanks, the PACKAGES_TO_REBUILD on top? I will remember that10:03
loologra_: fair enough; I've described this at length here, but should have documented in the spreadshhet10:03
brendandogra_, where's the krillin dashboard again? (i should really bookmark it)10:03
mvo_(hopefully )10:03
cjwatsonmvo_: yep10:03
ogra_lool, yeah, not everyone is around and not everyone reads all backlog :)10:03
cjwatsonmvo_: (only necessary because this is a landing of multiple packages)10:04
* mvo_ nods10:04
cjwatsonmvo_: I've copied the source to the ubuntu-rtm silo as well, so it can build in parallel10:06
=== tvoss is now known as tvoss|lunch
mvo_cjwatson: cool, once its build I will re-test on my n410:07
Mirvkalikiana: 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), test10:11
Mirv"usilo10" :)10:12
ogra_haha10:12
Mirvwe should have named the distro usilo instead of ubuntu-rtm10:13
ogra_lol10:13
davmor2asac: 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 works10:13
ogra_Mirv, then we could have a "wheat" release and a "corn" one :)10:13
asacdavmor2: well. this is not only software10:14
asacdavmor2: its also the provider that allows you to call a numer without sim10:14
asacdavmor2: not sure if there is a test number for providers10:15
asacthat is also whitelisted10:15
loolMirv, ogra_: I hav to upload meta in rtm to drop the hardcoded dep10:15
ogra_lool, there is one other change in the seeds, please pick that up alongside10:16
ogra_davmor2, i think the numbers come from your SIM and are hardcoded ...10:16
davmor2ogra_: :(10:17
davmor2ogra_: hang on it can't we are on about the test with no sim to emergency services10:18
ogra_(or from the network, not sure ... but we dont have any influence)10:18
loologra_, Mirv: 1.184 copied over10:19
ogra_davmor2, ask tony once he is up ... he could probably hack some intercepting test stuff in there that mangles the number or so10:19
ogra_oh, i see, didrocks uploaded it already10:19
ogra_great10:19
davmor2ogra_: yeah I will10:19
Mirvmvo_: cjwatson: are you handling also the click (re)publishing?10:25
cjwatsonyes10:25
cjwatsonthe train is wrong, that hasn't been retested10:25
Saviqdbarth_, fwiw it could make sense to make oxide-qt "Architecture: i386 amd64 armhf" to not waste other arches builders' time10:25
Mirvok, marking it so10:25
cjwatsondone for ubuntu-rtm too10:26
Saviqoh wow, it's a 5h build time for armhf ;(10:26
cjwatsonSaviq: don't optimise for other arches' builder time please10:27
Saviqcjwatson, ok10:27
cjwatsonSaviq: well, unless that's genuinely intrinsically never going to build elsewhere, which seems like a poor long-term assumption10:28
cjwatsonSaviq: it fails quickly enough on the other arches so isn't really a problem, and generally we'd rather have failures visible10:28
Saviqcjwatson, ok understood10:29
cjwatsonbrendand: 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:31
brendandcjwatson, sure i can check that it fixes the problem i saw and then continue with the rest of the testing10: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:32
cjwatsonsee "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 says10:33
mvo_cjwatson: :)10:33
Saviqdbarth_, yeah, makes sense10:33
cjwatsonthe only other arch with slow builders now is arm64, and we'll probably want oxide-qt for that in the not too distant future10:34
ogra_cant be slow, there is a 64 in the name :P10:35
ogra_psivaa, i just looked at krillin utopic ... seems there is also a device missing10:46
psivaaogra_: i missed that combi. let me take a look10:46
ogra_yeah, me too ... just struck me to take a look at that :)10:47
zbenjaminogra_: is there a problem with the current image? i get a reconnect loop after i enabled developer mode10:52
ogra_zbenjamin, hmm, weird, dbarth_ reports the same ... i cant reproduce it at all here10:53
psivaaogra_: the device was available, it failed in this step:10:53
psivaahablet-config writable-image10:53
psivaaerror: protocol fault (no status)10:53
psivaaerror: device not found10:53
ogra_psivaa, gah10:54
psivaaogra_: rerunning it whilst watching :)10:54
ogra_thanks10: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
psivaayea, looks like the same10:54
zbenjaminogra_: 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 work10:55
ogra_or 23310:55
zbenjamini did not upgrade since last week10:56
ogra_hmm10:56
zbenjamini wonder how i do the wipe now , with that reconnect problem10:56
ogra_from recovery10:56
* zbenjamin does a bootstrap10:56
ogra_or that, yeah10:57
brendandogra_, i suppose there's a known problem with pull-lp-source?11:03
ogra_brendand, on rtm, yes11:03
ogra_it doesnt know about the distro11:03
brendandogra_, ah ok - so how can we run click tests?11:03
ogra_with phablet-tools, as usual11:03
ogra_it was adjusted for this11:03
brendandogra_, ah probably i need to update phablet-tools again then11:04
brendandi'm getting a different error now - odd11:05
brendandIndexError from resource.py11:05
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:08
=== MacSlow is now known as MacSlow|lunch
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 ssh11:09
ogra_i cant reproduce it at all here :(11:09
zbenjaminogra_: i probably would if the keyboard on the login screen would come up11:10
ogra_zbenjamin, oh, old bug, reboot11:10
ogra_the wizard doesnt properly restart the OSK after it ran11:10
ogra_on a new boot all should be fine11:11
ogra_zbenjamin, so you are seeing that issue before you have a password set up ?11:11
ogra_(or a pin)11:11
zbenjaminogra_: no i did set up a pw in the wizard11:11
ogra_ok11:12
davmor2ogra_: on 24 I have a working keyboard on first boot11:13
ogra_zbenjamin, if you could somehow capture /var/log/upstart/android-tools-adbd.log that would also be helpful i think11:14
davmor2ogra_: there is however an issue triggering the sim unlock11:14
ogra_davmor2, funny, i didnt have any issue aftet OTA here today11:14
davmor2ogra_: this is a fresh install11:15
ogra_davmor2, yeah, there seems to be some difference here11:15
Mirvbzoltan: https://code.launchpad.net/~bzoltan/ubuntu-ui-toolkit/landing_05.09/+merge/233459 not approved11:16
kalikianaMirv: updated result: all works fine with unicorns and rainbows and even without ever turning on the network the cache works11:18
kalikianawhich is reaaaally nice :-D11:18
Mirvkalikiana: thanks for the testing!!11:21
zbenjaminogra_: phablet-shell does not work, can i somehow enable SSH from the terminal on the device?11:21
kalikianaogra_: unlock the phone first11:24
kalikianaer11:24
kalikianasorry11:24
kalikianazbenjamin: unlock the phone first11:24
zbenjaminkalikiana: developer mode is on, but my adbd does not work11:25
kalikianazbenjamin: and you did unlock?11:25
zbenjaminkalikiana: yes11:25
kalikianahere I get "Connection closed" if it's locked - otherwise phablet-shell is fine11:25
zbenjaminkalikiana: do you have the reconnect loop too?11:26
kalikianano adb is all fine11:26
kalikianaadb shell doesn't even seem to mind the screen lock11:27
kalikiana(maybe that is by design?)11:27
ogra_zbenjamin, android-gadget-service enable ssh ...11:35
ogra_(in terminal-app)11:35
zbenjaminogra_: i have a gazillion "stdin: is not a tty" in the log file11:36
ogra_zbenjamin, but you need your key on the device11:36
ogra_zbenjamin, thats fine11:36
ogra_(shouldnt cause issues)11:36
ogra_anything else in there ?11:37
zbenjamini just have the small terminal on the phone, didn't see anything else11:37
ogra_zbenjamin, well, if you have the terminal you can also use passwd to set a password ;)11:38
zbenjaminogra_: no, i just tail -f the file but i only get this line11:38
ogra_kalikiana, thats just not there yet :)11:38
ogra_zbenjamin, right, but that message is harmless11:39
zbenjaminogra_: i have a pw set but i have no key, and pw connection is disabled it seems11:39
ogra_i was hoping for some more usefull errors alongisde11:39
ogra_yeah, it is11:39
ogra_on security req.11:39
zbenjaminogra_: can i somehow get on the filesystem from bootloader or recovery?11:40
ogra_zbenjamin, pretty tricky on mako ... you need to create a mountpoint and loop mount the rootf img file11:41
ogra_*rootfs11:41
ogra_kalikiana, are you on 234 too ?11:42
* ogra_ wonders why some people see it and others dont11:43
zbenjaminogra_: what is the command for the mount?11:43
loolcjwatson: 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, i38611:43
lool ubuntu-location-provider-here | 0.1+14.10.20140829-0ubuntu1               | utopic/universe                    | source, amd64, arm64, armhf, i386, powerpc, ppc64el11:43
lool ubuntu-location-provider-here | 0.1+14.10.20140829-0ubuntu1               | ubuntu-rtm/14.09/universe          | source, amd64, armhf, i38611:43
kalikianaogra_: 2611:44
loolcjwatson: isn't 0.1+14.10.20140829~rtm-0ubuntu1~usilo10~1 a smaller version than 0.1+14.10.20140829-0ubuntu1?11:44
kalikianadon't ask me how the numbers map - it's the latest image from a few minutes ago11:44
loolcjwatson: should that not be refused from 14.09-proposed?11:44
ogra_kalikiana, ah, so you are on krillin and zbenjamin is on mako11:45
kalikianayes11:45
kalikianabut the images are the same, right?11:45
kalikianaexcept for the drivers11:46
ogra_yeah11:46
ogra_well, its far more than "drivers", but the rootfs is identical11:46
* ogra_ sighs about not having a spare device to do a proper bootstrap install 11:47
kalikianaogra_: I can flash a mako11:47
kalikianajust I don't always update both since it's kinda time consuming11:47
ogra_kalikiana, that would be massively helpful (if you can capture some data)11:48
loologra_: there are a bunch of issues migrating touch-meta around  :-(11:48
ogra_lool, hmm ?11:48
kalikianasure11:48
loologra_: in utopic, it's held by the click-scope tests being uninstallable11:48
loologra_: and in rtm, the langpacks are missing11:48
ogra_lool, you just did dput it directly to rtm, right ?11:48
davmor2ogra_: well you aren't using flo for anything important right ;)11:48
loologra_: to 14.09-proposed11:49
loologra_: I've copy-package-d it11:49
ogra_davmor2, no, but i dont care about flo either much ... the issue seems to be really mako specific11:49
loolsee http://people.canonical.com/~ubuntu-archive/proposed-migration/ubuntu-rtm/update_excuses.html11:49
ogra_lool, do a binary copy ... we dont have desktop-next in rtm11:50
MirvI need to afk for 1-2 hours, but I'll be back to check what's needed before robert is up11:50
loologra_: not sure why that'd help; the issue isn't with the new binaries; it's with proposed migration11:50
cjwatsonlool: copies are allowed to go backwards; direct uploads aren't11:51
ogra_lool, the issue is with desktop-next and the SDK11:51
ogra_neither is in rtm11:51
cjwatsonlool: this is occasionally actually useful :)11:51
loolcjwatson: can we kick it from -proposed?11:51
cjwatsonlool: sure11:51
loolcjwatson: that'd be helpful for provider-here11:51
loologra_: I understand, but I dont know how we're supposed to force it in11:51
ogra_by directly copying it to rtm instead of -proposed11:52
cjwatsonno!11:52
ogra_iirc we did that the last times11:52
cjwatsondo not ever do that!11:52
loolcjwatson: ^ perhaps you know; ubuntu-touch-meta can't migrate from 14.09-proposed due to broken deps11:52
lool(apparently)11:52
ogra_lool, again, these are not broken deps but completely unavailable stacks in rtm11:52
ogra_and ignorable ...11:53
loologra_: generally I feel we should not copy binaries to RTM; and I dont think we can copy to 14.09 anyway11:53
cjwatsonlool: IMO we should fork ubuntu-touch-meta for ubuntu-rtm and drop those binaries11:53
ogra_hmpf11:53
cjwatsonlool: ubuntu-location-provider-here/0.1+14.10.20140829~rtm-0ubuntu1~usilo10~1 removed; https://launchpad.net/ubuntu-rtm/+source/ubuntu-location-provider-here/+publishinghistory11:53
loolthanks11:54
ogra_cjwatson, cant we just set up a general pass-through for it in rtm proposed migration instead11:54
ogra_rather than having to keep to metas in sync11:54
ogra_*two11:54
cjwatsonogra_: while I could override it, that runs the risk of it allowing other things to break11:54
cjwatsonogra_: do you take responsibility for that?11:55
popeyMirv: 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
cjwatsonogra_: 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 somehow11:55
ogra_well, i should see them in the image changes11:56
cjwatson14.09 seems to have a fair few uninstallables already :-/11:56
ogra_so yeah, go ahead11:56
ogra_they would be removed/added then and should become visible in the manifest diff11:56
=== MacSlow|lunch is now known as MacSlow
cjwatsononly if they show up on images11:57
ogra_well, for rtm we dont really care if they dont ... people using the SDK get sdk-libs from utopic11:57
cjwatsonheh, I don't actually have a hints branch for RTM yet11:58
cjwatsonguess I'd better create one11:58
loolcjwatson: http://paste.ubuntu.com/8299266/ ?11:58
cjwatsonlool: that's what I'd do, but it appears that ogra_ disagrees11:59
loolcjwatson: didn't update meta map; seems to be fine to keep it; I assume we keep the seeds and germinate output from utopic11:59
cjwatsonshouldn't matter very deeply for metapackages11:59
ogra_lool, i really dont want to have to keep two distinct metas in sync all the time11:59
loologra_: the thing is that meta contains desktop-next and sdk which we haven't copied to 14.0912:00
loologra_: so we could split these in utopic12:00
ogra_since not everyone uploading to ubuntu might notify us etc12:00
loolbut that's painful too12:00
cjwatsonlool: well, I agreed above to force those uninstallables12:00
cjwatsonso let's just do that and move on12:00
ogra_yeah12:00
loolcjwatson: so ignore just ubuntu-sdk and ubuntu-touch-desktop-next?  fine with me12:00
ogra_neither of them are any relevant for rtm12:01
loolcjwatson: ah and that's when you realized you needed a dedicated branch because you dont want to ignore them on utopic-proposed migration; ok12:01
ogra_we should file a bug to solve this properly for next rtm ;)12:01
=== cprov changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: cprov | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Ping robru if any citrain jenkins jobs have unexpected results.
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:02
cjwatsonogra_: I don't have a problem with binary copies of ubuntu-touch-meta12:03
ogra_or would that confuse any archive tools ?12:03
cjwatsonthat was lool :)12:03
cjwatsonlool: right12:03
cjwatsonhttp://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu-rtm/revision/112:03
ogra_<ogra_> by directly copying it to rtm instead of -proposed12:03
ogra_<cjwatson> no!12:03
ogra_<ogra_> iirc we did that the last times12:03
ogra_<cjwatson> do not ever do that!12:03
ogra_i was referring to that reaction :)12:03
cjwatsonogra_: where did you get from that that I'm objecting to a binary copy? :)12:03
cjwatsonogra_: my objection is to directly copying to 14.09, bypassing -proposed12:04
ogra_ah12:04
=== seb128_ is now known as seb128
ogra_sorry, mis-read my own sentence :)12:04
cjwatsonheh12:04
loolcjwatson: 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
loolsounds error-prone to me12:04
ogra_well, for meta it doesnt make any difference12:05
loolI guess proposed migration woudl catch error if deps/shlibs are right12:05
cjwatsonlool: well, I had this conversation with sil but it was while I was at debconf so was pretty on and off the net12:05
ogra_utopic and rtm will be 100% identical12:05
cjwatsonlool: IMO proposed-migration should catch any significant problems and silo QA will catch the rest, so binaryful copies should generally be safe12:05
cjwatsonand would be less confusion over different binaries with same version12:05
=== orwell.freenode.net changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: psivaa | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Ping robru if any citrain jenkins jobs have unexpected results.
loolok; I'll try to default to that then12:05
cjwatsonlool: but apparently landing team folks disagreed, or else I misremember what I said to sil12:06
ogra_we have binaries with same versions all over the place for all initially synced stuff anyway12:06
ogra_at least if it didnt get updated in utopic12:07
jdstranddbarth_, ogra_: hey, I'm here. what do you need me to do?12:07
* ogra_ thinks thats a moot point12:07
loologra_: when we branched the archive, we knew they were built right12:07
cjwatsonogra_: all the initially-synced stuff was copied with binaries12:07
ogra_jdstrand, i think it was solved differently ...12:07
cjwatsonogra_: and copied from utopic, not from utopic-proposed, so should all have been fully built12:07
ogra_cjwatson, right, i just mean the version argument doesnt really matter12:08
cjwatsonafaik the only different-binary-same-version cases are things uploaded/copied after the branch12:08
loologra_: 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 lib12:08
loolit's a bug in our deps, but we might only discover it too late12:08
looltests should catch it, but we dont test everything12:08
cjwatsonlool: personally I don't think that's worth the effort of worrying about12:09
ogra_lool, oh, indeed, i agree we shouldnt binary copy libs that could have rdeps :)12:09
loolcjwatson: I heard you; just explaining the potential issue to ogra_12:09
ogra_but thats very unlikely to happen anyway12:09
loolwell cjwatson argues that almost all the time it should be ok12:09
loolanyway12:09
ogra_we didnt have many packages that bypassed the silos ... and definitely not a lib among them12:09
cjwatsonright, my general opinion is that spending hours of build time on low-probability events is a misallocation of resources, but whatever12:10
kalikianaogra_: 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_o12:11
kalikianacan I reset it?12:11
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_*checks12:13
mterryogra_, I missed the question?12:13
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_o12:14
ogra_<kalikiana> can I reset it?12:14
ogra_mterry, ^^12:14
davmor2mterry: 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:15
ogra_davmor2, does that happen on a flash without --developer-mode and --password ?12:16
mterrydavmor2, bug 1363405, has an MP12:16
ubot5bug 1363405 in ubuntu-system-settings (Ubuntu) "Setting a PIN can result in a passphrase instead" [High,Confirmed] https://launchpad.net/bugs/136340512:16
mterryogra_, yeah separately, I'm wondering if the wizard shouldn't show some warning on the password page if you already have a password set12:16
davmor2mterry: 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 bug12:16
ogra_(we need to somehow set the mode which doesnt happen yet)12:17
davmor2ogra_: I didn't have --password only --developer-mode12:17
ogra_mterry, i really wonder how we should do that btw ... we wont have any dbus from recovery12:17
* ogra_ will wait for sergiusens and discuss with him if he has any idea12:18
mterryogra_, ah interesting12:18
mterryogra_, you can edit the /var/lib/AccountsService/users/phablet file12:18
mterry(or some such path like that)12:18
ogra_ah, perfect12:18
mterryogra_, it's just a keyfile, should be easy to pipe some text into12:19
ogra_right12:19
davmor2ogra_: 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 so12:19
ogra_davmor2, yeah, smells like it12:19
mterryogra_, yeah, but the number of developers that put in a 4-digit PIN but actually want a passphrase has to be small12:20
mterryogra_, but might as well allow a switch I suppose12:20
mterryogra_, though design was talking about allowing a 4-8 digit PIN.  but anyway12:20
ogra_mterry, i personally expect to get a numberpad when doing something like --password=000012:21
ogra_and currently it would just give you a password prompt by default12:21
ogra_i think12:21
mterryogra_, right -- I think autodetection could work just fine12:22
ogra_mterry, oh, on the booted image later you mean ?12:22
ogra_that would indeed be more awesome than adding a hack to recovery12:23
mterryogra_, no I had meant in recovery but was just brainstorming12:23
ogra_ah, yeah12:24
ogra_well, lets see if sergiusens has an idea once he gets up12:24
mterryogra_, for us to do it on booted image later, we'd need to keep password in plaintext on disk12:24
ogra_oh, right ... nota good idea12:24
sergiusensogra_: mterry wrt to password and recovery, I only did exactly what I was told to12:25
sergiusensI don't mind plain text in recovery12:25
ogra_sergiusens, yes, and thats fine12:25
sergiusensit's a ci tool12:25
sergiusensif you use, you probably can care less about your password12:25
ogra_sergiusens, but the password mode for the UI doesnt get set the way we do it today12:25
ogra_we need an idea how to set it alongside12:25
sergiusensmterry: 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
sergiusensogra_: fine, but I'll add a note saying that the password is going to be saved in plain text12:26
mterrysergiusens, ogra_: I'd rather we keep the developer hacks in the developer tools12:26
sergiusensogra_: and just don't promote it!12:26
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 call12:27
sergiusensogra_: mterry if you look at https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/136599012:27
ubot5Ubuntu bug 1365990 in goget-ubuntu-touch (Ubuntu) "ubuntu-emulator create needs --developer-mode and --password options" [High,Confirmed]12:27
sergiusensI would just say we need "developer mode" inhibit switch and forget about this problem12:27
kalikianaogra_: mterry so… I can't even flash anymore since adb doesn't work… and I don't know whatever password may have been set12:28
sergiusensas in --developer-mode from u-d-f makes adb enabled always, pasword or no password12: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 emulator12:28
ogra_sergiusens, there is an upstart job that checks for the PW and disables it ... with a start on starting android-tools-adbd stanza12:29
mterrykalikiana, 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:29
ogra_sergiusens, it = adbd12:30
kalikianamterry: it complained the passwords didn't match, I had to cancel, next attempt it asks for the "existing passphrase"12:32
kalikianabtw I treid to add a PIN12:32
mterrykalikiana, aha!  You are hitting bug 1366814 it sounds like -- someone else reported that phrase "didn't match"12:33
ubot5bug 1366814 in ubuntu-system-settings (Ubuntu) "Configure lock pin or passphrase initially fails after upgrade to 229" [High,Incomplete] https://launchpad.net/bugs/136681412:33
mterrykalikiana, I haven't been able to reproduce12:33
kalikianamterry: mmmm just noticed the PIN I set and "did not work" actually works as a passphrase at the lock now12:37
* kalikiana confused12:37
mterrykalikiana, ah... then you must be experiencing the fixed (but not released) bug 136340512:37
cjwatsonlool,ogra_: ubuntu-touch-meta/1.184 should be migrating soonish12:37
ubot5bug 1363405 in ubuntu-system-settings (Ubuntu) "Setting a PIN can result in a passphrase instead" [High,Confirmed] https://launchpad.net/bugs/136340512:37
ogra_cjwatson, great ... i just need to clearify some device tarball stuff, please dont kick an image or anything yet12:38
loolcjwatson: thansk12:38
loolI see valid candidate, great12:39
cjwatsonogra_: wasn't planning to, enjoy12:39
cjwatsonmvo__,brendand: any luck with click testing?12:39
kalikianamterry: seems to work now, I disabled and re-entered the PIN and it works normally12:39
brendandcjwatson, 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 well12:40
mterrykalikiana, yup, I believe it based on the way that bug works12:40
kalikianamterry: cool, thanks a lot!12:42
ogra_kalikiana, what about adb ? do you see the reconnects ?12:42
cjwatsonbrendand: great, thanks12:42
ogra_now that your system is set up properly12:42
cjwatson[lunchtime, off out for an hour or so]12:42
kalikianaogra_: adb shell, phablet-shell work fine… no loop12:42
ogra_lol12:42
ogra_heisenbug12:42
kalikianaanything in particular I could try that would help?12:43
ogra_i wish i knew whats going on for the people that see it12:43
ogra_kalikiana, no, i think my mako is in the same state as yours12:43
ogra_so that one i can reproduce ...12:43
john-mcaleelyogra_, per your request, new device image pushed12:43
ogra_yay12:43
brendandmvo__, can you set the 'Tested' column for silo 3? I won't sign it off until it's in the 'Needs QA sign-off' state12:47
=== tvoss|lunch is now known as tvoss
dbarth_jdstrand: we copid the oxide binary to silo 212:49
dbarth_i think we're good at this stage, but i still need to finish smoke testing12:49
jdstrandok, cool12:50
mvo__brendand: done12:50
mvo__brendand: thanks a bunch for your testing12:51
brendandogra_, ah didn't #24 get systemd-shim?12:52
ogra_rtm or utopic ?12:53
ogra_brendand, yeah, rtm 24 did12:53
brendandhmmm12:54
brendandwhy does sim unlock still be borked....?12:54
ogra_brendand, why ? any issues with that ?12:54
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
zbenjaminogra_: weird i managed to create the .ssh/authorized_keys file but i still get access denied(publickey)12:55
ogra_zbenjamin, and you still have the loop too ?12:56
zbenjaminyes12:56
brendandogra_, oh12:56
ogra_brendand, at least i assume thats thereason12:56
ogra_we know that some breakage slipped through12:57
brendandogra_, could be. once that's sorted out we'll see12:57
ogra_john-mcaleely, looks like #25 is done, happy OTAing :)12:58
john-mcaleelyogra_, thank you!12:59
ogra_well, thank *you* :)13:00
ogra_cjwatson, wjat is the trick to get rmadison output for rtm btw ?13:13
* ogra_ just wanted to check for -meta and noticed he doesnt know how :P13:14
davmor2ogra_: well it's like checking for -dev only not ;)13:15
davmor2kenvandine: hey dude did you fix the keyboard appearing after the wizard on first boot?13:19
kenvandinedavmor2, not me personally, but yes that should be fixed13:20
kenvandinedavmor2, for rtm, that was probably part of the sync in silo 15 you tested yesterday13:20
kenvandinewhich included lots of fixes :)13:20
davmor2kenvandine: it is however the sim unlock number pad now isn't appearing after first boot :)13:20
Mirvpopey: calendar uploaded13:20
kenvandinedavmor2, where?  in the shell or in settings?13:21
kenvandinedavmor2, i guess it must be shell13:21
davmor2kenvandine: shell as it is the unlock request13:21
camakolanding-01913:21
kenvandinedavmor2, that doesn't use the OSK13:21
kenvandineit's a dialpad thing13:21
davmor2kenvandine: it's the dialpad thing13:22
brendandkenvandine, i just flashed 24 which has the new system-settings13:22
Mirvcjwatson: mvo__: how are the click landings?13:22
brendandkenvandine, good news - the keyboard does work now13:22
kenvandinedavmor2, so if that isn't showing, it is a different bug13:22
brendandkenvandine, bad news, sim unlock is broken13:22
kenvandinesince it's not the osk13:22
kenvandinebrendand, good... is there a "but" ?13:22
kenvandinebrendand, is there a changelog for image 24?13:22
brendandkenvandine, from what ogra_ told me the systemd-shim change landed, but there might have been some mistake with an ofono landing that broke it again13:23
davmor2brendand: reboot and try again I think this is what I've just been talking about13:23
kenvandinethere was some regressions that got published by mistake, in ofono13:23
jdstrandso, 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
kenvandinebrendand, what sim unlock?  talking about from in the shell?13:23
brendandkenvandine, same thing as i reported yesterday13:23
ogra_jdstrand, yeah, like magic13: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 landing13:24
brendandkenvandine, clicking on the button from indicator-network13:24
kenvandineok... that isn't related to system-settings13:24
jdstrandogra_: do I need to coordinate with QA or they are monitoring it?13:24
davmor2brendand: yes and nothing appears right?13:24
kenvandinebrendand, probably the same thing davmor2 just noted13:24
Mirvmvo__: ok, let's wait for ack from him still13:24
davmor2brendand: 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 unlock13:25
kenvandinedavmor2, can't be that...13:25
kenvandinedavmor2, that unlock isn't using the keyboard13:25
kenvandinemterry, ^^^ what could keep the dialpad from showing to unlock the pin after first boot?13:26
brendanddavmor2, well yesterday it was supposedly to do with systemd-shim13:26
brendanddavmor2, but that got updated with a 'fix' so i was told13:26
kenvandinebrendand, that shim problem caused many things to fail...13:26
kenvandinebut that is fixed13:26
* kenvandine updates to image 2513:27
mterrykenvandine, davmor2, is this when you press the "Unlock SIM" button nothing happens?13:27
mterrythat was supposed to be fixed by the shim yes13:27
davmor2mterry: yes13:27
brendandmterry, yes in image #2413:27
davmor2mterry: if I reboot though it works fine13:27
kenvandinemterry, i  tested that yesterday, but not right after the wizard13:27
brendandmterry, actually #25 too13:27
kenvandinei locked the pin after first boot... and rebooted13:27
kenvandinenot locked the pin then rebooted into the wizard to test13:27
mterrybrendand, and those have version 7-3 for systemd-shim?13:28
kenvandinei'll test that scenario now once 25 finishes installing13:28
popeyMirv: thanks13:28
brendandmterry, yes i do13:29
kenvandinedoesn't sound like systemd-shim since it works after a reboot13:29
davmor2mterry: ditto http://paste.ubuntu.com/8299904/13:29
kenvandinedoes regular pin unlock from the greeter work?13:29
kenvandinei think that's basically the same UI... not sure if it's the same code though :)13:29
mterrykenvandine, yeah... but that was a race so I could believe timing would matter.  But I guess not by that point in the boot process13:30
kenvandinebut i doubt any of that uses malit13:30
davmor2kenvandine: no it only displays the password line mterry has an mp for that already though13:30
kenvandinemterry, sounds like it's only failing after the wizard run13:30
mterrykenvandine, yeah that's not maliit13:30
kenvandinemterry, i've reproduced it... after the wizard run clicking unlocking sim in indicator-network just seems to do nothing13:34
kenvandinemterry, this is all i have in the indicator-network.log13:35
kenvandinehttp://pastebin.ubuntu.com/8299938/13:35
kenvandinea timeout13:36
mterrykenvandine, the indicator exits on a dbus timeout?13:36
kenvandinei don't think so13:37
kenvandineit was still running13:37
mterrykenvandine, 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 it13:37
mterrykenvandine, ah OK, I saw "terminate called"13:37
kenvandinenot sure what the wizard could have to do with it13:37
kenvandineyeah... not a good error message :)13:37
kenvandineand indeed unlock works after another reboot13:38
davmor2kenvandine: the wizzard takes the control of the keypad when you setup the pin initially, I don't know if it releases it.13:39
kenvandinedoesn't sound like that could be it... it looks like it can't talk to ofono ?13:39
mterrydavmor2, but this isn't a keyboard thing -- those PIN screens aren't using maliit13:39
davmor2mterry: 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:42
mterrydavmor2, I don't know what this issue is yet, but it's not likely to be that same cause13:43
mterrydavmor2, is there a bug yet?13:43
davmor2mterry: I haven't written one yet, brendand did you?13:44
brendanddavmor2, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1366745, but mterry duped it13:45
ubot5Ubuntu bug 1365095 in systemd-shim (Ubuntu) "duplicate for #1366745 Greeter not asking for pin code in image 11 (krillin)" [High,Fix released]13:45
mterrybrendand, ah yes after my test that didn't realize the wizard was crucial to reproducing13:46
mterrybrendand, can undup13:46
mterryOnly happens on krillin too...  Just like the shim issue.  Man, what's the deal with krillin13:47
brendandmterry, well if it's a timing issue13:48
brendandmterry, krillin is a bit slower13:48
brendandi think13:48
kenvandinemterry, any hints at where the bug is?  ofono? indicator-network?13:48
davmor2mterry: it hates you ;)13:48
mterrykenvandine, "instead nothing happens for a bit and then the indicator seems to reload" -- sounds like the indicator did crash13:48
kenvandinemterry, i just ran list-modems a few times after the wizard run and before trying to unlock13:49
kenvandinelooks fine...13:49
brendandmterry, i thought so too but there is nothing in /var/crash13:49
mterryhumph13:49
mterrykenvandine, I'd start with the indicator but could be anywhere13:50
kenvandinemterry, i think you're right13:50
kenvandinelooking at the process time on the network indicator13:50
kenvandineit has been runing 4 minutes shorter than my device has been up13:51
kenvandinebut not crash file13:51
kenvandinenote the longer delay is because i was running list-modems commands in between the wizard and trying to unlock13:51
davmor2mterry: 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
kenvandinetook a couple minutes13:51
davmor2kenvandine: ^13:52
kenvandinebingo.. you have a crash file for the indicator :)13:52
kenvandineis the wizard crash file current?13:52
kenvandineor maybe from yesterday when we knew it was crashing?13:52
davmor2kenvandine: fresh install13:52
kenvandineso it was wiped?13:53
davmor2kenvandine: yeap13:53
kenvandineok... what version of ubuntu-system-settings?13:53
kenvandineoh... the wizard crash fix isn't in the image yet13:53
kenvandineit's in the archive though13:54
davmor2kenvandine: indeed13:54
kenvandinei don't have the crash for that because i have the fixed version from the silo installed :)13:54
kenvandinei also don't have a crash file for indicator-network though... and still seeing the unlock problem13:54
kenvandinedavmor2, so link your indicator crash from errors.ubuntu.com to the bug report please13:55
davmor2kenvandine: if you want the indicator crash just keep hitting the sim unlock button13:55
davmor2kenvandine: eventually you'll see the indicator restart13:55
kenvandinedavmor2, i know mine restarted... but no crash file13:56
brendanddavmor2, can you play music from the scope on #25?13:57
kenvandinehttps://errors.ubuntu.com/oops/4aba9212-3824-11e4-9fdb-fa163e4ccdf213:58
kenvandinei bet that's it13:58
mterrykenvandine, should we assign to indicator people?13:58
=== fginther changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: fginther | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Ping robru if any citrain jenkins jobs have unexpected results.
kenvandinemterry, i think so... seems like a safe assumption13:59
kenvandinemterry, davmor2: ok... scratch all of that14:03
kenvandinei just did a dist-upgrade without any silos enabled14:03
kenvandineand i can no longer reproduce it14:04
kenvandinemaybe it was all triggered by the wizard crashing?14:04
kenvandinemy dist-upgrade included:14:04
mterrykenvandine, the report did note that it started happening with an upgraded USS14:04
kenvandine  indicator-location libsystemsettings1 qtdeclarative5-ubuntu-syncmonitor0.1 sync-monitor sync-monitor-uoa ubuntu-sdk-libs ubuntu-system-settings14:04
kenvandine  ubuntu-system-settings-wizard14:04
kenvandinewhich included the fix for the wizard crash14:04
mterrykenvandine, I don't know why the crash would trigger that behavior on the indicator side thoug14:05
cjwatsonogra_: just use rmadison, it works automatically14:05
kenvandinemaybe the session was in some weird state?14:05
* kenvandine tries again14:05
cjwatsonmvo__: should be fine, go ahead and publish14:06
ogra_cjwatson, bah, i swear it didnt when i tried last week14:07
kenvandinemterry, any chance after the wizard runs something restarts the indicator upstart job?14:08
Mirvmvo__: I'm trying to do that ^14:08
cjwatsonogra_: that's because I only fixed that on Thursday afternoon :)14:08
mterrykenvandine, we do do something like that, but I didn't think it was in the post-crash code, let me check14:08
kenvandinemterry, when it wasn't working, i noticed the upstart log file didn't exist even though the service process was running..14:08
kenvandineand it got created when i opened the indicator14:08
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
kenvandinemterry, but now i that is working, i see the upstart log file is there and being written too right after the shell starts14:09
mterrykenvandine, yeah we do that in the cleanup job: "initctl emit indicator-services-end" but that's pre-crash14:09
davmor2jhodapp: you about yet dude I'm blaming you for this completely ;)14:09
kenvandinemterry, so i'm confident the wizard crash fix fixed this14:09
ogra_oops14:09
kenvandinedavmor2, ^^14:09
mterrykenvandine, yay...?14:09
ogra_new artwork on nusakan14:09
jhodappdavmor2, I'm innocent!14:09
ogra_jhodapp, nobody belives you !14:10
kenvandinemterry, davmor2: i've gone through the wizard 3 times and works fine after :)14:10
mterrykenvandine, was there a bug for that wizard crash?  (for dup purposes)14:10
jhodapp:)14:10
jhodappdavmor2, what's up?14:10
ogra_rtm build triggered14:10
davmor2jhodapp: ha blagged now I know you're here ;)  in scope if you click on play in music nothing it happening14:10
jhodappdavmor2, url-dispatcher broken?14:11
ahayzen_davmor2, which image?14:11
kenvandinemterry, not sure if there was a bug, do you know davmor2?14:11
davmor2jhodapp: 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 fine14:11
davmor2ahayzen_: 24/2514:11
mterrykenvandine, no doesn't seem to be one (none listed in MP at least)14:12
davmor2jhodapp: hmm could be let's have a look and see if there is a crash14:12
kenvandineok... i'm happy all seems good :)14:12
kenvandinejust need a new rtm image :-D14:12
jhodappdavmor2, yeah that's not anything my code is in charge of handling14:12
davmor2jhodapp: okay in that case for a change it might not be your fault ;)14:13
jhodapptold yah! :)14:13
jhodapphaha14:13
kenvandinemterry, i'll work on getting your branches in a landing today14:14
imgbot=== trainguards: RTM IMAGE 26 building (started: 20140909 14:15) ===14:14
mvo__Mirv: hm, not known in space or time always sounds bad :/14:15
Mirvmvo__: 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
Mirvmvo__: seems appearing now14:15
mterrykenvandine, thank you!  (by just syncing utopic, right?)14:15
kenvandinemterry, you're recent MPs14:16
kenvandinenot in utopic yet14:16
mterrykenvandine, ah I see!  Yes, thanks14:16
kenvandinenp... thanks for the fixes14:16
mterrykenvandine, that password setting page has been a bear14:16
kenvandineyeah14:16
mterryall sorts of corner cases14:16
kenvandineseems in good shape now though :)14:16
davmor2ahayzen_: 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 fault14:16
kenvandinetakes a few iterations :)14:16
mterrykenvandine, you shut your jinxing mouth  :)14:16
kenvandinehaha14:16
* kenvandine zips it14:16
Mirvmvo__: 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 then14:17
ahayzen_davmor2, on #234 i just did 'Play in music app' on an album in the scope and it worked14:18
Mirvmvo__: to answer to myself, yes it seems correct, the same version is already in utopic-proposed14:19
ahayzen_davmor2, and playing a single track works as well so maybe it is just rtm that is broken?14:19
Mirvso now we just cross fingers that everything gets fixed by those uploads14:19
mvo__Mirv: yes, thats correct, only click needed the update14:19
Mirvexcept, hmm, the problems coming from the oxide problem...14:19
mvo__Mirv: yeah, my fingers are crossed too14:19
davmor2ahayzen_: could be14:19
ahayzen_davmor2, do any of the other url-handler calls work for other apps?14:20
kenvandinedavmor2, hey... btw  you were testing the location stuff yesterday14:20
davmor2kenvandine: I was14:20
kenvandineit wasn't working for me on krillin, but works GREAT on mako14:21
kenvandinedid it work for you on krillin?14:21
davmor2kenvandine: it worked fine on krillin for me14:21
davmor2kenvandine: 20-30 secs to get a fix14:21
kenvandineit seemed faster than that for me on mako14:21
kenvandinebut it never gets a fix on krillin...14:22
* kenvandine tries again with all the updates14:22
ogra_still doesnt work on mako for me :(14:22
ogra_nor on krillin14:22
davmor2ogra_: you need to leave the concrete bunker and see daylight ;)14:22
ogra_i only get "no location found" in here maps all the time14:22
ogra_davmor2, i thought it should work indoors too !14:22
kenvandinedavmor2, 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 app14:23
kenvandineogra_, i didn't at first...14:23
ogra_is that because i confirmed them in tsh past already ?14:23
kenvandinerebooting fixed that14:24
kenvandinewhich seemed odd14:24
davmor2ogra_: you haven't got silo 004 yet though right so you won't have the fix yet14:24
kenvandinestill no location fix..14:24
ogra_kenvandine, i havent gotten any since several images14:24
ogra_no matter how often i reboot14:24
ogra_davmor2, my mako has utopic14:24
kenvandinedavmor2, silo 4 landed14:24
ogra_that should have all bits and pieces, no ?14:24
kenvandineso was in my updates14:24
davmor2kenvandine: image 26 that is building now14:25
kenvandinemy mako was utopic-proposed, worked there14:25
kenvandinedavmor2, yeah... anyway i have all those packages that landed in silo 414:25
kenvandinei don't see how to debug this...14:25
davmor2kenvandine: :(14:25
ogra_tvoss, am i supposed to get any trust store popups at all ?14:26
kenvandinei even tried outside with gps enabled14:26
* ogra_ hasnt seen any in his -proposed install in two weeks or so 14:26
tvossogra_, n4?14:26
ogra_tvoss, yep14:26
tvossogra_, known bug, working on it14:26
ogra_N4 utopic-proposed14:26
ogra_ok14:26
ogra_tvoss, the conversation of the others sounded like it would be an ogra-issue :)14:27
ogra_since it seems to work for them14:27
davmor2ogra_: 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 requests14:27
tvossogra_, well, it is racy. Might well work for others14:27
kenvandinetvoss, what logs should i look at to get an idea why location isn't working on my krillin?14:27
kenvandinetvoss, i do see the app listed in location access in settings, and is enabled14:28
ogra_davmor2, only camer and mic ... both greyed out showing 014:28
kenvandineso sounds like it should be trusted14:28
tvosskenvandine, 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-service14:28
kenvandineok14:28
ogra_oh, wait14:28
davmor2ogra_: that's other apps not location14:28
kenvandineogra_, location access14:28
ogra_there is a new item in system-settings :P14:28
kenvandinenot other apps14:28
kenvandineyeah :)14:28
ogra_confusing14:28
davmor2ogra_: hahaha14:28
davmor2ogra_: in location is here maps listed?14:29
ogra_still ... apps just tell me there is no location service available14:29
ogra_davmor2, indeed14:29
ogra_osmtouch, gmaps and here14:29
davmor2ogra_: 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 one14:30
kenvandineE0908 17:07:32.856950  3970 skeleton.cpp:177] Error creating session: Client lacks permissions to access the service with the given criteria14:31
kenvandinetvoss, ^^ is that a problem?14:32
tvosskenvandine, yeah ... that's basically a denial14:32
tvosskenvandine, mind checking ps -ef | grep trust14:32
tvosskenvandine, n4?14:32
kenvandinekrillin14:33
kenvandineactually... those logs are from yesterday :)14:33
kenvandinemaybe i need to restart more than ubuntu-location-service14:33
rhuddiedoes 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:33
kenvandinetvoss, 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 window14:34
kenvandinephablet   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 session14:34
kenvandinetvoss, ^^14:34
tvosskenvandine, okay, that looks good14:35
* kenvandine rebooted with GLOG _v set14:35
tvosskenvandine, thank you14:35
kenvandineI0909 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 exist14:36
kenvandinetvoss, ^^14:36
kenvandinetvoss, so right now i have a sim in slot 214:36
kenvandineand nothing in slot 114:37
tvosskenvandine, hmmm, that exception is gracefully handled, though14:37
davmor2ogra_: told you you need to leave the concrete bunker and get into the sunlight ;)14:37
tvossogra_, mind wanna check that the window is not only painted on the wall!? :)14:37
ogra_davmor2, then i need to travle ... no sunlight here14:37
kenvandinetvoss, ok14:37
ogra_(thats why i had the balls to go outside without being molten :P )14:38
davmor2ogra_: if you can see there is sunlight :P14:38
kenvandinetvoss, wow... lots of logging now that the HERE app is trying to get a fix :)14:38
brendandogra_, i seem to not be the only one who has hit a problem running click tests, rhuddie got the same error14:39
tvosskenvandine, yup :) GLOG_v=100 is like "log the world"14:39
brendandogra_, could it be anything related to the developer-mode changes?14:39
tvosskenvandine, still got an item on my list to allow for enabling it at runtime14:39
ogra_brendand, perhaps ... though the smoke tests run fine14:39
kenvandinetvoss, ok... no fix and only logs are written to the INFO file14:40
ogra_brendand, you are on utopic, right ?14:40
kenvandinetvoss, should i pastebinit?14:40
tvosskenvandine, please, yes14:40
ogra_brendand, rtm didnt have the dev mode changes14:40
ogra_(yet)14:40
brendandogra_, could that upset phablet-tools?14:40
ogra_shoudlnt14:40
ogra_sergiusens, do you see any possible issue with using the new phablet tools with old adb mode ? i think everything is backwards compatible14:41
brendandogra_, sergiusens - http://pastebin.ubuntu.com/8300260/ is what we're seeing14:42
tedgAre there any traingaurds right now, or are we waiting for robru to finish breakfast?14:43
tedgAlso, qagaurds14:43
cjwatsonogra_,sergiusens: hm, speaking of phablet-tools, don't we need to make click-buddy's provision mode use pkcon --allow-untrusted now14:43
ogra_tedg, cyphermox_ should be able to help you14:43
cjwatson?14:43
cjwatsonmvo__: cc ^?14:43
cjwatson^-14:43
tedgogra_, Ah, cool.14:43
tedgcyphermox_, Can I get an rtm silo for line 55 please?14:44
ogra_cjwatson, did that land in any rtm image yet ?14:44
tedgcyphermox_, And can you please publish line 54?14:44
cjwatsonogra_: it's on its way, not actually in an image yet14:44
ogra_well, then we should indeed land the phablet-tools fix alongside14:44
cjwatsonsorry I only just noticed this14:45
bzoltanogra_:  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 scripts14:45
bzoltanogra_:  nopez14:46
mvo__ogra_: is that lp:phablet-tools ? let me check14:46
sergiusenscjwatson: yeah, I need to add that14:46
ogra_bzoltan, that needs to go (alongside with a change in adbd to ignore that call)14:46
MirvFYI we're still completely out of RTM silos, but QA has 5 silos under testing14:46
ogra_bzoltan, ?14:46
ogra_bzoltan, i have the paste hre14:46
sergiusensogra_: brendand if you are on rtm you need to specify --distro and --series14:46
bzoltanogra_: http://bazaar.launchpad.net/~ubuntu-sdk-team/qtcreator-plugin-ubuntu/trunk/revision/25114:46
ogra_http://pastebin.ubuntu.com/8300137/14:46
bzoltanogra_:  what version of the qtc plugin?14:46
ogra_bzoltan, no idea, ask dbarth_ or zbenjamin :)14:47
ogra_bzoltan, they both had the issue14:47
bzoltanogra_:  that is the old version14:47
mvo__cjwatson, ogra_: sorry I was not aware of this script lp:~mvo/phablet-tools/pkcon-allow-untrusted14:47
bzoltanogra_:  they both should upgrade :)14:47
ogra_bzoltan, ah, good to knwo14:47
ogra_bzoltan, anyway it exposed a bug in adbd, zbenjamin helped a lot to find it :)14:48
bzoltanogra_: cool :)14:48
=== Ursinha is now known as Ursinha-afk
brendandsergiusens, ah ok14:48
tedgMirv, I have two rtm silos that can be free'd with QA sign off :-)14:48
dbarth_bzoltan: wassup?14:49
brendandtedg, indicator-display?14:49
tedgbrendand, Yes, and indicator-datetime14:49
sergiusensbrendand: there isn't any reliable auto magic hints we can use on the image yet, or it would of been automatic14:49
brendandtedg, what's indicator-display meant to do?14:50
brendandtedg, it doesn't seem to add any new indicator14:50
Mirvtedg: yeah, the 016 of them is being tested by... right, brendan14:50
sergiusensbrendand: this is one of the pains of the ~rtm renaming, would of been mostly transparent otherwise14:50
bzoltandbarth_:  I have heard that you have problem with the adbd14:50
tedgbrendand, So an indicator on the panel when rotation lock is enabled.14:50
tedgbrendand, Show14:50
bzoltandbarth_:  what version of qtcreator-plugin-ubuntu do you have installed?14:50
tedgbrendand, 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, indeed14:50
dbarth_bzoltan: on #ubuntu-touch maybe14:51
brendandtedg, thanks14:53
* ogra_ wonders why the bot didnt pick up the running build 14:59
=== Ursinha-afk is now known as Ursinha
brendandpete-woods, jamesh - i'm testing the scopes silo15:09
brendandpete-woods, jamesh - it seems to break playback from the scope15:11
pete-woodsbrendand: sorry, which silo? I didn't realise I had any15:12
ogra_sergiusens, there is another phablet tools MP we need from pitti, i would like to get it into the same silo if possible15:15
brendandpete-woods, silo 14 in RTM15:16
brendandpete-woods, jamesh and Satoris are also mentioned as landers15:16
pete-woodsbrendand: it breaks the little preview widgets?15:18
brendandpete-woods, yeah the play button15:18
pete-woodsbrendand: is it broken for grooveshark / 7digital / local music / everything?15:20
brendandpete-woods, i haven't checked the remote stuff15:21
brendandpete-woods, i'm otp right now but as soon as i'm done we can talk through it15:21
pete-woodsokay15:21
pete-woodsbrendand: I have the same. local music previews seem to be broken15:25
brendandpete-woods, i hate to say it, but it seems like the test plan wasn't followed :/15:25
pete-woodsbrendand: seems like it. unfortunately I'm just the guy pushing the "tested" button15:25
Mirvcould 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.diff15:26
pete-woodsI guess I should be less trusting..15:27
sergiusensogra_: I'm in no hurry15:29
sergiusenslet it be queued15:29
sergiusensogra_: it's not in the spreadsheet though...15:29
ogra_sergiusens, can i add it to your line ?15:29
imgbot=== trainguards: RTM IMAGE 26 DONE (finished: 20140909 15:30) ===15:29
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/26.changes ===15:30
sergiusensogra_: depends, if it's qa like and requires too much testing, I don't want to land it15:30
sergiusensogra_: this one requires like zero testing15:30
ogra_https://code.launchpad.net/~pitti/phablet-tools/network/+merge/23176115:30
sergiusensogra_: as in, if affects phablet-click-test-setup or phablet-test-run I don't want it15:30
sergiusensogra_: as the testplan for those takes 6 to 8 hours15:30
ogra_i think it doesnt require more than storing/restoring the network config once to test15:30
ogra_its a change to phablet-config ... not for any test setup stuff15:31
sergiusensogra_: if it's properly reviewed/tested, I'll add ;-)15:32
ogra_sergiusens, i tested and pitt  did too15:32
=== seb128_ is now known as seb128
cyphermox_tedg: you should finish testing on your landings first...15:39
tedgcyphermox_, Which one? The rtm ones are tested.15:39
cyphermox_tedg: my bad, I wasn't up to date15:40
cyphermox_tedg: there are no rtm silos available right now, you'll get one as soon as possible15:41
* Mirv sees rsalveti battling with Train awesomeness15:42
rsalvetiMirv: lool: do you know what happened with silo 4 (rtm)?15:42
rsalvetihttps://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-00415:43
rsalvetitwo packages seems to be outdated comparing to the archive version of the same packages15:43
rsalvetiand publishing seems to be waiting for them to be available in the destination, but that will for sure fail15:43
tedgcyphermox_, Cool, thanks!15:44
Mirvrsalveti: 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:44
rsalvetithe version string in there is a bit confusing15:45
cjwatsonI had to remove ubuntu-location-provider-here from 14.09-proposed because the version copied in there was older than that already in 14.0915:46
cjwatsonsee scrollback from a few hours ago ...15:46
cjwatsonneeds a build with a newer version number :)15:46
Mirvrsalveti: 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 number15:46
Mirvthe HERE landing was a bit manual operation in both utopic and 14.0915:47
rsalvetiMirv: yeah15:47
Mirvso from what I see it's all ok except that the silo is wrong status15:47
rsalvetilool: can you confirm that?15:47
rsalvetiif so, we can probably clean that silo15:47
Mirvrsalveti: so, your 011 publishing...15:47
rsalvetiMirv: what's up?15:47
Mirvrsalveti: it failed. possibly because of robru's continous code cleanup, the sync publishing is quite bollocks at the moment, often.15:48
rsalvetiargh, just noticed =\15:48
Mirvrsalveti: my trick has been to change the sync:N to package name, reconfigure, build with watch_only and then publish15:48
rsalvetiright15:48
rsalvetilet me try that15:48
loolMirv: I think we can flush it now15:49
loolMirv: I had copied touch-meta and location-provider-here from ubuntu to ubuntu-rtm already15:49
loolMirv: touch-meta publishing was actually not needed BTW, but I should have noted that in the comments -- not just the changelog15:50
rsalvetiMirv: it seems I can't reconfigure the rtm silo for some weird reason15:50
Mirvlool: ok, thanks15:50
rsalvetigot the link, but went nowhere15:50
Mirvrsalveti: I do the "real" reconfigure via prepare-silo always15:50
Mirvwith the request ID15:50
rsalvetihm, ok15:50
ogra_lool, Mirv, it all landed http://people.canonical.com/~ogra/touch-image-stats/rtm/26.changes15:50
ogra_flush away :)15:50
rsalvetiMirv: same thing, jenkins ignored me15:51
loolwe should get a pull chain image to flush silos15:51
loollike in world of goo15:51
ogra_heh15:51
rsalvetiOops!15:52
Mirvrsalveti: jenkins just started totally ignoring my actions too...15:52
rsalvetiwhen trying to log-in15:52
rsalvetiseems jenkins is busted15:52
ogra_rsalveti, thats by design i thought15:52
rsalvetiseems to be more broken than the usual15:52
rsalvetivanguard? fginther I guess15:52
rsalvetiit seems ci-train.ubuntu.com is not behaving properly15:53
rsalvetican't log-in anymore15:53
rsalvetiIOError: [Errno 28] No space left on device15:54
ogra_lovely15:54
rsalvetiMirv: fginther: Ursinha: ^15:54
rsalvetithat seems to be why15:54
fgintheryuck15:54
Ursinhaoops15:54
rsalvetihttps://ci-train.ubuntu.com/job/prepare-silo/1924/console15:54
Ursinharsalveti: citrain is trainguards, but let me have a look15:54
ogra_i have some TB spare space on my desktop machine, you can NFS mount it ;)15:54
Ursinhaogra_: lol15:54
rsalvetiUrsinha: thought infra stuff like that was more for vanguard15:55
Ursinharobru: halp15:55
fgintherrsalveti, Ursinha, we've run into this before. We may have some control over this without going to IS15:55
Ursinhafginther: what is that?15:55
fgintherUrsinha, the last time this happened, the disk was full of defunct pbuilder chroots, we can remove those if that is the case15:56
fgintherbut the problems appear to run deeper then that :-(, I can't even login15:56
Ursinhafginther: what machine is that15:56
fgintherhttps://ci-train.ubuntu.com/15:56
rsalvetiUrsinha: http://community.sephora.com/t5/image/serverpage/image-id/116046i2AF73FFDE6096D06/image-size/original?v=mpbl-1&px=-115:57
UrsinhaLOL15:57
fgintherUrsinha, 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/console15:59
Ursinhafginther: I like the way you cheated jenkins15:59
fgintherUrsinha, anything over a day old under /var/cache/pbuilder/build can be removed15:59
Ursinhafginther: can we create a job to remove them or we need IS help?16:00
UrsinhaI can't seem to be able to login to that machine16:00
fgintherUrsinha, I think the jenkins user has sufficient rights to clean things up, let me check on that16:01
ogra_brendand, meeting ?16:01
ogra_popey, and you ? (or do you just skip the evening meetings)16:02
Ursinhafginther: am I supposed to be able to login to that machine with my regular user? or you're talking about logging into jenkins?16:03
fgintherUrsinha, I login to the jenkins UI16:04
fgintherwe don't have ssh access16:04
Ursinhafginther: ah, the UI, not the machine :)16:04
MirvUrsinha: rsalveti: jenkins started working again for me16:05
UrsinhaMirv: I just saw a new job here16:06
Ursinhafginther: did you remove the chroots already?16:06
fgintherUrsinha, not yet, there's a job created to do it, but it needed a little work16:06
fgintherpbuilder-clean16:06
=== Ursinha changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: Ursinha | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Ping robru if any citrain jenkins jobs have unexpected results.
fgintherUrsinha, running it now16:08
fgintherrsalveti, can you please retry that job?16:10
Mirvrsalveti: I did already for you, seems to work16:10
rsalvetifginther: Mirv: will retry16:11
Ursinhathat would be my next question, Mirv, fginther, can we just retry such jobs manually or should we use citrain tools for that?16:11
evcan someone explain to me why silos.previous exists?16:13
Mirvrsalveti: fginther: so, the retries worked.16:13
evwhy it needs this backup16:13
Mirvrobru: ^ see ev's question, you might have better idea than I do16:13
MirvUrsinha: the citrain tools are just wrappers around running the jobs16:13
evwe already do daily backups of /var/lib/jenkins, so I'm confused as to why we'd have an extra layer of backups16:14
Mirvso with the same parameters it should work16:14
Mirvsomething weird with rtm 008 still though, retrying again16:15
Mirvand the queuebot seems gone16:16
brendandtedg, so the rotation lock is not supposed to work at all right now - this landing purely provides the indicator?16:17
tedgbrendand, Correct16:17
tedgbrendand, The indicator is supposed to work, but not rotation lock itself. :-)16:17
brendandtedg, would be kind of good if the indicator closes after unsetting the lock16:17
brendandtedg, otherwise you get thrown to the location indicator - it's a bit jarring16:18
tedgbrendand, 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
tedgbrendand, I imagine it'll get refined.16:18
brendandtedg, ok seems fine then16:19
brendandtedg, -datetime next16:20
tedgbrendand, Woot! Thanks!16:20
brendandrobru, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/136674516:23
ubot5Ubuntu bug 1366745 in ubuntu-system-settings (Ubuntu) "Unlock SIM fails with latest ubuntu-system-settings installed" [High,New]16:23
kenvandinebrendand, that should be in image 2616:25
brendandkenvandine, did it land already?16:26
kenvandineyes16:26
kenvandineit was in the HERE silo16:27
kenvandine4 i think16:27
Mirvrsalveti: the train is a really train wreck atm, I'll salvage the rtm-008 still for publishing and then I'll let robru take over16:27
kenvandinebrendand, yes, it landed with rtm silo 4 this morning16:28
brendandkenvandine, ok. that's confusing - but we'll see i guess16:28
kenvandinewhere can i find changes for rtm images?16:28
Mirvnote to self: do no trust any "sync:N"16:29
brendandkenvandine, http://people.canonical.com/~ogra/touch-image-stats/rtm/16:30
kenvandinebrendand, thanks!16:30
brendandkenvandine, the build number corresponds to krillin16:30
kenvandineubuntu-system-settings-wizard from 0.3+14.10.20140904.2~rtm-0ubuntu1 to 0.3+14.10.20140908-0ubuntu116:30
brendandkenvandine, you asked earlier and i forgot to reply :/16:30
kenvandinebrendand, that had the fix16:30
brendandkenvandine, ok good16:30
rsalvetiMirv: thanks16:37
brendandtedg, datetime looks good16:41
brendandtedg, how do i test the fix for https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/135054416:46
ubot5Ubuntu bug 1350544 in Indicator Date and Time "Some translations are not loaded" [High,In progress]16:46
Mirvrsalveti: 008 published, although spreadsheet seems broken16: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 & rtm16:54
Mirvrobru: the jenkins problem probably broke spreadsheet updating somehow16:54
awe_please advise on how we can fix this16:54
Mirvrobru: I get "SyntaxError: Empty JSON strings" when trying to refreshSilosStatus16:55
rsalvetiMirv: great, thanks!16:58
=== Mirv changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: Ursinha | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: Spreadsheet updating broken, use Silo Dashboard! Ping robru if any citrain jenkins jobs have unexpected results.
robruMirv: ugh, what now?? OK i need to eat breakfast but I'll look at it soon17:01
Mirvrobru: yeah, no idea. jenkins now works, but the connection between spreadsheet and jenkins does not.17:02
Mirvrobru: have a fun day, I know I had...17:02
Mirvthe spreadsheet updating worked 1h ago, and broke at the same point we noticed jenkins had run out of space17:05
awe_robru, did you seem my question re: ofono/rtm?17:18
boikoMirv: is the jenkins out of space problem fixed already? (I have a silo that needs building)17:18
Mirvboiko: that's fixed, only jenkins <-> spreadsheet updating is broken17:20
Mirvso use http://people.canonical.com/~platform/citrain_dashboard/#?q= as much as possible17:20
boikoMirv: so I can trigger a build already? (silo 008)17:20
Mirvboiko: should be17:20
boikoMirv: thanks, let me try17:21
* Mirv redirects further questions towards Robert, I really need to start preparing for sleeping activities :)17:21
robruawe_: well, fix whatever regression you had found, then do a new landing for both utopic and rtm17:21
robruMirv: thanks for staying so late, I'm not feeling well today and only just starting to wake up17:21
ogra_robru, so did you find out why we have landings vanishing17:22
awe_robru, dude...the silo for utopic landed, the silo for rtm didn't land17:22
awe_so now we're out of sync17:22
robruogra_: I have a hunch but haven't been able to confirm it yet.17:22
Mirvrobru: no problem, take care17:22
awe_I have no idea how to fix this17:22
robruawe_: dude, I just told you, if you do a new landing to both, it'll be back in sync.17:22
robruawe_: 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:24
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 sync17:25
awe_robru, if a new landing is the only way to get things back in sync17:25
awe_then c'est la vie17:26
awe_if we'd had better communication between the lander (me), QA (davmor2) and CI, we wouldn't be in this position17:26
robruogra_: 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:26
awe_robru, we were mad that it was published because the testing pass hadn't been approved, nor had the MR17:27
ogra_robru, i didnt say we're lucky17:27
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 with17:28
awe_robru, I'm surprised as we discussed the regression and how it had been marked invalid during out standup17:28
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:29
sergiusenscopy-package and done17:30
infinitycjwatson: 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
infinitycjwatson: (Specifically thinking of glibc and its recent security updates, as prompted by the security team)17:30
awe_cjwatson, is it possible to create sbuild chroots based on rtm?17:31
robruawe_: 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:31
robruawe_: 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 all17:32
awe_https://code.launchpad.net/~phablet-team/ofono/lp1363413/+merge/23343417:32
awe_the merge proposal has the original testing details17:32
awe_the critical regression was: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/136623117:33
ubot5Ubuntu bug 1366231 in ofono (Ubuntu) "[krillin] When FlightMode disabled ConnectionManager interface isn't restored" [Critical,Invalid]17:33
infinityogra_: 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
robruawe_: 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 thme17:33
awe_and again, it was found to be Invalid earlier today17:33
ogra_infinity, i'll leave the binary decision to colin :)17:34
robruogra_: is it ok with you if we sync ofono from utopic to rtm?17:34
ogra_robru, ask QA, not me ... with me thats indeed ok (not a binary sync indeed)17:35
robruogra_: isn't that the whole problem? davmor2 toldme to sync it prematurely17:35
infinityIf 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:35
robruinfinity: get out of here with your debian terminology, we're too good for that crap! This. Is. Sparta!17:36
robruI mean, This. Is. CI Train!17:36
infinityrobru: "sync" is Ubuntu terminology. :P17:37
robruinfinity: anyway the people who birthed citrain invented all new terminology. sync doesn't mean what you think it means17:37
infinity*sigh*17:38
infinityWhy? :(17:38
infinityAnd what does it mean, then?17:38
robruinfinity: 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
robruand pray that it gets anywhere17:39
infinityKay.  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. :P17:40
robruinfinity: I don't work on the distro, I work on ci train ;-)17:40
infinity...17:40
robruinfinity: I know, it's a mess.17:40
infinity"I don't work on Linux, I work on the SCSI subsystem."17:41
davmor2ogra_, 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
robrudavmor2: ok17:41
robrudavmor2: ogra_ awe_: what packages are affected? just ofono?17:42
infinityAnyhow, I have to go play cat chauffeur.17:42
awe_robru, correct, just ofono17:42
davmor2robru: 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 it17:42
robruawe_: what's going on in silo rtm19? there's an ofono there17:44
awe_I have *no* idea17:44
awe_rsalveti, did you create this ^^17:45
awe_robru, looks like Mirv created it to fix the missed landing from yesterday17:46
robruawe_: 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 it17:47
awe_ok17:47
robruwell, I mean, maybe a double-check is in order then I'll publish it17:47
awe_yes, I will do so17:47
davmor2robru: yeah I'll hit it in a minute17:48
brendandtedg, an answer appreciated about verifying the bug - then i can sign silo 001 off hopefully17:56
rsalvetiI have nothing to do with rtm19 :-)17:59
Saviqdbarth_, what's the status of the oxide-qt landing?18:01
robrursalveti: your name is on it!18:03
rsalvetirobru: haha, I created the utopic one18:07
rsalvetithe rest was just automatic18:07
bfillerrobru: any idea while silo 12 for ubuntu not showing up correctly in the webview? line 56 on sheet18:09
robrubfiller: uh18:13
robrubfiller: yeah because http://people.canonical.com/~platform/citrain/ubuntu/landing-012 got truncated somehow18:16
robruoh it's truncated in the backend, too18:17
robrubfiller: I guess only a reconfigure can save it18:17
bfillerrobru: I will reconfigure it18:17
robrubfiller: no no18:17
robrubfiller: needs super admin reconfigure18:18
bfillerok18:18
robrubfiller: ok, silo 12 should be ready for a fresh build here.18:22
bfillerrobru: thank you18:23
robrubfiller: you're welcome!18:23
robrutvoss: around? your silo utopic 4 got itself into an inconsistent state somehow, I need to nuke it18:24
tvossrobru, how would that work?18:24
tvossrobru, how would that happen?18:25
robrutvoss: 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 work18:25
robrutvoss: we had ENOSPACE issues this morning, so I guess the files got truncated as a side effect18:26
tvossrobru, ack, let's do it then18:26
robrutvoss: ok silo 4 is ready for a fresh build if you wanna kick it off18:27
tvossrobru, still nothing in the silo for me18:27
robrutvoss: dashboard should update soon18:28
tvossrobru, ack18:28
robrutvoss: looks good to me18:28
balloonsplars, are the devices being run with a pin set now?18:31
robruqueuebot: haha, welcome back!18:31
balloonsI'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 set18:31
ogra_balloons, indeed, we have to, else adb wont work18:32
balloonsogra_, I knew that was going to happen, I just didn't think you landed it yet18:32
balloonsI wanted to be prepared, heh18:32
ogra_balloons, it is only in utopic18:32
ogra_not in rtm18:32
balloonsOHH, gotcha18:32
balloonsthat makes sense18:33
ogra_(but due tomorrow)18:33
balloonslol18:33
plarsballoons: do you mean the libcogl one we set as a test a while back?18:41
plarsballoons: or are you talking about something else?18:41
plarsballoons: oh, sorry I'm catching up18:41
plarsballoons: yes, we certainly set the password on devices now. Otherwise we have no adb18:42
balloonsplars, yea, I'm all covered ;-) I didn't think that landed yet.. and indeed it hasn't in rtm, but has in utopic18:42
plarsballoons: yes, but it should go into rtm soon enough18:42
balloonsyep, so anyways, we'll update tests accordingly to account for this18:43
balloonsI just wanted to do it BEFORE those changes landed not after18:43
davmor2ogra_: 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 jhodapp18:48
ubot5Ubuntu bug 1367400 in URL Dispatcher "url dispatcher doesn't seem to be triggering music to play in the music app." [Undecided,New]18:48
ogra_davmor2, blocker ?18:49
davmor2ogra_: certainly annoying and user facing and a regression so yes.18:49
jhodappI agree18:50
ogra_davmor2, can you tag it the right way ?18:50
ogra_so it lands on sils list18:50
davmor2ogra_: sure let me figure it out18:50
ogra_thx18:50
jhodappdavmor2, did you assign it to tedg?18:50
davmor2jhodapp: no feel free though18:50
jhodappdone18:51
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 fingers18:52
davmor2awe_: rebooting now18:52
awe_k18:52
davmor2ogra_: let me know if that shows up please18:54
ogra_davmor2, will do18:55
=== robru changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: Ursinha | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is sick, please ping cyphermox or rsalveti for landings.
davmor2ogra_: yay it did ;)18:56
ogra_awesome !18:56
tedgdavmor2, Are there any recoverable errors from that?18:56
davmor2tedg: I can have a look in a bit just reflashed to get the ofono stuff tested quickly18:57
tedgbrendand, You can't really unfortunately, it's an issue between LP and the package. It's before it gets on the device.18:57
tedgdavmor2, Okay, they should be still there if you didn't wipe.18:57
dbarth_Saviq: not been able to smoke test things this afternoon btween meetings and dev. mode; re-trying now18:58
Saviqdbarth_, I'll set it to not tested then18:58
brendandtedg, so what's the effect? the string should be translatable now?18:58
davmor2tedg: I always wipe, it gives me a clean image to test against18:58
Saviqdbarth_, FWIW it only built like an hour and a half ago... it takes 5½h to build on armhf...19:00
Saviqok finished 3h ago19:00
Saviqstill19:00
tedgbrendand, Not translatable, that the character when imported into launchpad should be readable in the webui.19:00
davmor2brendand, ogra_: confirming what kenvandine spotted that his fix which is in image 26 fixes the sim unlock issue on first boot19:03
kenvandinedavmor2, thx19:04
ogra_yay19:04
ogra_so no extra blocker for that one ... good :)19:04
davmor2ogra_: also I think the location blocker can be killed now19:04
dbarth_Saviq: uh, i thought this was a binary copy in that case19:04
dbarth_Saviq: building oxide indeed takes a looong time19: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 later19:05
Saviqdbarth_, 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 silos19:05
davmor2tedg: so I just repeated the test on this fresh install where will any issues show up?  .cache/url-dispatcher or elsewhere19:09
tedgdavmor2, /var/crash19:11
tedgdavmor2, They should show up as recoverable errors.19:11
davmor2tedg: nope I only see trust-store-skeleton and unity819:11
tedgdavmor2, Hmm, that's odd.19:15
looltrainguards, 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
tedgNot sure they're getting to URL dispatcher then.19:15
davmor2tedg: ouch that could be much worse then19:20
tedgdavmor2, Yeah, let me look into it some.19:20
tedgdavmor2, This is off an image, right?19:20
davmor2tedg: thanks19:20
tedgdavmor2, Or do I need a silo?19:20
davmor2tedg: no image 25/2619:21
tedgdavmor2, Same on utopic?19:21
davmor2tedg: I don't have a utopic device currently both on rtm19:21
tedgdavmor2, Okay, I'll switch mine over to be sure.19:22
cyphermox_robru: around?19:25
pmcgowanis anyone messing with launchpad team membership?19:29
pmcgowanI seem to have lost my powers19:29
awe_davmor2, can I publish?19:29
davmor2pmcgowan: are you logged in, I discovered that if there is  a db update you are logged out sometimes19:30
pmcgowanseb128, you know anything? I cant manage system settings anymore19:30
pmcgowandavmor2, yes logged in19:30
seb128pmcgowan, did you expire from any team?19:30
pmcgowanseb128, no email I saw19:31
pmcgowanlet me check junk19:31
davmor2pmcgowan: click on you personal tab and see if you have all team memberships19:31
pmcgowanlp keeps timing out19:32
dbarth_Saviq: ok, works as expected; i think we can re-try to land silo 2 now19:32
pmcgowanone of those days19:32
davmor2awe_: sim unlock is working consistently, sim selection works, second sim seems more stable (no guarantee on that ), sms works, calls in an out work19:32
awe_it's exactly what we landed in utopic19:33
awe_just needed a sanity check19:33
awe_and it was fully tested yesterday by me, the landing just vanished19:33
pmcgowanseb128, which team is bug maintainer or whatever for system settings?19:33
awe_so I think we're good to go19:33
davmor2awe_: yeap it is looking good here19:33
seb128pmcgowan, you triage the ubuntu package bugs right?19:33
pmcgowanseb128, right19:34
davmor2awe_: I see no crashes19:34
dbarth_seb128: did silo 15 land to get my location stuff next?19:34
awe_davmor2, ok... then I'll go ahead an publish19:34
pmcgowanseb128, but suddenly I cant set importance and assignment19:34
awe_your bug-control membership probably expired19:34
seb128pmcgowan, can you check if you are in https://launchpad.net/~ubuntu-bugcontrol ?19:34
awe_;)19:35
pmcgowanseb128, trying, p not answering my partiticpation19:35
seb128just open this page19:35
seb128it should write your status19:35
seb128it write that here " You are an indirect member of this team: "19:35
pmcgowanseb128, says I am not a member19:36
seb128there you go19:36
davmor2Right I'm outta here night all19:36
pmcgowanseb128, how'd that happen I wonder19:36
seb128pmcgowan, get mhall119 or bdmurray to add you back19:37
kenvandineseb128, can you test silo 14?19:37
seb128pmcgowan, default membership expire after 1 year I think19:37
seb128kenvandine, sure19:37
kenvandineseb128, specifically updates, with the system-image-dbus problem i'm seeing, i want someone else to verify :)19:37
seb128pmcgowan, you should have received emails about the expiration though ... do you ignore launchpad emails? ;-)19:38
pmcgowanseb128, uh oh19:38
pmcgowan;)19:38
pmcgowanI may have a filter thats a tad too aggressive19:38
mhall119pmcgowan: what do you need adding to?19:38
seb128hehe19:38
pmcgowanlol19:38
pmcgowanmhall119, ubuntu-bug-control19:38
seb128~ubuntu-bugcontrol he means19:38
robrucyphermox_: nah I'm off sick19:38
pmcgowanyeah that19:39
robrulool: feel free to keep it19:39
cyphermox_robru: who's looking after things? should I pay more attention to the landings?19:39
mhall119pmcgowan: what's your LP id?19:39
pmcgowanseb128, thanks, I will make a NEW filter for those19:39
robrucyphermox_: yeah if you don't mind, sorry i should have pinged you19:39
pmcgowanmhall119, pat-mcgowan19:39
seb128pmcgowan, 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 this19:40
pmcgowanseb128, yes, sigh19:40
mhall119pmcgowan: added you19:40
pmcgowanmhall119, ty19:40
mhall119np19:40
seb128pmcgowan, well, at least it explains the issue ;-)19:40
pmcgowanindeed19:40
robrucyphermox_: it should be in a reasonable state, ping me if anything really horrible comes up (like tracebacks in the logs)19:40
cyphermox_ack19:40
barryrobru: 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 rtm19:40
robrubarry: haha, best bet is just let other people tell you what to do.19:41
barryrobru: i am a good monkey, as you know19:41
cyphermox_barry: we can look at things19:41
barrycyphermox_: cool, thanks.  do ping me if you need a hand19:42
dbarth_hey guys, so i re-verified silo 2 now19:42
cyphermox_yeah19:42
dbarth_with the included oxide-qt packags to fix the dep problem19:42
=== fginther changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: fginther | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is sick, please ping cyphermox or rsalveti for landings.
cyphermox_ok19:42
dbarth_you should be able to clean th situation there, to let unity8 and Saviq land his work19:43
cyphermox_omg19:44
cyphermox_davmor2: still around?19:46
jdstrandelopio, ToyKeeper: fyi, rtm silo 002 is ready for QA signoff19:50
cyphermox_dbarth_: so what did you change, basically just copying oxide-qt to the silo, re-testing?19:51
dbarth_cyphermox_: yes19:52
dbarth_cyphermox_: to resolve the dependency in webbrowser-app19:52
cyphermox_no code changes?19:52
dbarth_nope19:53
dbarth_just smoke testing once oxide was part of the silo19:53
cyphermox_ok19:53
dbarth_i did a clean flash to r234, devmode19:53
dbarth_then apt-add-repo19:53
cyphermox_right19:55
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-run19:56
dbarth_cyphermox_: oxide-qt 1.2~bzr was in utopic this morning, not 1.2 final20:01
dbarth_cyphermox_: this is what i understood blockd the whole landing20:01
cyphermox_yes20:01
cyphermox_just a minute :)20:01
dbarth_nw20:01
tedgdavmor2, https://bugs.launchpad.net/url-dispatcher/+bug/1367400/comments/220:06
ubot5Ubuntu bug 1367400 in URL Dispatcher "url dispatcher doesn't seem to be triggering music to play in the music app." [Critical,New]20:06
tedgdavmor2, What did I do different there?20:06
elopiojdstrand: I hope ToyKeeper can take that one. I'll check back later if it's still pending.20:06
elopiotedg: 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
jdstrandelopio, 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:07
tedgelopio, Ah, okay. I'll just mark it "incomplete" then.20:08
dbarth_cyphermox_: it's using its webview and captures cookies20:08
cyphermox_so very crippling? ;)20:08
dbarth_cyphermox_: the cookie API changed between oxide 1.2~bzr, and 1.2 final20:08
dbarth_cyphermox_: yes, that's why they are in the same silo20:09
cyphermox_hm20:09
cyphermox_the thing is, oxide-qt never built on these arches, or at least 1.2~bzr doesn't seem to have20:09
dbarth_cyphermox_: but i checked that use case as well, ie create an account, enable the webapp, and autologin in twitter20:09
dbarth_yeah!20:09
cyphermox_so the depends was added?20:09
dbarth_hmm, not sure for ussoa20:09
dbarth_cyphermox_: yes, it was added as well:20:10
dbarth_+         liboxideqt-qmlplugin (>= 1.2.0),20:10
cyphermox_I see that20:10
cyphermox_yuck20:11
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 concerned20:13
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 here20:14
cyphermox_rsalveti: ^since you can confirm, this was requested by awe_20:14
cyphermox_oh20:14
cyphermox_dbarth_: could you point me to the thread?20:15
dbarth_cyphermox_: scroll back to this morning here, between Saviq and cjwatson20:16
rsalveticyphermox_: awe_ was testing that one, let's wait his feedback20:16
dbarth_but the qustion was raised on a couple of occasions already20:16
cyphermox_rsalveti: well, he asked me a few minutes ago before leaving to the gym20: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 do20:17
Saviqdbarth_, 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_yes20:19
balloonsplars, re: fm and terminal failures. Are we ok with letting those ride for the moment as they are only on utopic?20:19
plarsballoons: that's a question for sil2100, but iirc they are also failing on rtm20:20
plarsyeah, there's quite a few failures on rtm for them also. Either way, I'd suggest looking at those20:21
cyphermox_dbarth_: Saviq: as I understand it, cjwatson was fine with uninstallables for this kind of case. I hope I'm reading this right20:22
balloonsplars, can you provide a complete link? I see very small runs for those on rtm20:22
balloonsplars, mm.. touch-stable I guess has the full runs20:22
Saviqcyphermox_, you mean that on some arches you won't be able to install? I believe so, that was the case before already20:23
cyphermox_yes20:23
Saviqcyphermox_, 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 visible20:24
Saviqcyphermox_, as for uninstallables, it's probably best to make such a dependency optional if at all possible20:24
cyphermox_yeah20:24
cyphermox_Saviq: this case doesn't seem to be20:25
cyphermox_tedg: charles: I'm looking into the failure above20:25
charlescyphermox_, ty20: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 level20:26
cyphermox_once things transition from proposed it will get cleared up20:26
Saviqcyphermox_, one thing at least is needed, is to publish oxide-qt, is it in proposed already?20:26
cyphermox_it's already in the archive20:26
Saviqah20:27
Saviqcyphermox_, then yeah, adt just needs reruns then20:27
cyphermox_yes, and ussoa forced in20:28
Saviqright20:28
cyphermox_as per my last messages in #ubuntu-release20:28
tedgcyphermox_, Sorry, confused, which one?20:28
infinitySaviq: 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:29
cyphermox_rtm silo 120:30
Saviqinfinity, right, makes sense20:30
infinityie: 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:30
tedgcyphermox_, Ah, I see. Thanks!20:31
infinitycyphermox_ / Saviq: You can read the above as "no, I won't force in ussoa and raise the uninstallable count".20:31
cyphermox_I did read it that way20:32
cyphermox_I was just thinking "why didn't I think of it"20:32
Saviqinfinity, well, the count is already there20:32
balloonsplars, 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 one20:32
cyphermox_now, the problem is also how to fix this in citrain with the least amount of pain20:32
cyphermox_ie. on a half-done landing20:32
Saviqinfinity, that situation is already there in the archive, I'd say we need a bug against ussoa instead20:32
infinitySaviq: Err, no.20:33
infinitySaviq: The "situation" is in proposed, which is exactly what proposed is there for.  TO prevent the situation migrating to release.20:33
infinitySaviq: "It's broken in proposed, may as well call it a wash" would be ignoring the whole point of porposed. :P20:33
Saviqinfinity, ah, I thought that was just a bumped dep, not a completely new one20:33
infinitySaviq: It's a new dep.20:34
Saviqinfinity, no no, I thought it wasn't a new dep20:34
Saviqright20:34
cyphermox_itś a new dep20:34
* Saviq wonders if it was just a missing dep before, i.e. it didn't work anyway...20:34
infinityWhee, and it has rdeps too, of course.20:35
infinitySo glad we keep picking technologies that aren't actually ported.20:35
dbarth_cyphermox_: ok, so i guess all good for today20:36
dbarth_see you20:36
cyphermox_dbarth_: sorry, just trying to pick this up and piece the information back together20:36
Saviqinfinity, could you upload a fixed packaging version to proposed directly and we'll resync trunks as needed?20:36
infinitySaviq: 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 do20:37
Saviqinfinity, ah sorry, take care then20:37
infinityI wonder how painful it would be to port oxide to the 3 arches where it's FTBFS.20:37
Saviqinfinity, it was missing "gyp" which IIUC is some google built-time tool thingy20:38
infinitySaviq: No, no, gyp isn't missing, it's just missing platform definitions.20:38
Spadsalso a racial slur20:38
infinityThat bit is easy, what's not is that it might explode later. :P20:39
Saviqinfinity, right20:39
SaviqSpads, ;)20:39
infinityI could probably convince IBM to fix it on ppc/ppc64el, but not sure who I'd talk into fixing arm64.20:39
infinityAnd arm64 is something we should really deeply care about, since phones are going that route.20:40
infinityWe won't be armhf forever.20:40
Saviq+120:41
infinitycyphermox_: 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:42
cyphermox_ok20:43
cyphermox_thanks20:43
Saviqcyphermox_, ok, so to resolve this I believe we need just a bit of packaging changes (build-dep on liboxideq-qmlplugin) and the rdep infinity mentioned20:43
* cyphermox_ stabs iwldvm20:43
Saviqcyphermox_, so I'd vote for uploading a fixed version directly and we'll handle the resync tomorrow20:43
cyphermox_brb; I first need to fix my wifi if I want to be ableto upload anything at all20:43
Saviqsure20:44
infinityIt would probably be nice to make ubuntuone-credentials build-dep on ubuntu-system-settings-online-accounts to give the same hackish workaround.20:46
infinityAll the other rdeps are arch:all and thus not a big deal.20:46
infinityArgh.20:52
infinitycyphermox_: Hold the phone.20:52
cyphermox_aye20:52
infinitycyphermox_: The second level of rdeps has a ton of arch-specific stuff. :/20:52
cyphermox_where are you looking so that I can look at the same place?20:53
infinitycyphermox_: reverse-depends ubuntu-system-settings-online-accounts, and then drill down.20:53
infinitySo, removing this will break severl other bits (singon stuff, sync-monitor, etc)20:53
infinityOOI, why was the new dep needed? :P20:54
infinityStill 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 is20:56
infinity"Use new Oxide cookie API"20:57
infinityOh.20:57
infinityAre we pulling in a whole web rendering engine just for cookies? :)20:57
cyphermox_why not? :)20:58
cjwatsoninfinity: 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:05
cjwatsoninfinity: 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 why21:06
cjwatsonawe_: 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 similar21:07
infinitycjwatson: So, thoughts on ubuntu-system-settings-online-accounts?21:15
infinitycjwatson: 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
cjwatsoninfinity: Ugh.  Might be worth sucking it up for now; online-accounts is always tricky21:16
infinitycjwatson: I'm leaning to the latter for now, after evangelising the former.21:16
cjwatsonI suspect it will need something more involved21:16
cjwatsoninfinity: You'll want both force and force-hint IIRC21:17
infinitycjwatson: 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:17
cjwatsonAgreed21:19
infinitycjwatson: 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:20
infinitycjwatson: And I think when I initially asked "how do we do this", I was assuming a copy straight to RTM, bypassing CI.21:21
cjwatsonI 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
cjwatsonIt would be helpful for reduction in later panic if you could get QA signoff on the silo though.21:22
balloonsplars, I filed https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1367453, just fyi for the failures21:22
ubot5Ubuntu bug 1367453 in Ubuntu Terminal App "Security dialog causes tests to fail" [Critical,Confirmed]21:22
cjwatsonOtherwise we'll spend ages with people wanting to ascribe whatever's broken tomorrow to glibc ...21:22
plarsballoons: ack21:23
Saviqinfinity, so, FWIW, the dependency is not new (except it is new in debian/control), online accounts actually render web pages to log into services21:37
Saviqinfinity, so it basically should've been there already months ago, and now only bumped to use the new API calls21:38
cjwatsonqtcreator-plugin-ubuntu autopkgtest worked on retry; should clear some things out, including ubuntu/landing-00321:50
cjwatsonRetrying unity-scope-click autopkgtest too on the off-chance21:51
infinitycjwatson: Heh.  Well, I'll dance through the paperwork and hoops tomorrow for glibc, then.21:53
cjwatsonunity-scope-click passed too.22:10
=== fginther changed the topic of #ubuntu-ci-eng to: Train support: trainguards | Vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is sick, please ping cyphermox or rsalveti for landings.
* cjwatson squints at citrain22:15
cjwatsonIn what sense is ubuntu-rtm/landing-001 "All packages are in destination"?22:15
cjwatsonThe 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/+publishinghistory22:16
cjwatsonrobru,cyphermox_,rsalveti: I'm probably not the first to notice this, but don't believe citrain's lies for merge-and-cleanliness of sync silos22:16
cjwatsontedg: cc ^-22:16
cyphermox_yeah, it happened to me before22:17
cyphermox_it´s early enough that it´ s easier to fix22:17
infinitycyphermox_: For better or worse, ubuntu-system-settings-online-accounts is migrated now.22:22
cyphermox_infinity: thanks22:30
robrucjwatson: 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:36
cjwatsonrobru: ok, just wanted to make sure you knew about it, thanks, GWS22:42
cyphermox_cjwatson: so I guess it´s time to copy-package22:43
cjwatsonah yes, it's tested22: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-datetime22:44
cyphermox_ah!22:44
cjwatsonI have it queued up here if you want ...22:44
cyphermox_feel free22:44
cjwatsondone22:45
cyphermox_I'm trying to follow a discrete math class :)22:45
cjwatsonyou'll have to watch rmadison or something for when it's actually M&Cable22:45
cyphermox_sure22:45
cjwatsonor I guess https://launchpad.net/ubuntu-rtm/+source/indicator-datetime/+publishinghistory22:45
cjwatsondamn that hit Published quick :)22:45
cjwatson(in -proposed)22:45
cyphermox_woo22:45
cjwatsonok, published for real in 14.09 now; ubuntu-rtm runs quickly when it feels like it22:51
cjwatsoncleaning22:51
cyphermox_ah, yeah you want to tick the ignore project checkbox22:53
cjwatsonhad to ... that22:53
cyphermox_dah22:53
cyphermox_hmm, means I'll go merge the branch in manually22:54
cjwatsonthere's no 14.09 branch anyway22:54
cjwatsonwhich is reasonable since it's a sync22:54
cyphermox_oh, true22:54
cjwatsonwell, except a pseudo-sync with a different version number, but anyway22:54
cyphermox_ah, I meant to ask about this22:55
cyphermox_why are these syncs with ~rtm- ..., a version number lower than what's in utopic?22:56
cjwatsonI haven't the faintest idea22:57
cyphermox_ah, I thought it was somehow done on purpose, for some reason I didn't think of22:57
cjwatsonwell, I mean in general it's probably to reduce the incidence of different binaries with the same version number22:57
cjwatsonbut I don't think I agree with the practice of rebuilding22:58
cjwatsonlower than utopic will be because these are morally sort of backports - we want utopic to supersede eventually22:58
cyphermox_I was really expecting ubuntu -> ubuntu-rtm  transitioning to work much the same as debian -> ubuntu22:58
cjwatsonthe problem with that is that we're going to want to bulk-copy utopic (or v) over the top for the next time round22:59
cjwatsonwe might have a problem with mismatching binaries with the same version when we get there22:59
cyphermox_ok22:59
cjwatsonanyway, tired, ICBW, night23:00
cyphermox_good night, and thanks again!23:00
cyphermox_lies23:03
Saviqcyphermox_, thanks!23:09
cyphermox_Saviq: np23:10
ToyKeeperIs 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:17
cyphermox_what's the error message?23:20
cyphermox_I guess it could well not work23:20
ToyKeepercyphermox_: 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 Found23:21
cyphermox_yeah, that's broken alright23:22
cjwatson--distribution=ubuntu-rtm23:22
cjwatsonoh and probably --series=14.0923:22
cyphermox_cjwatson: are those parameters that can be passed to phablet-click-test-setup?23:23
ToyKeeperNope.23:23
cyphermox_ToyKeeper: update your phablet-tools maybe?23:26
cyphermox_seems to be in lp:phablet-tools23:26
ToyKeepercyphermox_: *facepalm* ...  thanks.  :)23:28
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)23:32

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!