[02:05] <imgbot> [03:50] <imgbot> [03:50] <imgbot> [07:49] <oSoMoN> trainguards: good morning, can I have a silo for line 66 please?
[07:50] <oSoMoN> robru, since you’re still around, did I fill correctly line 66 for webbrowser-app to be synced back to wily?
[07:52] <sil2100> oSoMoN: hey!
[07:53] <sil2100> oSoMoN: I just corrected the sync line, let's see if the syncing works
[07:53] <sil2100> Could you build silo 14?
[07:53] <oSoMoN> sil2100, thanks, will build it now
[08:07] <oSoMoN> sil2100, the copy seems to have gone ok (https://ci-train.ubuntu.com/job/ubuntu-landing-014-1-build/188/console), but the PPA doesn’t contain anything…
[08:12] <sil2100> WTH
[08:13] <sil2100> Ah, bummer
[08:15] <sil2100> oSoMoN: so one reason why there's nothing in the PPA is that the same silo was used to build the original version of the package... but I think that we can't use the current sync functionality for this
[08:15] <sil2100> Let me upload the package there manually
[08:16] <sil2100> oSoMoN: the thing is, the sync code only changes the version number between ubuntu and ubuntu-rtm, here it just sticks with the old version
[08:16] <sil2100> Which is bad
[08:17] <oSoMoN> okay
[08:18] <oSoMoN> sil2100, any estimate on when a working sync functionality will be available? I would hate to have to do two landings for each MR (with two branches every time), and I would equally hate to have to bother you or others to do manual syncs
[08:19] <sil2100> I think quickly modifying the sync functionality to work for our case should be a quick change
[08:20] <oSoMoN> good
[09:23] <john-mcaleely> sil2100, is now a good time to push the krillin rtm tarball? davmor2 +1's it
[09:24] <sil2100> john-mcaleely: hey! Yes, I guess it's fine :)
[09:24] <john-mcaleely> sil2100, button pushed. tarball pushed :-)
[09:25] <tsdgeos> cihelp: any idea what's up with http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity8
[09:25] <tsdgeos> don't really understand what https://jenkins.qa.ubuntu.com/job/wily-boottest-unity8/lastBuild/ means
[09:25] <tsdgeos> says vivid/universe but also says wily-boottest
[09:32] <sil2100> john-mcaleely: thanks o/
[09:51] <psivaa> tsdgeos: that appears to be a temporary glitch, afais it's the host being unable to ssh to the testbed, the next run was OK, it should pass now in the excuses
[09:52] <tsdgeos> psivaa: cool, so no action needed from our side, cool :)
[10:27] <oSoMoN> trainguards: can I publish silo 14 (wily) myself, or do I need to poke you for that?
[10:27] <sil2100> A trainguard needs to do it, let me publish then
[10:31] <oSoMoN> sil2100, thanks!
[10:57]  * sil2100 off to slowly prepare lunch
[11:43] <davmor2> sil2100, john-mcaleely: vivid tarball tested and passes
[11:44] <davmor2> sil2100: technically it fails but it fails in the same way as the none tarballed version so it passes really :)
[11:49] <sil2100> uh
[11:49] <sil2100> ;p
[11:49] <sil2100> That's good I guess..?
[11:54] <cwayne> sil2100, question: would updating a click in the store simply to match the version that's in custom require qa signoff?
[11:54] <davmor2> sil2100: msm is broken because 3g is broken and a video recorded from the camera won't playback :)
[11:54] <davmor2> mms even
[11:58] <john-mcaleely> the video playback issue davmor2 ?
[11:58] <john-mcaleely> anyway, sil2100 is now a good time to push it?
[12:08] <sil2100> john-mcaleely: yeah, no plans from our side :)
[12:09] <sil2100> cwayne: hm, normally I'd say it doesn't require
[12:11] <sil2100> cwayne: but let's ask davmor2 for opinion
[12:11] <john-mcaleely> sil2100, pushed
[12:18] <sil2100> \o/
[12:45] <pmcgowan> sil2100, why do I see a new rtm proposed image this morning
[12:46] <popey> pmcgowan: looks like cron job?
[12:46] <popey> 03:05 < imgbot> [12:48] <pmcgowan> popey, why is it 60MB
[12:49] <popey> dunno, last four changes files are blank http://people.canonical.com/~ogra/touch-image-stats/
[12:49] <davmor2> pmcgowan: new tarball maybe
[12:49] <pmcgowan> which we didnt intend to push to krillin
[12:54] <sil2100> pmcgowan: tarball upload :)
[12:54] <sil2100> Ah, for krillin too?
[12:55] <sil2100> hm, new custom?
[12:55] <sil2100> Ah, nvm
[12:55] <pmcgowan> point is we shouldn't see any updates
[12:55] <sil2100> Yeah, it seems there's a new device tarball in the krillin channel as well
[12:55] <sil2100> john-mcaleely: ^ ?
[12:56] <sil2100> Ah, wait, I think john-mcaleely pushed for both, but we don't intend to copy the krillin one
[12:56] <sil2100> But I guess they want to keep both devices in sync in -proposed
[12:57] <john-mcaleely> yeah, proposed krillin image to have the current codebase available
[12:58]  * sil2100 needs to jump out to the vet now
[12:58] <sil2100> Let me switch to my shell, brb
[13:18] <alex-abreu> trainguards can you reconfigure silo 32
[13:41] <kenvandine> trainguards: i appear to have angered the train with silo 20
[13:41] <kenvandine> ubuntu-system-settings-online-accounts is hanging up promotion of settings in wily, so i tried to do a sync from wily-proposed... which didn't work of course, and now it doesn't let me fix the job
[13:47] <mpt> Hi, when I try to “citrain device-upgrade 36” I just get a “usage:…” spiel telling me that the silo number must be from “1..20”. How can I fix this? (I’m using phablet-tools 1.1+14.10.20141002-0ubuntu1 on Ubuntu 14.04.)
[13:47] <jgdx> cihelp: ^
[13:47] <Ursinha> trainguards, ^
[13:48] <jgdx> right :s
[13:51] <kenvandine> mpt, missing the password
[13:51] <kenvandine> citrain device-upgrade SILO PASSWORD DISTRO
[13:51] <kenvandine> citrain device-upgrade 36 0000 ubuntu
[13:51] <kenvandine> for example
[13:51] <kenvandine> oh... 1..20?
[13:51] <kenvandine> maybe there's multiple issues :)
[13:52] <mpt> Why … why … why didn‘t I notice that
[13:52] <mpt> It’s because I noticed the problem with the last line of the output, and didn’t examine further
[13:53] <mpt> Anyway…
[13:53] <mpt> Command '"SUDO_ASKPASS=/tmp/sudo_askpass.wgdf sudo -A apt-get update -qq ; echo ADB_RC=\$?"' returned non-zero exit status 100
[13:53] <mpt> W: Failed to fetch http://ppa.launchpad.net/phablet-team/ppa/ubuntu/dists/wily/main/binary-armhf/Packages  404  Not Found
[13:53] <kenvandine> oh... you're on the werewolf!
[13:53]  * mpt goes to report a bug on the out-of-date usage instructions in the meantime
[13:53] <mpt> No, I’m on 14.04
[13:53] <kenvandine> the device
[13:54] <kenvandine> it added the silo ppa as wily
[13:54] <mpt> yes
[13:54] <kenvandine> not vivid
[13:54] <kenvandine> and we don't have wily packages built in that ppa
[13:54] <mpt> aha
[13:55] <mpt> So “ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/devel-proposed/krillin.en” is not, currently, a good idea?
[13:56] <jgdx> mpt, did you remove the broken ppa on the device?
[13:56] <kenvandine> mpt, right now it's not
[13:56] <mpt> jgdx, it doesn’t matter now if I have to reflash it with vivid, right?
[13:56] <kenvandine> ubuntu-touch/rc-proposed/krillin.en
[13:56] <kenvandine> i think
[13:57] <kenvandine> devel-proposed just changed to wily
[13:57] <jgdx> mpt, okk. But great that you found a solution!
[13:57] <mpt> jgdx, whoa there, let’s not jump to conclusions ;-)
[13:58] <kenvandine> jgdx, multiple issues... including the switch to wily  for devel-proposed :)
[13:58] <mpt> Channel ubuntu-touch/rc-proposed/krillin.en not found on server https://system-image.ubuntu.com
[13:59] <mpt> See, jgdx, told you ;-)
[14:00] <kenvandine> mpt, i might not have had that channel exactly right
[14:01] <Guest98059> there is a ubuntu-touch/rc-proposed/bq-aquaris.en
[14:01] <kenvandine> mpt, it might be ubuntu-touch/rc-proposed/bq-aquaris.en
[14:01]  * kenvandine looks for the email
[14:01] <mpt> Ok, that’s downloading stuff
[14:01] <pmcgowan> lets see what
[14:02] <mpt> A “version 3”
[14:07] <pmcgowan> mpt, you may need to wait, that channel seems busted
[14:07] <mpt> pmcgowan, it downloaded three files without error. It said “Failed to enter Recovery”, but it always says that.
[14:08] <mpt> (Where by “always” I mean “every time I’ve tried it today”)
[14:08] <pmcgowan> mpt, the contents are not correct, its a mix of vivid and rtm
[14:08] <pmcgowan> we need another build
[14:08] <mpt> ok
[14:10] <ogra_> imgbot, status 197 vivid
[14:10] <imgbot> Status: succeeded, Started: 2015-05-14 02:03:12 UTC, Finished: 2015-05-14 02:58:18 UTC
[14:10] <imgbot> Build URL: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/vivid/ubuntu-touch/+build/26784
[14:10] <imgbot> Changelog: http://people.canonical.com/~ogra/touch-image-stats/vivid/197.changes
[14:10] <ogra_> great ...
[14:11] <ogra_> vivid changelogs moved to a subdir ... (havent copied them all yet, but all new ones will be created there)
[14:22] <pmcgowan> ogra_, so our channels seem to be very conflated right now
[14:22] <pmcgowan> hoping sil2100  shows up to start fixing them
[14:23] <ogra_> pmcgowan, right, i dont know yet what to do with wily changelogs or even where exactly point the bot to on system-image.u.c
[14:24] <kenvandine> Mirv, i see you had kicked some of the adt jobs, any idea what's up with ubuntu-system-settings-online-accounts failing in wily-proposed?
[14:24] <pmcgowan> ogra_, we have no valid vivid channel currently
[14:24] <ogra_> well, devel-proposed still points to vivid i think
[14:24] <pmcgowan> nopes
[14:24] <ogra_> oh
[14:24] <pmcgowan> wily it seems
[14:24] <kenvandine> ogra_, apparently not
[14:25] <pmcgowan> but the rc-proposed has wrong tarballs
[14:25] <kenvandine> arale yes
[14:25] <pmcgowan> kenvandine, ?
[14:25] <kenvandine> arale changed channels from vivid-proposed to devel-proposed
[14:25] <kenvandine> which is still vivid
[14:25] <kenvandine> but i think they did the channel rename first
[14:26] <kenvandine> i suspect that'll get switched to wily too
[14:26] <kenvandine> but they renamed the channel yesterday
[14:26] <kenvandine> i think
[14:26] <ogra_> it pulls the rootfs tarball from the devel-proposed channel i think
[14:26] <kenvandine> so it requires a manual channel switch or just edit the channels.ini
[14:27] <ogra_> kenvandine, oh, btw, why cant i open any urls anymore on my vivid phone ... looks like url-dispatcher appends some junk now ...
[14:27] <kenvandine> ugh
[14:27] <kenvandine> tedg`, ^^
[14:28] <tedg`> ?
[14:28] <kenvandine> tedg`, are you still trying to pass url-dispatcher to me?  people keep pinging me about it :)
[14:28] <ogra_> i see something like "&uct=1427058370" appended to every url in the browser
[14:29] <tedg> kenvandine, Ha, sorry, I'll tell you sometime :-)
[14:29] <tedg> Hmm, I don't think that's URL dispatcher…
[14:29] <ogra_> well, doesnt happen on rtm with the same app
[14:30] <tedg> Can you grab a dbus log? You can see what URL gets sent.
[14:31] <dobey> cihelp: can we get a re-build for the jenkins MP testing for https://code.launchpad.net/~alecu/unity-scope-click/refunds-previews/+merge/257444 ? the build should happen on wily, but i think maybe i filled the form slightly wrong when trying to start the build myself or something, because it seems to be failing to create a valid recipe file
[14:32] <ogra_> tedg, bah, it is actually a bug in the app ...
[14:33] <ogra_> (it hands the wrong thing to Qt.openUrlExternally() ... )
[14:34] <tedg> ogra_, Ah, cool.
[14:44] <alecu> dobey: thanks for handling that.
[14:45] <dobey> sure
[14:48] <rsalveti> pmcgowan: $ ubuntu-device-flash query --device="mako" --list-channels
[14:48] <rsalveti> ubuntu-touch/devel-proposed (alias to ubuntu-touch/vivid-proposed)
[14:49] <rsalveti> sil2100: are you currently fixing that? ^
[14:49] <rsalveti> broke boot testing for proposed-migration
[14:50] <rsalveti> do we actually have any wily image?
[14:50] <rsalveti> we have the rootfs, but not sure if imported at system-image
[14:50] <ogra_> yes, it is
[14:50] <ogra_> oh, wily ... no, not yet afaik
[14:51] <pmcgowan> rsalveti, yeah the channels are all borked
[14:51] <pmcgowan> I think its a holiday or something
[14:51] <rsalveti> pmcgowan: who is fixing that?
[14:51] <pmcgowan> cant find anyone to do it
[14:51] <ogra_> sil2100 ... once he is back from the vet i guess
[14:51] <rsalveti> would guess sil2100 / slangasek
[14:51] <pmcgowan> slangasek, not here yet
[14:54] <ogra_> well, you will need to fix capomastor at the very same time too
[14:54] <ogra_> ...
[14:55] <rsalveti> that as well, yeah
[14:56] <rsalveti> and they just renamed the channels
[14:56] <rsalveti> and fix the krillin en->es issue as well
[14:56] <rsalveti> all sorts of issues
[15:03] <alex-abreu> trainguards can you reconfigure silo 32
[15:13] <robru> alex-abreu: bah, train won't let me reconfigure from vivid->wily, will free & reassign
[15:14] <alex-abreu> robru, thx
[15:15] <robru> alex-abreu: you're welcome, silo 26 now
[15:15] <davmor2> ogra_, rsalveti: current krillin image has a wily rootfs
[15:21] <rsalveti> davmor2: haha, who knows why
[15:26] <sil2100> Back :|
[15:26] <sil2100> Took a while
[15:27] <sil2100> What's up with channels?
[15:28] <rsalveti> sil2100: all br0ken :-)
[15:28] <sil2100> Defnie that please ;p
[15:29] <rsalveti> sil2100: no wily channel, devel-proposed still pointing out to vivid (breaking proposed-migration boot testing)
[15:29] <rsalveti> sil2100: and it seems ubuntu-touch/devel-proposed/krillin.en got a wily rootfs, not sure how
[15:29] <rsalveti> besides the krillin.en->krillin.es issue that slangasek is already working on a fix
[15:30] <sil2100> hm, ok, none of these seem to be related to my recent changes at least
[15:31] <sil2100> Well, I switched vivid-proposed to use vivid a few days ago, but that shouldn't be related
[15:31] <sil2100> Although devel-proposed was an alias to vivid-proposed
[15:31] <rsalveti> right
[15:31] <rsalveti> guess we first need to create wily channels
[15:31] <rsalveti> and then sort out the aliases
[15:32] <rsalveti> we had so many emails with suggestions and so on that I don't know anymore what is the desired layout
[15:33] <ogra_> well, as i understood slangasek he doesnt want a wily channel
[15:33] <ogra_> but to import directly inot devel-proposed
[15:33] <ogra_> *into
[15:33] <ogra_> and vivid would become stable-proposed or some such
[15:34] <ogra_> in any case please tell me about the final outcome so i can adjust the bot and changelog creation tools
[15:36] <ogra_> sil2100, oh, and publich holiday here, i wont be at the meeting ...
[15:39] <rvr> boiko: Silo 24 approved.
[15:39] <kenvandine> is anyone looking into the autopilot failures blocking promotion from wily-proposed to wily?
[15:40] <kenvandine> specifically ubuntu-system-settings-online-accounts, which is also blocking system-settings
[15:40] <kenvandine> looks like it should be affecting more
[15:40] <kenvandine> FileNotFoundError: [Errno 2] No such file or directory: '/sbin/initctl'
[15:40] <kenvandine> from autopilot
[15:42] <kenvandine> trainguards: ^^
[15:42] <robru> kenvandine: hm?
[15:43] <kenvandine> that test has been failing all week
[15:43] <kenvandine> keeping packages stuck in proposed
[15:43] <ogra_> kenvandine, i think you wanted cihelp :)
[15:43] <kenvandine> maybe :)
[15:43] <kenvandine> but this isn't CI, it's really landing right?
[15:43] <ogra_> is it ?
[15:44] <Ursinha> kenvandine: landing == citrain, proposed-migration is after that
[15:44] <robru> kenvandine: train-guards have nothing to do with proposed migration.
[15:44] <rvr> Can someone review this merge proposal? Silo is blocked because nobody reviewed and approved it https://code.launchpad.net/~jhodapp/media-hub/fix-1451816/+merge/258805
[15:45] <rsalveti> ogra_: yeah, don't mind not having a dedicated channel for it, as long we have one :-)
[15:45] <kenvandine> Mirv had been kicking the build, i guess i'll bug someone else then :)
[15:45] <kenvandine> it looks like any of our packages that run autopilot tests as autopkgtests are going to be broken in wily
[15:46] <kenvandine> holding up all our landings :/
[15:46] <ogra_> rsalveti, yeah, same here ... i might even have misunderstood slangasek ... as long as i know the final setup for the tools to point to i'm fine though :)
[15:46] <fginther> kenvandine, you are referring to this? https://jenkins.qa.ubuntu.com/job/wily-adt-ubuntu-system-settings-online-accounts/lastBuild/
[15:46] <kenvandine> yes
[15:46] <jhodapp> rsalveti, I know I asked you to do the review on that MR that rvr mentioned above, do you have time or should I get someone else?
[15:46] <fginther> Ursinha, this is proposed-migration
[15:47] <Ursinha> fginther: I know
[15:47] <kenvandine> fginther, looks like that should effect quite a few of our packages
[15:47] <ogra_> kenvandine, a few, yeah http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[15:47] <kenvandine> yup... i was looking at that
[15:47] <fginther> Ursinha, sorry, I misread your last msg
[15:48] <kenvandine> makes me wonder if autopilot or uitk is broken on wily?
[15:48] <Ursinha> kenvandine: I'm aware of the QA team working on sorting out autopilot issues, hi elopio :)
[15:49] <elopio> sorry, what?
[15:49] <kenvandine> http://d-jenkins.ubuntu-ci:8080/job/wily-adt-ubuntu-system-settings-online-accounts/ARCH=amd64,label=adt/12/console
[15:49] <kenvandine> elopio, is autopilot working on wily?
[15:49] <Ursinha> kenvandine: we are working on sorting the boottesting issues, the autopilot issues it's better talk to the QA team directly I'd think
[15:50] <kenvandine> it's blocking my wily landing, which is blocking me syncing to vivid overlay ppa :/
[15:51] <elopio> FileNotFoundError: [Errno 2] No such file or directory: '/sbin/initctl'
[15:51] <kenvandine> elopio, i'm trying to land those autopilot fixes in settings :)  bug the failing autopkgtests for uss-uo is blocking the proposed migration :(
[15:51] <kenvandine> s/bug/but/
[15:51] <elopio> why wily wouldn't have /sbin/initcl ?
[15:51] <ogra_> why would it ?
[15:52] <ogra_> systemd doesnt use it ;)
[15:52] <fginther> Ursinha, kenvandine, this may actually be the ubuntu-ui-toolkit, it's the one referencing /sbin/initctl: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/tests/autopilot/ubuntuuitoolkit/environment.py
[15:52] <fginther> elopio, systemd instead of upstart
[15:52] <elopio> ok, that's a big change.
[15:52] <fginther> oh, ogra_ beat me to it
[15:52] <ogra_> :)
[15:52] <elopio> the unity scripts use it, and the toolkit scripts do.
[15:52] <kenvandine> right
[15:53] <kenvandine> which is going to break everything
[15:53] <elopio> *everything*
[15:53] <ogra_> which was one reason to not have wily phone images ;)
[15:53] <Ursinha> so everything is actually broken
[15:53] <kenvandine> robru, i screwed up silo 20.... asked for help earlier but nobody was around
[15:53] <kenvandine> i tried to sync from wily-proposed :)
[15:53] <kenvandine> now it doesn't let me reconfigure it back
[15:54] <kenvandine> Ursinha, right.... so we are going to have a ton of proposed migration issues
[15:54] <rsalveti> jhodapp: I partially tested it, will finish today
[15:54] <rsalveti> sorry for the delay
[15:54] <jhodapp> rsalveti, awesome thanks! rvr^
[15:54] <Ursinha> slangasek: sil2100, we have to do something urgent :) communication is all mixed up and now no one knows where to land things for what and why
[15:54] <elopio> so, any pointers at how systemd handles env vars?
[15:54] <jhodapp> rsalveti, np man, I know you're very busy atm
[15:55] <ogra_> elopio, https://wiki.ubuntu.com/SystemdForUpstartUsers ?
[15:55] <rsalveti> ogra_: did we already switch to systemd at wily?
[15:55] <rsalveti> for touch?
[15:55] <elopio> ogra_: thanks.
[15:55] <ogra_> rsalveti, nope ... but not sure how touch plays into proposed migration here
[15:55] <rsalveti> ogra_: right, proposed-migration just needs a wily image
[15:55] <ogra_> rsalveti, i rather think it isnt involved, is it ?
[15:56] <ogra_> yeah
[15:56] <rsalveti> that's the main issue atm
[15:56] <elopio> bzoltan: you around? Can we do a quick toolkit release for wily after I add a check for systemd?
[15:56] <elopio> I doubt the part of /quick toolkit release/.
[15:56] <ogra_> huh ?
[15:57] <ogra_> that should be empty since ages
[15:57] <robru> ogra_: ugh, race condition, should be fine to try that again...
[15:57] <ogra_> robru, that was thrown out weeks ago :)
[15:57] <robru> ogra_: well nobody freed the silo, it's been sitting htere dirty
[15:57] <ogra_> oh ?
[15:58] <robru> ogra_: ppa even still has your packages in it
[15:58] <ogra_> i'm pretty sure i saw the bot tell me it is empty after either rsalveti or sil2100 cleaned it
[15:58] <ogra_> weird
[15:58] <ogra_> probably i'm mixing it up with another sillo
[15:58] <robru> ogra_: I can free it if you no longer want it then
[15:58] <rsalveti> maybe it got created again after the ss issues we had
[15:58] <ogra_> yeah, throw it out
[15:58] <rsalveti> who knows
[15:58] <ogra_> yeah
[15:59] <robru> rsalveti: nope, because it had ogra_'s manual uploads in the PPA. that's not something we'd accidentally recreate.
[15:59] <kenvandine> trainguards, do i need QA verification for autopilot fixes only?
[16:00] <robru> kenvandine: I guess not? definitely not for wily
[16:00] <kenvandine> for vivid?
[16:00] <kenvandine> QA did a review of the branch
[16:00] <robru> kenvandine: ehhh. officially all vivid landings would require qa.
[16:00] <rsalveti> robru: then maybe we ended up cleaning another silo instead
[16:00] <kenvandine> okie dokie
[16:00] <rsalveti> haha
[16:00] <robru> kenvandine: better ask qa for an exemption ;-)
[16:01] <robru> kenvandine: also I freed 20. try again, but with 'wily' instead of 'wily-proposed'
[16:01] <kenvandine> i'd think they would be happy just seeing the results of the ci test run
[16:02] <kenvandine> robru, well i can't because of the busted uitk/autopilot in wily... blocking proposed migration
[16:02] <kenvandine> robru, so i think i'm going to land those branches for vivid instead, basically a dual landing :)
[16:02] <robru> kenvandine: ok
[16:13] <slangasek> Ursinha: why do people not know where to land things?  Didn't sil2100 already address this in his mail?
[16:15] <Ursinha> slangasek: there is confusion about what series are things based/pointing to so people can expect things to pass or fail
[16:16] <slangasek> ok, didn't I already address that in /my/ mail?
[16:17] <slangasek> sorry if this comes across poorly, but in my other ear I have QA telling me that there are bugs in the actual configuration of the channel vis-a-vis what's supposed to be there, so I'm urgently working on fixing /that/
[16:17] <Ursinha> slangasek: I'm not saying you haven't done that, but there is still confusion and I'm not sure why, maybe it needs more clarification
[16:18] <Ursinha> slangasek: sure, most urgent things first :)
[16:19] <slangasek> cwayne: hi, can you confirm that this is the correct url that we should use for the custom tarball on the ubuntu-touch/rc-proposed/bq-aquaris.en channel, now that this channel is updated to point to vivid? http://s-jenkins.ubuntu-ci:8080/view/cambridge/job/BQ Tarball Vivid - Gated/lastSuccessfulBuild/artifact/custom.tar.xz
[16:19] <slangasek> (as opposed to the previous URL, http://s-jenkins.ubuntu-ci:8080/view/cambridge/job/BQ International Tarball - Gated/lastSuccessfulBuild/artifact/custom.tar.xz)
[16:21] <bzoltan> elopio: sure we can, it can be as quick as normally ... full testing :) ~16 hours
[16:21] <bzoltan> elopio:  sorry for the reaction time ... today was holiday in most European countries
[16:22] <elopio> bzoltan: that's what I thought :)
[16:22] <elopio> ok, I'll get running to see if we can get it released tomorrow.
[16:22] <bzoltan> elopio:  btw, how is your travel arrangements?
[16:22] <elopio> I'll look for teammates to help testing.
[16:23] <elopio> bzoltan: I have updated the details in the spreadsheet already.
[16:23] <bzoltan> elopio:  OK
[16:23] <bzoltan> elopio:  we had massive fights to push the version separation refactoring to the staging...
[16:23] <bzoltan> elopio:  I have tested pretty much all apps and run all the AP tests and have not seen any problems
[16:24] <bzoltan> elopio:  so in my view the staging is good to go
[16:24] <bzoltan> elopio:  but tomorrow I will kick off a real testing ... I donot start it today because my wife would simple kill me
[16:24] <cwayne> slangasek, confirmed.
[16:24] <slangasek> cwayne: great, thanks
[16:24] <slangasek> cwayne: should I expect a different url for wily, or will we continue to use the vivid tarballs for now?
[16:25] <boiko> rvr: great! thanks a lot!
[16:25] <elopio> bzoltan: of course. Tomorrow is good. I'll make the smallest change possible, with tests to make sure I do not disturb anything existing.
[16:25] <cwayne> slangasek, *eventually* i assume there will be a wily one, but not quite yet
[16:25] <slangasek> cwayne: check
[16:26] <bzoltan> elopio:  and of course the Jenkins tests are acting up ... crap it is
[16:37] <robru> bfiller: need MPs, not branches
[16:38] <bfiller> robru: crap, let me fix
[16:40] <bfiller> robru: fixed
[16:45] <robru> bfiller: ok, silo 20
[16:52] <cyphermox> cihelp: could someone please take a look at the mark-pending-current job? It seems it hasn't been able to complete its task for a little while
[16:55] <plars> cyphermox: looks like it could be some firewall issue, I'll check it out
[16:58] <psivaa> plars: cyphermox if this is related to desktop, then we have a failure in the desktop default tests,
[16:58] <cyphermox> there are two things, yes
[16:58] <cyphermox> there is possibly an issue with the desktop tests, but there is also a firewall issue
[16:58] <plars> psivaa: right, but even when it's supposed to mark the images current it can't: see http://d-jenkins.ubuntu-ci:8080/job/mark-pending-current/2569/console
[16:58] <plars> psivaa: I'm filing an RT for it now
[16:59] <psivaa> plars: thanks
[17:01] <cyphermox> plars: psivaa: thanks!
[17:17] <elopio> cihelp, kenvandine: would it be to bad to wait until monday for my branch with systemd support to land, to check with pitti that the fix makes sense?
[17:19] <kenvandine> i went ahead and created a landing for vivid instead
[17:19] <kenvandine> so it won't hold me up to much
[17:19] <kenvandine> elopio, but this will affect others too...
[17:19] <elopio> kenvandine: ok. Sorry about that.
[17:19] <kenvandine> np
[17:19] <elopio> yes, I'll make the branch now.
[17:19] <kenvandine> it was bound to happen :)
[17:19] <kenvandine> well, i was sure the switch to wily wouldn't be smooth :)
[17:19] <elopio> but without somebody who knows about systemd, I'm afraid of making something stupid.
[17:20] <kenvandine> elopio, understood
[17:20] <elopio> for example, I have no idea what happens with the --global flag when setting variables.
[17:21] <kenvandine> ogra_, do you know enough about systemd to review elopio's branch?
[17:28] <dobey> hmm
[18:13] <slangasek> ok; is there anybody about who has a phone provisioned with ubuntu-touch/devel-proposed who could help me with a test?  maybe rsalveti or davmor2?
[18:16] <rsalveti> slangasek: can flash one, give me a minute
[18:20] <om26er> plars, Hi!
[18:20] <om26er> plars, where can I see smoke testing results for arale ?
[18:21] <plars> om26er: you can't yet, hopefully soon - we just got access to the system-image server, and there was the channel name change, and some other issues blocking it. Also when we have results, they won't look sensible because there's some bug with autopilot and also the version string is wrong still
[18:21] <plars> om26er: I hope to have *something* visible today though
[18:21] <om26er> plars, thanks, looking forward
[18:30] <rsalveti> slangasek: alright, what do you need?
[18:30] <rsalveti> current build number: 197
[18:30] <rsalveti> device name: mako
[18:30] <rsalveti> channel: ubuntu-touch/devel-proposed
[18:30] <rsalveti> alias: ubuntu-touch/vivid-proposed
[18:35] <slangasek> rsalveti: ok - I'm still waiting for the importer to run, but hopefully I'll be switching you painlessly to ubuntu-touch/devel-proposed/ubuntu without a full update
[18:37] <jhodapp> robru, om26er why did https://code.launchpad.net/~jhodapp/qtubuntu-media/fix-1438115 get published?
[18:38] <jhodapp> I'm still working on the fix :)
[18:38] <om26er> jhodapp, ouch, a new card appeared there, I was able to verify the fix as well
[18:39] <jhodapp> om26er, yeah it was mostly fixed but certain albums still caused the right timing to break it on Arale
[18:39] <jhodapp> om26er, it's fine...what is there is an improvement for sure...I'll do another MR and silo for the last fix
[18:40] <om26er> jhodapp, ok, makes sense.
[18:40] <jhodapp> om26er, no big deal, just wanted to see what happened...surprised me to get an email saying it was merged :)
[18:58] <slangasek> rsalveti: ok, could you please try a system-image update from the commandline and see what happens?  (probably nothing, no new images available yet)
[18:59] <rsalveti> [systemimage] May 14 18:59:37 2015 (4446) Already up-to-date
[18:59] <rsalveti> yeah
[18:59] <rsalveti> slangasek: ^
[19:01] <slangasek> rsalveti: ok, keen
[19:02] <slangasek> rsalveti: now let me see what happens if we put a new image onto that channel.  Can you keep this device as-is for an hour or two while I do this?
[19:03] <rsalveti> slangasek: yup
[19:29] <robru> jhodapp: yeah i hit publish because QA said it was good. Not sure who submitted it to qa though
[19:36] <jhodapp> robru, ok thanks
[19:46] <slangasek> rsalveti: ok, check again please?
[19:48] <rsalveti> slangasek: http://paste.ubuntu.com/11135337/ seems to be all good
[19:49] <slangasek> rsalveti: and your channel.ini after update?
[19:50] <rsalveti> slangasek:
[19:50] <rsalveti> http://paste.ubuntu.com/11135352/
[19:50] <slangasek>  rsalveti groovy, thanks!
[19:51] <rsalveti> np
[21:51] <jhodapp> robru, can I please get a silo for line 68?
[21:52] <jhodapp> robru, also, I want it synced to wily as well...anything I need to do manually?
[22:22] <robru> jhodapp: sorry for the delay, my IRC client isn't pinging me today for some reason
[22:22] <robru> jhodapp: so I guess the policy that everybody agreed on is that you have to land to wily first and then sync back to vivid, overlay ppa is the new RTM.