=== salem_ is now known as _salem === _salem is now known as salem_ === salem_ is now known as _salem [04:30] morning [05:10] I wonder what abyss now is in question [05:10] Mirv: abyss means the packages are nowhere but the original ppa [05:11] Mirv: indeed I've busted publication. I'm on it [05:12] or... actually... [05:12] robru: yes, I know what it means, but I also know it didn't go into any queue etc [05:12] robru: busted publication might explain it (but that "or..." does not) [05:13] my first thought was that someone has accidentally converted Feature Freeze into All Stop Freeze :) [05:13] Mirv: sorry this always bites me. jenkins runs exclusively python3 but publishing runs in python2 and so it always explodes when I commit python3isms to trunk [05:13] robru: no problem, I'm happy that I caught this early [05:14] Mirv: ok I think I have a fix but it's just a guess for now. we'll find out within 5 minutes. [05:15] so it seems (opened the commit log) ok, let's see [05:16] Mirv: uhhhhh... not sure what's happening now. I fixed the original traceback it seems but now some expected output is missing, not sure what it's doing. [05:18] Mirv: oh ok, it looks good now. that was a really strange delay though [05:18] veebers: yeah the last autopilot silo never landed [05:18] robru: right, now it's there [05:19] robru: oh what, really? I thought it had (I'm sure we had a convo about it landing) [05:19] veebers: we had a convo about me publishing it. it's been stuck in proposed since then [05:20] robru: ah I see, me misunderstanding then. What actions do I need to take at this poinr about that [05:20] right there's a regression on autopilot-gtk autopkgtest claimed http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#autopilot [05:20] point* [05:20] * veebers looks [05:21] veebers: yeah what Mirv said. it's possible the failure is unrelated, if so you may want to poke somebody in #ubuntu-release to see if they can wave you through. if not you need to fix the bug and republish [05:23] robru, Mirv: Ah right, it appears that something has changed in wily that autopilot-gtk needs to take into account now. I'll have to look into that [05:24] veebers: alright I'm way EOD, Mirv should be able to publish for you when you're ready [05:26] robru: ack thanks [05:26] you're welcome [05:27] Mirv: FYI, I'm about to EOW and head to an appointment so It's unlikely that I'll be able to do anything about this until Monday [05:39] veebers: alright [07:17] hey trainguards, may i ask for a silo for request 216? [07:17] pstolowski: you can assign your own now [07:18] robru, ah, I didn't know that; indeed, thanks :) [07:18] pstolowski: you are empowered! ;-) [07:18] pstolowski: I'm not here. Mirv can help if you hit any issues [07:19] robru, sure, thanks! [07:19] * pstolowski feels truly empowered [07:22] pstolowski: you're welcome [07:25] pstolowski: congrats on your first own assigning :) [07:26] robru fails at convincing that he's not here [07:30] Mirv: ssshhh I'm sleeping [07:30] Zzzzzzzzz [07:31] :) [07:31] Mirv: OK goodnight! [07:42] hmm, I should automate this "wipe device clean" a bit more.. setting writable, skipping intros etc [08:15] pete-woods: does dual landing for hud make any sense? I know libhud2 is on the images but probably not used for anything? [08:16] Mirv: yeah that's a fair point. I guess we could just land for wily [08:17] pete-woods: alright. reconfiguring and publishing for wily only. [08:17] Mirv: thanks :) [08:17] otherwise QA will get shivers from something landing on an image without their approval [08:17] they already said they aren't interested in this silo (https://trello.com/c/9tB8Royf/2209-211-ubuntu-landing-030-hud-pete-woods) FYI [08:18] I obviously ran my own checks (i.e. ran the test plan myself) that it still works [08:18] pete-woods: ah :) but it's of no benefit on the phone anyway? [08:18] indeed [08:18] right, better not touch the overlay then [08:19] I hadn't realised that QA weren't interested in the legacy desktop, tbh [08:19] that's changed since last time I landed HUD [08:19] wonder if this means we don't check if any of the indicators (which are used on both desktop and touch) work on desktop when landing [08:19] pete-woods: well they are not interested in the legacy desktop if the package is being landed to overlay PPA which is not in use there [08:20] pete-woods: yeah more generally too you're probably correct, this would change towards 16.04 LTS probably. the traditional desktop development has been mostly "upstream assures it's good" [08:21] Mirv: well of course I never break anything ;) [08:21] Mirv, my point was if it's for the legacy desktop on vivid it should be an SRU [08:21] pete-woods: well that's a given! :) [08:22] jibel: yes, I understood that and that's correct [08:22] and follow the SRU process [08:22] but not worth it as such [08:22] indeed [08:22] it's not actually got any serious bugfixes [08:22] there's a small memory leak of a string or two [08:22] but not worth an SRU [08:23] ogra_: are you around to ack hud removing unity-voice dependency and some valgrind changes? https://ci-train.ubuntu.com/job/ubuntu-landing-030-2-publish/lastSuccessfulBuild/artifact/hud_packaging_changes.diff [08:23] if it's the legacy desktop on wily, just land it if it doesn't require a FFe [08:29] sil2100, sorry, we're getting a new washing machine and they just called they will deliver in 10-15min so i have to skip today ... [08:29] Mirv, ^^^ after that :) [08:29] ogra_: ACK [08:29] ogra_: I WISH I had my new washing machine, ordered last Sunday, clothes are piling up! [08:29] ogra_: I so envy you! [08:31] need a wifi enabled laundrette [08:31] You can then guard against this happening while you're there:- https://www.youtube.com/watch?v=8-V8wd_aGPI [09:44] Mirv, hey, may I ask you kick the build for ppc64el only? occasional test failure on ppc bites us from time to time [09:45] Mirv, in silo 31 [10:20] pstolowski: ok [10:20] building, let's see if it needs a couple of retries [10:21] pstolowski: it's also possible for you to skip ppc unit tests, it's not we're going to need running scopes on ppc hardware extremely soon [10:21] pstolowski: example at http://anonscm.debian.org/cgit/pkg-kde/qt/qtdeclarative.git/tree/debian/rules?h=ubuntu [10:22] line 15 + 71-75 [10:23] Mirv, yeah, that's a good idea, thanks for that [10:24] or mostly just 15 + 71 + endif [10:36] Mirv: simpler and more robust (because it won't break if one architecture name is a substring of another): ifeq (,$(filter $(DEB_HOST_ARCH),$(testskip_architectures))) [10:37] Mirv: whoops, I mean ifeq (,$(filter $(testskip_architectures),$(DEB_HOST_ARCH))) I think [10:42] cjwatson: right, thank you for improving on it [10:44] thanks cjwatson! [10:46] ogra_: how's the washing machine and the requested ack? :) [10:46] Damn those not working shortcuts [10:50] Mirv, can you re-post the link, i dont have the backlog on this machine [10:50] ogra_: https://ci-train.ubuntu.com/job/ubuntu-landing-030-2-publish/lastSuccessfulBuild/artifact/hud_packaging_changes.diff [10:51] and the washing machine is still sitting cuddly wrapped in its styroform dress at the top of my basement stairs :) [10:52] sil2100: do you have history if archive admins agree that something was in queue before FF if the CI Train package was requested a binNEW review before FF? the problem is I've been trying now 5-6 times asking for review on Wed, Thu and today, but now the FF is in and it would be a bit silly to require FFe. it's just unfortunate technical problem that the CI Train publishings can't be done since they ov [10:52] ercome binary NEW queue [10:52] ogra_: ok :) I finally got SMS that no washing machine for me today, only on Monday evening [10:52] hah, you too ? [10:53] ogra_: after 10 years of serving well, it ceased to be... [10:53] lol, what a coincidence [10:53] indeed [10:54] Mirv: feature freeze has always been interpreted as "if you got it in before FF and then it's sat in a queue, the delay is not your problem" [10:54] cjwatson: yes, the definition of the queue is the problem, since with CI Train the queue means "ask on #ubuntu-release to look over at the PPA, then publish bypassing the queue" [10:55] Mirv, ACK, looks ok to me [10:55] ogra_: thanks! [10:55] Mirv: I'll look shortly anyway [10:55] I don't think it needs an FFe, it was ready beforehand, but we should avoid taking too long [10:56] funny to have valgrind as build dep ... poor builders :) [10:56] (shortly => after the people currently trying to get out of this house to go on holiday have finished, since it's a bit noisy right now) [10:57] cjwatson: thank you, and no pressure, I'll just keep on asking once or twice a day until I get hold of someone who more routinely does the reviews [10:57] in case something else comes up === marcusto_ is now known as marcustomlinson [11:31] sil2100: bzoltan_: with Mir 0.15 in wily the 009 silo should be made vivid only (if it'd to be landed). UITK can still be merged and Mir'd be made a source only upload at which point Mir team would handle themselves the vivid overlay 0.14 patch <-> wily 0.15 release delta [11:32] of course, the emulator is not trivially usable at its current state even with 009 [11:39] kgunn: you handling silo 17? ↑↑ [11:41] sil2100: bzoltan_: I see #elsewhere that Kevin is already executing that plan to make it vivid only [11:48] tsdgeos: yeah, i think gerry is actually fiddling with it...he just updated an mp [11:48] oki [11:49] Mirv, kgunn: ok, just be sure to at least prep a landing that will have the wily changes staged somewhere [11:50] Mirv: still investigating the no-shortcuts bug in appmenu-qt5, but so far it seems we might need to distro-patch (and forward to Qt5) a modification that would help us forwarding shortcut execution to the platform theme [11:51] sil2100, we should probably land 25 even if the string is not perfect then we'll iterate if the translation is too incorrect in some languages [11:51] Yeah, +1 on that [11:51] The sooner this lands, the sooner we get the translations [11:52] rvr, I'm approving 25 [11:52] it's difficult to find the right line in bileto from an silo number [11:53] * greyback has to search [11:53] I usually use the dashboard and click on the ID to get me to the bileto landing [11:53] jibel: Ack [11:54] Publishing [11:54] sil2100: So, do you know have powers to generate langpacks? [11:54] it'd be more natural to sort by silo number instead of request id IMO [11:55] bfiller, kenvandine: could you guys later create a wily silo with the same translation change? [11:55] rvr: well, I could, but not entirely - there are different steps here and there [11:55] First we need to get the translations in [11:55] Then I can poke the right people [11:58] jibel: the number in dashboard could actually easily be a link to an anchored line in the bileto [11:58] filing a wishlist item [11:58] jibel: oh, actually it is already a link [11:59] ..like sil said [11:59] good that I found about it too, I didn't know :) [12:03] Mirv, yeah same on the trello board, I added a link from the card to the request. But for both cases it requires to open 2 applications just to find a request in bileto [12:03] or user ctrl+f [12:03] use* [12:04] and bileto and the dashboard are a bit redundant, should be the same app === _salem is now known as salem_ [12:09] I suppose that's the plan for the nearest future [12:24] Mirv, bah, empty changelog in unity-system-compositor [12:24] (train bug ??) [12:33] ogra_: must be, and same for qtmir. both of the MP:s do have a commit message. [12:35] hmm, i thought it would block on that [12:37] sil2100, yeah, wily had a manual upload that was never synced back to trunk, we need to get that merged back into trunk first [12:56] kenvandine, sil2100 : seeing errors with silo 25 publish, do we know how to fix this? [12:56] bfiller: it copied the packages correctly at least, let me take a look at it [12:56] sil2100, thx [12:57] sil2100: if i remove an mp/project from a silo but what is left behind is still good...does it _have_ to be rebuilt? [12:57] silo 9 uitk still good, but i need to pull mir out as it's a dual landing... [12:58] kenvandine, bfiller: looks like it was a one-off issue, now it's all good [12:59] sil2100, great, thanks [12:59] kgunn: hey, if you remove a whole project then it shouldn't require a rebuild - besides the case where the other packages built against the project you want to remove and might not work with some other versions [12:59] But I suppose that's not the case here [12:59] sil2100: thanks [12:59] bfiller, sil2100: to land it in wily, i need to merge the changelog changes from wily into trunk and do a new dual landing [13:00] kenvandine: ok, so it's still dual landable? [13:00] it's a major version bump, so i was avoiding doing that until we knew vivid was good to go [13:00] yeah [13:00] sil2100: do i just remove and then do a reconfig? or do you need to manunally remove the old packages?...or is it all just magic? [13:00] sil2100, during the gcc5 transition they bumped the major version to match the soname [13:01] i think [13:01] no code changes, just changelog i believe [13:01] sil2100, i just didn't want to do that to get the one fix in ota6 [13:01] kenvandine: good choice I suppose [13:02] sil2100, so is it safe to fix that now? [13:02] i guess i should wait until you spin an image [13:02] kgunn: remove them from bileto and reconfigure the silo (with the assign button) and I'll remove the leftover packages from the PPA [13:02] kgunn: what silo is it? [13:02] it'll be silo 9 [13:02] sil2100: ^ [13:02] kenvandine: wait a bit, we never know if we won't require a trust-store fix or something :) [13:03] kenvandine: but I suppose a silo can be prepared beforehand [13:03] kgunn: on it - removing mir [13:03] yeah, but i was going to push the changelog change right to trunk [13:03] so if we need another fix, it would include that [13:03] sil2100, i think if i included the version bump in a MR citrain would get angry, right? [13:04] kenvandine: hm, no, it might actually just work, we allow modifications of the changelog, although there are certain cases that can cause it to go highwire [13:04] i thought the version bump would mess up the generated version [13:05] i can give it a try I guess :) [13:08] No, when you bump the version number in a MP for the train, it will try to interpret its upstream version and append the CI Train bits to it [13:08] As long as it's UNRELEASED of course ;) [13:47] sil2100: robru: are there plans to handle git for merge proposals leading to uploads via ci-train? does that already work? [13:47] morphis: ^ [13:48] cyphermox: currently only bzr works sadly, CI Train has a hard-assumption that everything is in bzr [13:48] ok [13:48] But I know there are plans to include git support [13:48] just curious :) [13:48] yeah, colin mentiojed plans [13:48] -j [13:48] I'm asking about ci train, not LP [13:48] But, as you know, there are plans for like 200 other things too ;p [13:48] yes. [13:49] hehe, yeah [13:49] So sadly not sure when we'll get to that ;/ [13:49] no worries, just trying to get a picture of things [13:49] cyphermox, well, MP support in LP is a prerequisite for the train [13:49] ogra_: sure. [13:50] ogra_: I already see a button on pages so, I figure some things exist; not that it's critical for me. [13:51] * ogra_ still prefers bzr over git ... but i guess i cant stay forever in the past :) [13:53] I still prefer bzr as a handy distro tool whenever I need to quickly do something, but I've managed to migrate my normal packaging workflow to git otherwise [13:56] I used git a lot in the past so I like it, but I don't have anything against bzr really, it works well for everything I need [13:57] git needs configuration to do everything and it can do everything, bzr has well thought out defaults, is simpler and better integrated [14:00] jibel, hello! are you ok if silo 31 is published without qa (a small wily packaging change), or do you want to take a look? [14:04] ogra_: it's not the past. it's just a better future :) [14:04] heh [14:06] jibel: ^ [14:10] pstolowski, yeah it's wily only, we don't verify them manually [14:10] greyback, thanks. Someone will pick it up [14:10] thanks! [14:12] jibel, thanks [14:15] ogra_: to clarify, I said it ought to happen, but I have no plans for that myself [14:16] ah [14:16] ogra_: but git MP support certainly exists in LP [14:16] I'm not aware of any missing prerequisites at this point [14:16] ah, then the train should be portable (technically) [14:23] hmmm [14:24] pstolowski: ok, it seems we have some CI Train bug [14:25] The package has an empty changelog entry even though the merge has a proper commitlog [14:26] sil2100, the commit message was added after packages have been built [14:26] Ah, ok... [14:26] pstolowski: will require a rebuild then [14:26] sil2100, ok, doing [14:26] Thanks! [14:46] cihelp: unity-system-compositor and qtmir boottests fail with mir 0.15 release since the mir drivers were updated (Which get updated through the seeds). Can you help confirm and pass them? [14:55] AlbertA, is there a new mir driver package too? The last time we ran into a problem I thought we learned that all we needed to do was pull in mir-graphics-drivers-android [14:56] fginther: do the boottest do that now? [14:56] AlbertA, yes [14:58] fginther: umm... [15:02] AlbertA, the base image being used is a little stale, would that make a difference? [15:02] fginther: potentially, like if protobuf-lite9v5 is not there [15:03] but wouldn't that be installed through the deps? [15:03] AlbertA, I would assume so. [15:04] fginther: I'll try locally here.... where do I see which image was used? [15:04] AlbertA, http://d-jenkins.ubuntu-ci:8080/job/wily-boottest-unity-system-compositor/ws/provision.log/*view*/ [15:04] davmor2: jibel: So, attaching several images to an MMS and changing contact's picture several times with both the camera and the gallery show no ghosts in the spread and there are no crashes. This is krillin with silo 17. [15:05] AlbertA, if you can't view that, the answer is "Flashing version 7 from ubuntu-touch/devel-proposed-g++5/ubuntu" [15:05] \o/ [15:05] rvr, okay can you run the qtmir test plan too + some exploratory tests [15:06] rvr, I'm testing it too [15:06] jibel: Would be good to check it also in arale [15:06] rvr, yeah, I am on arale [15:16] grumph, three time this week that the promixity captor seems to not work at the end of a call [15:17] like I take the phone away from my ear and it doesn't turn the screen on [15:17] didi anybody else noticed such issues on rc-proposed bq? [15:17] fginther, did you get CI reconfigured for content-hub? [15:17] kenvandine, yes, it should be on vivid+overlay now [15:18] fginther, awesome, thanks [15:19] jibel: I'm seeing "no data sources available" untranslated in the greeter [15:21] rvr, this bug has been there since image 1 [15:21] I thought it was fixed long time ago [15:22] bug 1398016 [15:22] bug 1398016 in libusermetrics (Ubuntu) "In the "unlock" screen the message "No data sources available" still in English after change the system language to pt-BR" [Medium,Confirmed] https://launchpad.net/bugs/1398016 [15:23] cjwatson: ping [15:23] sil2100: Please tell me what you want and I'll reply when I'm around. [15:23] jibel: Amazing [15:23] cjwatson: hey! So, I wanted to know: we pushed a new version of trust-store to the bzr trunk with additions to the translation templates [15:24] cjwatson: I see that those are available in the trust-store vivid translations, but they did not appear in the ubuntu-rtm/15.04 translations [15:25] cjwatson: shouldn't uploads to the overlay + bzr trunk cause the templates to be imported automatically to 15.04? [15:25] sil2100: Should do [15:25] sil2100: I'm in the library with no VPN right now, can't check logs [15:26] cjwatson: for instance, looking here: https://translations.launchpad.net/trust-store/trunk/+pots/trust-store/pl/+translate <- the template is present, but in https://translations.launchpad.net/ubuntu-rtm/15.04/+source/trust-store/+pots/trust-store/pl/+translate it is not [15:27] cjwatson: is wgrant around to help us out if anything? [15:28] sil2100: He's on holiday this week, back next week [15:28] sil2100: I'll have a look when I get home and see if it's something obvious at the copy job level [15:28] cjwatson: ok, thanks :) [15:28] Is this OMG urgent, i.e. I should get up and leave now? :) [15:29] Not OMG urgent, no worries ;) We're anyway waiting for one more template change before I would request an export [15:29] So we're anyway blocked [15:29] But I'd like to get it into translators hands soonish [15:30] So take your time and we would be grateful if you could take a look once you're back [15:30] OK [16:00] sil2100, can you free silo 38, no longer need it [16:01] jhodapp: ACK [16:02] thanks [16:02] jibel: There ain't no ghosts [16:03] rvr, cool, but is there anything else? [16:03] jibel: The silo seems to work fine, I run the test plan and did exploratory testing and haven't found anything wrong. Have you? [16:05] ping cihelp. I need some job parameters on core app jenkins modified. both ubuntu-docviewer-app-ci and ubuntu-docviewer-app-ci-autolanding need to be updated to point at lp:ubuntu-docviewer-app/reboot rather than lp:ubuntu-docviewer-app [16:05] rvr, actually I see lot of shadows [16:05] jibel: :-/ [16:05] at least 6 shadow windows in the spread [16:05] kgunn, ^ [16:05] jibel: In arale? [16:06] yes [16:06] Installing silo 17 there [16:06] but overall it's a huge improvement no crash and shadows are rather difficult to trigger [16:07] rvr, if you didn't find anything I'd +1 the silo [16:08] rvr, I think shadows in the spread are apps shot by OOM killer [16:09] Ouch, pstolowski left [16:09] greyback_, ^ on arale with silo 17 [16:09] jibel: Hmm [16:09] jibel: right... [16:09] jibel, rvr, did you notice issues with the proximity detector nor turning the screen on when getting the phone off your ear to hang up a call? [16:09] so it's not perfect but no crashing [16:09] kgunn, yeah, it's a +1 from me [16:10] rvr, what do you think? [16:10] jibel: Yeah, +1 [16:10] seb128, yes [16:10] jibel, is that reported? [16:10] seb128, if the call last longer than the screen timeout [16:11] seb128, not sure [16:11] that was not set as ota blocker? [16:11] it's quite visible/annoying [16:12] let me check if I find a bug [16:13] jibel, bug #1483127 [16:13] bug 1483127 in telephony-service (Ubuntu) "Proximity does not turn screen on during a call" [Undecided,New] https://launchpad.net/bugs/1483127 [16:13] seb128, thanks [16:13] yw [16:13] sil2100, ^ [16:13] it was reported 10 days ago :-/ [16:14] boiko, ^ is that one for you? [16:14] That's really bad [16:14] kgunn: ^ (since bfiller is not around) [16:15] kgunn: could you take care of triaging it? I leave it up to you guys to decide if it's a blocker or not [16:15] But for me it would be pretty annoying and visible [16:18] +1 [16:18] sil2100, it's annoying and a regression in OTA6, it fell through the cracks [16:18] it's also discussed on the other IRC [16:18] Right, I can reproduce that proximity sensor bug [16:19] 17 approved [16:20] sil2100: The trust-store build doesn't appear to produce a translations tarball [16:21] sil2100: So that's why the scheme for copying those translations tarballs into 15.04 didn't work. In fact, I've no idea how they got into vivid [16:21] cjwatson: huh? But why do the templates appear in the trunk version? And we also have some existing translation templates for trust-store in ubuntu-rtm/15.04 [16:21] hmm [16:21] The ones that are there would have been copied from vivid [16:21] Maybe they were previously uploaded manually? [16:21] Or something [16:22] Maybe, not sure... I think we'll need the trust-store people on this one [16:22] kenvandine: do you know who could help out with this? ^ [16:22] Or there might be something more sinister going on [16:22] It could be a failure of something in the chain that arranges for pkgstriptranslations to run [16:23] It does have .mo files [16:23] not sure... [16:24] tvoss, it would be really great to get that translation fix in wily :) [16:24] Not only in wily [16:25] Would be good to have the translations working anywhere, since as cjwatson mentioned it seems that we can't really get the template files imported into LP [16:25] Either because the build is not creating them or for some other reasons [16:25] I'm still investigating [16:25] cjwatson: thanks [16:25] cjwatson, kenvandine, sil2100, trust-store is in universe and not using X-Ubuntu-Use-Langpack: yes [16:25] that's probably why it doesn't import translations? [16:25] seb128: built in a PPA, shouldn't matter I thought [16:25] Then how did we get them before? [16:26] sil2100, not sure if we'll have other fixes, if not could you copy the silos approved to the snapshot and kick an image before you EOD? [16:26] Oh [16:26] jibel: ACK, sure thing [16:28] It's a non-virtual PPA, so it translates it to the component in the primary archive and pretends it's primary, so universe, right. But as sil2100 says that still doesn't explain why it worked before [16:28] The .mo files are there, so worst case, you could jam translations manually into the package and they won't be stripped [16:29] But I think it would be better to set X-Ubuntu-Use-Langpack: yes [16:29] kenvandine: ^- [16:29] tvoss, ^^ could you? if you're still around [16:30] sil2100: trust-store was in main for a while [16:30] https://launchpad.net/ubuntu/+source/trust-store/+publishinghistory [16:30] So that's probably why [16:30] Oh? [16:30] hum, did the call start/end sound changed [16:30] I assume whatever pulled it in stopped doing so [16:30] it sounds really unpleasant and I didn't have that feeling before [16:30] OK, so mystery solved [16:31] Except that I'm not entirely sure how the modified translation got into vivid, but that could have been manual action [16:31] translation? [16:31] you mean template? [16:32] we did some template uploads through the webui for those content store new strings, but that was for wily I think [16:32] fginther: so on the bootest failures... for unity-system-compositor is that it will be a newer mir server version (running the new driver) and qtmir nested server since it's not updated will attempt to talk to the newer server but using an older driver version) which won't work so unity8 won't start [16:32] I mean template yes [16:33] fginther: for qtmir is similar but in reverse....it will be a newer nested server trying to talk to an older mir server, which also won't work [16:33] I could probably search webapp logs for it but it would take ages and I think would ultimately not be very interesting. X-Ubuntu-Use-Langpack: yes seems like the right answer [16:34] cjwatson, well, in any case I uploaded a new template to https://translations.launchpad.net/ubuntu/wily/+source/trust-store/+pots/trust-store/+upload this morning [16:34] dunno about other series [16:34] AlbertA, so if unity-system-compositor and qtmir were updated together it would work? [16:34] fginther: right [16:37] AlbertA, ack. I'll give them a pass then [16:42] seb128: could you copy the new template from the overlay-ppa version of trust store to the ubuntu-rtm/15.04 series? [16:42] * sil2100 doesn't yet know how to do that [16:42] ;) [16:43] sil2100, done from https://translations.launchpad.net/ubuntu-rtm/15.04/+source/trust-store/+pots/trust-store/+upload [16:45] balloons, I've added that to the list, will try to get it done today [16:45] fginther, ack and ty [16:46] sil2100, imported [16:46] https://translations.launchpad.net/ubuntu-rtm/15.04/+source/trust-store/+pots/trust-store/fr/+translate [16:46] :-) [16:47] \o/ [16:47] seb128: thankz [16:47] :) [16:47] seb128: for me this link says: "Not allowed here" [16:47] The +upload one [16:47] sil2100, not enough power yet ;-) [16:48] I feel so... so weak! [17:02] fginther, not as big a deal, but I noticed http://91.189.93.70:8080/job/ubuntu-calendar-app-autolanding/1407/console didn't fail when it should have. The landing portion of the job 'failed', but it shows green oddly enough === joc_ is now known as joc|away [17:04] balloons, ah thanks. I want to say that's a known bug, but I'll have to look. If not I'll add it. [17:05] sil2100: why if unity has been uploaded to distro (landing-019), upstream has not been updated yet? I see that xpathselect has not been updated, but... Shouldn't upstream been updated before (or together with) downstream? [17:05] sil2100: it looks weird in this way... I guess that when a package lands then upstream should be updated promptly [17:11] Trevinho: silo 19 is not landed... The branches get merged after all packages migrate [17:12] robru: i see, but.... since unity landed in distro I was expecting its branches to be merged... So doing it *per project*, not *per silo* [17:13] Trevinho: yeah, no. Silos are handled per silo. If you want to merge that one you can trigger it manually but then you'll lose reporting on the migration status of xpathselect [17:14] Trevinho: also if unity depends on changes in xpathselect you should have noted that in the packaging so they'd migrate together [17:14] robru: it's not an hard dependency... [17:15] robru: othewise I would have done it [17:15]