[06:55] <bzoltan> Mirv:  the version separation MR is still having problems  ... feels a but strange https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/2285/console
[07:14] <Mirv> bzoltan: looks like a job for cihelp
[07:14] <Mirv> network problems
[07:15] <Mirv> bzoltan: oh, that was probably during the break that was announced
[07:16] <Mirv> bzoltan: once again it's rebuilding
[07:54] <bzoltan> Mirv:  thanks
[08:08] <bzoltan> Mirv: Do you think if it is possible that the UITK packages built by CI/Jenkins are incompatible with the fresh image with the overlay PPA?
[08:10] <Mirv> bzoltan: no, I don't know if MP:s are built using overlay PPA:s correctly or not
[08:11] <bzoltan> Mirv: ok...do you know which channel has the standard vivid image without the overlay ppa?
[08:12] <bzoltan> Mirv:   or maybe I just need to purge the PPA on the device
[08:12] <ogra_> bzoltan, there is no such thing
[08:13] <bzoltan> ogra_:  Good to know.. so CI/jenkins builds against a rootfs what is equivalent with the vivid+overlay?
[08:13] <ogra_> yes, indeed, since that is what we work with
[08:13] <ogra_> dropping the overlay PPA would mean going backwards in time ... to release day
[08:14] <ogra_> we shouldnt have called it overlay :) it is an extension of the archive in this case
[08:15] <bzoltan> ogra_:  I see. Thanks for the clarification... in this case my build artifects are to blame :) if something does not work after I install them
[08:16] <Mirv> bzoltan: oh yes, the CI/jenkins definitely uses the latest image which include overlay, that's ture
[08:28] <sil2100> ^ ignore that ;)
[09:20] <tsdgeos> jibel: i was told that silo 39 would automagically appear in https://trello.com/b/AE3swczu/qa-testing-requests-for-questions-ping-eu-jibel-us-jfunk-or-ubuntu-qa-on-ubuntu-ci-eng because it's set as "QA needs to sign off" in the CI train spreadsheet, but maybe i missed something?
[09:20] <tsdgeos> is there something i need to do?
[09:54] <sil2100> tsdgeos: it should, but maybe the bot has some trouble today
[09:55] <tsdgeos> ok :/
[09:55] <sil2100> jibel: maybe the yesterday's switch of the bot got things broken?
[10:14] <jibel> sil2100, no I didn't push it into production.
[10:15] <jibel> sil2100, brendand_ disabled it because we cannot login to LP from the instance it is running on
[10:15] <sil2100> jibel: oh? What happened? Firewall changes?
[10:16] <jibel> sil2100, it seems to be an issue in wadllib on precise
[10:18] <jibel> tsdgeos, ^^ as soon as the bot is back the card will be created
[10:18] <sil2100> ogra_: hey! We seem to be missing the .changes file for 192 :)
[10:18] <ogra_> oops, will fix
[10:23] <ogra_> imgbot, status 192 vivid
[10:24] <imgbot> Status: succeeded, Started: 2015-05-07 02:03:11 UTC, Finished: 2015-05-07 02:55:51 UTC
[10:24] <imgbot> Build URL: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-touch/+build/26200
[10:24] <imgbot> Changelog: http://people.canonical.com/~ogra/touch-image-stats/192.changes
[10:24] <ogra_> fixed :)
[10:31] <sil2100> o/
[10:31] <sil2100> Thanks :)
[10:36] <davmor2> sil2100: ogra_  says fixed, what that actually means is until you look away from the screen or need to use it ;)
[10:44] <pete-woods> trainguards: hi guys. could I get wily silo 34 reconfigured please? I've added a new MR for cmake-extras
[10:47] <sil2100> pete-woods: on it
[10:47] <pete-woods> sil2100: thanks!
[10:49] <sil2100> pete-woods: should be done, yw!
[10:51] <cjwatson> jibel: that seems a little improbable - e.g. snakefruit is a very heavy user of launchpadlib and is on precise
[11:00] <didrocks> fginther: hey, again the i386 machine is broken, I tried to reuse the snapshot revert job to bring it up again, but seems it didn't want to start the jenkins slave job (ps-trusty-desktop-revert-snapshot-daily/1182/console). This job started successfully multiple times yesterday, not sure what happened…
[11:03] <pete-woods> random question, but does anyone know what LP is actually up to when packages are built, but not published in a PPA?
[11:04] <pete-woods> are we waiting on some sort of cron timer or something like that?
[11:04] <didrocks> pete-woods: from what I know, there is a cron timer going over all ppas and doing the actual archive publication
[11:05] <didrocks> (and so, the time depends on how many ppas need to publish new binary packages, a little bit similar than the archive itself)
[11:05] <pete-woods> I guess there's also a fair amount of if you git the start of a "tick" you wait a long time
[11:05] <pete-woods> but if you are near the end, then great
[11:05] <pete-woods> *hit
[11:05] <didrocks> yeah, depends if you are lucky or not :)
[11:05] <didrocks> that's one of the reason the train (if that part didn't change) is actually checking the archive file itself to say "published"
[11:06] <pete-woods> right, that explains that then :)
[11:06] <cjwatson> Indeed.  The publisher takes non-zero time.
[11:06] <cjwatson> And there are a lot of PPAs.
[11:20]  * sil2100 off to prepare lunch
[12:28] <davmor2> sil2100, john-mcaleely: krillin vivid device tarball is good
[12:28] <davmor2> cwayne: did you update the vivid krillin custom tarball at all?
[12:28] <john-mcaleely> davmor2, o/
[12:29] <sil2100> john-mcaleely: you can push!
[12:31] <davmor2> sil2100: there were a couple of issues highlighted but they already exist in the default image, mms/3g fails if there is no password in the apn config and the video issue that jhodapp is getting the blame for even if it is qtmedia :D
[12:32] <davmor2> sil2100: these won't block this landing but would block ota4 just as a heads up
[12:32] <jhodapp> davmor2, ha...confirmed that it is qtmultimedia...I found the build number that introduced that regression so now I'm trying to figure out what broke it
[12:33] <davmor2> sil2100: see told you he'd blame qt, I still say it's all jhodapp 's fault cause it's multimedia and leave it at that ;)
[12:33] <jhodapp> davmor2, no comment
[12:33] <davmor2> jhodapp: nice work thought on a plus side :)
[12:33] <davmor2> though even
[12:34] <jhodapp> davmor2, thanks :)
[12:36] <sil2100> hah ;)
[12:36] <sil2100> Blame Mirv !
[12:37] <cwayne> davmor2, i built the proposed one at the same time as the other one yesterday
[12:38] <davmor2> cwayne: so the one in vivid is good then cool, I'll test that after an emulator and mako sanity run
[12:38] <cwayne> davmor2, sil2100: btw ogra_ brought to my attention some missing translations from the new custom we pushed the other day :/  I have a fix ready in case it's critical
[12:39] <sil2100> cwayne: uh, missing translations in RTM?
[12:39] <cwayne> sil2100, yeah :/
[12:40] <sil2100> cwayne: are those missing for all languages?
[12:42] <cwayne> sil2100, 1 string, yeah
[12:42] <jhodapp> sil2100, I am blaming Mirv :)
[12:45] <jhodapp> Mirv, ping
[12:46] <Mirv> jhodapp: pong
[12:47] <jhodapp> Mirv, hey, the last qtmultimedia upload on krillin vivid image #193 broke playback of ubuntu touch camera recorded videos
[12:47] <jhodapp> Mirv, what was that update for?
[12:48] <Mirv> jhodapp: don't ask me, I wasn't involved ;) rsalveti's landing
[12:48] <Mirv> debian/patches/debian/patches/qgstreamercapturesession_avoid_race_eos.patch
[12:49] <jhodapp> Mirv, ok :)
[12:49] <Mirv> so a fix to bug #1433563
[12:49] <jhodapp> Mirv, oh right
[12:49] <jhodapp> Mirv, I'll talk to him thanks
[12:50] <jhodapp> rsalveti, let me know when you're online
[12:50] <Mirv> it moves one line around https://code.launchpad.net/~rsalveti/kubuntu-packaging/qgstreamercapturesession_avoid_race_eos/+merge/256881
[12:51] <rsalveti> jhodapp: Mirv: just krillin?
[12:51] <jhodapp> rsalveti, yeah
[12:51] <rsalveti> that was required to fix audio recording
[12:52] <rsalveti> doesn't make any sense
[12:52] <rsalveti> to be device specific
[12:52] <jhodapp> rsalveti, yeah, but it seems to have broken video playback
[12:52] <rsalveti> but that code is only executed in the end of the pipeline
[12:52] <rsalveti> or when pausing
[12:52] <rsalveti> did we really validate that reverting that package fixes it?
[12:52] <jhodapp> rsalveti, I traced it using gdb and then confirmed by finding the build number
[12:52] <jhodapp> rsalveti, not yet, about to do that
[12:53] <rsalveti> easy to rebuild that package and change that line
[12:54] <jhodapp> rsalveti, ok...I'm on krillin image 192 right now and it doesn't display this broken behavior...so I'm going to upgrade just this package next
[12:56] <rsalveti> imgbot: map 190
[12:56] <rsalveti> imgbot: map 190 vivid
[12:56] <rsalveti> nah
[12:56] <rsalveti> imgbot, map 190 vivid
[12:56] <imgbot> mako ubuntu version: 190 maps to krillin version: 203"
[12:56] <imgbot> mako ubuntu version: 190 maps to generic_x86 version: 192"
[12:56] <rsalveti> imgbot, map 180 vivid
[12:56] <imgbot> mako ubuntu version: 180 maps to krillin version: 193"
[12:56] <imgbot> mako ubuntu version: 180 maps to generic_x86 version: 182"
[12:57] <rsalveti> imgbot, map 179 vivid
[12:57] <imgbot> mako ubuntu version: 179 maps to krillin version: 193"
[12:57] <imgbot> mako ubuntu version: 179 maps to generic_x86 version: 182"
[12:57] <rsalveti> imgbot, map 178 vivid
[12:57] <imgbot> mako ubuntu version: 178 maps to krillin version: 191"
[12:57] <imgbot> mako ubuntu version: 178 maps to generic_x86 version: 180"
[12:57] <rsalveti> no 192 for krillin haha
[12:57]  * davmor2 takes away rsalveti 's right to abuse the bot
[12:58] <jhodapp> rsalveti, hmm, it downloaded and installed a 192
[13:06] <rsalveti> jhodapp: that probably means we had a device tarball update
[13:06] <rsalveti> which would cause the version bump
[13:06] <jhodapp> rsalveti, hmm, ok...so it's not your qtmultimedia update but it is something in that build #
[13:07] <rsalveti> that would be my guess
[13:07] <jhodapp> rsalveti, just upgraded the packages for qtmultimedia and it still plays
[13:07] <jhodapp> rsalveti, yeah looking at your change there's no way it could be that
[13:07] <rsalveti> so we need to understand what changed at the device tarball side
[13:07] <jhodapp> rsalveti, the bug is in a different part of qtmultimedia...it's not creating the QSGVideoNode instance
[13:08] <jhodapp> rsalveti, yeah, where do you see those changes?
[13:08] <rsalveti> jhodapp: would need to track barajas
[13:08] <rsalveti> jhodapp: john-mcaleely might be able to help you
[13:09] <jhodapp> john-mcaleely, ping
[13:09] <john-mcaleely> jhodapp, pong
[13:10] <jhodapp> john-mcaleely, trying to track the device tarball changes for krillin build #193
[13:10] <jhodapp> john-mcaleely, how/where can I see what changed?
[13:10] <john-mcaleely> #193 on which channel?
[13:11] <jhodapp> john-mcaleely, vivid-proposed
[13:12] <john-mcaleely> jhodapp, Description: ubuntu=20150507,device=20150326-f0c5ba5,custom=20150507,version=205
[13:12] <john-mcaleely> not 192
[13:13] <jhodapp> john-mcaleely, not 192?
[13:14] <john-mcaleely> 192 is not latest in ubuntu-touch/vivid-proposed
[13:14] <john-mcaleely> for krillin
[13:14] <jhodapp> john-mcaleely, right, trying to trace a bug
[13:14] <john-mcaleely> aha, ok
[13:15] <john-mcaleely> jhodapp, that device tarball is
[13:15] <john-mcaleely> http://people.canonical.com/~jhm/barajas/master/device_krillin-20150326-f0c5ba5.changes
[13:15] <john-mcaleely> Description: ubuntu=20150421,device=20150326-f0c5ba5,custom=20150421,version=192
[13:16] <jhodapp> john-mcaleely, what's the version after that?
[13:16] <jhodapp> john-mcaleely, can I see that too?
[13:16] <john-mcaleely> jhodapp, http://people.canonical.com/~jhm/barajas/master/device_krillin.build
[13:16] <john-mcaleely> shows that is the current device tarball
[13:17] <john-mcaleely> there's one I'm *about* to publish
[13:17] <jhodapp> ok
[13:17] <john-mcaleely> but it's not live
[13:17] <jhodapp> john-mcaleely, the latest has no description inline
[13:17] <jhodapp> just a hash
[13:18] <ogra_> there should be a matching .changes file in the same dir ...
[13:18] <jhodapp> ogra_, don't see one for latest
[13:18] <john-mcaleely> jhodapp, the hash matches
[13:19] <john-mcaleely> jhodapp, (otp)
[13:19] <ogra_> http://people.canonical.com/~jhm/barajas/master/device_krillin-20150326-f0c5ba5.changes
[13:19] <ogra_> that is the one matching the build id
[13:20] <jhodapp> oh I get it
[13:20] <jhodapp> right
[13:20] <ogra_> 5f3d334 Disabling CONFIG_VT_CONSOLE_SLEEP to avoid the flood of vt-switch events from logind
[13:20] <ogra_> perhaps this ?
[13:20] <rsalveti> nops
[13:20] <jhodapp> no nothing in there looks suspicious
[13:20] <ogra_> (assuming you look for rge black video issue)
[13:20] <rsalveti> I think it's just easier to bisect the barajas tree
[13:20] <jhodapp> yeah, playing recorded videos
[13:21] <ogra_> rsalveti, why nops, how do you know dropping that option doesnt perhaps disable other CONSOLE options in the config ?
[13:21] <fginther> sil2100, so with the phone images staying on vivid, is there a plan to keep the pre-merge CI on vivid as well? Or should trunks move to wily and we should create SRU branches for vivid?
[13:22] <ogra_> (perhaps one that affcts the codecs)
[13:22] <jhodapp> ogra_, well the issue is qtmultimedia isn't creating the QSGVideoNode instance
[13:22] <jhodapp> ogra_, that much I know already
[13:22] <sil2100> fginther: hey, so I don't have any definite guidelines from higher-ups and I don't want to enforce my own policies
[13:23] <rsalveti> ogra_: because I did that change :-)
[13:23] <ogra_> heh, ok
[13:23] <rsalveti> and that is also on RTM
[13:23] <ogra_> what was ppl_agent again ?
[13:23] <fginther> sil2100, heh :-).  I've been poking steve about this, but his apparently been busy with other things
[13:23] <sil2100> fginther: so for now let's leave CI on vivid until we have a clear understanding ;)
[13:23] <jhodapp> rsalveti, why do you think the culprit might be in the device tarball for this bug?
[13:23] <rsalveti> jhodapp: because there is no rootfs update for 192
[13:23] <sil2100> fginther: yeah, he mentioned that we still need to figure it out
[13:24] <rsalveti> when we get a version bump like this, it is either device tarball or custom tarball updates
[13:24] <rsalveti> since we don't have a custom in there
[13:24] <jhodapp> rsalveti, right but 192 works fine
[13:24] <rsalveti> imgbot, map 178 vivid
[13:24] <jhodapp> rsalveti, it's 193 that is broken
[13:24] <rsalveti> imgbot, map 179 vivid
[13:24] <imgbot> mako ubuntu version: 178 maps to krillin version: 191"
[13:24] <imgbot> mako ubuntu version: 178 maps to generic_x86 version: 180"
[13:24] <imgbot> mako ubuntu version: 179 maps to krillin version: 193"
[13:24] <imgbot> mako ubuntu version: 179 maps to generic_x86 version: 182"
[13:24] <rsalveti> oh, 192 is fine?
[13:24] <jhodapp> yes
[13:25] <rsalveti> but you updated the package and still worked right?
[13:25] <jhodapp> yes
[13:25] <rsalveti> there is no changelog for 179
[13:25] <rsalveti> http://people.canonical.com/~ogra/touch-image-stats/180.changes
[13:25] <rsalveti> just 180
[13:25] <jhodapp> rsalveti, yeah, it's 180
[13:25] <ogra_> so 179 was a device or custom tarball
[13:25] <jhodapp> http://people.canonical.com/~ogra/touch-image-stats/180.changes
[13:26] <rsalveti> right, which is why I was thinking it was an issue with the device tarball
[13:26] <jhodapp> rsalveti, let me try upgrading the rest of the packages from the 180 diff and see if any of those break it...if not then yes I agree it's device or custom
[13:26] <rsalveti> cool, alright
[13:27] <ogra_> rsalveti, 180 was a custom tarball
[13:27] <ogra_> well, 179 i mean
[13:27] <ogra_> hmm
[13:28] <ogra_> actually ... 180 was custom and rootfs at the same time
[13:28] <ogra_> 179: version_detail": "ubuntu=20150409,device=20150326-f0c5ba5,custom=20150409,version=179"
[13:28] <ogra_> 180: "version_detail": "ubuntu=20150410,device=20150326-f0c5ba5,custom=20150410,version=180"
[13:28] <ogra_> device didnt change at all
[13:29] <rsalveti> do we get any denials?
[13:30] <kenvandine> rvr, you're the last to comment on the card for vivid silo 15, it's still under testing, not blocked but nobody is assigned?
[13:30] <kenvandine> rvr, did it get forgotten? :-p
[13:30] <rvr> kenvandine: It's confusing... That's actually a trick to calculate how much time does it take to test silos.
[13:31] <john-mcaleely> jhodapp, sorry
[13:31] <john-mcaleely> jhodapp, did you find what you needed?
[13:31] <rvr> kenvandine: The QA team was busy doing other things these days
[13:31] <rsalveti> ogra_: jhodapp: if we get denials it could be related with custom
[13:31] <john-mcaleely> or still seeking?
[13:32] <kenvandine> rvr, ok, just making sure it's not forgotten. that wasn't clear
[13:32] <jhodapp> john-mcaleely, still trying to narrow down what caused the bug...I'm good for now but will probably have another question soon
[13:32] <jhodapp> rsalveti, apparmor denials?
[13:32] <ogra_> john-mcaleely, i think we're fine ... device didnt change around the time the issue started
[13:32] <rsalveti> jhodapp: yes
[13:32] <jhodapp> rsalveti, let me check that next
[13:32] <john-mcaleely> ah, right. ok
[13:33] <john-mcaleely> I'm slightly off the hook then
[13:33] <jhodapp> john-mcaleely, for now ;p
[13:33] <john-mcaleely> sil2100, so, I got distracted. is now a good time still for the new vivid krillin tarball?
[13:39] <jhodapp> rsalveti, nope, none of those packages cause the regression
[13:40] <jhodapp> rsalveti, if I download the device and custom tarballs for 193, how do can I manually flash those?
[13:51] <rsalveti> jhodapp: there is a device argument in ubuntu device flash
[13:51] <jhodapp> rsalveti, alright
[13:52] <rsalveti> --device-tarball
[13:52] <rsalveti> there is also one for custom
[13:52] <rsalveti> just flash without --wipe/bootstrap
[13:52] <jhodapp> rsalveti, awesome thanks
[13:52] <rsalveti> then you can easily test and validate your environment
[13:53] <jhodapp> rsalveti, indeed
[14:02] <fginther> sil2100, slangasek, we really need an answer on how to handle this vivid-wily transition. It's blocking other wily work and may lead to confusion for the upstream teams as well until we have a clear direction. I'm happy to discuss alternative approaches.
[14:02] <sil2100> fginther: +1
[14:18] <fginther> didrocks, the i386 node is working again. I had to fix a larger problem of a full disk :-(
[14:22] <john-mcaleely> sil2100, davmor2 krillin-vivid tarball pushed
[14:23] <sil2100> john-mcaleely: \o/ thanks :)
[14:23] <davmor2> john-mcaleely: \o/
[14:54] <renatu> hey guys since, jenkis is not in a good shape (most of autopilots tests fail to run due some wrong configuration or network errors) can we disable the autopilots on jenkins and just keep the output debian files? This will save us a lot of time
[14:55] <robru> cihelp ^
[14:57] <fginther> renatu, can you point to a specific example so that I know which tests you are referring to?
[14:57] <charles> trainguards, could I get silos for spreadsheet rows 61 and 62? I added these to the spreadsheet earlier but looks like the silo request fell in the bitbucket
[14:58] <charles> eg, no request ids for those rows
[14:59] <charles> yay
[15:00] <robru> charles: 16 and 35
[15:01] <Ursinha> renatu: opa :) we're investigating the networking issues now (things got bad after the rack move yesterday), if you point us to the failing jobs we can have a look
[15:01] <charles> robru, thanks :)
[15:01] <robru> charles: you're welcome
[15:02] <sil2100> robru: you woke up for the meeting? :)
[15:02] <alan_g> trainguards Silo 021 testing done. You can publish.
[15:03] <sil2100> alan_g: ACK!
[15:03] <robru> sil2100: well it's not like I can read meeting cancellation emails while I sleep!
[15:03] <sil2100> hmmm
[15:03] <sil2100> robru: don't publis silo 21
[15:03] <sil2100> alan_g: hm, why is it set to not needing QA sign-off?
[15:04] <alan_g> because camako set that. (He says only needed for RTM)
[15:04] <renatu> fgimenez, Ursinha, ok let me try a new build, I will ping you if still falling. Thanks
[15:04] <sil2100> alan_g: it's a big landing, right? Anything that's not a 100%-risk-free change shouldn't land without QA sign-off
[15:05] <sil2100> alan_g: no, we require sign-off for vivid since 2 months ;) Since we'll be switching our stable branch to vivid in the next weeks
[15:05] <sil2100> alan_g: only landings to wily currently don't need QA
[15:05] <sil2100> But wily is more like hm, a playground right now
[15:05] <alan_g> sil2100: ack
[15:05] <sil2100> alan_g: anyway, no harm done :)
[15:06] <sil2100> alan_g: if anything, the https://wiki.ubuntu.com/citrain/LandingProcess docs are up-to-date with current policies
[15:27] <robru> alesage: Mirv: slangasek: https://code.launchpad.net/~robru/phablet-tools/fix-overlay-pinning/+merge/258514 can you guys take a look at this one-liner?
[15:30] <sil2100> robru: looks goodish, but just in case I wouldn't put the pin priority that high ;) But that's just cosmetics
[15:31] <robru> sil2100: yeah I wasn't sure what a good number would be. needs to be at least 1002 to beat the overlay ppa pin, but then i thought maybe some space inbetween would be prudent
[15:41] <alesage> robru, just taking it for a spin
[15:41] <robru> alesage: thanks
[15:43] <robru> alesage: so you should expect a mix of overlay PPA packages and silo ppa packages, perhaps similar to http://paste.ubuntu.com/11011081/
[15:43] <didrocks> fginther: argh, anything I can do to help preventing this?
[15:43] <didrocks> fginther: and thanks!
[15:44] <fginther> didrocks, the host system is just missing some active monitoring. It was a different VM that had become out of control and was consuming too much disk
[15:45] <didrocks> fginther: ah ok, not those vm's faults then! Good to know and that explains why I couldn't restart it myself :)
[15:46] <alan_g> sil2100: just checking my understanding: the policy you referred me to says QA sign-off for /1/ "TRAINCON-0" and /2/ "For all landings to the ubuntu-rtm branch". Is it wrong?
[15:46] <sil2100> alan_g: hah! Ok, you found one place where it's not modified ;) The landing instructions in the first section have it explained
[15:47] <sil2100> alan_g: thanks for mentioning, let me change that, this part was always managed by QA
[15:48] <alan_g> sil2100: yw :)
[16:15] <robru> jibel: http://people.canonical.com/~platform/citrain/?C=M;O=A raw json with mp lists
[16:20] <dobey> trainguards: can i get a reconfig for ubuntu/landing-022 please? had to do a merge and resubmit for one MP to resolve a conflict
[16:21] <robru> dobey: you have permission to reconfigure as long as you're not adding a new project
[16:22] <dobey> robru: how do i reconfigure then? i don't see a link for that on the dashboard or in the spreadsheet
[16:23] <robru> dobey: "Landing Tools" menu in the spreadsheet. just click the right row first.
[16:24] <dobey> "This app needs authorization to run"
[16:25] <dobey> oh, i have to log in again in google, ok
[16:29] <dobey> hmm
[16:29] <dobey> i guess it didn't work
[16:56] <dobey> hmm
[17:11] <dobey> cihelp: are the silo PPAs being cross-compiled for arm?
[17:13] <ogra_> nothing is cross compiled in the official infra
[17:13] <ogra_> it is always native
[17:14] <ogra_> there are virtualized armhf PPAs though ... i dont think the silos are vitrual
[17:15] <dobey> hmm
[17:16] <robru> dobey: silos are definitely devirt, that's a security requirement for publishing in ubuntu archive.
[17:16] <robru> dobey: also silos >30 are new, are you seeing a problem there? hopefully they weren't misconfigured when they were created.
[17:16] <dobey> this error doesn't make any sense then; and i'm not sure why it's happening. and i don't have a wily on arm anywhere to really test it
[17:16] <dobey> robru: this is in 22
[17:17] <dobey> https://launchpadlibrarian.net/205880848/buildlog_ubuntu-wily-armhf.unity-scope-click_0.1.1%2B15.10.20150507.1-0ubuntu1_BUILDING.txt.gz
[17:17] <robru> dobey: definitely devirt then
[17:18] <robru> dobey: hmm, that is tricky. the only way I know to fix those is to have it installed on a device and poke at it with apt. time to do-release-upgrade on a phone? ;-)
[17:18] <dobey> yeah; the error makes sense to me only in the context of cross-build though; and a new version of ubuntuone-credentials was even released last night into wily without any problems :-/
[17:19] <dobey> robru: yeah, i guess i'll have to debootstrap a chroot on a phone to see
[17:19] <dobey> also, debootstrap is a weird name for a tool that actually bootstraps something :P
[17:21] <robru> dobey: heh
[17:21] <robru> dobey: oh, the ubuntuone-credentials was only published 4 hours ago, maybe this is a transient error due to running the build before the package fully published? might be worth trying the build one more time before mucking with debootstrap
[17:22] <dobey> oh, is publishing to the ports archive that slow?
[17:23] <robru> dobey: well I'm not sure exactly at what time your build was started.
[17:24] <dobey> robru: very recently; and i've already tried to rebuild once
[17:24] <robru> dobey: oh if you already rebuilt it then I dunno, sorry. yeah try debootstrap
[17:28] <robru> brb
[17:29] <dobey> yeah, and looking at ports server, the packages are already there; and these are coming from ftpmaster.internal anyway (though maybe ftpmaster.internal is behind?)
[17:30] <jhodapp> imgbot, map 181 vivid
[17:30] <imgbot> mako ubuntu version: 181 maps to krillin version: 195"
[17:30] <imgbot> mako ubuntu version: 181 maps to generic_x86 version: 184"
[17:34] <dobey> well, at least making a wily chroot isn't too bad; i already had a vivid chroot, so just copying it and then tweaking sources.list and doing dist-upgrade works well enough to get a chroot fairly quickly
[17:44] <dobey> robru: so fun. in a wily chroot on my nexus4, i added the landing-022 ppa, and did apt-get build-dep unity-scope-click, and it's installing everything just fine :-/
[17:45] <dobey> so trying to build again :-/
[17:54] <dobey> bah, it's still failing :(
[17:56] <robru> dobey: sorry, that's gone beyond my skill level. maybe infinity or cjwatson can give some more insight into that.
[17:57] <dobey> yeah, or wgrant when he shows up
[17:57] <dobey> would be nice if the lp builders were configured to output verbose apt error messages for these things
[18:23] <cjwatson> ogra_: even virtualised PPAs aren't cross-compiled
[18:24] <ogra_> cjwatson, thats what i said
[18:24] <ogra_> (i think)
[18:24] <cjwatson> ogra_: you implied that virtualisation or not was somehow relevant to dobey's question; it isn't, neither virt nor devirt are cross-compiled
[18:25] <cjwatson> dobey: heh, the problem is you can't really get apt to be very verbose in a useful way without considerable logic
[18:26] <cjwatson> dobey: easiest way is to build a chdist instance locally with the appropriate sources.list and play with that
[18:26] <dobey> cjwatson: chdist would be different from my existing wily chroot somehow?
[18:27] <cjwatson> yes, you can easily set one up for a different architecture etc.
[18:27] <cjwatson> can't seem to get it to go wrong here though
[18:28] <dobey> well i've got the chroot on my phone, so it's armhf already. but i can't get it to fail there either :-/
[18:30] <dobey> so i don't know what else to do at this point
[18:31] <cjwatson> I'm continuing to investigate in between evening stuff
[18:31] <dobey> cjwatson: ok, thanks
[18:43] <cjwatson> dobey: it seems OK here too, retrying
[18:44] <dobey> i've rebuilt (via ci train dash) 3 times now with the same failure
[18:44] <cjwatson> dobey: looking at recent archive changes, there's a pretty good chance that this was due to arch skew in -proposed with https://launchpad.net/ubuntu/+source/glib-networking/2.45.1-1, which only just built ~50 minutes ago
[18:44] <cjwatson> prior to that there were several hours where it was skewed on amd64 vs. armhf
[18:45] <dobey> oh, is -proposed being pulled in here too?
[18:45] <cjwatson> yes
[18:45] <cjwatson> did your chroot include that?
[18:45] <cjwatson> anyway, it's building now
[18:45] <cjwatson> and is past the previous failure
[18:45] <dobey> ah, ok. no, i don't have -proposed in my chroot
[18:46] <dobey> i thought the PPA builders didn't have proposed enabled
[18:46] <cjwatson> this isn't a property of the builders
[18:46] <cjwatson> it's a property of the PPA
[18:46] <cjwatson> and all the silos are configured with -proposed enabled by default, because otherwise there is no way to execute library transitions involving silos
[18:46] <dobey> ok. well now i know that the silos are configured that way :)
[18:47] <cjwatson> it can be turned off temporarily if need be, but usually better not to
[18:47] <dobey> thanks again
[18:48] <cjwatson> dobey: here's the chdist procedure: http://paste.ubuntu.com/11013254/
[18:48] <cjwatson> you can then play around fairly arbitrarily with apt-get's resolver; you just can't actually install any packages, so say no to its prompt
[18:50] <dobey> ok
[19:45] <robru> cjwatson: thanks for following that up, so i guess i was right originally, just needed time before rebuilding? How can i check that in the future?
[20:34] <fginther> slangasek, another ping on the vivid to wily transition question. I see that some projects (like lp:indicator-sound) have already moved to wily and have created 15.04 SRU branch, but most have not. Is this just something that needs to be transition on a case-by-case basis?
[21:40] <slangasek> fginther: ok, so I finally found time to look up https://wiki.ubuntu.com/citrain/LandingProcess#Landing_your_change_to_Ubuntu_RTM
[21:41] <slangasek> fginther: the policy shouldn't change, just the names; so projects can either have a single branch landing both places, or use separate branches
[21:43] <fginther> slangasek, cool, so if I understand correctly, the first action is to land the change into the development release (which is now wily). To me that implies that everything should be wily based and then use a separate branch only in cases where it is needed.
[21:47] <pmcgowan> fginther, are you talking phone releases? if so everything needs to land i the vivid PPA as we won't release from wily
[21:48] <fginther> pmcgowan, that is what I'm talking about.
[21:48] <fginther> pmcgowan, will the upstream projects ignore wily at this time?
[21:48] <pmcgowan> fginther, ok so we will pretty much land everythign both places from what I undestand
[21:49] <fginther> pmcgowan, ok, that clarifies things a bit
[21:49] <pmcgowan> fginther, but landing to vivid will not be the exception, so sounds like single branch two landings
[21:50] <pmcgowan> or whatever the project wants I suppose
[21:50] <fginther> pmcgowan, it's sounds like the preferred approach would be to build single branches against both wily and (vivid + overlay_PPA)
[21:50] <pmcgowan> I suspect so
[21:51] <pmcgowan> default case
[21:51] <fginther> pmcgowan, thanks
[21:57] <sil2100> pmcgowan: is that a final decision? I mean, I guess that's one way I understood it, but I want to know if that's the guideline
[21:57] <sil2100> Since I heard multiple conflicting things
[21:59] <pmcgowan> sil2100, we need to keep wily up to date or we will suffer later, I am not sure how much testing we will devote to it
[21:59] <pmcgowan> sil2100, but we release from vivid for the foreseeable future
[22:04] <awe> hey sil2100, was wondering who should do the NM copy per slangasek's last email.  I can do, but wasn't sure if I had permissions to do so?  We also probably want to copy from vivid-security as opposed to vivid
[22:05] <awe> ( I think as vivid-security and vivid-updates both have 4ubuntu15.1 vs 4ubuntu15 in vivid )
[22:12] <sil2100> awe: I can do it if anything, not sure if I'll be able to do the copy today still since it's past midnight, but I'll try
[22:12] <sil2100> If not then I'll copy it tomorrow in the morning if you don't mind :)
[22:15] <awe> sil2100, yea...no worries about doing it tomorrow, that'd be fine thanks
[22:15] <awe> get some sleep1
[22:29] <rsalveti> robru: hey, can you try assigning silo for line 69?
[22:29] <rsalveti> not really able to load the page to assign silos here
[22:29] <rsalveti> not sure if slow, but trying to load the configure page for more than 2 minutes already
[22:33] <Ursinha> fginther: I wonder if something changed in the lab that you might need vpn to access ci-train.ubuntu.com
[23:16] <cjwatson> robru: best is probably to follow the paste I showed so that you can dig through things with apt-get
[23:16] <cjwatson> robru: I don't have a straightforward script for you though
[23:41] <robru> cjwatson: thanks
[23:41] <robru> rsalveti: sorry, was out. looks like you got it