dobeyfginther: hey. looks like lp:ubuntuone-credentials/rtm-14.09 is building on vivid? can you change it to build on rtm?00:27
dobeywell, i need to go. later00:41
ToyKeepermandel: You around?  The pause-click-updates silo passed, but there's still a remaining bug in that UI flow...  sometimes the "Update" button goes directly to "Resume" instead of "Pause".  This happened before the silo though, so the silo can still land.00:46
ToyKeeper(tap "Update", progress bar starts to move, button label changes to "Resume"...  tap it, the label changes to "Pause", and then afterward everything works as intended)00:47
mandelToyKeeper, I am indeed around, yes, I did notice that without the silo too, very ugly indeed... but I'll have to fix that in next iteration00:47
mandelToyKeeper, we need to re-do most of the logic there and did not want to add a huge delta so late00:48
robrudobey: building where? in a silo?00:48
ToyKeepermandel: Okay, just wanted to make sure you were aware of it.  :)00:48
mandelToyKeeper, yes, AFAIK ken knows too00:48
mandelToyKeeper, we are re-writting this little by little.. the last developer did a poor job00:49
ToyKeeperSorry it took so long; has been a very busy day so far.00:49
mandelToyKeeper, no problem, as long as it gets there :)00:49
mandelToyKeeper, is 2 am here, do you mind setting it to QA approved? I think that is the only thing left, right?00:50
* mandel is a little tired 00:50
ToyKeepermandel: Already done.  -queuebot/#ubuntu-ci-eng- trainguards, ubuntu-rtm/landing-019: Packages built. Testing pass. QA signed off. You can publish.00:50
mandelToyKeeper, thx! Then I'm off to bed00:50
robrumandel: yep, just hit publish on that00:51
mandelrobru, thx!00:51
robrumandel: you're welcome00:51
imgbot=== IMAGE 73 building (started: 20150122-02:10) ===02:10
fgintherdobey, oops, sorry about that. Fixed and retriggered the two MPs that had already executed02:18
imgbot=== IMAGE RTM 208 building (started: 20150122-03:10) ===03:10
imgbot=== IMAGE 73 DONE (finished: 20150122-03:30) ===03:30
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/73.changes ===03:31
imgbot=== IMAGE RTM 208 DONE (finished: 20150122-04:20) ===04:20
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/208.changes ===04:20
=== marcusto_ is now known as marcustomlinson_
=== marcustomlinson_ is now known as marcustomlinson
=== chihchun_afk is now known as chihchun
pstolowskitrainguards morning! can somebody review the packaging changes in silo 15?08:15
pstolowskitrainguards sorry, nvm. i've just been told this change is on hold atm08:15
=== Guest54456 is now known as Laney
seb128sil2100, hey, how are you?09:19
seb128sil2100, random question for you :-)09:20
seb128sil2100, is http://people.canonical.com/~lzemczak/landing-team/ubuntu-rtm/ generated manually? just wondering why it's at 205 when current image is 20809:20
sil2100seb128: hey! It's generated automatically on my machine currently, but I think I need to increase the sync period ;)09:24
sil2100seb128: should be all there now09:24
seb128sil2100, thanks09:25
seb128sil2100, just curious, why are some versions missing?09:25
sil2100seb128: this usually means that the given image is a result of a tarball upload09:25
seb128do we have the details about those tarball changes somewhere?09:26
sil2100For instance 206 was a new custom and 207 was a new device tarball09:26
ogra_there should be mails about them09:26
ogra_(not sure to which of the MLs )09:26
sil2100Sadly nowhere formalized... we and the testers usually get e-mails regarding the tarball changes09:26
sil2100ogra_: yeah, but for instance cwayne1 sends it to a CC list, not a ML09:27
sil2100Maybe we should think about changing that09:27
ogra_we definitely should09:27
brendandogra_, is there an easy way to reproduce the conditions for this? https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/138276709:35
ubot5Launchpad bug 1382767 in ubuntu-system-settings (Ubuntu RTM) "Bluetooth device with no name leads to details page with no header, no way to go back" [High,In progress]09:35
sil2100ogra_: just in case, meeting! ;) Not much for you though!09:36
ogra_brendand, i think the name detection was fixed at some point ...09:36
ogra_sil2100, ooops, sorry09:36
brendandogra_, hmmm, that makes it hard to verify :)09:36
sil2100satoris: once the thumbnailer migrates I'll assign the sync silo for you09:50
satorissil2100: ack, thanks.09:51
=== psivaa_ changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping psivaa | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: none
=== Elleo_ is now known as Elleo
sil2100satoris: as for silo rtm/14 - just make sure that after you build the packages that they're the ones that you expect it to be10:47
sil2100i.e. that it's the version from today10:47
satorissil2100: ack, will check.10:49
brendandmzanetti, hey - i'm trying to test silo 16 for RTM10:57
brendandmzanetti, it's supposed to reduce the time before sending SIGSTOP10:57
brendandmzanetti, but i have to say it still feels like 3 seconds with the silo installed10:57
bzoltan_ogra_:  the ubuntu-sdk-qmake-extras is landed so the https://code.launchpad.net/~bzoltan/ubuntu-seeds/qmake_enablers/+merge/247148 is now safe to land too11:14
brendandmzanetti, ping11:20
mzanettibrendand: hey11:21
mzanettiis it?11:22
mzanettilet me check11:22
brendandmzanetti, i tested using video playback in browser and a game (pathwind)11:22
mzanettimhm... reading the code it does set the timer to 1.5 secs11:23
mzanettibrendand: I'm installing the silo atm, to give it another try11:26
mzanettibrendand: hey, you sure you have installed the correct package?11:31
mzanettibrendand: seems the citrain tool fails to install the ppa11:31
brendandmzanetti, yeah11:31
brendandmzanetti, i just reflashed without the silo and it seems like it might be a bit quicker with the silo11:32
mzanettibrendand: I actually thought it was 5 secs before11:32
mzanettireading the code I see that the interval was changed from 3 to 1.511:33
brendandmzanetti, yeah it feels like 5 secs without and 3 secs with11:33
brendandmzanetti, maybe there's some overhead which makes it feel a bit longer in reality11:33
Chipacatrainguards, could i have a silo for row 64?11:33
mzanettiyeah, loading the greeter and lockscreen images for sure does take some resources11:33
mzanetti(those images are dropped from ram when not needed)11:34
sil2100Chipaca: on it11:34
Chipacasil2100: cheers11:34
Chipacasil2100: thanks11:36
=== barry` is now known as barry
=== MacSlow is now known as MacSlow|lunch
Chipacais there something wrong with the builders? the build is getting killed :(12:25
Chipacafatal error: unexpected signal during runtime execution12:26
Chipacathat's either something killing it explicitly, or possibly an OOM12:27
sil2100In the PPA?12:27
Chipacahttps://launchpadlibrarian.net/195549325/buildlog_ubuntu-vivid-i386.ubuntu-push_0.67%2B15.04.20150122.1-0ubuntu1_FAILEDTOBUILD.txt.gz fwiw12:28
Chipacathat's i386; arm and amd64 built ok12:28
Chipacaarmhf* :)12:28
cjwatsonChipaca: signal 0xb, that's SIGSEGV12:29
cjwatsonnot a builder problem12:29
Chipacacjwatson: what is it then?12:29
cjwatsonsegmentation fault12:30
brendandmzanetti, yeah so with the silo it's about 3 seconds and without about 4.5 seconds12:30
cjwatsoni.e. invalid memory access in your program12:30
Chipacacjwatson: yes, but why?12:30
brendandmzanetti, exactly 1.5 seconds difference12:30
cjwatsonyou get to debug it, have fun12:30
brendandmzanetti,  but quite difficult to tell apart without comparing side-by-side12:30
cjwatsonany number of reasons for segfaults12:30
mzanettibrendand: yep, I've counted that too12:30
brendandmzanetti, hardly seems worth it :)12:31
mzanettidunno... afaik there was a huge discussion about it12:31
mzanettiI wasn't part of it12:31
* Chipaca grumbles12:31
mzanettibrendand: in any case, this silo does more12:31
brendandmzanetti, i guess it can't be lowered too much or will cause some issues12:32
mzanettibrendand: the important part is to inhibit phone deep sleep while the app is "suspending" (not the -ing, not -ed)12:32
cjwatsonChipaca: since it would appear to be in malloc, perhaps native code somewhere has corrupted the malloc arena by way of a buffer overflow or similar.  valgrind may help12:32
mzanettinarf... I really should re-read stuff before I press enter :D12:32
mzanettibrendand: the important part is to inhibit phone deep sleep while the app is "suspending" (note the -ing, not -ed)12:32
mzanettiforgetting one "e" kinda changes the whole thing :)12:33
mzanettisil2100: please reconfig silo rtm/001, row 32 for me. We've added a telephony branch that should go together with the unity branch12:34
Chipacacjwatson: yeah ... but that's golang, not me, doing the malloc12:34
mzanettisil2100: I'll be syncing with boiko in order to queue telephony landings properly12:34
Chipacacjwatson: that is, it's not _my_ native code :)12:34
cjwatsonChipaca: I know, but this kind of fault can cause a crash distant from the cause12:34
Chipacacjwatson: and i've never seen it in testing here, hence why i suspected the builders12:35
cjwatsonChipaca: prior corruption in the malloc arena might only cause a crash somewhat later.  that's why you use valgrind12:35
cjwatsonChipaca: and it can be somewhat non-deterministic.  this is very unlikely to be a builder fault, you just need to look harder :)12:35
cjwatsonChipaca: I can assure you that we don't go around randomly SIGSEGVing stuff on builders for the fun of it12:36
cjwatsonand OOMs don't cause SIGSEGV12:36
* Chipaca looks into using valgrind with go12:36
cjwatson(well, not the OOM killer at any rate, of course if you get NULL back from malloc and fail to handle it then that could be a problem, but I doubt that's the case here; the builders have plenty of memory)12:36
Chipacacjwatson: yeah, i hadn't realised it was a sigsegv when i asked at start12:36
sil2100mzanetti: ok12:39
Chipacacjwatson: go doesn't play well with valgrind at all (dies with rt_sigaction nonesense)12:44
bzoltan_sil2100:  have you seen ogra_ today?12:54
ogra_bzoltan_, i'm working nearly fulltime on snappy nowadays, please be patient, i'll try to get to it before EOW12:55
sil2100bzoltan_: yes, he's here12:55
sil2100^ ;)12:55
bzoltan_ogra_:  No pressure :) I just need this package in the chroots very badly.12:56
ogra_well, any core-dev can help you12:56
Chipacasil2100: is there an easy way to try a rebuild of a package from vivid? getting a weird error, and realising it hasn't been rebuilt since some rather big changes elsewhere in the stack.12:56
=== alan_g is now known as alan_g|lunch
=== MacSlow|lunch is now known as MacSlow
sil2100Chipaca: you mean, like a no-change rebuild for one architecture?13:09
Chipacasil2100: changed the mp to a dummy one, reconfigured silo, forced rebuild worked for me. hope i'm not breaking anythign.13:09
Chipacasil2100: both 32 bit architectures actually13:10
Chipacathere might be a problem with go in vivid on 32 bits13:10
Chipacawe'll see13:10
Chipacathere also might be a bug in our code, but if so it's a nasty one13:10
sil2100In this case it should be ok if you just want to rebuild the existing package without any new changes ;)13:10
Chipacayeah, just to establish whether it's sane13:11
Chipacabefore i go digging :)13:11
Chipacaso, ubuntu-push FTBFS on 32-bit x86 (at least) on vivid13:18
Chipacaand now what?13:18
* Chipaca gives up and goes to live on a farm13:19
sil2100Chipaca: when was the last time ubuntu-push was built in vivid?13:20
Chipacasil2100: the day before golang 1.3 hit the archive13:20
sil2100We need to check which dependencies changed and trying to triage what could be wrong13:20
Chipacadecemebr 11th13:20
mzanettisil2100: I've approved that now ^. sorry, missed it before13:28
sil2100mzanetti: uugh, I see some problems with publishing, one moment13:30
mzanettierr, wat?13:30
sil2100Yeah... not sure what's wrong, need to dig deeper13:31
mzanettiok. let me know if I can help13:32
sil2100Ok, the train again ate a whole directory, and with the new publisher just a watch-only rebuild doesn't help13:42
sil2100And since I don't have access to the machine working around it would be the most painful thing ever13:42
sil2100So let me try pushing it to the archive manually13:42
sil2100Or wait, geh13:43
sil2100mzanetti: ok, let me do all the merges and releases manually, since the only other way would be to re-built both packages13:46
mzanettisil2100: did this break because of the not top-approved branch?13:47
sil2100mzanetti: no, I doubt it, not sure what happened - something in the backend went really wrong13:47
sil2100Ah, I think I see the possible problem ;/13:50
sil2100mzanetti: so, it seems it wasn't the backend that broke it - you did a build once and aborted it half way when it was preparing the package, which is really really dangerous13:51
sil2100mzanetti: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-016-1-build/75/console13:51
sil2100mzanetti: in this place it started branching the bzr qtmir branch but couldn't finish since it was aborted, and CI Train completely lost track of its state here13:52
mzanettiyes, I did that, I clicked build and noticed I forgot to reconfig first13:52
mzanettiok, will be more careful with that13:52
sil2100mzanetti: you should only abort the build job when the packages are created and pushed to the PPA, when it's waiting on them to finish building13:52
sil2100Since we can't make sure that we can abort at any place sadly ;)13:53
sil2100Ok, anyway, let me try doing stuff manually13:53
=== alan_g|lunch is now known as alan_g
popeycihelp: http://s-jenkins.ubuntu-ci:8080/job/calendar-app-click/ seems to build two clicks each time a merge lands. which is wrong/odd.14:02
oSoMoNtrainguards: can I have a silo for line 68, please?14:06
sil2100oSoMoN: sure! At lunch now, but let me try quicky assigning14:07
oSoMoNsil2100, no rush, have your lunch first!14:07
fgintherpopey, looking14:08
=== psivaa_ changed the topic of #ubuntu-ci-eng to: Need a silo or CI Train support? ping trainguards | Need help with something else? ping cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: none
popeyfginther: thanks14:20
fgintherpopey, it's fixed now. There was an older .click left in an old build directory. It just needed a proper cleanup.14:22
popeyhaha, ok :)14:22
Chipacasil2100: could you switch that silo over to rtm? i'd like to test this build against the rtm build deps14:36
Chipacasil2100: this is a test build, not something for any archive14:36
sil2100Chipaca: let me get you another test silo then14:39
sil2100Since switching to rtm would mean I would have to free this one up and assign a new one14:39
sil2100Chipaca: ok, created a new row - the other rtm row you have let's leave for the right RTM release14:41
kenvandinersalveti, what's up with silo 18, the bluetooth agent stuff?14:44
Chipacasil2100: thanks14:46
kgunnfginther: i feel bad bothering you again...but we are seeing between 50% and 100% of building before failing for reasons unrelated to build or tests14:47
kgunne.g. http://jenkins.qa.ubuntu.com/job/mir-clang-vivid-amd64-build/1007/console14:48
kgunnfailures on cloud-worker-10 and cloud-worker-1114:48
kenvandinersalveti, i have other branches to land, can i pass by your's ?14:49
kgunnev: just a heads up i'm pestering francis again ^14:50
evkgunn: cihelp is preferable. We don't have a vanguard in this slot today because Ursula is on holibobs14:51
fgintherkgunn, I or someone from the team will have a look shortly. I didn't specifically make any modifications for mir-clang-vivid-amd64-build yesterday, but will have a closer look at this and the other mir jobs today15:03
kenvandinebrendand, why is silo 4 blocked?  do you need anything from jgdx or I?15:07
brendandkenvandine, there seems to be an issue with the manual operator selection15:08
brendandkenvandine, jgdx is looking at it15:08
kenvandinebrendand, ok, thanks15:08
kenvandineas long as someone is on it ;)15:08
ricmmsil2100: could I get a silo for ^15:35
sil2100ricmm: sure!15:35
sil2100ricmm: assigning, but it seems lool has platform-api also in silo 22 already15:36
oSoMoNtrainguards: can silo 14 be published, please?15:39
ricmmsil2100: thank you15:43
sil2100oSoMoN: sure, one moment!15:43
sil2100mzanetti: ok, all bits landed manually - apologies if there are any mistakes15:44
mzanettisil2100: ack, will check. thanks a lot15:44
sil2100mzanetti: I already noticed a small typo in my commit-message, but I would call that a no-issue ;p15:45
sil2100(sorry about that)15:45
sil2100kenvandine: eek!15:51
sil2100kenvandine: you need to rebuild silo 29 it seems15:51
sil2100kenvandine: someone released something in the meantime from what CI Train says15:51
mzanettisil2100: don't worry about that :D15:51
* kenvandine wonders how that could happen15:51
kenvandinesil2100, where does it say that?15:52
sil2100kenvandine: ^15:52
kenvandinesil2100, it uploaded fine15:52
sil2100kenvandine: ok! I know what happened!15:52
sil2100kenvandine: I pushed publish after you published the silo yourself ;)15:52
sil2100kenvandine: sorry, forgot that you do all your publishing yourself!15:53
kenvandineyeah... sorry :)15:53
kenvandinei wish that status updated quicker...15:53
sil2100kenvandine: anyway, nevermind me ;p Apologies from my side, simply forgot about this!15:53
kenvandinefortunately no harm can be done there :)15:53
kenvandinersalveti, i'll rebuild 18 after this is merged15:54
kenvandinersalveti, i went ahead and passed you :)15:54
=== mvo_ is now known as mvo
loolsil2100: ah thanks for the reminder, I'll push this16:01
=== chihchun is now known as chihchun_afk
brendandkenvandine, do you know a way to test https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1383732 ?16:15
ubot5Launchpad bug 1383732 in Canonical System Image "E-book content type" [Undecided,In progress]16:15
kenvandinebfiller, ^^ mind passing on what Elleo gave you to brendand?16:17
bfillerbrendand: it's in the test plan for content-hub, linked in the sheet16:17
kenvandineeven better :)16:18
dbarth_ogra_: hey, do you have time to seed that apparmor extension today?16:31
rpadovanicihelp : I need to switch the development focus of calculator to another branch, what steps are required to keep jenkins working?16:33
fgintherrpadovani, we usually just need to know the branch name16:34
rpadovanifginther, lp:ubuntu-calculator-app: the actual focus is on trunk, we want to switch to reboot (lp:ubuntu-calculator-app/reboot)16:35
fgintherrpadovani, that should be all we need, someone should be able to get this setup today16:38
rpadovanifginther, that's cool, thanks! Will you take care to change it on LP too or will you ping me and I'll change it?16:39
fgintherrpadovani, hold on16:39
fgintherrpadovani, switching branches around in LP is the project maintainer's responsibility... but it sounds like you want to completely switch lp:ubuntu-calculator-app to point to the reboot branch?16:40
fgintherrpadovani, yes, it looks like I missunderstood16:42
rpadovanifginther, yes, isn't this what happen when you change the development focus on lp?16:42
rpadovanifginther, my only worry is about jenkins, it will need to take from lp:ubuntu-calculator-app and not lp:ubuntu-calculator-app/reboot anynore16:42
fgintherrpadovani, sorry about that. Yes, in this case, we just need to disable the jobs that look at the reboot branch16:43
rpadovanifginther, ok, great, so could I go or do I wait your ping?16:49
mzanettitrainguards: row 74 would be ready for a silo, but not in a hurry with it. so whenever some of you has some free minute16:50
fgintherrpadovani, it's safe to switch now. I've disable the jobs so as not to result in double builds16:51
sil2100mzanetti: o/16:52
mzanettithanks :)16:53
rpadovanifginther, thanks, done!16:54
brendandbfiller, thanks for silo 216:59
fgintherkgunn, I've also moved the mir-clang and mir-android builds to the larger nodes. The clang job appeared to be hitting resource limitations17:03
kgunnalan_g: camako ^ fyi17:03
fgintherkgunn, will keep monitoring those larger nodes to make sure there is enough to go around17:03
alan_gfginther: thanks17:05
Chipacasil2100: I'm done with silo ubuntu-rtm/landing-015, thank you17:16
sil2100Chipaca: excellent, let me free it up17:19
Chipacaconfirmed the FTBFS is vivid-only, fwiw17:19
Chipacasil2100: also if you want to clean up landing-016 (from row 64), i'm not going to use it17:30
Chipacatrainguards, could i have a silo for row 64 please?17:36
Chipacasil2100: hi. I meant row 65; 64 is the one to nuke :)17:36
Chipacabecause, ftbfs on vivid :(17:36
sil2100Chipaca: hmmm, but we'll have to get this somehow to vivid anyway...17:37
Chipacasil2100: yes, of course17:37
sil2100One moment please, still OTP17:37
Chipacasil2100: but for that we need to determine what in all that's changed in vivid has triggered the FTBFS (biggest candidate being golang 1.3)17:37
sil2100robru: ping!17:51
sil2100Chipaca: anyway, I'll leave this vivid silo assigned so that we don't forget that it needs to land for vivid as well17:52
Chipacasil2100: ok ... i won't forget though, because it's already on our automatically-tested development "trunk", and that's all that gets pushed to vivid17:52
Chipacasil2100: so as you wish. If you run short of silos, nuke it :)17:53
sil2100Chipaca: yeah, let me leave a comment on that one ;)17:54
sergiusenssil2100: can I sync a package from vivid-proposed?18:04
sil2100sergiusens: that's a good question - sadly I think not but let me do a quick check since I think we're copying it from the release pocket directly18:06
sergiusenssil2100: can you do a manual dput to a silo then?18:06
sergiusenssil2100: my problem is similar to Chipaca's but different, as I'm using gcc-go18:06
sergiusenssil2100: and the new gcc-go requires me to make packaging changes that will be bad for ubuntu-rtm as it doesn't have the latest gcc-go18:07
sergiusenssil2100: oh well, I guess I can setup an rtm branch too18:07
sil2100sergiusens: yeah, if I confirm it cannot be done I'll do that for you then, will keep you updated18:07
sil2100But an rtm branch might be a better solution in case this is a long-standing problem18:08
sergiusenssil2100: I don't expect ubuntu-rtm to survive that long :-P18:08
sil2100hah ;)18:08
sergiusenssil2100: empty MP commits work fine still, right?18:08
sil2100sergiusens: yeah18:09
sergiusenssil2100: ok, I'll give that a go18:09
sil2100sergiusens: huh, it seems that it should be possible to do a sync from proposed18:23
sergiusenssil2100: hah, I just got the above setup18:23
sergiusenssil2100: line 58; but we can try do the sync18:24
sil2100sergiusens: CI Train just uses getPublishedSources() without specifying the pocket argument, and in this case LP just returns everything18:24
sil2100I don't have 100% guarantee, but it should just work since that's the only thing I see18:24
sergiusenssil2100: oh, needs code changes?18:24
sergiusenssil2100: then lets not experiment today :-)18:24
sil2100No no, should just work ;)18:24
sergiusenssil2100: oh, what's the syntax?18:24
sil2100Just saying that I can't say for 100%18:24
sergiusenssil2100: I already have everything staged the other way around, so it's easy to revert18:25
sil2100Try simply writing in the source package name list: 'sync:ubuntu,vivid the_package_name' (nuntium I suppose?)18:25
sergiusenssil2100: let's give it a try18:25
sil2100And at least we'll know for sure if this works ;)18:25
sergiusenssil2100: yup, nuntium, and it will sync from proposed? crazy :-)18:25
sil2100Yeah ;p I think no one thought about the case that something might be stuck in proposed ;)18:25
sergiusenssil2100: if you want to setup line 58 we will know :-)18:26
sil2100sergiusens: assigning, let's hope it works - at least there would be less additional work for everyone18:26
sil2100At least for now18:26
sil2100bfiller: could you top-approve https://code.launchpad.net/~renatofilho/address-book-app/fix-1411323-rtm/+merge/247142 ?18:27
bfillersil2100: done18:28
sergiusenssil2100: at least it picked the right one :-)18:29
sil2100sergiusens: oh, so it works? ;)18:30
sil2100bfiller: thanks!18:30
sergiusenssil2100: I'll need to sync in a package dep (build time only)18:40
sil2100sergiusens: ah, missing from the rtm archive? Or need a different version?18:41
sergiusenssil2100: missing from the rtm archive18:41
sil2100sergiusens: ok, wait, what package do you need? We'll just copy it over18:41
sergiusenssil2100: golang-go-flags-dev18:41
jhodapprobru, can you please land vivid silo 1?18:44
sil2100jhodapp: publishing o/18:44
jhodappthanks sil210018:44
sil2100jhodapp: robru is sick today, cyphermox will be your US trainguard for today :)18:45
jhodappawesome, good to know18:45
sil2100(once I EOD)18:45
sergiusenssil2100: did you make the copy though?18:46
sil2100sergiusens: slangasek is copying it now, since we need an archive admin for things like this18:46
sil2100Should be in the archive soon18:46
sergiusenssil2100: thanks!18:46
sergiusenssil2100: I give you permission to leave then :-P LOL18:47
sil2100Hah! No worries, still a few e-mails to write ;)18:47
sergiusenssil2100: in case you didn't notice, I fixed the emulator last night18:47
sil2100sergiusens: thanks! Noticed that, I just finished mentioning it in the landing e-mail even18:48
sil2100Makes things much easier for QA18:48
sil2100sergiusens: ok, looks good -> https://launchpad.net/ubuntu-rtm/+source/golang-go-flags18:49
sil2100So far at least18:49
sergiusenssil2100: so should I retrigger from ci train or someone else from the ppa itself?19:01
sil2100sergiusens: hm, it's best if I simply rebuild it in the PPA19:01
sil2100We'll save some resources this way19:01
sil2100One moment19:01
sil2100sergiusens: I'll add this 'rebuild in PPA' feature to the train once we have power of redeploying it once again19:01
sil2100cyphermox: ok, I need to go EOD now really as it's latish here, leaving the train in your hands19:04
sil2100sergiusens: rebuilt and it succeeded \o/19:04
sergiusenssil2100: thanks19:04
cyphermoxany thing I need to be aware of before I break things?19:04
sil2100cyphermox: just don't get too much frustrated if things start blowing up ;) The train does that19:04
sil2100No no, all is ok19:04
cyphermoxanything that absolutely must not be landed?19:05
sil2100No, QA makes sure to only sign-off things that are wanted in ubuntu-rtm19:07
sil2100So just land anything that they +119:07
sil2100No breakages in sight19:07
sil2100Ok, see you tomorrow and thanks again!19:08
jhodappricmm, reviewed your MR, 2 minor fixes needed19:12
alecucyphermox: may I ask you for a silo for line 74?19:34
kgunntrainguards can someone publish rtm silo320:01
cyphermoxricmm: need me to rebuild silo 8?20:05
ricmmcyphermox: yes please something weird happened to it20:30
ricmmor I can do it myself I guess20:30
cyphermoxpushing buttons...20:30
cyphermoxI think it should just work with a retry20:31
kgunnthanks queuebot20:55
kgunncyphermox: actually...i see mzanetti has a vivid silo, i'll hop in that one, but it'll need a reconfig21:02
cyphermoxtoo late ;)21:02
cyphermoxwell, not too late21:02
cyphermoxwhich silo is that?21:02
mzanetticyphermox: yes21:03
cyphermoxtrainguards: just testing my highlight21:03
kgunnmzanetti: oh my..you're still on21:04
cyphermoxkgunn: just let me know when you're ready for the reconfig21:04
kgunnmzanetti: just fyi, gonna dump josh's screen shot fixes in there (usc included)21:04
kgunncyphermox: yep...ready21:04
mzanettikgunn: did someone review that?21:07
kgunnmzanetti: usc branch yeah.... camako and kdub21:07
mzanettikgunn: looking into the unity branch I'd say there is something to fix still... but should be easy (no architectural thing). lemme look if I can find him21:08
kgunnyeah josh is on21:08
cyphermoxrsalveti: kenvandine: have you had a chance to test and confirm my agent fixes?21:50
kenvandinecyphermox, i don't have a way to test it, i think rsalveti was supposed to do that21:50
rsalvetiI got a bunch of failures, which were also happening in pure vivid21:50
rsalvetiso couldn't really test that silo21:50
kenvandinecyphermox, i'd really like to get that landed though21:50
rsalvetiwill give another shot later today, need to open bugs for the issues I had21:50
kenvandinei just rebuilt it since i landed another silo earlier21:50
rsalvetikenvandine: thanks for that21:51
kenvandinersalveti, i think i'll want to do another landing tomorrow, so if we can get 18 published before then, great21:52
rsalvetikenvandine: yeah, will keep you posted21:53
kenvandinersalveti, thx21:54
pmcgowancharles, can you build silo 1222:07
cyphermoxI'll be out for a bit to get dinner, I will process any changes as soon as I'm back22:40

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!