[08:18] <sil2100> mvo: hey! Yeah, right now we don't support syncing packages that don't have a CI Train ver number, you'll have to do a direct upload with the version demangled
[08:18] <sil2100> s/demangled/changes
[08:18] <sil2100> *changed
[08:20] <mvo> sil2100: what the best way forward for me, can I just give it a ci-train friendly version number?
[08:26] <sil2100> mvo: that could work, but I think your packaging has some metadata set that tells the train: "don't change my version number to a CI Train version"
[08:27] <sil2100> You would have to change that, I can take a look if that's the case
[08:27] <sil2100> Since once that flag is gone, the train will automatically prepare the version number to be train compatible
[08:27] <sil2100> mvo: but wait a moment
[08:27] <mvo> ok
[08:28] <sil2100> You might have found a bug in the train
[08:28] <mvo> heh
[08:28] <mvo> ok
[08:29] <sil2100> Or maybe not...
[08:29] <sil2100> So yeah, I suppose that's the only option to use dual landings
[08:29] <sil2100> Since otherwise the train wouldn't know how to change the version numbers to not have conflict
[08:29] <sil2100> (too much guessing work would be needed)
[08:31] <sil2100> mvo: if you don't mind the big CI Train-compatible versioning, simply remove X-Auto-Uploader: no-rewrite-version from debian/control and rebuild
[08:40] <mvo> sil2100: thanks, if cjwatson is ok with me removing "X-Auto-Uploader: no-rewrite-version from debian/control" I will do that. I wonder why this wasn't a issue before? has something changed here?
[08:41] <sil2100> mvo: it's only an issue for dual-landings, which robru wrote when we switched to the overlay-PPA, so not long ago
[08:41] <sil2100> mvo: click probably wasn't dual landed before
[08:42] <mvo> sil2100: I see, thanks that makes sense
[08:51] <cjwatson> mvo: Your call
[08:56] <mvo> cjwatson: thanks!
[08:57] <mvo> sil2100: meh, I accidently clicked on "build" in ubuntu/landing-21 instead of in my click ppa, no harm fortunately. sorry for that
[08:57] <sil2100>  No worries, happens to me sometimes too ;p
[09:34] <mvo> sil2100: meh, fun! now it dislikes me for "bzr: ERROR: Inconsistency between source format and version: version is not native, format is native." when I remove the mangling. maybe I just do it manually (which makes me wonder what the benefit of the train is if I do it manually?)
[09:35] <sil2100> Ah, right, the package format ;|
[09:36] <sil2100> mvo: yeah, the train dual landings make sense and help a lot when dealing with train-specific packages
[09:41] <mvo> sil2100: I would love to use it, any hints what I can try to make it work? switching to non-native?
[09:44] <sil2100> mvo: yeah... the train is a bit of a stupid entity (mostly because it was only a proof-of-concept), so non-native is the way to go if you want to use it...
[09:44] <sil2100> The CI Airlines was supposed to be the smart thing
[09:44] <sil2100> But it never happened
[09:50] <sil2100> huh, now that's strange
[09:50] <sil2100> Ah!
[09:50] <sil2100> mvo: you're missing a .bzr thingie
[09:50] <mvo> sil2100: oh, in the version number?
[09:50] <sil2100> No no
[09:50] <sil2100> mkdir -p .bzr-builddeb
[09:50] <sil2100> cat >.bzr-builddeb/default.conf <<EOF
[09:50] <sil2100> [BUILDDEB]
[09:50] <sil2100> split = True
[09:50] <sil2100> EOF
[09:50] <mvo> oh, of course. thanks
[09:51] <sil2100> Do this in your project :)
[09:51] <mvo> thanks sil2100
[10:47] <karni> rvr: (Cc davmor2) Hi, I was away yesterday, sorry. I'll look into it, I was sure I merged those missing translations properly. Today gets it from Telegram, those strings should be translated.
[10:47] <rvr> karni: Ack
[10:48] <davmor2> karni: boo or yay which ever works for you today ;)
[10:48] <karni> lol
[11:31] <jgdx> davmor2, how's config hell?
[11:35] <davmor2> jgdx: I hate you, I have an effigy of you that I burning now ;)  so freeradius has 100 setups everyone is different all are mostly old, some bits of some work some bits don't and visa versa, it is not fun at all.
[11:40] <jgdx> davmor2, it's popey's bug. I kindly request all malice be directed towards him :d
[11:41] <jgdx> but maybe you have other QA guys that are close to an eduroam network and have access?
[11:41] <jgdx> idk
[11:41] <popey> \o/
[11:42] <popey> I filed that bug when I was at Oggcamp in Liverpool in 2013. I'll be back there in Oct/Nov this year. Would be great to report progress on the bug at that event ㋛
[11:47]  * davmor2 stabs the popey voodoo doll repeatedly with a small pin
[11:48] <davmor2> jgdx: Hmm I wonder if wolverhampton uni uses it
[11:50] <popey> good luck getting a user/password
[12:31] <dobey> trainguards: my silo (21) seems confused now because apparently mvo tried to build it earlier without specifying any options and actually meant to build a different silo. i did a WATCH_ONLY build, but the status doesn't seem to be updating properly?
[12:32] <sil2100> dobey: what's wrong with its status?
[12:32] <dobey> sil2100: it says "No packages are being considered..."
[12:32] <sil2100> 14:27 -queuebot:#ubuntu-ci-eng- Silos: ubuntu/landing-021 (dobey, alecu, charles)
[12:32] <sil2100>           Packages built (pay-service, unity-scope-click)
[12:32] <dobey> yes
[12:32] <sil2100> The queuebot disagrees ;)
[12:33] <sil2100> Remember, the CI Train spreadsheet status updates every 5 minutes
[12:33] <dobey> ok now the dashboard has the right thing
[12:33] <sil2100> Better trust the dashboard and queuebot
[12:33] <sil2100> Google is slow
[12:33] <dobey> the dashboard was wrong too :)
[12:33] <dobey> but it's right now
[12:33] <sil2100> Yeah, since the QA status is coming from the spreadsheet
[12:34] <sil2100> So until that updates, it won't have all the info
[12:34] <dobey> ok
[12:34] <dobey> thanks
[12:44]  * sil2100 off to lunch
[13:07] <dobey> jibel: hi, the MPs for landing-021 are reviewd/approved now, so is unblocked now for qa i think :)
[13:10] <jibel> dobey, thanks, moved to ready.
[13:11] <jibel> dobey, I probably already asked, but what is the reason of the unsatisfied dependencies in the ci jobs?
[13:12] <dobey> jibel: unity-scope-click needs the new libpay, which is not available in jenkins (but is obviously satisfied in the silo since both are in it)
[13:22] <jgdx> davmor2, will we miss the string freeze for this? USS has another high pri branch on the tracks. :)
[13:24] <jgdx> (no update for 5 hours worries me :))
[13:25] <jgdx> sil2100, when do we have string freeze?
[13:31] <davmor2> jgdx: one last thing to test I think I have the server setup right now
[13:33] <jgdx> davmor2, wee
[13:54] <charles> trainguards, queubot is right, I'm ready for a silo for line 74 :)
[13:59] <Laney> cihelp: hi, can you give me any more info on https://jenkins.qa.ubuntu.com/job/wily-boottest-ubuntu-touch-meta/lastBuild/console please? It looks installable to me - is there pinning involved, or anything else?
[13:59] <josepht> Laney: looking
[14:04] <oSoMoN> ubuntu-qa: is there anyone who could validate silo 2 soon-ish? I’m asking because I have another webbrowser-app silo lined up for landing today (will be ready for validation very soon), it contains user-facing string changes so it has to land today
[14:05] <rvr> davmor2: ^ Can you?
[14:05] <jibel> om26er_, ^
[14:05] <Laney> josepht: If nothing else you could add "-oDebug::pkgProblemResolver=true" to the appropriate apt-get invocation which should get it to give more output
[14:05] <jibel> rvr, davmor2 is on another silo
[14:05] <rvr> Ah
[14:06] <rvr> jibel: I thought he moved it to passed
[14:06] <om26er_> jibel, sure, i'll take a look
[14:06] <jibel> actually he just landed it
[14:06] <jibel> yeah
[14:06] <davmor2> jibel: it passed
[14:08] <davmor2> jgdx: ^ by the way incase you missed it finally found a guide that worked :)
[14:09] <jibel> davmor2, great, you won the title of expert in freeradius configuration ;)
[14:10] <jgdx> davmor2, yeah dave can you come configure my home router?
[14:10] <davmor2> jgdx: there is still no certification verification it is only enterprise level user/password  but it works :)
[14:11] <jgdx> davmor2, great work!
[14:19]  * sil2100 gazes at poor ogra_ 
[14:20] <ogra_> sil2100, i'll try to get to it today (rushing from meeting to meeting atm)
[14:22] <jgdx> seb128, ^
[14:22] <jgdx> seb128, what's the solution to silo 40's publishing?
[14:23] <seb128> jgdx, good question, I've no idea ;-)
[14:23] <seb128> landing team can probably help
[14:23] <seb128> either commit the change from wily to trunk and rebuild the silo
[14:23] <seb128> or overwrite the archive version
[14:24] <jgdx> trainguards: can silo 40 overwrite the archive version?
[14:24] <jgdx> trainguards: there was a manual upload that can be overwritten/discarded.
[14:25] <seb128> it would be better if it was not
[14:25] <seb128> but I don't want to delay landings on it
[14:25] <seb128> I might just redo another manually upload with those changes after the landing :p
[14:25] <sil2100> jgdx: yes, that can be done by an override flag, we do recommend to merge in the changes manually to trunk though
[14:26] <sil2100> But if time is of the essence, there's a flag for overriding that check
[14:26] <jgdx> sil2100, time is of essence.. seb128, you okay with overwrite?
[14:26] <seb128> if we merge to trunk then we need a silo rebuild
[14:26] <seb128> jgdx, sure, I'm just going to redo a manual upload after you :p
[14:26] <davmor2> jgdx: https://dani33l.wordpress.com/2014/11/ this is the working guide, there are a couple of things I had to do on top 1 is documented at the bottom the other was to use phpadmin to ensure the user was created on first attempt it wasn't
[14:26] <sil2100> Use FORCE_REBUILD when building
[14:26] <jgdx> seb128, what if we include your branch in silo 22?
[14:26] <sil2100> That's like our magic flag for almost everything
[14:27] <seb128> jgdx, that would be good
[14:27] <jgdx> great
[14:27] <jgdx> sil2100, am I to do the publish with the override flag or is that you guys?
[14:28] <sil2100> We'll do that now
[14:28] <jgdx> sil2100, awesome, thank you
[14:29] <sil2100> Published!
[14:32] <jgdx> sil2100, wonderful. Quick question, will silo 22, when built, see the changes made by silo 40?
[14:33] <jgdx> if not, where's the answer to that question? Launchpad?
[14:35] <seb128> jgdx, we might get a conflict on the changelog, I think I'm just going to manually commit/push to trunk once the current landing is merged in, then we can rebuild the silo
[14:36] <jgdx> seb128, okay, you'll let me know when I can rebuild?
[14:36] <seb128> jgdx, ok
[14:54] <charles> makes sense
[14:58] <josepht> Laney: the output is here: http://d-jenkins.ubuntu-ci:8080/job/wily-boottest-ubuntu-touch-meta/21/artifact/results/log
[14:59] <robru> sil2100: mvo: https://wiki.ubuntu.com/DailyRelease/InlinePackaging these are the packaging instructions for making packages compatible with the train
[14:59] <pstolowski> sil2100, hey! where do I find packages with debug symbols for stuff from overlay ppa?
[14:59] <Laney> josepht: no debug output there...
[15:00] <sil2100> pstolowski: hm, not sure if we have that setup
[15:00] <mvo> robru: nice, thanks a bunch
[15:02] <Laney> josepht: maybe it went to apt-get-install.stderr, what happened to that?
[15:02] <robru> mvo you're welcome
[15:03] <josepht> Laney: I'm trying to track it down now
[15:04]  * Laney knows not how to attach artifacts to jenkins
[15:08] <rvr> bfiller: You don't have permission to access /~bfiller/com.ubuntu.gallery_2.9.1.1205_armhf.click on this server.
[15:12] <pstolowski> sil2100, hmm that's really unfortunate :(
[15:17] <pmcgowan> sil2100, pstolowski our tracking document says its supported
[15:17] <pmcgowan> This makes it possible to query the Launchpad librarian directly for debug symbols associated with a package in any ppa.
[15:18] <sil2100> Maybe, maybe someone else would know more details
[15:20] <pmcgowan> maybe its not debug packages though just querying the symbols
[15:20] <pstolowski> pmcgowan, awesome, this would save me a lot of time
[15:20] <pstolowski> pmcgowan, what is the 'tracking document'?
[15:21] <pmcgowan> cjwatson, maybe you can advise us
[15:21] <pmcgowan> pstolowski, compares ppa wth derived distro https://docs.google.com/document/d/1iQebOdbio-8k4vMcHAZ8SPhqAUlQws47SihlHKfrxOQ/edit
[15:21] <abeato> sil2100, is it possible to drop the version of a package in a silo once it has been built once by modifying the version in the changelog?
[15:22] <karni> rvr: (Cc robru) I've updated the Telegram click with translations. Not sure if it was not there, or just not translated, but I ensured this time spanish translation for scope strings are in the click package. Ready for re-review (as it was only blocked on i18n). Thanks
[15:23] <cjwatson> pstolowski: What specific package is this?
[15:24] <sil2100> abeato: hey! What do you mean by that? You mean like, dropping a version that's already released in the archive?
[15:24] <pstolowski> cjwatson, libunity-scopes3
[15:24] <abeato> sil2100, no
[15:24] <abeato> sil2100, I have version 6900 for ofono in silo 6
[15:25] <cjwatson> pstolowski: It's right there in http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/unity-scopes-api/
[15:25] <abeato> sil2100, I modified the changelog setting the version to 6898
[15:25] <abeato> sil2100, but the package version did not change
[15:26] <cjwatson> pstolowski: You can put something like "deb http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid main/debug" in sources.list if you want apt to be able to fetch it
[15:26] <sil2100> abeato: yeah, it's not really possible... if, let's say, 6900 is now in the PPA, it's not possible to upload anything that has a smaller or equal version
[15:26] <pstolowski> cjwatson, great! thanks for help
[15:26] <cjwatson> sil2100,pmcgowan: ^- it's definitely set up :)
[15:26] <sil2100> abeato: hm, wait, maybe a smaller version would be possible
[15:26] <sil2100> cjwatson: excellent!
[15:26] <abeato> sil2100, Ihow?
[15:27] <pmcgowan> cjwatson, awesome thanks
[15:27] <sil2100> abeato: since the PPA won't allow a same-version upload, but if I remove the package from the PPA it *might* allow upload of the lower version
[15:27] <sil2100> Let me check
[15:27] <cjwatson> For completeness, you can also download them directly from LP: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+packages, search for "unity-scopes-api", expand
[15:27] <cjwatson> sil2100: correct
[15:27] <abeato> sil2100, ok
[15:29] <sil2100> abeato: ok, I'm removing the package from the PPA, now you should be able to upload/build the smaller version
[15:29] <abeato> sil2100, awesome, thanks!
[15:31] <rvr> karni: Ack
[15:31] <karni> :)
[15:33] <sil2100> abeato: yw!
[15:34] <rvr> karni: Did you update the link to the new click file in the document?
[15:35] <karni> rvr: yes, 1.3.8.112 version has the new link on the line above
[15:35] <karni> I also uploaded it to people.c.c
[15:36] <jgdx> seb128, I'm going away soon. Could you do the build?
[15:36] <jgdx> sil2100, when is the string freeze?
[15:36] <om26er> dbarth, Hi!
[15:36] <rvr> karni: Thanks
[15:36] <karni> rvr: thank you
[15:36] <om26er> dbarth, could you point to the relevant code for bug 1421009 fix in silo 2 ?
[15:39] <sil2100> jgdx: it was planned for today EOD
[15:44] <dbarth> om26er: hi, ok, 1 sec.
[15:44] <jgdx> seb128, I'll go ahead and build silo 22
[15:44] <dbarth> om26er: hmm, not a bug i'm on
[15:46] <dbarth> om26er: ah, via
[15:46] <dbarth> https://code.launchpad.net/~mardy/ubuntu-system-settings-online-accounts/lp1447175
[15:47] <dbarth> om26er: that would be : https://code.launchpad.net/~mardy/ubuntu-system-settings-online-accounts/lp1447175/+merge/257251
[15:47] <dbarth> ie, this merge makes it so that it builds fine with qt 5.5; is that what you were looking for ?
[15:47] <om26er> dbarth, hmm, interesting. thanks
[15:47] <om26er> dbarth, well it claims to also fix a unity8 hang
[15:47] <om26er> thats what 1421009 is about
[15:47] <dbarth> right
[15:48] <dbarth> om26er: apparently, beacuse of it being a threading issue, itself fixed by qt5.5, so requiring OA to also be qt5.5 compatible
[15:49] <dbarth> zipping through the initial bug report
[15:49] <om26er> dbarth, aaah, ok, so we just assume its fixed :)
[15:51] <jgdx> sil2100, when's EOD?
[15:54] <sil2100> jgdx: you still have the whole day today, I suppose tomorrow when I wake up we'll no longer be accepting any new string changes
[15:55] <sil2100> If, of course, this won't get overrided by the product team, as it all depends if we have everything we need in the image
[15:55] <jgdx> sil2100, okay, great.
[16:02] <abeato> sil2100, it is still building 6900, I guess that cannot change after the birst build :-/
[16:04] <dbarth> om26er: yes; otherwise, all good for the rest of the tests?
[16:05] <om26er> dbarth, yes, everything looks good, just need to verify a few more scenarios
[16:05] <dbarth> ok nw
[16:09] <seb128> jgdx, k, with what?
[16:15] <rvr> karni: "No se pueden recuperar sus datos de Telegram" \o/
[16:15] <karni> PHEW
[16:26] <jgdx> seb128, what are you responding to? :)
[16:26] <seb128> jgdx, <jgdx> seb128, I'll go ahead and build silo 22
[16:26] <seb128> jgdx, but seems like the landing didn't work? https://launchpad.net/ubuntu/+source/ubuntu-system-settings
[16:26] <seb128> or was it not a wily/dual landing?
[16:27] <jgdx> it was
[16:28] <jgdx> sil2100, what's the status on silo 40? Something abyss something. Not sure what that means
[16:33] <rvr> karni: Do you have a test plan for Telegram somewhere?
[16:33] <karni> yes, I think it's linked in the relesae notes, lemme see now
[16:34] <rvr> karni: Ah, the spreasheet, nice
[16:34] <karni> rvr: do you have relesase notes open? there's 'QA results'
[16:34] <rvr> Thanks
[16:34] <karni> rvr: one older (initial QA pass), and the latter I left empty IF you wanted to do a full pass
[16:34] <karni> rvr: in any case, these contain sub-sheets, for instance, with test descriptions
[16:34] <karni> rvr: I think this document is pretty crazy if you asked me :D (beefed up)
[16:35] <rvr> karni: hehe. Great, I'll run a subset.
[16:35] <karni> :)
[16:36] <sil2100> jgdx: looking
[16:38] <sil2100> jgdx, seb128: the rsync file looks okayish, I'm a bit worried that maybe the package got rejected because of the dest version being different, but in the past it worked fine
[16:39] <josepht> Laney: here's what I was able to get: http://d-jenkins.ubuntu-ci:8080/job/wily-boottest-ubuntu-touch-meta/26/artifact/results/apt-get-install.stderr
[16:39] <Laney> josepht: bah!
[16:40] <sil2100> seb128: you have access to snakefruit?
[16:41] <seb128> sil2100, no
[16:43] <sil2100> slangasek: hey! You have a moment to help us out with something? We published a package through the train to wily and it doesn't look like it appeared... not sure if the copy-package even happened for it
[16:44] <slangasek> sil2100: package?
[16:44] <sil2100> ubuntu-system-settings
[16:44] <sil2100> https://ci-train.ubuntu.com/job/ubuntu-landing-040-2-publish/11/artifact/packagelist_rsync_landing-040-wily/*view*/ <- this was the rsync file
[16:45] <jgdx> sil2100, it's dual, btw
[16:45] <slangasek> sil2100: would it have failed if there was another version of u-s-s still in wily-proposed?  (which was the case until 6 hours ago)
[16:47] <slangasek> sil2100: it looks cleanly copyable; do you want me to copy it now?
[16:58] <jgdx> trainguards: ^ please, could we give slangasek an answer on this? :)
[16:58] <sil2100> slangasek, jgdx: sorry, was otp
[16:58] <sil2100> slangasek: no, it shouldn't have failed
[16:58] <sil2100> Could you copy it?
[16:59] <sil2100> Not sure what caused the issue as I'm not sure if the copy2distro doesn't provide much debugging logs
[16:59] <robru> sil2100: man we really need better logging from copy2distro
[17:00] <jgdx> sil2100, np, thanks
[17:25] <jgdx> bfiller, starting testing now
[17:25] <bfiller> jgdx: great, I'll test it as well
[17:26] <slangasek> sil2100, jgdx: copied now
[17:26] <sil2100> slangasek: thanks!
[17:27] <jgdx> slangasek, thanks
[17:28] <jgdx> sil2100, I'm going to see the new versions here https://launchpad.net/ubuntu/+source/ubuntu-system-settings ?
[17:28] <sil2100> jgdx: the new wily version
[17:28] <jgdx> okay
[17:28] <jgdx> it goes in the ppa as well I assume
[17:29] <sil2100> http://people.canonical.com/~lzemczak/overlay-ppa-version <- this script can be used to check the version in the overlay
[17:29] <sil2100> It's already there
[17:31] <jgdx> okay thanks
[17:36] <sil2100> dbarth: hey! How's the new oxide? I didn't see a silo for it yet
[17:36] <jgdx> bfiller, we need another build after 40 has been copied to wily. And I'll also drop an MP from the silo.
[17:36] <sil2100> Is it under testing?
[17:37] <jgdx> bfiller, okay silo 40 now in wily, building…
[17:37] <bfiller> jgdx: just installed and testing 22, after choosing a contact to forward the number to and pressing "Set" I get a message saying "Call forwarding can't be changed right now"
[17:38] <jgdx> bfiller, what happens if you try again?
[17:38] <bfiller> jgdx: I can't as it grays out the option and text for "Forward every incoming call"
[17:39] <jgdx> bfiller, go back and in again? that's per design if your carrier disallows forwarding
[17:39] <dbarth> sil2100: hmm, we haven't made a new build
[17:40] <bfiller> jgdx: ok let me try, don't like the text either way - it should tell me my carrier doesn't support it if that's the case
[17:40] <jgdx> bfiller, we have no way of knowing
[17:40] <dbarth> i need to worry about that
[17:40] <bfiller> jgdx: so it worked the second time
[17:40] <bfiller> jgdx: when I manually entered the number
[17:41] <jgdx> bfiller, what happened in the first attempt?
[17:41] <bfiller> jgdx: I think I see the problem
[17:42] <bfiller> jgdx: seems to do with the phone number formatting
[17:42] <jgdx> bfiller, what's the number?
[17:42] <bfiller> jgdx: when selected from the contact it puts the (617)489-xxxx and when I enter manually it puts +1617489xxxx
[17:42] <bfiller> jgdx: the first case fails and the second case works
[17:43] <jgdx> ugh, dashes? :|
[17:43] <bfiller> guessing that's the issu?
[17:43] <jgdx> yea
[17:44] <bfiller> jgdx: I have 2 numbers for my contacts, nice dialog comes up and asks me to select one and it uses the format (xxx) xxx - xxxx and that's what gets copied into the text field
[17:44] <jgdx> yup
[17:45] <bfiller> jgdx: when using the keypad it has no formatting and after I press set it seems to correctly add the country code of +1
[17:45] <jhodapp> robru, can you please reconfigure silo 38 for me?
[17:46] <robru> jhodapp: I hereby deputize you in the name of holy train guardyness, you may now reconfigure your own silos! ;-)
[17:46] <jhodapp> robru, haha, thanks :)
[17:46] <jhodapp> robru, no longer want to do my dirty work huh ;)
[17:46] <robru> jhodapp: you're welcome. let me know how it works.
[17:46] <robru> jhodapp: no no, I'm empowering you to be able to work independently.
[17:46] <robru> ;-)
[17:46] <jhodapp> much appreciated :)
[17:47] <robru> jhodapp: I'll still be here to clean up if anything explodes though
[17:47] <bfiller> jgdx: shall I cancel the build until we can resolve that issue?
[17:47] <jgdx> bfiller, makes sense. We should deal with dashes, but I'm not sure where to draw the line. Will talk to boiko
[17:47] <bfiller> jgdx: should strip out all the formatting
[17:47] <jgdx> bfiller, I don't have an immediate good solution though
[17:48] <jgdx> okay
[17:48] <bfiller> jgdx: does the formatted number come from the vcard import or are you formatting on your own?
[17:49] <jgdx> bfiller, comes from the vcard import, translated into a model of qtcontacts.
[17:50] <bfiller> jgdx: so pretty sure there is a libphonenumber or something that should give you the unformatted number for that string? renato or boiko might know
[17:50] <jgdx> bfiller, that'd be great
[17:50] <boiko> robru: regarding silo 44, I discussed with bfiller and salem_ about it, and we decided to temporarily have a separate bzr branch for vivid for telephony-service
[17:51] <boiko> robru: could you please reconfigure the silo to be vivid only? I have re-created the merge proposals against that branch already
[17:52] <robru> boiko: you have the power to reconfigure now. just note I put the overlay PPA in column L for you
[17:52] <boiko> robru: ah nice, thanks!
[17:52] <robru> boiko: you're welcome
[17:53] <robru> boiko: let me know if you have any issues
[17:53] <boiko> robru: sure
[17:53] <jhodapp> robru, where's the reconfigure button located?
[17:53] <boiko> jhodapp: it is in the landing tools menu
[17:54] <robru> jhodapp: "Landing tools" menu at the very top of the page.
[17:54] <jhodapp> ah ok cool
[17:54] <boiko> jhodapp: just make sure any column of the row you want to reconfigure is selected
[17:54] <robru> jhodapp: just make sure you have the right row selected first
[17:55] <jhodapp> robru, cool, I'm not seeing landing tools on the spreadsheet page...I refreshed even
[17:56] <robru> jhodapp: it's at the top of the page, not the first row of the spreadsheet.
[17:56] <robru> "Addons Help Landing Tools"
[17:58] <jhodapp> robru, I don't have that, or I'm just blind :)
[17:58] <jhodapp> robru, oh I see it now
[17:58] <robru> jhodapp: yeah, there
[17:58] <jhodapp> next to Help
[18:01] <robru> heh, 6 conflicting silos, most excellent.
[18:03] <robru> jhodapp: did you get it? didn't see the bot ping saying the silo is ready to build
[18:03] <jhodapp> yes it worked
[18:05] <robru> jhodapp: ok looks good, not sure why we didn't see the bot ping about that
[18:05] <robru> anyways, I'm off for lunch, if anything explodes I'll fix it later!
[18:07] <jgdx> bfiller, there's an issue with the connection type in Cellular panel, removed that MP from the list so that won't be an issue for next build.
[18:08] <bfiller> jgdx: ack
[18:10] <boiko> robru: would you mind removing the wily packages from silo 44's ppa?
[18:11] <jhodapp> robru, yeah it is weird, but it successfully reconfigured according to the console output
[18:23] <rvr> karni: Update approved
[18:24] <karni> rvr: great news! that's a green light for release?
[18:24] <rvr> karni: Yes
[18:24] <karni> (as far as QA is concerned)
[18:24] <karni> rvr: \o/ thank you
[18:29] <robru> boiko: sure one sec
[18:30] <robru> boiko: ok wily should disappear in a sec. let me know if you need any more help with that
[18:37] <boiko> robru: thanks!
[18:43] <robru> boiko: you're welcome
[19:16] <robru> brb
[19:17] <oSoMoN> ubuntu-qa: I’m waiting on silo 2 to finish landing, I’ll then rebuild silo 16 and will need validation from you guys, will there be someone available to ack it before EOD? It contains user-facing string changes, hence the need to land it today
[19:18] <rvr> oSoMoN: Maybe alesage or om26er
[19:18] <oSoMoN> ok, thanks
[19:19] <alesage> oSoMoN, someone will get it :)
[20:59] <robru> oSoMoN: silo 2 is free & clear
[21:03] <oSoMoN> robru, I’ve seen that, thanks
[21:04] <oSoMoN> I’ve rebuilt silo 16, running some tests locally and will hand over to QA in a moment
[21:06] <robru> oSoMoN: cool, no worries
[21:07] <robru> oSoMoN: oh heh, just checked the timestamps, didn't realize I'm an hour late, lol
[21:07] <oSoMoN> :)
[21:28] <kgunn> trainguards not really sure if i should whine here....but why is it when i run u-d-f query --list-channels --device=flo
[21:28] <kgunn> it's showing only devel available ?
[21:28] <kgunn> no stable ?
[21:28] <kgunn> or maybe i'm confused....
[21:28] <kgunn> if i a want vivid+overlay on flo....what channel should i use
[21:28]  * kgunn thot it was stable
[21:30] <kgunn> or rc
[21:31] <robru> kgunn: errr, dunno, sorry
[21:31] <kgunn> robru: do you have a guess who should i whine to
[21:31] <kgunn> ?
[21:31] <oSoMoN> ubuntu-qa: silo 16 is now ready for sign-off
[21:31] <robru> kgunn: maybe more of a question for rsalveti or ogra_ ... not really sure
[21:31] <oSoMoN> alesage, ^^
[21:31] <alesage> oSoMoN, ack
[21:32] <ogra_> robru, not really anymore ... feel free to direct any snappy questions to us :P
[21:32] <ogra_> the whole channel re-org happened after we changed teams
[21:32] <robru> slangasek: what can you tell kgunn about 'u-d-f query'? I'm not familiar with that
[21:32] <kgunn> not so much about query but the result :)
[21:32] <kgunn> for flo
[21:33] <kgunn> vs mako i get all the combos i want....
[21:33] <robru> kgunn: slangasek did the channel reorg, so I guess he's the guy.
[21:33] <ogra_> all i know is that it suppresses all -proposed channels on purpose
[21:33] <kgunn> ta
[21:33]  * kgunn is gonna bet money he's lighting fireworks and saying hold my beer right about now
[21:34] <ogra_> flo might not have a stable entry simply because it isnt on the QA list for stable releases ?
[21:34] <slangasek> right, nobody's promoting any flo images to stable
[21:34] <charles> kgunn, lol
[21:34] <slangasek> because they wouldn't be "stable"
[21:34] <ogra_> http://system-image.ubuntu.com/ubuntu-touch/stable/ ... no flo in any of the subdirs
[21:34] <slangasek> AIUI there's been zero qa on flo for the past 6 months
[21:34] <kgunn> slangasek: but if i want vivid+overlay on flo...what do i do ?
[21:34] <ogra_> yep
[21:34] <slangasek> kgunn: ubuntu-touch/rc-proposed/ubuntu - which is one of the hidden developer-only channels
[21:35] <kgunn> cool....thanks
[22:15] <ogra_> slangasek, so with adduser and shadow being patched for extrausers support in wily i was wondering if there is any benefit to sync that into the overlay PPA
[22:16] <slangasek> ogra_: I guess it's not all that useful on its own, but only if someone is going to do the work to make use of it higher up the stack
[22:17] <ogra_> well, you could add new users on a phone
[22:17] <ogra_> without hacking the files manually