=== chihchun_afk is now known as chihchun === vrruiz_ is now known as rvr [14:04] heya can someone check https://requests.ci-train.ubuntu.com/#/ticket/1145 to see if it published [14:04] trainguards ^ [14:06] pmcgowan: doesn't look like it is published [14:07] dobey, yeah [14:07] the overlay ppa has a lower version than in the silo ppa, anyway [14:33] robru, any suggestion on that silo? [14:50] trainguards ? [15:27] trainguards, https://requests.ci-train.ubuntu.com/#/ticket/1100 says "failed to build" but when I look at jenkins it seems everything went OK [15:34] ssweeny: but looking at the ppa it's backed by seems to indicate the armhf arch failed with [15:34] https://launchpadlibrarian.net/250214125/buildlog_ubuntu-vivid-armhf.location-service_2.1+15.04.20160328-0ubuntu1_BUILDING.txt.gz [15:34] other archs built fine [15:35] kgunn, aha, thanks! [15:35] interesting === chihchun is now known as chihchun_afk [17:14] ssweeny: yes, a successful jenkins run just means the *source* package build succeeded, you need to look at the PPA [17:16] pmcgowan: kenvandine: I suspect the diff is against vivid proper, logs look like it was switched to point at overlay after the diffs were generated, re-diffing just to be sure [17:19] robru, thanks [17:21] pmcgowan: kenvandine: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-1145/2016-03-28_17:21:02/vivid/android/packaging_changes.diff yes this diff looks much more sensible [17:22] robru, great can we go ahead and publish it then? [17:22] pmcgowan: sure, just needs a core dev, I can't do it. kenvandine ? [17:24] I gotta grab some breakfast, bbiab [17:29] sure [17:29] pmcgowan, that does look much better :) [17:31] robru, the status is in generating diffs, can i publish like that? [17:31] or do i need to wait for the status to change [17:35] pmcgowan, publishing [17:36] ERROR: No artifacts found that match the file pattern "*". Configuration error? [17:36] robru, ^^ [17:49] kenvandine: that's fine, that just means that it did a PPA copy directly rather than writing a manifest file for copying to the real archive [17:49] kenvandine: and yeah you could have published while the status was still 'generating diffs', diff generation was already over (as evidenced by the fact that you were looking at the finished diff), it just hadn't updated the status yet, which happens every 15 min. [17:52] ok === _salem is now known as salem_ === salem_ is now known as _salem === _salem is now known as salem_ === salem_ is now known as _salem [20:55] robru: ping [20:56] lpotter: hi [20:57] hi. I get a 401 error when trying to create a new landing request [20:58] lpotter: have you ever used it before? [20:59] no :) [21:02] lpotter: so you're wanting access then? what are you working on? [21:02] yes, I need to try and land some QtNetworking fixes [21:04] lpotter: ok I'll add you to the team [21:05] thank you [21:05] I'm lorn-potter on launchpad, btw [21:08] lpotter: ok, I added you to the team, you'll have to log out and log back in. and read: https://wiki.ubuntu.com/citrain/LandingProcess I'll be around to answer questions periodically if you're unsure about anything [21:10] ta [21:11] yw [22:01] robru: what does that mean, or rather, what do I do to fix that? ^^ [22:11] lpotter: i don't understand what you're trying to do [22:16] lpotter: let me know what your goal is, and I'll review your ticket [22:17] trying to build packages to test/land [22:17] copying them over from my ppa [22:18] and sorry, citrain noob here :) [22:19] lpotter: so I'll have to copy stuff from your ppa, the sync feature doesn't work like that, that's a vestigial feature from when ubuntu-rtm was a different distro [22:19] The error is that it's trying to adjust the version number and failing [22:20] lpotter: and do you have the gles package prepped? [22:20] no [22:22] lpotter: have you been coordinating with Mirv? He usually handles qtbase. [22:25] not on this one. I was instructed to do my own, since I have not yet created a landing request [22:42] lpotter: sorry got distracted. So if you're ready i can copy your packages in but you'll need the gles twin before you can actually publish this. [23:11] well, not going to publish it just yet, but will get the gles package up there [23:14] lpotter: OK let me know when you get the gles prepped and I'll copy both at the same time. [23:15] will do