[00:21] Yeah, no network indicator. Woot. It still works if you access it by sliding from a different indicator though. === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === jamesh_ is now known as jamesh [03:24] === trainguard: IMAGE 30 DONE (finished: 20140515 03:25) === [03:24] === changelog: http://people.canonical.com/~ogra/touch-image-stats/30.changes === [07:10] sil2100: hey. you probably don't know if the qtcreator go plugin was preNEWed or not? it seems it was published anyhow and after didier poked rsync it's now in NEW queue [07:10] so if it was not, now it'd need normal new review [07:35] Mirv: so, I didn't ask Didier to preNEW it yet, but I checked the packaging quickly and it was fine [07:35] Mirv: not sure if robru found someone for a preNEW [07:35] sil2100: ok. yeah, there is no comment from robru about preNEWing, so I guess we'd need to ask didier (or some other arch admin) to do proper NEW review on the one that is in queue [07:36] I explicitly left a comment on the landing that it needs a preNEW, hope robru didn't skip that! [07:36] hum, I would prefer regular archive admins review it [07:37] as the normal process "let it in the queue and it will be picked" is supposed to work [07:37] you can't rely on me forever :) [07:37] with the train, there is no really need for prenewing anyway [07:38] it was more for daily-release, as another build would come [07:40] True true! === psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CI Train support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: - [08:08] sil2100, so that slightly messy indicator-network landing broke it it seems ... [08:11] plars: it's possible I got some of the fine details of the script wrong, I suppose - check what it produced [08:14] * sil2100 sighs [08:15] ogra_: well, it was the lander's responsibility to test if it doesn't break anything [08:15] ogra_: I guess that even running unity8 AP tests should have failed for that landing [08:16] well, it doesnt show up but seems functional [08:16] and in fact there is no upstart job to start it in the package anymore [08:18] hmm no, there should be [08:24] - stop; exit 0 [08:24] + if [ "x$UPSTART_EVENTS" != "x" ] ; then [08:24] + stop; exit 0 [08:24] + fi [08:24] i'm pretty sure this is the issue ... [08:24] will need to test after the meeting [08:25] WTF [08:26] though this should only kick in on non touch sessions ... hmm [08:27] well ... we'll find out ... i really thought Wellark had tested this though :/ [08:28] Morning all [08:28] psivaa, both results for 29 and 30 seem to be stuck in "Syncing" on the dashboard [08:29] popey, sil2100: just updated I don't see nm indicator on the device [08:29] I do however seem to have the ability to send sms and connect to the internet so I think it is only nm-indicator [08:29] but you won't be promoting this image [08:29] davmor2, see backlog :) [08:29] davmor2: yeah, ToyKeeper already pointed that out on the mailing list, we're discussing this already ;) [08:29] I don't want to revert the indicator landing, would prefer to just fix it [08:29] i'll debug this after the meeting [08:29] sil2100, ogra_: only just logged on [08:29] :) [08:29] ogra_: yes, i've asked ev to take a look at the instance where dashboard is running. i could not find any other reasons [08:30] davmor2: bug 1319587 [08:30] bug 1319587 in indicator-network (Ubuntu) "Indicator-network icon missing on device" [Critical,Confirmed] https://launchpad.net/bugs/1319587 [08:30] popey: thanks [08:34] dbarth: hey! one webbrowser-app landed again. I assigned the next one in order to osomon's "Minor fix for the default UA string on devices". there's another "image download support in browser" pending which is blocked now by that. [08:38] sil2100: hey, we might have a fix for the last alarm clock failure at https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/alarm-dow-fix/+merge/219637. Testing in progress. [08:47] sil2100, Mirv, didrocks: ok, what's the issue with silo9? [08:48] people have reported that indicator-network "disapeared" on images 29 and 30 [08:48] Wellark, so after yourt indicator-network change the indicator is gone from the panel --- [08:48] did the unitu8 package land? [08:48] nope [08:49] well, there you go. [08:49] and i guess we wont land anything til thats fixed [08:49] well, silo9 contains a unity8 branch for a reason. [08:49] you mean landing unity8 will fix it ? why were they not in the same silo then ? [08:49] they are [08:50] for a reason [08:50] ah [08:50] which is exactly that they have to land together [08:50] and given the reports seems the unity8 branch did not land [08:50] unity8 needs manual massaging by a release-team person to get out of proposed [08:50] as if it's missing indicator-network "seems" to have dissaepared [08:51] right ... looks like a race in the landing process :P [08:51] we are talking proposed images here, right+ [08:51] Wellark, sorry for blaming you :) [08:51] please tell me we did not make a promoted image.. [08:51] indeed we do [08:51] last promoted was 28 [08:51] indicator landed in 29 [08:51] ogra_, the packaging should have been adapted with appropriate depends/conflicts/... [08:51] no worries [08:51] if things were interdependant [08:51] I bumped that version now [08:52] seb128, tryick for packages that are unity7 and 8 [08:52] ogra_, well, it's easy to make i-n breaks on unity8 << new-version [08:52] seb128, Laney, btw, good to have you here, seems tzdata broke a timezone test in system-settings [08:52] did it? [08:52] Uh oh [08:52] seb128: i-n and unity8 do not depend on each other [08:53] well, at leasst i assume it was that [08:53] Wellark, yet, updating one breaks the other [08:53] link please [08:53] seb128: well, that's just unfortunate [08:53] Laney, http://ci.ubuntu.com/smokeng/utopic/touch/mako/30:20140515:20140513.2/8026/ubuntu_system_settings/ [08:54] Laney, thats image 30 ... for 29 we see the same [08:54] ogra_: I just pinged on #ubuntu-desktop too [08:54] and filed a bug [08:54] At first sight I would not jump to the conclusion that this is caused by tzdata [08:54] the real question here is why the unity8 from silo9 did not hit proposed [08:54] Mirv, awesome,. thanks [08:54] unity8 is in proposed, but it's stuck there [08:54] http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity8 [08:54] Laney, well, it started to show up after this changeset: http://people.canonical.com/~ogra/touch-image-stats/29.changes [08:55] sil2100: was there still some special thing to do with unity8? [08:55] Laney, if you see something else that could be at fault ... go for it :) seemsed tzdata was an obvious candidate [08:55] *seemed [08:55] what does this message mean? [08:55] The test is checking that you see the right text when nothing is entered in the search field [08:55] In silo landing-009. Migration: One package at least is not available at the destination. unity8 (7.86+14.10.20140514.1-0ubuntu1) is in the proposed pocket. [08:55] So that seems very unlikely to me [08:56] Mirv: devel-proposed images are built from proposed? right? [08:56] well, it started reliably after the abvopve image changes ... not saying it must be tzdatza :) [08:56] so at this point I don't care if unity8 is stuck there [08:57] just smelled very related that a tz test fails after tzdata changed [08:57] I need to know why didn't the unity8 package from silo9 hit proposed [08:57] Mirv: no, we should be fine :) [08:58] Laney: thanks for the version bump! [08:58] sil2100, so lets have one image right after unity8 landed ... then i'll do the AP seed change and lezs have another one [08:58] sure [08:59] sil2100, Mirv, didrocks: could someone please answer my question --^ [09:00] Wellark: no, the devel-proposed means it's proposed for evaluation and promotion to another channel, not that its packages would come from -proposed [09:00] Wellark: ah! [09:00] Wellark: sorry, missed your ping, unity8 was blocked in -proposed because there's an additional step that has to be performed with each unity8 release [09:01] sil2100: didn't you just answer to me that "no, we should be fine" regarding special things/extra steps? ;) [09:01] Mirv: that step has been done ;) Laney bumped the version didn't he? ;) [09:02] Wellark, it *did* hit proposed ... it just didnt hit anything after this ;) [09:02] sil2100: ok! so then it's stuck for some reason on build-depending on libunity-mir1 on the powerpc/ppc64el/arm64 [09:02] Mirv, sil2100: ok. thank you. then why was indicator-network moved out of proposed before unity8 that was explicitly on the same silo? [09:02] Wellark: they aren't protected on that level unless a versioned dependency is added in packaging [09:02] Wellark, unity8 needs special love from an archive admin to go from -proposed to the archive [09:02] sil2100: oh, ok! now valid candidate. [09:02] so it'll go in now. [09:03] Wellark, you are missing a dependency to prevent it from moving alone [09:03] Mirv: yep :) [09:03] and we can launch an image build [09:03] right [09:03] Mirv: ok. fair enough. would have guessed the -proposed -> proper would be a manual or semi manual process as well. [09:03] only for cewrtain packages [09:04] these are both ci-train packages [09:04] most of them move automatically ... unity8 is speacial ... [09:04] so you need to add a dependency like seb128 mentioned above [09:04] then indicator-network will be held back together with unity8 next time [09:05] ok. that is not going to happen. as there is no dependency chain between individual indicators and unity8 which provides the indicator rendering [09:05] just add that dependency with your next change ... [09:05] and this kind of a "breakage" only happens if the "protocol" is modified [09:05] err, there obviously is [09:06] you just hit an issue because of it :) [09:07] Mirv: hi, what would you like me to do with the webbrowser-app landings? [09:08] Wellark: that's what Breaks is for [09:08] if a certain version of unity8 provides a needed protocol you need to have a dependency saying "only install me if at lest unitzy8 version xyz is availeble" [09:08] well, when a "protocol" change, you need to rename a binary, or use conflicts or something to ensure the clients of the protocols get updated in sync [09:08] *available [09:08] what cjwatson said [09:08] dbarth: tell/decide if that osomon's landing is good to go next while bfiller's can wait [09:09] ok, checking [09:09] (I'm assuming that there's something else that depends on both indicator-network and unity8, so that the Breaks will be effective for proposed-migration) [09:09] Wellark, you just say "breaks with anything before xyz" ... next time your protocol changes you bump that "before xyz" [09:09] dbarth: in addition to that, would you like to work on landing "Corrective silo for OA" today? robert earlier removed the silo. we're still low on silos, but your request is still quite early so it'd be fine if it can be worked on today. [09:09] that will guarantee that your protocol is in sync [09:09] Or you use Provides to declare a protocol version, and declare Breaks on the old versions (if it's suitably numbered) [09:10] (might be too much effort if the protocol isn't already versioned) [09:10] Mirv: you did well to put it aside [09:11] i'm just tying to land online account stuff and alex's manifest stuff as well [09:12] * Mirv merge & cleaning silo 009 now [09:13] o/ [09:14] Mirv: do you know what that ghost landing is ;p ? By ghost landing I mean, there is a ghost as the lander [09:14] Mirv: so, let bill's request pass [09:14] Mirv: line 37 [09:14] Mirv: the whitespace fix is not a critical bug AFAICT [09:14] Mirv: and the branch from Alex on silo 17 can also wait, we'll rebuild after bill's branch lands, no wories [09:14] Mirv: all set? [09:15] sil2100: haha! ;) oops. [09:15] Mirv: now it's less spooky, thanks ;) [09:16] dbarth: ok, so I'll assign silo to bill's branch instead of osomon's, thanks. [09:20] Wellark, bug 1319728 [09:20] bug 1319728 in indicator-network (Ubuntu) "indicator-network needs to declare a minimal version of unity8 in the package dependencies" [Undecided,New] https://launchpad.net/bugs/1319728 [09:20] sil2100: There's no EMEA webops vanguard coverage this week [09:21] err, echan, sorry [09:25] sil2100: do you want me to deploy it? At least, that would be done, the only difference is that the new field will be mandatory until the plugin lands [09:25] didrocks: if there is no risk involved, then let's deploy :) [09:25] sil2100: yeah, keep me posted at your first publication :) [09:27] sil2100: the charm will be needed to be updated to include the plugin though [09:28] sil2100: deployed [09:30] \o/ :) [09:33] ogra_: so, rmadison says unity8 is in the archive now - did you kick a new image? [09:33] not yet ... doing so now [09:34] Thanks :) [09:34] sil2100: so, dialer and messaging_app tests came back green with 30 on the rerun. but filemanager still had a failure [09:34] psivaa: thanks, filemanager seems to have become a bit more flaky after the new AP it seems [09:35] well, lets see with the python3 stuff [09:36] i suspect we run the wrong tests in some places with the py2 bits installed [09:39] === trainguard: IMAGE 31 building (started: 20140515 09:40) === [10:14] sil2100 Mirv can you reconf silo 003 for me? [10:14] sergiusens: reconfigure [10:22] sil2100: yes, reconfigure [10:23] I have this conflict with packaging practices; the golang packaging status quo, defacto in debian is to prepend golang- to the source package name; this is sort of in conflict with citrain it seems [10:24] I guess you'll just force me to change the source package name, so I guess I'll just do that [10:24] :-/ [10:27] :) I'm not sure what sort of citrain policy you're thinking about though. [10:28] hi all, is it a known issue that on image #28 the volume buttons don't work? [10:28] on a N4, that is [10:29] Mirv: the one where lp:branchname == source package name ;-) [10:29] Mirv: I couldn't reconf because I have lp:udm (to go get launchpad.net/udm), but named the source package golang-udm [10:32] you should be able to, it's just a warning telling you are a bad confusing upstream :) [10:32] * didrocks has saw so many people bzr branch lp: that I think it's valuable to match [10:38] didrocks: it doesn't let me reconf though ;-) [10:39] didrocks: I'm following policy now fwiw [10:39] sergiusens: hum, it's a bug though, do you have the output? [10:39] I can probably fix it [10:39] didrocks: it's in the choo choo [10:39] well, a direct link will be appreciated :) [10:40] didrocks: (07:13:34) CI-SNCF: sergiusens (landing-003): Reconfigure failed: udm was not in the initial list of components for that silo. You can't reconfigure the silo yourself. Please ask the landing team to reconfigure it for you. (https://ci-train.ubuntu.com/job/landing-003-0-reconfigure/17/console) [10:40] great [10:40] and udm was in the initial list? [10:41] didrocks: lp:udm, yes; I didn't change the list; I only hit reconf because I don't like the ci bot message saying I rebuilt in the changelog, when the only reason I wanted to rebuild was to get a nicer changelog [10:41] yeah, I know, I'm a changelog freak [10:41] sergiusens: if you just provide "udm" in the rebuild list, you don't need a reconfigure [10:42] and it won't say "rebuilt force" [10:42] fored* [10:42] forced* [10:42] in your changelog :p [10:42] didrocks: oh, interesting [10:42] sergiusens: partial rebuilds of a stack (so explicit) is always possible [10:43] but interesting, so there is obviously a bug in the reconfigure, it shouldn't then end up into that situation [10:43] sergiusens: mind opening a bug? I may look at it whenever I can [10:43] or if sil2100 beats me to it :) [10:43] he needs to get his hand dirty a little bit in the train I think :p [10:43] * sil2100 in a meeting ;) [10:43] didrocks: where against? cupstream2distro still? [10:43] sergiusens: yeah, cupstream2distro [10:44] ok, so, first assignement was https://ci-train.ubuntu.com/job/prepare-silo/406/console I guess [10:44] with: WARNING:root:Project name (udm) doesn't align with the source package name (golang-udm) [10:46] sergiusens: ok, found the bug, not really sure how to fix it in a elegant way for now [10:47] didrocks: parse debian/control for Vcs-Bzr ? [10:47] sergiusens: not resilient enough [10:47] oh, I've got all needed infos actually [10:48] sergiusens: mind if I reconfigure your silo? [10:48] bug 1319771 [10:48] bug 1319771 in Canonical Upstream To Distro "Silo reconfigure for non trainguard fails when lp:branchname different than source package name" [Undecided,New] https://launchpad.net/bugs/1319771 [10:48] not sure if you started to build yet [10:48] didrocks: yeah, but let me fall back to the original state, one sec [10:48] sure [10:51] didrocks: good to go [10:51] let's see… === MacSlow is now known as MacSlow|lunch [10:53] sergiusens: ah, this was before the new package name [10:54] sergiusens: so, yeah, in that case, it will ask for someone to reconfigure [10:54] but if you package name stays stable [10:54] and package name != source branch name [10:54] you will be able to self-reconfigure [10:54] (which is the main case) [10:54] I pushed the fix for it [10:55] so let's try, I'm reconfiguring as the admin for your new package name [10:55] and then, self-reconfigure [10:57] sergiusens: here we go: https://ci-train.ubuntu.com/job/landing-003-0-reconfigure/20/console [11:00] oh, success, nice [11:01] I guess I should start a faq [11:01] didrocks: is most of this codebase migrating to the airline? [11:01] I guess they have their own codebase [11:01] sil2100: might be imported :-) [11:02] ;) [11:02] * sil2100 is back from meetings [11:02] sergiusens: they are stealing pieces [11:02] sil2100: FYI ^ [11:02] and everytime I do a relevant changes, I'm pinging them [11:02] yeah, this first part makes sense, and francis is familiar with it [11:23] didrocks: sil2100 I'm a bucket of problems today: https://ci-train.ubuntu.com/job/landing-003-1-build/49/console [11:24] Looking [11:24] and these are the contents of my MP http://bazaar.launchpad.net/~sergiusens/udm/empty/revision/3 [11:25] I honestly don't want to bring in issues :-) I swear! [11:25] I wonder why the changelog looks so broken! As if there was some merge conflicts ;p But I don't see any message about that [11:26] because it is CI :P [11:26] all CI changelogs are a mess [11:26] well, try the merge yourself… [11:26] you will see a conflict [11:26] rather than ogra_ being wrong and ranting wrongly [11:26] http://people.canonical.com/~didrocks/citrain/silos/landing-003/udm/debian/changelog [11:26] Ag [11:26] is the result of merging your branch into it [11:26] didrocks, well, i only see the output on -changes ... with lots of duplication etc [11:26] ogra_: so it's rather people editing the changelog manually whic hare doing mess [11:26] Forgot about the rsync mirror! [11:26] ogra_: patch welcomes [11:27] peope should just use dch proper in their commits :P [11:27] ogra_: see, they don't, like this conflict ^ [11:27] and assemble a sane changelog [11:27] yeah [11:28] * ogra_ will happily refuse to go through any debian/changelog enntries in five years when we need to find whom to attributs a certain change to because microsoft sued us or some such :P [11:29] didrocks: but everything below Initial packaging is autogenerated [11:29] ogra_: somewhere is there a list of the images that got promoted from 1 [11:29] didrocks: I thought if we provided a changelog it would not try and generate one [11:30] sergiusens: it doesn't for this commit [11:30] davmor2, yes, but that wont help if the chanelog attributes the changes to "CI Bot" [11:30] sergiusens: it will for the previous ones [11:30] since the latest release [11:30] davmor2, you need a proper changelog in the package to have proper histroy ... [11:30] ogra_: a bug that you are welcome to investigate [11:30] ogra_: but you still have bzr commit authors anyway [11:31] didrocks, yeah, i know ... if i ever find that much spare time i probably will :) [11:31] * didrocks is seeing so much negativness, it's tiring [11:31] really dude… [11:31] same for me [11:31] but you have time to rant though [11:31] ogra_: no I need a list to updat julien on what blockers were present in each promoted image. I thought he only wanted it doing for the end of Trusty. It turns out he wants it forever :) [11:31] until then i'll just make sure to not be involved in that future lawsuit ;) [11:31] anyway, back to work [11:31] didrocks: heh, the reason I wanted to do this was because I had 2 'Initial packaging', one from the commit message and another from the debian/changelog [11:31] davmor2, ugh [11:31] sergiusens: let me take a look at the exact mechanism [11:32] davmor2, i guess you can only go through didrocks and sil2100's landing mails then [11:32] sergiusens: yeah, hence the conflict, you can tag a release if you want to avoid that, but you will need a changelog entry with it [11:32] ogra_: I know the blockers I just need to know the images that were promoted :) [11:32] i doubt you will find any other summary of blockers despit that [11:32] anyway, i'll let sil2100 guiding you, he has enough info [11:33] I'll go through the mails :) [11:33] davmor2, ah thats easy ... [11:33] sil2100: yeah, if I have a list of DOs and DONTs or point me to the code and I'll use that as my guideline :-) [11:33] davmor2, http://system-image.ubuntu.com/ubuntu-touch/trusty/mako/index.json ... all promoted trusty images ... just grep for "description:" [11:34] ogra_: cool thanks [11:34] davmor2, http://system-image.ubuntu.com/ubuntu-touch/utopic/mako/index.json ... same for utopic [11:35] ogra_: ah yeah trusty we have Utopic is the ones I'm after ta [11:38] * ogra_ wonders why imgbot didnt notify about 31 yet ... seems to be done ... [11:39] imgbot, stunt [11:39] * imgbot rolls on its back and purrs [11:39] hmm, still alive [11:40] oh, it was actually reconnecting exactly when the build finished ... bah [11:40] === Image #31 DONE === [11:40] === changelog is at http://people.canonical.com/~ogra/touch-image-stats/31.changes === === alan_g is now known as alan_g|lunch === dednick is now known as dednick|lunch [11:51] dbarth: FYI your SRU bug is unverified https://bugs.launchpad.net/bugs/1302780 so it hasn't gone in even though it's 14 days old [11:51] Ubuntu bug 1302780 in webbrowser-app (Ubuntu Trusty) "[webapp-container] Google Apps For Business support when using an external SSO provider" [High,Fix committed] [11:57] brb! [11:59] dbarth: you can btw follow these things on http://people.canonical.com/~ubuntu-archive/pending-sru.html - green ones (=verification-done) with days >= 7 will be handled by the SRU team and migrate to release pocket === cjohnston changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cjohnston | CI Train support - US: robru, cyphermox, rsalveti - EU: sil2100, Mirv, didrocks | CITrain support no answer: use mup bot after 30 minutes, but choose right timezone | Known issues: - === MacSlow|lunch is now known as MacSlow [12:03] sergiusens: give me some moments regarding that problem, ok :) ? Need to context switch for a small moment === psivaa is now known as psivaa-afk [12:06] ogra_, sil2100: the unity8 fix doesn't show wifi/3g on the phone signal bars [12:06] oh and now wifi is turned off again by default I'm assuming 3g might be the same [12:06] sigh [12:07] turned on wifi now I see it in the indicator [12:07] sounds like the same issue we have with manta then [12:08] geh [12:08] Then even good that I didn't consider promoting anything today [12:08] davmor2: after rebooting it's the same? [12:09] sil2100: lunchtime i'll reboot it as I go down to eat and let you know when I get back [12:09] sil2100, so i assume the fix lies somewhere between cyphermox and Wellark :) [12:10] ;) [12:10] Damn, have to jump out for lunch as well, didn't eat breakfast yet [12:10] * ogra_ has to go afk for a while too [12:10] davmor2: give us a sign after lunchtime, we then fill in a bug and poke those two bad persons [12:13] Mirv: can i just mark the package verified? or i have to resubmit fully [12:14] cause i can attest the fix works and doesn't create regressions; so will mark it done as well [12:19] sil2100: no worries [12:20] unity8 should no longer require manual attention from #ubuntu-release [12:21] yay !!! [12:22] (tested as best I can considering, but do let me know if the next one explodes ...) [12:34] manual attention for unity8 by ubuntu-release? anything interesting was going on there? === jhodapp|afk is now known as jhodapp === greyback is now known as greyback|food [12:38] yaay! [12:38] cjwatson: thanks ;) [12:39] sil2100: same thing after a reboot [12:39] asac: yeah, so normally an additional step was required every time a new unity8 was released [12:39] davmor2: uh, sucks... could you fill in a bug for easy tracking? [12:40] sil2100: on it [12:40] Thanks :) [12:40] asac: a hack to cope with a weird special case that I've now buried a bit more competently [12:40] i like buried :) [12:41] might eventually allow us to hire into roles like "technical archeologists", which could be a first :) [12:42] I kind of feel that's what my job already is half the time. :-) [12:42] "so, um, what did we intend by this ten years ago" === tedg is now known as ted === alan_g|lunch is now known as alan_g [12:43] sil2100: o/ silo 16 ready to land [12:44] dbarth: awesome! Will publish after done with lunch [12:45] dbarth: the SRU is process is there that once the fix goes into -proposed, someone installs it specifically from there, tests it, and marks it as verification-done. so it's not related to our landing (it has already landed), but whether the final SRU step of copying from -proposed to -updates happens or not [12:46] Mirv: i know but was (again) trying to get external feedback [12:46] but happy to mark verification-done myself [12:47] thanks for the dashboard link btw, that really helps [12:47] dbarth: yeah, it's sometimes hard to get as the people experiencing the bug might not necessarily find the LP bug or the SRU guidelines on how to proceed [12:47] dbarth: you're welcome [12:48] Mirv: will you publish silo 16;) ? [12:48] Mirv: if you have a free moment [12:49] sil2100: yes I was just going once more through the MP:s of it, actually [12:50] err... [12:50] /tmp/hudson1545565889933478490.sh: line 4: BUILD_USER_ID: unbound variable [12:50] sil2100: are you aware of any recent changes to the code? [12:50] https://ci-train.ubuntu.com/job/landing-016-2-publish/16/console [12:51] argh, that wouldn't work then as long as we don't have the plugin [12:51] I can fix that [12:51] however Mirv, you should really read that channel :p [12:51] sil2100: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1319812 [12:51] Ubuntu bug 1319812 in indicator-network (Ubuntu) "Indicator-network is doing odd things" [Critical,New] [12:52] or, it's better for it to fail, it shouldn't fail if you set the value [12:52] Mirv: did you set the launchpad user name id? [12:52] see the new field [12:56] yeah, confirmed it won't fail if you use the parameter [13:00] sil2100: any news on the plugin deployement? === ted is now known as tedg [13:01] Mirv: still with us? I'll leave for some exercise in 10 minutes, all good for the publication now? [13:10] I take that as a yes :) away now. [13:11] :) [13:11] didrocks: so, still lunch, but working on that with webops and Evan [13:11] asac, note that this had its good and bad sides ;) we found a good bunch of missing or broken dependencies over the last weeks due to unity8 being held :) [13:11] didrocks: :) ok [13:12] the last one just today [13:12] cjwatson: cool, shall i change your title :)? [13:12] hehe [13:12] i think its like ying and yang [13:12] yeah [13:12] where there are architects, there need to be archeologists :) [13:12] oh, now I connect the discussion to the actual result [13:12] black matter [13:13] it surely makes a good business card entry :) [13:13] Mirv: so, just use your launchpad name until the plugin is installed in that field [13:13] Mirv: then, you won't need it apart if you sponsor for someone else [13:13] like there is a packaging change and you ack it [13:13] Chief Technical Archeologists - call me when you lost sight of whats going on and i will dig through your dirt :) [13:13] CTA :) [13:14] didrocks: thanks! [13:14] yw! hoping everything is fine :p [13:14] ah, no, there is a typo (weird, it passed pyflake…) [13:15] asac: I will probably cope with it as it is :) [13:15] (now I got AttributeError: 'module' object has no attribute 'get_person') [13:15] yeah [13:15]