/srv/irclogs.ubuntu.com/2015/08/21/#ubuntu-ci-eng.txt

=== salem_ is now known as _salem
=== _salem is now known as salem_
=== salem_ is now known as _salem
Mirvmorning04:30
MirvI wonder what abyss now is in question05:10
robruMirv: abyss means the packages are nowhere but the original ppa05:10
robruMirv: indeed I've busted publication. I'm on it05:11
robruor... actually...05:12
Mirvrobru: yes, I know what it means, but I also know it didn't go into any queue etc05:12
Mirvrobru: busted publication might explain it (but that "or..." does not)05:12
Mirvmy first thought was that someone has accidentally converted Feature Freeze into All Stop Freeze :)05:13
robruMirv: sorry this always bites me. jenkins runs exclusively python3 but publishing runs in python2 and so it always explodes when I commit python3isms to trunk05:13
Mirvrobru: no problem, I'm happy that I caught this early05:13
robruMirv: ok I think I have a fix but it's just a guess for now. we'll find out within 5 minutes.05:14
Mirvso it seems (opened the commit log) ok, let's see05:15
robruMirv: 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:16
robruMirv: oh ok, it looks good now. that was a really strange delay though05:18
robruveebers: yeah the last autopilot silo never landed05:18
Mirvrobru: right, now it's there05:18
veebersrobru: oh what, really? I thought it had (I'm sure we had a convo about it landing)05:19
robruveebers: we had a convo about me publishing it. it's been stuck in proposed since then05:19
veebersrobru: ah I see, me misunderstanding then. What actions do I need to take at this poinr about that05:20
Mirvright there's a regression on autopilot-gtk autopkgtest claimed http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#autopilot05:20
veeberspoint*05:20
* veebers looks05:20
robruveebers: 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 republish05:21
veebersrobru, 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 that05:23
robruveebers: alright I'm way EOD, Mirv should be able to publish for you when you're ready05:24
veebersrobru: ack thanks05:26
robruyou're welcome05:26
veebersMirv: 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 Monday05:27
Mirvveebers: alright05:39
pstolowskihey trainguards, may i ask for a silo for request 216?07:17
robrupstolowski: you can assign your own now07:17
pstolowskirobru, ah, I didn't know that; indeed, thanks :)07:18
robrupstolowski: you are empowered! ;-)07:18
robrupstolowski: I'm not here. Mirv can help if you hit any issues07:18
pstolowskirobru, sure, thanks!07:19
* pstolowski feels truly empowered07:19
robrupstolowski: you're welcome07:22
Mirvpstolowski: congrats on your first own assigning :)07:25
Mirvrobru fails at convincing that he's not here07:26
robruMirv: ssshhh I'm sleeping07:30
robruZzzzzzzzz07:30
Mirv:)07:31
robruMirv: OK goodnight!07:31
Mirvhmm, I should automate this "wipe device clean" a bit more.. setting writable, skipping intros etc07:42
Mirvpete-woods: does dual landing for hud make any sense? I know libhud2 is on the images but probably not used for anything?08:15
pete-woodsMirv: yeah that's a fair point. I guess we could just land for wily08:16
Mirvpete-woods: alright. reconfiguring and publishing for wily only.08:17
pete-woodsMirv: thanks :)08:17
Mirvotherwise QA will get shivers from something landing on an image without their approval08:17
pete-woodsthey already said they aren't interested in this silo (https://trello.com/c/9tB8Royf/2209-211-ubuntu-landing-030-hud-pete-woods) FYI08:17
pete-woodsI obviously ran my own checks (i.e. ran the test plan myself) that it still works08:18
Mirvpete-woods: ah :) but it's of no benefit on the phone anyway?08:18
pete-woodsindeed08:18
Mirvright, better not touch the overlay then08:18
pete-woodsI hadn't realised that QA weren't interested in the legacy desktop, tbh08:19
pete-woodsthat's changed since last time I landed HUD08:19
pete-woodswonder if this means we don't check if any of the indicators (which are used on both desktop and touch) work on desktop when landing08:19
Mirvpete-woods: well they are not interested in the legacy desktop if the package is being landed to overlay PPA which is not in use there08:19
Mirvpete-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:20
pete-woodsMirv: well of course I never break anything ;)08:21
jibelMirv, my point was if it's for the legacy desktop on vivid it should be an SRU08:21
Mirvpete-woods: well that's a given! :)08:21
Mirvjibel: yes, I understood that and that's correct08:22
jibeland follow the SRU process08:22
Mirvbut not worth it as such08:22
pete-woodsindeed08:22
pete-woodsit's not actually got any serious bugfixes08:22
pete-woodsthere's a small memory leak of a string or two08:22
pete-woodsbut not worth an SRU08:22
Mirvogra_: 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.diff08:23
jibelif it's the legacy desktop on wily, just land it if it doesn't require a FFe08:23
ogra_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
ogra_Mirv, ^^^ after that :)08:29
sil2100ogra_: ACK08:29
Mirvogra_: I WISH I had my new washing machine, ordered last Sunday, clothes are piling up!08:29
Mirvogra_: I so envy you!08:29
popeyneed a wifi enabled laundrette08:31
popeyYou can then guard against this happening while you're there:- https://www.youtube.com/watch?v=8-V8wd_aGPI08:31
pstolowskiMirv, hey, may I ask you kick the build for ppc64el only? occasional test failure on ppc bites us from time to time09:44
pstolowskiMirv, in silo 3109:45
Mirvpstolowski: ok10:20
Mirvbuilding, let's see if it needs a couple of retries10:20
Mirvpstolowski: 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 soon10:21
Mirvpstolowski: example at http://anonscm.debian.org/cgit/pkg-kde/qt/qtdeclarative.git/tree/debian/rules?h=ubuntu10:21
Mirvline 15 + 71-7510:22
pstolowskiMirv, yeah, that's a good idea, thanks for that10:23
Mirvor mostly just 15 + 71 + endif10:24
cjwatsonMirv: 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:36
cjwatsonMirv: whoops, I mean   ifeq (,$(filter $(testskip_architectures),$(DEB_HOST_ARCH)))   I think10:37
Mirvcjwatson: right, thank you for improving on it10:42
pstolowskithanks cjwatson!10:44
Mirvogra_: how's the washing machine and the requested ack? :)10:46
sil2100Damn those not working shortcuts10:46
ogra_Mirv, can you re-post the link, i dont have the backlog on this machine10:50
Mirvogra_: https://ci-train.ubuntu.com/job/ubuntu-landing-030-2-publish/lastSuccessfulBuild/artifact/hud_packaging_changes.diff10:50
ogra_and the washing machine is still sitting cuddly wrapped in its styroform dress at the top of my basement stairs :)10:51
Mirvsil2100: 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 ov10:52
Mirvercome binary NEW queue10:52
Mirvogra_: ok :) I finally got SMS that no washing machine for me today, only on Monday evening10:52
ogra_hah, you too ?10:52
Mirvogra_: after 10 years of serving well, it ceased to be...10:53
ogra_lol, what a coincidence10:53
Mirvindeed10:53
cjwatsonMirv: 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
Mirvcjwatson: 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:54
ogra_Mirv, ACK, looks ok to me10:55
Mirvogra_: thanks!10:55
cjwatsonMirv: I'll look shortly anyway10:55
cjwatsonI don't think it needs an FFe, it was ready beforehand, but we should avoid taking too long10:55
ogra_funny to have valgrind as build dep ... poor builders :)10:56
cjwatson(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:56
Mirvcjwatson: 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 reviews10:57
Mirvin case something else comes up10:57
=== marcusto_ is now known as marcustomlinson
Mirvsil2100: 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 delta11:31
Mirvof course, the emulator is not trivially usable at its current state even with 00911:32
tsdgeoskgunn: you handling silo 17? ↑↑11:39
Mirvsil2100: bzoltan_: I see #elsewhere that Kevin is already executing that plan to make it vivid only11:41
kgunntsdgeos: yeah, i think gerry is actually fiddling with it...he just updated an mp11:48
tsdgeosoki11:48
sil2100Mirv, kgunn: ok, just be sure to at least prep a landing that will have the wily changes staged somewhere11:49
sil2100Mirv: 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 theme11:50
jibelsil2100, we should probably land 25 even if the string is not perfect then we'll iterate if the translation is too incorrect in some languages11:51
sil2100Yeah, +1 on that11:51
sil2100The sooner this lands, the sooner we get the translations11:51
jibelrvr, I'm approving 2511:52
jibelit's difficult to find the right line in bileto from an silo number11:52
* greyback has to search11:53
sil2100I usually use the dashboard and click on the ID to get me to the bileto landing11:53
rvrjibel: Ack11:53
sil2100Publishing11:54
rvrsil2100: So, do you know have powers to generate langpacks?11:54
jibelit'd be more natural to sort by silo number instead of request id IMO11:54
sil2100bfiller, kenvandine: could you guys later create a wily silo with the same translation change?11:55
sil2100rvr: well, I could, but not entirely - there are different steps here and there11:55
sil2100First we need to get the translations in11:55
sil2100Then I can poke the right people11:55
Mirvjibel: the number in dashboard could actually easily be a link to an anchored line in the bileto11:58
Mirvfiling a wishlist item11:58
Mirvjibel: oh, actually it is already a link11:58
Mirv..like sil said11:59
Mirvgood that I found about it too, I didn't know :)11:59
jibelMirv, 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 bileto12:03
jibelor user ctrl+f12:03
jibeluse*12:03
jibeland bileto and the dashboard are a bit redundant, should be the same app12:04
=== _salem is now known as salem_
sil2100I suppose that's the plan for the nearest future12:09
ogra_Mirv, bah, empty changelog in unity-system-compositor12:24
ogra_(train bug ??)12:24
Mirvogra_: must be, and same for qtmir. both of the MP:s do have a commit message.12:33
ogra_hmm, i thought it would block on that12:35
kenvandinesil2100, yeah, wily had a manual upload that was never synced back to trunk, we need to get that merged back into trunk first12:37
bfillerkenvandine, sil2100 : seeing errors with silo 25 publish, do we know how to fix this?12:56
sil2100bfiller: it copied the packages correctly at least, let me take a look at it12:56
kenvandinesil2100, thx12:56
kgunnsil2100: 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
kgunnsilo 9 uitk still good, but i need to pull mir out as it's a dual landing...12:57
sil2100kenvandine, bfiller: looks like it was a one-off issue, now it's all good12:58
kenvandinesil2100, great, thanks12:59
sil2100kgunn: 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 versions12:59
sil2100But I suppose that's not the case here12:59
bfillersil2100: thanks12:59
kenvandinebfiller, sil2100: to land it in wily, i need to merge the changelog changes from wily into trunk and do a new dual landing12:59
sil2100kenvandine: ok, so it's still dual landable?13:00
kenvandineit's a major version bump, so i was avoiding doing that until we knew vivid was good to go13:00
kenvandineyeah13:00
kgunnsil2100: 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
kenvandinesil2100, during the gcc5 transition they bumped the major version to match the soname13:00
kenvandinei think13:01
kenvandineno code changes, just changelog i believe13:01
kenvandinesil2100, i just didn't want to do that to get the one fix in ota613:01
sil2100kenvandine: good choice I suppose13:01
kenvandinesil2100, so is it safe to fix that now?13:02
kenvandinei guess i should wait until you spin an image13:02
sil2100kgunn: remove them from bileto and reconfigure the silo (with the assign button) and I'll remove the leftover packages from the PPA13:02
sil2100kgunn: what silo is it?13:02
kgunnit'll be silo 913:02
kgunnsil2100: ^13:02
sil2100kenvandine: wait a bit, we never know if we won't require a trust-store fix or something :)13:02
sil2100kenvandine: but I suppose a silo can be prepared beforehand13:03
sil2100kgunn: on it - removing mir13:03
kenvandineyeah, but i was going to push the changelog change right to trunk13:03
kenvandineso if we need another fix, it would include that13:03
kenvandinesil2100, i think if i included the version bump in a MR citrain would get angry, right?13:03
sil2100kenvandine: hm, no, it might actually just work, we allow modifications of the changelog, although there are certain cases that can cause it to go highwire13:04
kenvandinei thought the version bump would mess up the generated version13:04
kenvandinei can give it a try I guess :)13:05
sil2100No, 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 it13:08
sil2100As long as it's UNRELEASED of course ;)13:08
cyphermoxsil2100: robru: are there plans to handle git for merge proposals leading to uploads via ci-train? does that already work?13:47
cyphermoxmorphis: ^13:47
sil2100cyphermox: currently only bzr works sadly, CI Train has a hard-assumption that everything is in bzr13:48
cyphermoxok13:48
sil2100But I know there are plans to include git support13:48
cyphermoxjust curious :)13:48
ogra_yeah, colin mentiojed plans13:48
ogra_-j13:48
cyphermoxI'm asking about ci train, not LP13:48
sil2100But, as you know, there are plans for like 200 other things too ;p13:48
cyphermoxyes.13:48
ogra_hehe, yeah13:49
sil2100So sadly not sure when we'll get to that ;/13:49
cyphermoxno worries, just trying to get a picture of things13:49
ogra_cyphermox, well, MP support in LP is a prerequisite for the train13:49
cyphermoxogra_: sure.13:49
cyphermoxogra_: I already see a button on pages so, I figure some things exist; not that it's critical for me.13:50
* ogra_ still prefers bzr over git ... but i guess i cant stay forever in the past :) 13:51
MirvI 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 otherwise13:53
sil2100I 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 need13:56
Mirvgit needs configuration to do everything and it can do everything, bzr has well thought out defaults, is simpler and better integrated13:57
pstolowskijibel, 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:00
dobeyogra_: it's not the past. it's just a better future :)14:04
ogra_heh14:04
greybackjibel: ^14:06
jibelpstolowski, yeah it's wily only, we don't verify them manually14:10
jibelgreyback, thanks. Someone will pick it up14:10
greybackthanks!14:10
pstolowskijibel, thanks14:12
cjwatsonogra_: to clarify, I said it ought to happen, but I have no plans for that myself14:15
ogra_ah14:16
cjwatsonogra_: but git MP support certainly exists in LP14:16
cjwatsonI'm not aware of any missing prerequisites at this point14:16
ogra_ah, then the train should be portable (technically)14:16
sil2100hmmm14:23
sil2100pstolowski: ok, it seems we have some CI Train bug14:24
sil2100The package has an empty changelog entry even though the merge has a proper commitlog14:25
pstolowskisil2100, the commit message was added after packages have been built14:26
sil2100Ah, ok...14:26
sil2100pstolowski: will require a rebuild then14:26
pstolowskisil2100, ok, doing14:26
sil2100Thanks!14:26
AlbertAcihelp: 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:46
fgintherAlbertA, 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-android14:55
AlbertAfginther: do the boottest do that now?14:56
fgintherAlbertA, yes14:56
AlbertAfginther: umm...14:58
fgintherAlbertA, the base image being used is a little stale, would that make a difference?15:02
AlbertAfginther: potentially, like if protobuf-lite9v5 is not there15:02
AlbertAbut wouldn't that be installed through the deps?15:03
fgintherAlbertA, I would assume so.15:03
AlbertAfginther: I'll try locally here.... where do I see which image was used?15:04
fgintherAlbertA, http://d-jenkins.ubuntu-ci:8080/job/wily-boottest-unity-system-compositor/ws/provision.log/*view*/15:04
rvrdavmor2: 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:04
fgintherAlbertA, if you can't view that, the answer is "Flashing version 7 from ubuntu-touch/devel-proposed-g++5/ubuntu"15:05
davmor2\o/15:05
jibelrvr, okay can you run the qtmir test plan too + some exploratory tests15:05
jibelrvr, I'm testing it too15:06
rvrjibel: Would be good to check it also in arale15:06
jibelrvr, yeah, I am on arale15:06
seb128grumph, three time this week that the promixity captor seems to not work at the end of a call15:16
seb128like I take the phone away from my ear and it doesn't turn the screen on15:17
seb128didi anybody else noticed such issues on rc-proposed bq?15:17
kenvandinefginther, did you get CI reconfigured for content-hub?15:17
fgintherkenvandine, yes, it should be  on vivid+overlay now15:17
kenvandinefginther, awesome, thanks15:18
rvrjibel: I'm seeing "no data sources available" untranslated in the greeter15:19
jibelrvr, this bug has been there since image 115:21
rvrI thought it was fixed long time ago15:21
jibelbug 139801615:22
ubot5bug 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/139801615:22
sil2100cjwatson: ping15:23
cjwatsonsil2100: Please tell me what you want and I'll reply when I'm around.15:23
rvrjibel: Amazing15:23
sil2100cjwatson: hey! So, I wanted to know: we pushed a new version of trust-store to the bzr trunk with additions to the translation templates15:23
sil2100cjwatson: I see that those are available in the trust-store vivid translations, but they did not appear in the ubuntu-rtm/15.04 translations15:24
sil2100cjwatson: shouldn't uploads to the overlay + bzr trunk cause the templates to be imported automatically to 15.04?15:25
cjwatsonsil2100: Should do15:25
cjwatsonsil2100: I'm in the library with no VPN right now, can't check logs15:25
sil2100cjwatson: 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 not15:26
sil2100cjwatson: is wgrant around to help us out if anything?15:27
cjwatsonsil2100: He's on holiday this week, back next week15:28
cjwatsonsil2100: I'll have a look when I get home and see if it's something obvious at the copy job level15:28
sil2100cjwatson: ok, thanks :)15:28
cjwatsonIs this OMG urgent, i.e. I should get up and leave now? :)15:28
sil2100Not OMG urgent, no worries ;) We're anyway waiting for one more template change before I would request an export15:29
sil2100So we're anyway blocked15:29
sil2100But I'd like to get it into translators hands soonish15:29
sil2100So take your time and we would be grateful if you could take a look once you're back15:30
cjwatsonOK15:30
jhodappsil2100, can you free silo 38, no longer need it16:00
sil2100jhodapp: ACK16:01
jhodappthanks16:02
rvrjibel: There ain't no ghosts16:02
jibelrvr, cool, but is there anything else?16:03
rvrjibel: The silo seems to work fine, I run the test plan and did exploratory testing and haven't found anything wrong. Have you?16:03
balloonsping 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-app16:05
jibelrvr, actually I see lot of shadows16:05
rvrjibel: :-/16:05
jibelat least 6 shadow windows in the spread16:05
jibelkgunn, ^16:05
rvrjibel: In arale?16:05
jibelyes16:06
rvrInstalling silo 17 there16:06
jibelbut overall it's a huge improvement no crash and shadows are rather difficult to trigger16:06
jibelrvr, if you didn't find anything I'd +1 the silo16:07
jibelrvr, I think shadows in the spread are apps shot by OOM killer16:08
sil2100Ouch, pstolowski left16:09
jibelgreyback_, ^ on arale with silo 1716:09
rvrjibel: Hmm16:09
kgunnjibel: right...16:09
seb128jibel, 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
kgunnso it's not perfect but no crashing16:09
jibelkgunn, yeah, it's a +1 from me16:09
jibelrvr, what do you think?16:10
rvrjibel: Yeah, +116:10
jibelseb128, yes16:10
seb128jibel, is that reported?16:10
jibelseb128, if the call last longer than the screen timeout16:10
jibelseb128, not sure16:11
seb128that was not set as ota blocker?16:11
seb128it's quite visible/annoying16:11
jibellet me check if I find a bug16:12
seb128jibel, bug #148312716:13
ubot5bug 1483127 in telephony-service (Ubuntu) "Proximity does not turn screen on during a call" [Undecided,New] https://launchpad.net/bugs/148312716:13
jibelseb128, thanks16:13
seb128yw16:13
seb128sil2100, ^16:13
seb128it was reported 10 days ago :-/16:13
seb128boiko, ^ is that one for you?16:14
sil2100That's really bad16:14
sil2100kgunn: ^ (since bfiller is not around)16:14
sil2100kgunn: could you take care of triaging it? I leave it up to you guys to decide if it's a blocker or not16:15
sil2100But for me it would be pretty annoying and visible16:15
seb128+116:18
jibelsil2100, it's annoying and a regression in OTA6, it fell through the cracks16:18
seb128it's also discussed on the other IRC16:18
rvrRight, I can reproduce that proximity sensor bug16:18
jibel17 approved16:19
cjwatsonsil2100: The trust-store build doesn't appear to produce a translations tarball16:20
cjwatsonsil2100: 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 vivid16:21
sil2100cjwatson: 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.0416:21
sil2100hmm16:21
cjwatsonThe ones that are there would have been copied from vivid16:21
cjwatsonMaybe they were previously uploaded manually?16:21
cjwatsonOr something16:21
sil2100Maybe, not sure... I think we'll need the trust-store people on this one16:22
sil2100kenvandine: do you know who could help out with this? ^16:22
cjwatsonOr there might be something more sinister going on16:22
cjwatsonIt could be a failure of something in the chain that arranges for pkgstriptranslations to run16:22
cjwatsonIt does have .mo files16:23
kenvandinenot sure...16:23
kenvandinetvoss, it would be really great to get that translation fix in wily :)16:24
sil2100Not only in wily16:24
sil2100Would 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 LP16:25
sil2100Either because the build is not creating them or for some other reasons16:25
cjwatsonI'm still investigating16:25
sil2100cjwatson: thanks16:25
seb128cjwatson, kenvandine, sil2100, trust-store is in universe and not using X-Ubuntu-Use-Langpack: yes16:25
seb128that's probably why it doesn't import translations?16:25
cjwatsonseb128: built in a PPA, shouldn't matter I thought16:25
sil2100Then how did we get them before?16:25
jibelsil2100, 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
cjwatsonOh16:26
sil2100jibel: ACK, sure thing16:26
cjwatsonIt'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 before16:28
cjwatsonThe .mo files are there, so worst case, you could jam translations manually into the package and they won't be stripped16:28
cjwatsonBut I think it would be better to set X-Ubuntu-Use-Langpack: yes16:29
cjwatsonkenvandine: ^-16:29
kenvandinetvoss, ^^ could you?  if you're still around16:29
cjwatsonsil2100: trust-store was in main for a while16:30
cjwatsonhttps://launchpad.net/ubuntu/+source/trust-store/+publishinghistory16:30
cjwatsonSo that's probably why16:30
sil2100Oh?16:30
seb128hum, did the call start/end sound changed16:30
cjwatsonI assume whatever pulled it in stopped doing so16:30
seb128it sounds really unpleasant and I didn't have that feeling before16:30
cjwatsonOK, so mystery solved16:30
cjwatsonExcept that I'm not entirely sure how the modified translation got into vivid, but that could have been manual action16:31
seb128translation?16:31
seb128you mean template?16:31
seb128we did some template uploads through the webui for those content store new strings, but that was for wily I think16:32
AlbertAfginther: 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 start16:32
cjwatsonI mean template yes16:32
AlbertAfginther: 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 work16:33
cjwatsonI 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 answer16:33
seb128cjwatson, well, in any case I uploaded a new template to https://translations.launchpad.net/ubuntu/wily/+source/trust-store/+pots/trust-store/+upload this morning16:34
seb128dunno about other series16:34
fgintherAlbertA, so if unity-system-compositor and qtmir were updated together it would work?16:34
AlbertAfginther: right16:34
fgintherAlbertA, ack. I'll give them a pass then16:37
sil2100seb128: 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 that16:42
sil2100;)16:42
seb128sil2100, done from https://translations.launchpad.net/ubuntu-rtm/15.04/+source/trust-store/+pots/trust-store/+upload16:43
fgintherballoons, I've added that to the list, will try to get it done today16:45
balloonsfginther, ack and ty16:45
seb128sil2100, imported16:46
seb128https://translations.launchpad.net/ubuntu-rtm/15.04/+source/trust-store/+pots/trust-store/fr/+translate16:46
seb128:-)16:46
sil2100\o/16:47
sil2100seb128: thankz16:47
sil2100:)16:47
sil2100seb128: for me this link says: "Not allowed here"16:47
sil2100The +upload one16:47
seb128sil2100, not enough power yet ;-)16:47
sil2100I feel so... so weak!16:48
balloonsfginther, 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 enough17:02
=== joc_ is now known as joc|away
fgintherballoons, ah thanks. I want to say that's a known bug, but I'll have to look. If not I'll add it.17:04
Trevinhosil2100: 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
Trevinhosil2100: it looks weird in this way... I guess that when a package lands then upstream should be updated promptly17:05
robruTrevinho: silo 19 is not landed... The branches get merged after all packages migrate17:11
Trevinhorobru: 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:12
robruTrevinho: 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 xpathselect17:13
robruTrevinho: also if unity depends on changes in xpathselect you should have noted that in the packaging so they'd migrate together17:14
Trevinhorobru: it's not an hard dependency...17:14
Trevinhorobru: othewise I would have done it17:15
Trevinhobut, still I was hoping that once a package was landed in distro, then also its sources were merged...17:15
robruTrevinho: that is what happens, just after the last package lands in distribution17:16
Trevinhoyeah I figured it now, but not sure I agree it's the best solution17:16
Trevinhorobru: anyway, who can unblock libxpathselect? Since I've just triggered a recompilation with gcc5, and the failures (http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#xpathselect) aren't actually anything new17:19
Trevinhonor caused by that..17:19
robruTrevinho: you'd have to talk to #ubuntu-release about getting things unstuck from proposed17:19
Trevinhook, thanks17:19
robruYou're welcome17:20
=== alan_g is now known as alan_g|EOW
tvosskenvandine, I'm around now, what do you want me to do?18:13
kenvandinetvoss, cjwatson noticed trust-store isn't using langpacks properly18:18
kenvandinehe said to set X-Ubuntu-Use-Langpack: yes18:18
kenvandinethat goes in debian/control18:18
tvosskenvandine, ack18:20
tvosskenvandine, do you need that today?18:20
kenvandinei assume... cjwatson: ^^18:20
kenvandineor sil2100: ^^18:22
sil2100Not particulary today, since seb manually uploaded the templates18:27
bfillersil2100: can we publish silo 17?18:32
tvosskenvandine, I can prepare mp and silo Sunday, travelling to London anway18:33
kenvandinetvoss, me too :)18:34
kenvandinewell traveling tomorrow18:34
bfillerrobru: around?19:07
robrubfiller: hiya19:07
bfillerrobru: mind publishing silo 17?19:07
robrubfiller: sure19:08
sil2100+1 on that19:08
* sil2100 was AFK to do some housework19:08
bfillerthanks19:08
bfillersil2100: do you know if silo 16 that landed earlier today is in an image yet?19:08
sil2100bfiller: no, not yet, but jibel asked me to build an image before I go EOD with whatever is available19:09
bfillersil2100: but if I update from overlay ppa it should be there right?19:09
sil2100Yeah19:09
sil2100bfiller, jibel: ok, I suppose we won't get anything more besides the 2 silos today... I'll copy over the qtmir packages to the snapshot and create a new image20:16
sil2100+ the trust-store translation fix20:16
bfillersil2100: Kaleo fix going to be ready soon20:27
kgunnfginther: were you gonna poke that mir0.15 in proposed pocket thru ?20:27
AlbertAfginther: the mir boottest will fail also in a similar manner to qtmir/usc... because it will install an updated libmirclient library that wants to talk to a new server (i.e. new qtmir or new USC) but won't be available20:28
AlbertAfginther: so unity8 will fail to start too there20:29
AlbertAfginther: unless both qtmir/usc are updated20:29
fgintherkgunn, I had't check that one as I didn't know it needed to be included. I can push that one forward also20:29
kgunnfginther: thanks, i think so20:29
bfillerAlbertA: any progress on proximity bug?20:30
kgunnbfiller: dang dude20:30
AlbertAbfiller: yeah I see what the issue is... but it requires some careful addition to not break the "short notification timeouts" that was added20:31
bfillerkgunn: you know about this one right?20:31
kgunnyes20:31
bfillerkgunn: ok, came up this afternoon20:31
kgunnbfiller: yes...hence my "dang dude" as in it's only been a couple of hours :)20:31
bfillerkgunn: lol20:31
bfillerkgunn: c'mon man, crank it out, time is short :)20:32
bfillergetting on a plane soon20:32
bfillerwell not that soon20:32
kgunnit'll get there20:32
* bfiller has his firehose out20:33
kgunnbfiller: when do you arrive london ?20:33
bfillerkgunn: flying sat night, arrive sun morning20:37
kenvandinebest thing about london, it's one of the few places I can fly direct20:39
kenvandinei never even get direct flights within the US20:39
sil2100bfiller: should I wait with kicking the image then?20:41
bfillersil2100: alesage_ are you testing silo 40? I tested it already and am good with it, just trying to decide if we should wait to spin an image with it or you need more time20:42
alesage_bfiller, I've been looking at, yes, probably need a little more time with it just to give a full pass on camera20:43
alesage_bfiller, working on now20:44
sil2100Ok then, I can still be around for a while20:44
bfillerjhodapp: does silo 40 need to be rebuilt or it has the latest?20:44
jhodappbfiller, has the latest20:45
jhodappwait sorry20:45
jhodappone more build20:45
bfillerjhodapp: ok so respin and then mark ready for QA please20:46
jhodappbfiller, alright it's building the one change I requested from the code review20:46
jhodappwill do20:46
bfillerthanks20:46
fgintherAlbertA, kgunn, mir should be unblocked shortly20:51
AlbertAfginther: thanks20:54
sil2100I go AFK for ~30-45 minutes, I'll be back later and kick an image if everything is ready20:59
kgunnta21:02
=== salem_ is now known as _salem
cjwatsonkenvandine: what's in London?21:44
sil2100alesage_: are you looking at silo 40?21:51
alesage_sil2100, yes about to pass it21:51
sil2100\o/21:51
alesage_woo!21:52
alesage_sil2100, hiya, just want to make sure we're clear on 40--sitting across from jhodapp21:58
jhodappsil2100, just need to make sure silo 40 is not stuck in the landing process22:01
sil2100ACK22:16
sil2100Ok, copying it over to the snapshot and kicking a new image22:17
=== _salem is now known as salem_
sil2100bfiller, jibel: image building22:35
sil2100I go offline now, havew a good weekend everyone22:36
=== salem_ is now known as _salem
=== chihchun_afk is now known as chihchun

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