[02:05] <imgbot> [02:46] <robru> rsalveti: hah, I hit publish just after you. no harm done though
[02:46] <rsalveti> haha, alright
[03:30] <imgbot> [03:30] <imgbot> [03:47] <bfiller> robru: something broken with publishing of rtm 20, looks like trying to publish an older version of libsynthesis than what is in the ppa
[03:48] <robru> bfiller: hm, no it published fine, just the thing monitoring the publication is confused about the versions...
[03:49] <bfiller> robru: ah ok, was just worried cause I saw that message on the dashboard
[03:49] <robru> bfiller: yeah, didn't notice it until you mentioned it. but if you check https://launchpad.net/ubuntu-rtm/+source/libsynthesis it has the right version. I'll merge the silo then.
[03:50] <bfiller> robru: cool, thanks
[03:50] <robru> bfiller: you're welcome!
[04:10] <bzoltan_> robru:  May I get a silo for the 82 line?
[04:11] <robru> bzoltan_: silo 8
[04:12] <bzoltan_> robru:  sweet, thank you
[04:12] <robru> bzoltan_: you're welcome
[11:04] <john-mcaleely> ogra_, you around? I assume I'm good to push a *vivid* device tarball in the next 30 mins or so, machinery wise?
[11:14] <rsalveti> john-mcaleely: omg, system-image finally built: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-008
[11:14] <rsalveti> after more than 10 times trying to rebuild it in 3 different ppas
[11:16] <john-mcaleely> rsalveti, something's odd, because the dashboard reports it as 'silo ready to build'
[11:16] <rsalveti> john-mcaleely: that's fine, it's just not in sync yet
[11:16] <rsalveti> doing that now
[11:16] <john-mcaleely> although when I looked at the console this morning, it seemed to be fine
[11:16] <rsalveti> because I used dput manually
[11:16] <john-mcaleely> aha
[11:16] <rsalveti> so doing a watch-only build now
[11:17] <john-mcaleely> so I'll push a vivid tarball with the updates in it shortly
[11:17] <rsalveti> it's only in sync when building from MRs
[11:17] <rsalveti> great
[11:17] <john-mcaleely> (just doing the normal QA on it now)
[11:17] <rsalveti> crap, the list of packages are wrong
[11:17] <rsalveti> maybe the syntax changed
[11:19] <rsalveti> should be fine now
[11:27] <rsalveti> john-mcaleely: alright, published for rtm, green light for the new device tarball and new custom
[11:27] <rsalveti> then on monday we can coordinate the landings on the new distro that was created for the hotfix (new series)
[11:27] <john-mcaleely> rsalveti, great thanks.
[11:27] <john-mcaleely> rsalveti, yeah, makes sense
[11:28] <john-mcaleely> device tarball will be same for new-distro and & rtm - there's only been this change
[11:28] <john-mcaleely> will tee it up for rtm shortly.
[11:29] <rsalveti> great
[11:32] <john-mcaleely> http://people.canonical.com/~jhm/barajas/master/device_krillin-20150207-e081aea.tar.xz
[11:32] <john-mcaleely> http://people.canonical.com/~jhm/barajas/master/device_krillin-20150207-e081aea.changes
[11:33] <john-mcaleely> http://people.canonical.com/~jhm/barajas/master/device_krillin-testresults-20150207-e081aea.ods
[11:33]  * rsalveti going away, beach time
[11:33] <rsalveti> later
[11:33] <john-mcaleely> new krillin vivid device tarball ^
[11:33] <john-mcaleely> later!
[11:34] <john-mcaleely> now pushed. I expect it will land in #102
[11:36] <john-mcaleely> uh oh?
[12:30] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20150207-49c0dd8.tar.xz
[12:30] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-20150207-49c0dd8.changes
[12:31] <john-mcaleely> http://people.canonical.com/~jhm/barajas/ubuntu-rtm-14.09/device_krillin-testresults-20150207-49c0dd8.ods
[12:31] <john-mcaleely> sil2100, ricmm rsalveti ^ device tarball to go with -008. I don't think the landing order matters
[12:31] <john-mcaleely> will wait for a +1 from QA before pushing
[13:03] <cjwatson> fwiw it's a new distroseries not a new distro
[13:03] <cjwatson> ubuntu-rtm/14.09-factory
[13:04] <cjwatson> still part of rtm
[13:39] <john-mcaleely> thanks!
[15:57] <jgdx> I can't really install rtm silo 7
[15:57] <jgdx> the packages are available, but wont install
[18:57] <bzoltan_> Validating the UITK for Vivid is pain.. like pure pain. The device goes to reboot loop 3-4 times during the test sequence... the flashing tool fails randomly, the network manager is unstable. It is super hard on Vivid.
[21:25] <imgbot> [21:25] <imgbot> [23:33] <john-mcaleely> aha