/srv/irclogs.ubuntu.com/2015/10/14/#ubuntu-unity.txt

=== maclin1 is now known as maclin
=== davidcalle_ is now known as davidcalle
tsdgeosMirv: ping09:56
Mirvtsdgeos: pong10:03
tsdgeosMirv: was speaking with Saviq about the audiorole issues with Qt 5.510:04
tsdgeosgiven that QML doesn't have ifdefs10:04
tsdgeosit would be cool if we could make our vivid Qt support the new roles10:04
tsdgeosand maybe even probably the W+1 Qt 5.5 support the old roles for a while10:04
tsdgeosto have a proper deprecation process10:04
tsdgeosotherwise it's very hard for us to have code that works both in w+1 and in vivid/overlay10:05
Saviqit's not even about QML not having ifdefs, but the fact that we'd break apps setting the old property name10:06
Mirvtsdgeos: oh right, you're thinking about the dual landing aspect? but I guess changing the audio roles in vivid could be seen as a risk.10:06
tsdgeosthat to10:06
tsdgeosMirv: i don't want to change them10:06
tsdgeosMirv: i want to add the new ones10:06
Saviqwe need to support both ones10:06
tsdgeosyep10:06
Mirvtsdgeos: ok. so how to eventually drop the support for non-upstream ones?10:06
Saviqin both vivid+overlay (which won't get Qt 5.5 will it?) and wily10:06
SaviqMirv, we'd need to follow a deprecation process like the SDK does10:07
MirvSaviq: well in an ideal world we could upgrade vivid+overlay to Qt 5.5. after some sunny day I get to publish 5.5 to wily+1, I can create a PPA to see how it looks there.10:07
Saviqyeah I meant wily+110:07
SaviqMirv, sure, but that's not a target, yet, so when we land 5.5, we need to make sure stuff works there, too10:08
Mirvtsdgeos: so, I think the supporting of dual roles in qtmultimedia is actually the first thing that should be landed, so that you can continue shipping unmodified Unity 8 to both10:08
Saviqyup10:08
Mirvtsdgeos: can you come up with a patch for qtmultimedia that works on top of the current Qt 5.5 branch? maybe then we can switch the 5.4 qtmultimedia to the same set of patches (new upstream ones + yours filling up the old support)10:08
Saviqwe need to coordinate with SDK guys10:08
Mirvdual landing silos can now be done for manual upload packages too, so we could have one silo to land to both wily+vivid overlays10:09
SaviqMirv, OTOH, https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/QtMultimedia.Audio/ does not publish the Role prop...10:09
tsdgeosSaviq: what needs coordination with the SDK?10:10
MirvSaviq: yeah, I don't think anyone is using it as it's only been there since summer10:10
Saviqtsdgeos, deprecation process10:10
Mirvin order to land to vivid overlay we'd need to not deviate wily from it, so I think first up is landing qtmultimedia 5.4.2 (wily) and 5.4.1 (vivid) and just keep the 5.5 PPA up-to-date too10:11
SaviqMirv, tsdgeos, if it's not a public prop, maybe we don't need to jump through those hoops, but rather just backport the new patch to 5.410:11
Saviqbzoltan_, ping10:11
tsdgeosid' we fine with that10:12
Saviqwould definitely be easier10:12
tsdgeos./usr/share/click/preinstalled/com.ubuntu.clock/3.5.364/share/qml/alarm/AlarmSound.qml:        audioRole: MediaPlayer.alert10:13
tsdgeosseems the clock at least is using it?10:13
tsdgeos./usr/share/ubuntu/settings/system/qml-plugins/sound/SoundsList.qml:        audioRole: MediaPlayer.alert10:13
tsdgeosand ↑ whatever it is10:13
MirvSaviq: tsdgeos: but just backporting the new patch to 5.4 would still mean we need to upgrade qtubuntu-media, qtubuntu-camera and unity8 in vivid-overlay10:13
Mirvtsdgeos: ok, I guess it was announced then somewhere and started to be used10:14
SaviqMirv, yes10:14
Saviqtsdgeos, well, clock and settings we'd have to update10:14
Mirvsounds like the original proposal is needed, otherwise this is expanding a bit too much10:14
Mirvhowever you wish. if only 5.4 backport is needed, I can handle that and give you a silo to put wily+vivid unity8 etc in10:14
Saviqbut indeed without a new framework we won't be able to publish a new version of them10:15
tsdgeosSaviq: i'm just scared it may be used outside "our stuff"10:15
Saviqtsdgeos, well, that's the question - if it's used without being public, not really our fault10:15
* Mirv creates a silo anyway for a new dual landing10:16
Saviqwe can't keep stable APIs of stuff we didn't commit to10:16
SaviqMirv, tsdgeos, let's not do anything just yet and find out what's the real status of it10:16
Saviqif it's only been built in for internal use, maybe we can deal with that10:16
tsdgeosoki10:16
* tsdgeos puts the work on this on a halt10:16
Mirvtsdgeos: fix for 5.5 anyway welcome, it's a bit annoying to edit QML files by hand10:17
Saviqyeah we can have an MP up for 5.5 compatibility anyway10:18
Saviqas that's where we wanna get in any case10:18
Mirvjhodapp should know how the audio role API came to be, is it supposed to be public and what usage is there10:18
Mirvjhodapp: mostly we're interested if we did commit to the old API already, ie do we need do keep compatibility with both the old and new one until the old one is properly deprecated10:19
SaviqMachines vs. Machines has it commented out10:20
Saviqdidn't find it anywhere else10:20
* Saviq emailthreads10:20
=== marcusto_ is now known as marcustomlinson
SaviqMirv, so this output https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1493851/comments/8 is from 5.5?10:26
ubot5`Ubuntu bug 1493851 in qtubuntu-media (Ubuntu) "Port to upstreamed versions of Audio Role patch" [High,In progress]10:26
SaviqFWIW they don't advertise the role property in upstream 5.5 docs either http://doc.qt.io/qt-5.5/qml-qtmultimedia-audio.html10:26
MirvSaviq: yes, or strictly speaking it's a backport of Qt 5.6's upstream patch that we was submitted by us. the point is that it's better to switch earlier than linger it later... one option of course would be to postpone it and remove the patches until 5.6. but by then we might have more usage of the old API..10:27
Saviqoh right10:27
tsdgeosi think the best would be supposrt both for 5.510:27
tsdgeossince technically it's not there yet10:27
tsdgeosand then remove it for 5.610:28
tsdgeosbut yeah needs input from bzoltan_ & SDK10:28
Saviqtsdgeos, so what got renamed actually? the enums?10:28
tsdgeosSaviq: yep10:29
Saviqack10:29
tsdgeosah no10:29
tsdgeosboth enum and property10:29
tsdgeosrole instead of audioRole10:29
Saviqrly http://doc-snapshots.qt.io/qt5-5.6/qml-qtmultimedia-audio.html#audioRole-prop ?10:29
tsdgeoshmmm10:30
tsdgeosok i guess what happenend is not that the audioRole is now part of 5.5 import10:31
tsdgeosnot of 5.4 import10:31
tsdgeosthat's going to be a mess10:31
tsdgeoswe need the 5.0 import to still work for vivid10:31
Saviqso for 5.0 and 5.4 we'd need to support the old enum values10:32
Saviqand leave 5.5 be10:33
Saviqbut then we can't make 5.4 forward-compatible10:33
Saviqso we need a new framework for 5.5 anyway10:33
Saviqit seems for as long as we want to support vivid/5.4 we'll need to make the 5.0 and 5.4 imports work10:49
Saviqno need for new enums in 5.0 or 5.4 import, though10:51
Saviq/food10:53
tsdgeosMirv: ping#210:56
tsdgeosMirv: unping for now10:57
Mirvhmm11:07
Saviqgreyback_, please merge lp:~dandrader/qtmir/mousePointer in multimonitor11:07
greyback_bah conflicts11:08
greyback_Saviq: conflicts resolved, prob ok, but will build to make sure11:10
tsdgeosMirv: ok, ping again, i can't seem to install silo 12 and get a bootable phone11:12
tsdgeosMirv: have you tried lately?11:12
Mirvtsdgeos: "did you read the manual"?11:13
greyback_Saviq: yeah builds ok11:13
tsdgeosMirv:  probably not11:13
Mirvtsdgeos: https://wiki.ubuntu.com/Touch/QtTesting11:13
Mirvtsdgeos: and yes, yesterday I think the last time11:14
Mirvtsdgeos: because of wily overlay pinning is now needed on wily too.. plus using it makes the 012 less likely to break. but citrain tool won't (ever) work.11:15
Saviqgreyback_, tx11:57
SaviqMirv, robru just tried a different approach in citrain tool (sent email around last night), still won't work?11:58
=== alan_g is now known as alan_g|lunch
MirvSaviq: yeah I think robru's new method should work (I checked the MP), so once it's in archives I can update the instructions12:05
Mirvsince apt install without archives being disabled should also install the new depends, and citrain already does pinning12:05
Saviqyup12:06
=== JMulholland_ is now known as JMulholland
jhodappMirv, as long as the new roles map to the same old role inside of pulse audio it doesn't matter12:27
tsdgeosMirv: i have a black screen following the instructions on an areale12:37
tsdgeosah because notifications12:37
tsdgeosobsiously12:37
Mirvjhodapp: ok, you can reply to Saviq's e-mail too to make the answer as verbose as possible. the thing is we have at least internal apps that use the old API that would break if not updated or if both API:s would be supported together for some time12:52
Mirvtsdgeos: obviously12:52
Saviqdandrader, hey, can you please merge lp:~gerboland/qtmir/multimonitor → lp:~dandrader/qtmir/surviveEmptyTexture → lp:~dandrader/qtmir/multimonitorNext12:53
* greyback_ really wants a staging branch12:53
Saviqgreyback_, it wouldn't help that much this time, too many projects involved12:54
jhodappMirv, sure, moving to the new API is fine as long as they use the equivalent new role...but yeah I'll reply12:54
Saviqgreyback_, at least half of MPs in silo 22 depend on other projects to go with, which means they shouldn't be staged12:56
=== alan_g|lunch is now known as alan_g
greyback_Saviq: unless those projects also had a staging branch..12:56
Saviqgreyback_, no, because at that point you introduce a requirement for both stagings to get released at the same time12:57
greyback_which the train could do12:57
Saviqgreyback_, not what I mean, if one of the projects' staging could not be released for whatever reason, the other one's blocked12:58
greyback_Saviq: I'm not meaning a general staging branch for other projects, but unity8 could have a  qtmir-staging branch, with only the changes qtmir needs12:59
Saviqgreyback_, not sure what's the difference between individual MPs at that point13:00
Saviqbut maybe13:00
greyback_Saviq: no need to chain branches13:00
greyback_that's the only benefit13:00
greyback_not major, but might help for these mammoth silo situations13:00
Saviqgreyback_, you need to chain stagings ;)13:01
Saviqbecause unity8/staging will conflict with unity8/qtmir-staging13:01
dandraderSaviq, done13:01
Saviqdandrader, thanks13:01
greyback_Saviq: we'd only release one at a time. I try to only release unity8 & qtmir changes combined13:02
Saviqdednick, can you please merge lp:~dandrader/qtmir/multimonitorNext → lp:~nick-dedekind/qtmir/remove-dpkg-CMAK_INSTALL_PREFIX → lp:~unity-team/qtmir/touch_tracing13:02
Saviqgreyback_, well, that's not the case in this mammoth silo, we're releasing everything for unity8 and qtmir together13:02
dednickSaviq: hm. thought i did that already13:04
Saviqdednick, you did, but we had a change up the chain13:04
Saviqthat we need down the chain...13:04
Saviqok I can't flash mako over usb any more :[13:04
dednickSaviq: ah. k13:04
dednickSaviq: i don't see any conflicts.13:05
Saviqdednick, nope13:06
dednickSaviq: ah. didnt think that was necessary if no clnflicts13:06
dednickSaviq: done13:06
Saviqdednick, there are some down the chain, but couldn't get bzr to comply13:06
Saviqltinkl, ↑ you can merge wheelEvent13:06
ltinklSaviq, against what?13:23
Saviqltinkl, against the prerequisite13:25
Saviqltinkl, lp:~lukas-kde/qtmir/wheelEvent13:25
ltinklSaviq, lp:~unity-team/qtmir/touch_tracing  right?13:26
ltinkl(that's the prereq currently)13:26
Saviqltinkl, yup13:27
Saviqltinkl, that should have the fixed MouseButtons bit13:27
ltinklSaviq, ye, on it13:27
ltinklSaviq, merged13:37
Saviqltinkl, ack13:38
tsdgeosSaviq: Mirv: commented at https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/150288313:43
ubot5`Ubuntu bug 1502883 in qtdeclarative-opensource-src (Ubuntu) "Impossible to pull to refresh scopes with Qt 5.5" [Undecided,New]13:43
tsdgeosi'd say we just wait for Qt 5.5.113:44
Saviqtsdgeos, ack13:44
tsdgeossince once i updated the files regarding the flickable it went back to normal13:44
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader
=== Guest77290 is now known as balloons
Saviqltinkl, GAH, you got green CI, how'd you do it!? ;)14:53
ltinkl\o/14:53
ltinklwaiting for https://code.launchpad.net/~lukas-kde/unity8/fixLogin1Tests/+merge/272493 rebuild14:53
ltinklhopefully it will also be green :)14:53
* Saviq tempted to rebuild just to see if you cheated14:54
ltinklSaviq, btw is there a CI job that runs on trunk?14:54
Saviqltinkl, we can trigger one on demand14:55
Saviqltinkl, we could trigger it on push to trunk, but that's too late, 'innit ;)14:58
ltinklye14:58
SaviqI hope at some point we'll have them run in silo14:58
tsdgeosyeah15:06
tsdgeosthat's particularly useful for MRs that require unity-api15:06
tsdgeoswhere CI is all failures15:06
Saviqtsdgeos, oh for that we need smarter CI that can take prerequisites from other projects into account15:07
tsdgeosSaviq: or just run on silos :D15:08
tsdgeosso at least we can run all the tests in a silo15:08
Saviqtsdgeos, sure, we need both, really15:08
ltinklhaving a CI-enabled would also prevent breakages that don't happen in isolated MPs15:14
ltinkllike, 2 individual MPs might be fine but when combined together it would fail15:14
Saviqbbl15:16
Saviqwhoo Mir 0.17 landed, means we might even think of landing 22 tomorrow15:17
Mirvtsdgeos: thanks, 5.5.1 should be fiiinally out tomorrow, hopefully. hopefully it fixes ~everything, but at least that bug..15:27
tsdgeosMirv: are there many issues?15:27
Mirvtsdgeos: still unresolved some UITK, some FTBFS:s, https://bugs.launchpad.net/bugs/+bugs?field.tag=qt5.5 - and no-one else besides me has tried it out or filed bugs so there might be more (and probably is)15:32
tsdgeosi see15:34
tsdgeosMirv: regarding https://bugs.launchpad.net/ubuntu/+source/u1db-qt/+bug/144718215:51
ubot5`Ubuntu bug 1447182 in u1db-qt (Ubuntu) "u1db-qt FTBFS with Qt 5.5" [High,Triaged]15:51
tsdgeos$ LC_ALL=C apt-cache policy u1db-qt15:51
tsdgeosN: Unable to locate package u1db-qt15:51
tsdgeos?¿15:51
tsdgeosah it's not the name of the pacakge15:52
tsdgeosmy fault sorries15:52
=== dandrader|afk is now known as dandrader
dandradergreyback_ greyback__ sorted out the surface resize threading issues. but it will need tripple buffering18:18
dandradergreyback__ only way I see of doing it with double buffering is using a non-threaded qsg renderer18:18
greyback__dandrader: that's not ideal18:18
greyback__but I can see why that would be an option18:19
dandradergreyback__, or using a "crop or pad" resize method18:19
greyback__which no-one else in the world does, and we don't do either18:20
dandradergreyback__, this is actually what unity 7 does18:20
greyback__dandrader: who needs to be triple buffered, the compositor and/or client?18:20
dandradergreyback__, but it's worse. it's more like a "crop or pad with random memory"18:20
dandradergreyback__, client18:21
greyback__dandrader: ok, well doing better than unity7 would be best18:21
greyback__dandrader: could you document your reasoning please?18:22
greyback__this is something where looking at code won't obviously explain your approach18:22
greyback__and a picture or two would help a lot18:22
greyback__duflu could have insights on this too18:22
robruSaviq: Mirv did you try the new tool? I think it's not perfect but I think I know how to make it perfect, will experiment more today18:29
Saviqrobru, I replied to the CFT email18:43
robruSaviq: thanks18:43
dandradergreyback__, branches are up for review: https://code.launchpad.net/~dandrader/qtmir/surfaceItemFillMode/+merge/27444919:23
=== dandrader is now known as dandrader|afk

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