[00:42] robru: hmn, no idea [00:43] bfiller, rogue robots proposing branches? :-D [00:44] robru: those MR's have already been merged from the ubuntu release [00:45] bfiller: great [00:45] bfiller: did you test it in rtm? [00:46] robru: yes I tested the click package in both ubuntu and rtm [00:46] works fine [01:08] it's pretty amazing... the here location service stuff is working really well on my mako! [01:09] totally not working on my krillin... [01:09] but... it gets a location amazingly fast on mako :-D [01:09] and it's nice to see the apps listed on location access in system-settings :) [01:15] bzoltan: Not sure if you're around, but the uitk silo appears to introduce at least six new test failures in ubuntu-system-settings. :( [01:15] ToyKeeper, that makes me sad :( [01:15] ToyKeeper, bug i'm am really thankful you are catching them :) [01:15] s/bug/but [01:16] ... should have found it earlier, but it sounded like brendand had another issue blocking it so I was waiting on him. [01:23] hmmm [01:24] jdstrand: citrain woes? I broke everything, working on it though [01:24] robru: I needed to copy in a new version of apparmor to utopic silo 014 [01:24] ok [01:25] yeah I tried a reconfigure, had an error so I did a prepare. the prepare had an import error [01:25] so, I leave you to it [01:25] I'll* [01:25] (this was utopic silo 014 if you wanted something to look at) [01:25] jdstrand: nope I got it, thanks [01:26] cool. I'll keep an eye out here for when things are fixed again [01:26] thanks [01:26] jdstrand: ok it should be working right now, please try again ;-) [01:27] oh, that was fast :) [01:27] jdstrand: yeah it was a silly mistake, fixed it easily ;-) [01:27] ok, the reconfigure worked [01:34] robru: hesitant to ask you in the midst of ci-woes, but any ideas or help on stuck unity8 migration? silo19 [01:35] robru: all seems fine, thanks! [01:37] jdstrand: you're welcome! [01:37] kgunn: not sure, retrying the adt runs for you [01:37] (apparently I can do that...) [01:38] thanks... [01:38] kgunn: but otherwise you should ping an #ubuntu-release person for -proposed migration issues, like infinity or cjwatson [01:39] i see in ubuntu-release some discussion about it...and it being complex and may need a [01:39] a pitti to look at it [02:04] === trainguards: IMAGE 234 building (started: 20140909 02:05) === [02:06] https://ci-train.ubuntu.com/job/deploy-citrain/250/console God. Fucking. Damnit. [02:06] I want that hour of my life back. [02:07] http://bazaar.launchpad.net/+branch/cupstream2distro/revision/721#citrain/manual/jenkins-templates/prepare-silo-manual.xml.tmpl [03:04] === trainguards: RTM IMAGE 24 building (started: 20140909 03:05) === === cprov__ is now known as cprov [03:41] robru: are you still around? [03:41] I do not get what the problem is here: https://ci-train.ubuntu.com/job/ubuntu-landing-010-1-build/52/console === psivaa_ is now known as psivaa [03:49] === trainguards: IMAGE 234 DONE (finished: 20140909 03:50) === [03:50] === changelog: http://people.canonical.com/~ogra/touch-image-stats/234.changes === [04:11] bzoltan: the gles upload probably gets rejected for some reason or another. as you can see, ppa doesn't have it despite multiple builds [04:12] Mirv: I see that. What i do not see is why it happens [04:12] Mirv: "Some source packages were never published in the ppa" No shit, Sherlock ... that is a new package I just added to the sheet. [04:13] Mirv: and the QtC pugin package gets rejected too in the same PPA. [04:16] I don't see anything wrong with the mp :( [04:19] Mirv: Me neither. Maybe a reconf helps [04:19] === trainguards: RTM IMAGE 24 DONE (finished: 20140909 04:20) === [04:20] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/24.changes === [04:21] Mirv: the good thing is that I managed to pull off the test plan for the UITK. It is all good. All the tests are at east as green as the RTM is. Only the camera app is freezing, but that is not UITK related. [04:24] Mirv: and the other proble is that the cick+qtc-plugin-ubuntu is blocked http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html [04:24] Mirv: and so that blocks the next landing :( [04:25] Mirv: What the hack? "dpkg-source: error: cannot fstat file ./ubuntu-ui-toolkit-gles_1.1.1239+14.10.20140908.orig.tar.gz: No such file or directory" [04:28] bzoltan: Not sure if you saw it earlier, but the uitk silo appears to introduce at least half a dozen new test failures into ubuntu-system-settings. [04:29] ToyKeeper: I have logs from the 128 AP tests of the ubuntu_system_settings. Al OK [04:29] All [04:29] bzoltan: I got 6-7 failures out of 128. The base image was 122/122 pass. [04:30] ToyKeeper: I was running during my night against the image #233 [04:31] ToyKeeper: here are the logs -> http://paste.ubuntu.com/8296368/ [04:31] The base image I used was krillin rtm 23. I don't really care much what the results were on a non-krillin non-rtm image. [04:32] At least, for a rtm landing anyway. [04:32] ToyKeeper: I have run 17 times the ubuntu_system_settings tests during the last 7 days. Never seen a single faiure. [04:33] ToyKeeper: I can take a look. [04:34] ToyKeeper: do you have the logs? [04:35] bzoltan: Yes, I just pastebinned it... looks like it exceeded the scrollback though, so I'd need to re-run to get anything before the beginning of the log. https://pastebin.canonical.com/116558/ [04:35] ToyKeeper: The lanidg process of the UITK is that first I test the silo against the Ubuntu image. If that is OK then we land on Ubuntu. After that I test the RTM sio against the latest RTM image. So double testing... now I am working with the Ubuntu image. [04:36] bzoltan: right, that migration needs resolving first. I tried reconfiguring the new silo but I think it's probably something else. very weird errors. [04:37] bzoltan: FWIW, on two successive test runs, I got 6 failures the first time, 7 failures the second. What changed between was I moved a bunch of stuff out of ~/ on my notebook, since the first logs seemed to include a 'cd ; echo *' and I wanted to rule out weird file names as a cause of errors. [04:38] ToyKeeper: What image do you test agains? [04:39] bzoltan: Latest krillin rtm image, whatever it is. Today it was #23. [04:39] ToyKeeper: The first few faiures are "autopilot.exceptions.StateNotFoundError: Object not found with name '*' and properties {'objectName': 'dialpadSounds'}." That is a classic flakiness [04:40] I saw some other failures, but those were all present in the base image too. Only ubuntu-system-settings changed after adding the silo, though I didn't make it all the way through all the components so there could be others. [04:40] ToyKeeper: who is developing the AP tests for that app? [04:41] bzoltan: Flakiness? Not sure who wrote those bits of code. [04:42] ToyKeeper: Few question ... have you checked the version of the UITK before and after adding the silo? Was the ~phablet/autopilot/ubuntuuitoolkit diectory removed? [04:42] bzoltan: In any case, it seemed curious that 6 tests were added and 6-7 tests failed. [04:42] At the moment I don't have the silo installed. [04:43] ToyKeeper: I do not know what causes the problem there :( But the logs do not point to the UITK [04:44] bzoltan: In any case, I add the PPA, disable all other package sources, apt-get dist-upgrade, re-add the basic package sources, then run the autopilot tests. In this case it failed to run at all the first time due to a gpg error, but after overriding that I was able to get test results. [04:44] (overriding == manually apt-get install the two packages apt complained about, then re-run phablet-test-run) [04:45] ToyKeeper: I do not like to run apt-get dist-upgrade because it brings other packages too [04:45] bzoltan: That's why I disable all other package sources first... so that it can *only* get packages from the silo. [04:45] ToyKeeper: I see [04:46] It seems like there are probably process differences to explain the different test results... but I'm not sure what the process differences are. [04:46] ToyKeeper: I am struggling a lot with the AP tests.. and when I say a lot I do mean it :) let me show how I do it. [04:47] For me, I flash fresh and wipe, then manually get online via nmcli, install the silo as described earlier, reboot, then go through the welcome wizard, set a time zone, disable automatic updates, reboot to work around the current OSK bug, then remount / rw and start on the AP tests. [04:48] ToyKeeper: http://paste.ubuntu.com/8296476/ `./uitk_test_plan.sh -c -p ppa:ci-train-ppa-service/landing-010 -f system_settings` [04:48] Er, re-adding regular package sources before starting on the AP tests since otherwise they can't even install. And sometimes I have to manually install a couple packages from the silo first to work around missing gpg keys. [04:49] bzoltan: I do not have uitk_test_plan.sh... I have only https://wiki.ubuntu.com/Process/Merges/TestPlan/ui-toolkit [04:49] ToyKeeper: That script is in the UITK source tree tests/ and this version is in the actual release candidate. [04:49] ToyKeeper: that script executes the UITK tesp plan. [04:50] ToyKeeper: It is a lot help ... [04:50] If the test plan is a shell script, the documentation needs to point to that instead of what it says now. [04:50] ToyKeeper: I need to update the test plan [04:51] QA is executing the test plan in the wiki, because that's what's linked to from the landing spreadsheet. [04:51] If the test plan is wrong, it's kind of an automatic fail. [04:51] ToyKeeper: That script is a new development. I made it to make my life less miserable. [04:52] ToyKeeper: I do not think QA would ever run my script :) [04:52] ToyKeeper: that script is for local validation [04:53] I was very tempted to make a script like that earlier today, since uitk tests are almost entirely automated anyway. [04:54] I'm happy to see there is one, but we need to get you and QA testing the same things or we'll end up with failed landings like today. [04:55] I'm of the opinion that anything which can be automated should be. [05:33] hmmh [05:34] robru: I've a weird problem where even after manual prepare-silo reconfig (https://ci-train.ubuntu.com/job/prepare-silo/1897/console) watch_only build gives nothing (https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-020-1-build/5/console). not sure if it could be related to your latest batch of changes. [06:05] mvo_: the cick and qtc plugin landing is stuck. Do you know how to make it move? [06:05] mvo_: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html -> autopkgtest for click 0.4.29.1build1: Regression [06:06] bzoltan: that looks like a failure to upload, id guess you should rebuild but it seems that hadn't worked for you. Not sure what else to try. Can Mirv do a manual upload for you? [06:06] I mean the one you pinged me about [06:07] robru: I have tried all combination of rebuilds... it seems that the silo is busted [06:07] bzoltan: I'm afk but Mirv should be able to free and reassign [06:08] robru: I think manual upload might be the only option, or indeed freeing and reassigning [06:08] robru: that gallery-app rtm-020 silo is really weird [06:09] Mirv: yeah i have no idea what happened there. If it's a problem just free it and resynchronize utopic [06:10] Brb [06:10] I'll do that [06:10] or hmm, I could take someone to simply publish it manually [06:16] bzoltan: yeah, we are waiting for the ubuntu-rtm QA verification [06:16] bzoltan: the click/packagekit changes need to land there as well [06:17] bzoltan: I should have waited with the publishing to -proposed even until it lands in ubuntu-rtm, but I made a mistake here [06:19] bzoltan: ok I was able to upload the -gles package there manually now. the qtcreator plugin will succeed once the previous landing has properly finished. [06:20] mvo_: Is not that regression mark a problem? [06:20] bzoltan: that too, there is also a explicit bugreport to prevent it from leaving utopic-proposed [06:20] bzoltan: I look at the test failure right now [06:21] mvo_: thanks. I totally forget about that landing. Because it actually blocks the next landing. [06:22] mvo_: is the click transition also breaking the unity8 migration to release pocket? http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html - regressions in qtcreator-plugin-ubuntu/unity-scope-click [06:24] mvo_: hmm, is the rtm 003 really going forward since it's not marked as having been tested by upstream? ie is it on QA team's radar? [06:24] it was not even marked as "Ready", but I changed that to Yes now that it had a silo and had built already [06:28] Mirv: oh? well I tested it yesterday and it should be good on utopic [06:28] Mirv: its waiting for QA for the ubuntu-rtm landing [06:28] Mirv: or am I missing something? [06:37] mvo_: the line 39 says "Packages built", it's not "QA needs to sign off" [06:37] mvo_: there's no "Testing pass?" set to "Yes" together with the rtm image number it was tested by upstream [06:38] so upstream tests first, only after that QA will start testing [06:38] Mirv: sorry for that, let me fix it [06:40] Mirv: I did test this in the line before for the normal ubuntu utopic archive, pardon my ignorance about the workflow, I will retest this with the ubuntu-rtm channel image now (that is correct?) [06:41] mvo_: ok! yes, the rtm landing should be tested separately on the rtm image, and even noticing that apt-add-repository doesn't work correctly (unless it got fixed) so you need to edit sources.list manually to add that rtm-003 silo [06:42] Mirv: thanks, download is now running [06:59] cjwatson: if you don't mind, we've a very problematic silo and would need ./copy-package -d ubuntu-rtm -s 14.09 --ppa=ci-train-ppa-service --ppa-name=landing-020 --to-primary --to-distribution=ubuntu-rtm --to-suite=14.09-proposed gallery-app [07:00] cjwatson: it's cosmetics mostly, since it's not installed from archives anyhow and is already in the store, but just so I can mark that problematic rtm silo as "done" at some point. [07:00] the silo just doesn't want to recognize there's something in it... [07:19] cihelp: ps-trusty-desktop-amd64-1 is down, can you turn it back up, please? [07:27] thanks mvo! [07:28] brendand: we'd have rtm-003 (signature checking etc) as a priority one landing to QA, since it's blocking next landings in both utopic and rtm (interestingly) [07:28] since the utopic + rtm landings need to go hand in hand, and now the utopic landing is stuck in proposed and probably also the reason why unity8 is in utopic proposed still [07:31] Mirv, i guess that's my next port of call then [07:32] didrocks: there is a migration going on from the lab to the cloud and given the number of ps-* slaves offline I suspect they are involved. You want to check with ev/fginther (I've been in vacations then ill so I don't know the details) [07:33] vila: he told me that for now we keep that machine until the migration is complete [07:33] vila: and he rebooted it yesterday as well, due to the same issue [07:33] so, if you can reboot it, that would be appreciated so that the daily tests can run :) [07:33] didrocks: urgh, ok, let me see if those beasts are documented [07:34] * didrocks crosses fingers :) [07:34] vila: it's a vm AFAIK [07:34] brendand: that's a bit what I was thinking, thanks :) [07:36] except my krillin is not charged - hmmm. [07:36] * brendand waits a few minutes [07:38] didrocks: the server is running but I can't connect via ssh (no credentials for me there), do you know where the VM is hosted ? [07:39] vila: I guess on the same that the i386, I can connect on that one, but unsure how to know where the host is? [07:40] hehe [07:40] vila: the IP of the i386 vm is 10.98.2.79, if that can help [07:40] no idea [07:41] vila: s-jenkins is the jenkins connected to it [07:41] that was my guess, I'm there and searching [07:42] vila: http://s-jenkins.ubuntu-ci:8080/computer/ps-trusty-desktop-amd64-1/ [07:42] didrocks: that doesn't tell us much does it ? [07:42] didrocks: that's where the vm connect to but it can be anywhere [07:43] yeah… [07:44] no /var/lib/libvirt on s-jenkins, probably not there [07:45] vila: ssh naartjie /usr/bin/sudo virsh snapshot-revert ps-trusty-desktop-amd64-1 1410056823 [07:45] naartjie maybe? [07:46] vila: it's back online, calling the snapshot revert virsh command [07:47] didrocks: looks more promising [07:48] vila: so yeah, it's up now thanks to that, don't bother more! Thanks for looking :) [07:48] ack [08:02] ogra_`, what's the new option i need to specify to get developer mode enabled after flashing? [08:02] ogra_`, apart from --developer-mode of course [08:05] pren--password= [08:05] err [08:05] brendand, --password= ... with a password supplied [08:07] robru, no landing mail ? [08:13] I more or less know the situation, but maybe robru will write a belated landing mail in his morning :) [08:15] Mirv, yeah, its not for me, i have some followers on G+ that read my re-post of them every day though [08:15] whats that dirt on my nick ? === ogra_` is now known as ogra_ [08:15] wiped away :) [08:16] :) [08:16] pete-woods, hmm, did you do the seed meger yourself ? [08:16] *merge [08:17] (the commit message looks like ...) [08:18] ogra_: I have no idea how I'd even do that [08:18] funny ... [08:20] * ogra_ just wanted to merge but notices that someone else did already ... and bzr log only has your name [08:20] (whoever did it forgot to re-generate the metapackage) [08:29] Saviq, whats up with https://code.launchpad.net/~unity-team/unity8/new-adbd/+merge/233684 ? greyback set it to "needs fixing" at 19:30 with some serious error message and 30min later he set it to approved without explanation [08:30] ogra_, the error was only for our run-on-device script, so no impact on anything [08:30] ogra_, it's currently stuck in proposed due to oxide-qt fiasco [08:30] dbarth_, you around? [08:31] Saviq, ah, ok [08:34] Saviq: yes [08:35] dbarth_, we have a problem with the oxide-qt 1.2 landing, they got stuck in proposed because oxide-qt is 1.2~, which is lower than 1.2 [08:35] uh [08:35] dbarth_, is there an actual oxide-qt 1.2 coming somewhere, or should the dependencies be >= 1.2~? [08:35] Saviq: I thought unity8 is stuck because of the click landings in -proposed? [08:36] Mirv, no, it's because ↑ [08:36] Saviq: we should adjust dependencies [08:36] or rather [08:36] 1.2 official should be in 1-2 weeks max. [08:37] Saviq: ok, just looking at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html autopkgtests failed for unity-scope-click and qtcreator-plugin-ubuntu, but do those fail because of oxide and not click? [08:37] i don't have the schedule in mind, but we get a stable evey 6 weeks; and we just branched off 1.3 so 1.2 should be declared stable official soon [08:37] Mirv, that's what jibel_ found, yes [08:37] ok [08:37] that won't help fo today, so the easiest is to adjust deps i think === jibel_ is now known as jibel [08:38] dbarth_, yeah, Mirv, can you please upload webbrowser-app and ubuntu-system-settings-online-accounts with the deps adjusted? [08:39] I'll help with silos when just told so [08:39] do you want me to upload a new set of packages to fix that? [08:40] tvoss, thostr_: RTM silo004 we are finally able to test it. I wanted to know though how quick should I get a fix? With it in place though location service stops crashing, but trust store is still crashing [08:41] davmor2, sorry, gimme 10 to context switch [08:42] Mirv, I thought you could upload directly to proposed to not wait for silo? [08:44] Saviq: no, I can't. in two weeks possibly for some packages. [08:45] and Qt I can upload [08:45] 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] Mirv, oh ok, can dbarth_ use the same silo then? can it be un-published? [08:46] ok, so i just rebuild in silo 2 and ping you back once done [08:46] Mirv: i'll double check deps with you in a minute [08:50] Saviq: actually there is an oxide-qt-1.2! [08:50] https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages [08:50] we prepared it last friday and i thought this was the one stuck [08:51] Mirv: when you get a moment could you push http://s-jenkins.ubuntu-ci:8080/job/terminal-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.terminal_0.5.141_armhf.click to the store? [08:51] so the webbrowse-app dependency is correct [08:52] Mirv: also http://s-jenkins.ubuntu-ci:8080/job/filemanager-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.filemanager_0.3.275_armhf.click please [08:53] dbarth_, when will it reach proposed at least then? [08:54] dbarth_, because until it's in https://launchpad.net/ubuntu/+source/oxide-qt, stuff's broken [08:54] dbarth_, so you know the fallout, even unity8 is blocked in proposed currently [08:54] mvo_, hello - i am testing silo 3 [08:55] dbarth_, because UITK and click scope tests can't run due to the unsatisfiable dependency [08:55] and that's what unity8 is gated on [08:57] Saviq: let me ask for the proposed copy; either its that, or a larger revert for silo 2, because the silo does *not* work with the older oxide build [08:58] seb128, i'm hitting some problems with the reset device option on image 24 (which has the updated system settings) [08:58] Saviq: sorry still in meeting. same silo can probably be used in this case. [08:58] seb128, i recall kenvandine mentioned last week that he saw the same thing (before landing it) [08:58] brendand, what sort of reset? [08:59] brendand, the factory reset? [08:59] seb128, yeah erase and reset everything [08:59] seb128: reset launcher is that meant to clear off any pinned apps if so it doesn't [08:59] Saviq: who has permissions to binary copy stuff to -proposed? [08:59] seb128, after pressing the button nothing happens [08:59] brendand, no idea about that, I never tried it and didn't work on it [08:59] davmor2, it's meant to reset the launcher as the title suggest [08:59] Saviq: from a test pov, i have checked that new build of oxide with webbrowser + core webapps, so it's good to go [08:59] davmor2, it only apply after restart, the dialog tell you about that no? [09:00] seb128, ok. is there anyone else around who might know about it or i suppose i need to wait for kenvandine? [09:00] brendand, jgdx but he might not be on yet [09:00] seb128: no just a push button that says reset launcher there is no text anywhere [09:01] dbarth_, archive admins at the moment probably, the correct thing to do would be to dput it in a silo (even the same silo as the webbrowser and settings) [09:01] seb128: oh no it thows up a popup [09:01] dbarth_, that Mirv can help you with (right Mirv?) [09:01] that didn't happen before [09:01] Saviq: dbarth_: no I can't, you'll need a core-dev to copy to archives [09:01] cjwatson, is mvo_ around today? [09:01] davmor2, :-) [09:01] like ogra_ (in the same meeting) [09:02] brendand, he is, he said he had to be away from some minutes, a bit earlier on #distro [09:02] brendand: he was in the morning [09:02] seb128: by before I mean like 2 minutes ago when I tried it [09:02] where I got him to test the rtm silo [09:02] davmor2, weird, I can't confirm that, wfm [09:02] seb128: might just of been a glitch [09:02] could be [09:04] dbarth_: can you reiterate to ogra_ what needs to be copied from where to utopic-proposed to fix oxide, and why doe it fix that? [09:05] I understood so far as some apps depend on oxide (>=1.2), while it should be (>=1.2~) [09:05] and that problem blocks unity8 from migrating among else [09:06] Mirv: no, i got i wrong initially; i thought the new oxide upload was stuck in proposed, but actually it's not there yet [09:06] Mirv: silo 2 rquires that 1.2 oxide, not the previous ~bzr releases [09:07] ogra_: so jdstrand uploaded that new build to the security proposed ppa on friday in prep for that landing [09:07] so we just have to wait ? [09:07] popey: filemanager and terminal done [09:08] ogra_: the oxide-qt-1.2 in the security proposed ppa should be migrated to utopic proposed now, to unblock silo 2 [09:08] well, i guess we need someone from the security team for that copy, right ? [09:09] ogra_: we can wait for jdstrand to double check, yes [09:09] ok [09:09] Saviq, we have quite some errors in unity8 tests on both images, is someone looking into that ? [09:10] ogra_, silo 19 [09:10] ok [09:10] ogra_, adb fallout, or rather password-required fallout [09:10] Saviq, cant be ... rtm has the same errors and still the old adb [09:10] we didn't support password-protected unity8 tests [09:10] ogra_, but it's probably flashed with passwords now [09:10] utopic has 12 failures, rtm 9 [09:11] i dont think rtm is yet ... [09:11] * ogra_ chacks [09:11] *checks [09:11] ogra_, in any case, utopic silo 19, rtm silo 10, tested yesterday with 100% success rate [09:11] it'd be in already if not for the oxide-qt problem [09:11] export IMAGE_OPT=--device=krillin --developer-mode --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --wipe [09:11] not with --password yet [09:13] so it shouldnt behave any different than before yet [09:18] asac: rtm silo 004 is granted [09:18] ogra_: Mirv: ^ === 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. [09:19] oops === 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. [09:19] yes i see it ... silly focus [09:20] publishing [09:21] why is thostr_ suddenly owning all the HERE stuff ? :) [09:21] ogra_: it's lool!!! ;) [09:22] haha [09:22] i thought so :) [09:22] he just doesnt want to be held responsible if it fails [09:22] ugh [09:23] Mirv, any ide what that means ? (rtm 004) ^^^ [09:23] *idea [09:24] does it check against utopic instead of rtm [09:24] mvo_, cjwatson - after installing silo 3 packages won't install from the store [09:24] lool, ! [09:24] lool, you messed up the version ! [09:24] 0.1+14.10.20140829~rtm-0ubuntu1~usilo10~1 (Newer version available) [09:25] asac, that will need a re-upload or some such [09:25] with proper versioning [09:26] Mirv, did you finish your meeting? could we add source-only oxide-qt to utopic silo 2, or how do we do this? [09:28] Mirv: the ubuntu-rtm/landing-008 seems to work nicely [09:28] ogra_: Mirv tried to figure out already but we still do not know what is wrong with the silo10, it does not accept any packages. Would you please take a look at it? [09:28] Mirv: I disabled network to see that the cache actually works [09:29] kalikiana, I think you mean utopic silo 8? [09:30] not rtm [09:31] ogra_: probably justlacking watch_only build [09:32] * Mirv runs [09:32] Mirv, with that versioning ? [09:32] Saviq: can you please give exact instructions what needs to be done? copy/upload what from where to where? [09:32] ogra_: hmm [09:33] ogra_: whats the problem with that version? [09:33] Saviq: I can oxide-qt to silo2 nd reconfigure [09:33] mvo_: is there any news about the click+qtc plugin landing? [09:33] ogra_: will it break the world if we pump it in like that? [09:33] the last bit with tildes i think [09:33] ogra_: hmm, let's see [09:33] right, let Mirv do his magic ... [09:33] ogra_: what does it mean? [09:33] i ma not sure [09:33] lool: ^^ [09:33] ogra_: it probably needs to be changed to be manually configured. the sync process is really botched up. but it just needs a few extra clicks. [09:33] Mirv, https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+sourcepub/4393535/+listing-archive-extra to utopic silo 2 please [09:34] ogra_: can you reupload withright version? [09:34] asac, but that would mean re-testing too, no ? [09:34] ogra_: so what can we do? [09:34] lets see if Mirv can somehow massage it through [09:34] thanks [09:34] i think that would be best [09:34] if not, yes, we might need to re-uplaod [09:35] the questio then is, do we need re-signoff from QA or do we just trust the rebuild [09:35] bzoltan: ubuntu-rtm is verified by me now, so the next step is QA [09:35] ogra_: i think just doing a quick smoke run to see that it is not completely busted is fine if its source identical [09:35] k [09:36] yeah, i doubt it would introduce any issues [09:36] dbarth_, ok, so Mirv will upload oxide-qt from your PPA to silo 2, it could probably use some testing to confirm and will need to be published again [09:36] mvo_: brendand has some issues to represent, or potential issues [09:37] brendand: did you install click, packagekit, packagekit-tools ? i.e. all the stuff from the silo? [09:37] brendand: the updated packagekit/packagekit-tools is crucial [09:37] mvo_, yes - i have everything i'm sure. i can double check [09:37] Mirv: aha, just saw it, thanks! [09:38] brendand: could you please kill packagekitd too? or reboot? [09:38] mvo_, several times :) [09:38] brendand: :( [09:38] * Mirv starts copy-pasting higlights to emacs... I'll respond to each at some point :) [09:39] Saviq: srccopy fine? [09:39] Mirv, yeah [09:40] mvo_: is not that "regression" https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-click/lastBuild a problem? [09:40] Mirv: are you sure you don't want the -b option for that copy from ubuntu-rtm/landing-020? [09:41] brendand: so if all the packages from the ppa are installed, the output of /usr/lib/packagekit/packagekitd -v would be nice, ie. start that on a terminal and then run a install via the store. but I can also try to reproduce it again, I was using ubuntu-rtm/devel-proposed image #30 for my tests. do you have the same [09:41] cjwatson: no, sorry, -b yes please :) [09:41] bzoltan: yes it is a problem, that's one reason this is blocked [09:41] bzoltan: yes, sorry, this issue is fixed with a branch I prepared [09:41] Saviq: dbarth_ oxide copied to landing-002 === nik90_ is now known as nik90 [09:42] mvo_, i have the latest image for krillin [09:42] Mirv, thanks a bunch [09:42] cjwatson: mvo_: OK, I just want to make sure that the process is not stalled. I have an other set of MP in queue already. [09:42] asac: ogra_: HERE published [09:42] Mirv: done, using new preferred syntax: copy-package --from=~ci-train-ppa-service/ubuntu-rtm/landing-020 -s 14.09 --to=ubuntu-rtm --to-suite=14.09-proposed -b gallery-app [09:43] brendand: I only have a n4, so not sure if/what the differences are, but it should not matter, unless there is no debsig-verify installed or something like this [09:43] cjwatson: oh! thanks for that, good toknow that syntax [09:43] kalikiana: so no regressions in location related apps, but the bug is fixed? [09:43] Mirv, I've added oxide-qt to the sources, can you please reconfigure silo 2? [09:44] mvo_, http://paste.ubuntu.com/8298378/ [09:44] Mirv: ok; do you need something more to unblock that landing at this stage? [09:44] Mirv, yay [09:44] Mirv: yay :) [09:45] * asac waits for a new image [09:45] ogra_: Mirv: how are our regressions going on rtm? [09:45] i think unity made it with the input fix? [09:45] 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] dbarth_: hmm, I think se Tested to No and retest after oxide has built? [09:46] asac: unity8 is stuck in proposed because of this oxide problem being resolved with dbarth_ and ogra_ [09:46] and Saviq [09:46] asac: otherwise it would be resolved, and we could move to publishing it to rtm [09:46] Mirv: ok, i can redo some smoke testing yes [09:46] Mirv: ok. thanks [09:46] Mirv: do we know if there are any other bad regressions taht slipped into rtm? [09:46] Saviq: done and running watch_only build [09:46] ogra_: when was last rtm image kicked? [09:47] i didnt get a notifcation for ages here [09:47] Mirv: basically that means osm touch - all the others are web apps [09:47] asac: davmor2 is of the general opinion that let's see after the current blockers are fixed, whether there's something hiding behind those fixes. currently no big marked-as-blockers. [09:47] brendand: packagekitd must be run as root [09:47] mvo_: ^- [09:47]