/srv/irclogs.ubuntu.com/2015/09/29/#ubuntu-mir.txt

kgunnrobert_ancell: did you want to land that silo 59 xmir ? or is that just for testing....02:14
kgunni guess question is, are you gonna land that using the citrain ?02:14
robert_ancellkgunn, I'm waiting bregma and co to confirm it's really better before landing02:14
kgunnrobert_ancell: we were just discussing02:15
kgunnrobert_ancell: definitely better aiui02:15
robert_ancellkgunn, oh, I was expecting to use the CI train - but I've never got that far with a silo before02:15
robert_ancellGood02:15
robert_ancellThe downside is we can't land it into wily, so it has to go through the CI train to get into the overlay PPA right?02:16
bregmaI think the strategy need to be to branch so we can land in vivid+overlay while wily is frozen, then backport to "upstream" for X (ie. 16.04 X, not x.org X)02:18
bregmaotherwise we're blocked02:18
bregmaand there's a good chance we'll never ship a device with wily (jumping from vivid+overlay to 16.04 LTS + overlay)02:19
robert_ancellbregma, the package in the silo is a branched version - we'll update the XMir patch in x-series02:20
bregmaanyway, robert_ancell, ChrisTownsend says silo 59 is much, much better (does not crash) but still has damaage problems, and I believe duflu has more bugfixes waiting to go in on top02:20
bregmalanding silo 59 would be a good thing at this point02:21
robert_ancellbregma, ok, cool. So we should land that into the overlay PPA02:21
robert_ancellAnd do another silo when it's improved02:21
dufluNot more fixes in mind, but I have created three accurate-ish bug lists for Xmir02:21
dufluLots of bugs remain02:21
robert_ancellDoes anyone know the next step for this silo. Do I just click publish on https://requests.ci-train.ubuntu.com/#/ticket/405 or do I need to ask someone from the CI team.02:26
robert_ancell?02:26
bregmarobert_ancell, you need to change "No QA Needed" to "Publish without QA"02:31
robert_ancellbregma, ok, done. Do I then publish myself?02:32
bregmarobert_ancell, I think so, robru sent an email last week about that, but it doesn;t hurt to ask on #ubuntu-ci-train for clarification02:33
bregmaI seem to have deleted the email02:34
robert_ancellbregma, there's no-one in #ubuntu-ci-train it seems... What server?02:34
robert_ancellah, #ubuntu-ci-eng02:35
robert_ancellbregma, kgunn, OK, it appears to be in the overlay PPA now03:07
dufluRAOF: Going for a diff record? :)05:13
dufluI see it's gone now05:13
RAOFTurns out when you have a full-file conflict with every file in the repository the diff is pretty big!05:13
=== chihchun_afk is now known as chihchun
dufluRAOF: Happened again05:28
dufluUmm, the mir 0.16.0 tarball is 50MB05:30
dufluwtf?05:30
dufluOoh. Cemil included the .bzr repo :)05:31
RAOFHehd.05:34
RAOFWe should probably work out why linking with ld.gold fails.06:10
RAOFgold is much, *much* faster to link.06:10
RAOF(Like roughly an order of magnitude)06:11
dufluRAOF: What is gold?06:11
RAOFThe gold linker. It's the replacement...ish for the standard bfd linkerl.06:11
dufluOh  https://en.wikipedia.org/wiki/Gold_(linker)06:11
RAOFI think we might be technically underlinking.06:14
RAOFAlso have multiple wildcards in the symbols.map, which gold dislikes (and *might* be UB)06:16
dufluWell, avoiding the wildcards would at least make us think about ABIs more :)06:19
dufluHopefully it would be semi-automated tho06:19
RAOFNo, I mean we have MIR_CLIENT_9 { global: stuff... local: * } MIR_CLIENT_9.1 { global: stuff... local: *};06:20
dufluOh06:20
RAOFThe two wildcards overlap, so it's not defined which block matches.06:20
* duflu thinks he's not the only one who never bothered to learn about local:*06:21
RAOFIt's a poor-man's -fvisibility=hidden :)06:21
RAOFHm. We should totally use that for mirclient.06:22
anpoki guess only the last one should have local:*?07:40
anpokor only the first?07:44
=== chihchun is now known as chihchun_afk
anpokalan_g, alf_: https://code.launchpad.net/~andreas-pokorny/mir/libinput-platform-pointer-settings/+merge/272501/comments/687606 thoughts?09:27
alan_ganpok: on my list09:28
anpokthe actual answer spans over to comments.. one that was started by a sleepy-me..09:28
anpok*two09:28
=== marcusto_ is now known as marcustomlinson
=== marcusto_ is now known as marcustomlinson
=== chihchun_afk is now known as chihchun
=== alan_g is now known as alan_g|lunch
=== alan_g|lunch is now known as alan_g
tsdgeosguys, did i do this right?13:35
tsdgeoshttps://code.launchpad.net/~aacid/mir/fix_forward_declarations/+merge/27275113:35
tsdgeosproper target branch and stuff?13:36
alf_Saviq: Do MPs for unity8 need an explicit changelog change or is the change automatically picked up from the commit messages?14:07
Saviqalf_, no changelog, just the commit message on the merge proposal14:08
alf_Saviq: thanks14:08
tjaaltonhi, should unity8 desktop session work in current wily, or did my mesa11 break it?-)14:09
alan_ggreyback_: CI now happy with https://code.launchpad.net/~alan-griffiths/qtmir/small-refactoring-of-MirWindowManager/+merge/26669814:10
alan_gtjaalton: I'm not sure what the state of u8 desktop is, but AFAIK the mesa 11 drop just broke Mir compilation, not runtime.14:21
guest42315tjaalton, https://bugs.launchpad.net/ubuntu/+source/mir/+bug/149942514:25
ubot5`Ubuntu bug 1499425 in xorg-server (Ubuntu) "xmir black window (mesa 11.0.0)" [High,New]14:25
anpoktjaalton: hm a lot has changed inXmir .. I believe the wily version requires the -damage to workaround lots of redarw issues14:32
anpok*parameter14:32
anpokoh ok duflu already answered that..14:33
anpoks/tjaalton/guest4231514:34
guest42315que dice? oh yeah :D -damage doesn't work14:35
* guest42315 ubuntuonair in 20 min http://ubuntuonair.com/14:38
=== dandrader is now known as dandrader|afk
tjaaltonah just compilation, no biggie then :)14:42
tjaaltonso if the blank screen on login is due to the xmir bug then I guess it's known14:42
tjaaltonand I did notice that one already, but thought it would be more native than using xmir14:46
anpoktjaalton: there is a high probability that those are not related14:47
tjaaltonok14:48
tjaaltoncould be I'm hitting a skylake display bug14:50
=== dandrader|afk is now known as dandrader
=== chihchun is now known as chihchun_afk
=== alan_g is now known as alan_g|EOD
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader
=== Cimi_ is now known as cimi

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