#ubuntu-qt 2018-06-01
<greyback> valorie: tsimonq2: hey! yes I lurk :)
<ahayzen> Hi, has anyone seen an issue with Qt on 18.04 where one can't start apps inside a container ? I get an error like this when trying to start qtcreator/qmlscene from inside a container https://pastebin.ubuntu.com/p/Y9WmngQKFm/ (the same thing works fine under 16.04 and 17.10 but not 18.04) ... and seems others have had the same https://forum.snapcraft.io/t/crash-qt-gui-aplication-build-with-core-18-on-ubuntu-18-04-lxd/5385   Or is there
<ahayzen> something else i need to do...
<mitya57> ahayzen: I would say, please file a bug with a complete stacktrace. Otherwise it is hard to tell what happens.
<ahayzen> mitya57, ok against which package though? qtbase-opensource-src ?
<mitya57> Right, that one.
<mitya57> By complete I mean, with the debug packages (libqt5core5a-dbgsym libqt5gui5-dbgsym libqt5dbus5-dbgsym libqt5opengl5-dbgsym) installed.
<ahayzen> right, ok i'll see if i can extract some info :-)
<mitya57> Thanks :)
<ahayzen> mitya57, i've reported https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1774739 with a stacktrace https://pastebin.ubuntu.com/p/WKKGmxqqSx/ let me know if you need more info. I've added a Dockerfile which reproduces the issue (i believe the same should happen with LXD). Also note if one changes the distro in the Dockerfile from 18.04 to 17.10 or 16.04 and bionic to artful, xenial it works.
<ubottu> Launchpad bug 1774739 in qtbase-opensource-src (Ubuntu) "Running Qt apps inside a 18.04 container crashes" [Undecided,New]
<ahayzen> seems potentially and issue in dbus somewhere...
<ahayzen> *an issue
<lubot> <tsimonq2> That looks familiar.
<lubot> <tsimonq2> I can't say where I've seen it before, though.
<ahayzen> tsimonq2, it potentially also affects people trying to run Qt apps on the core18 snap, from what was said in the snapcraft forum link ^^
<ahayzen> maybe that's where you have seen/heard of it
#ubuntu-qt 2018-06-02
<lubot> <tsimonq2> @ahayzen, I tend to call "not it" on snap-only issues in packages I help maintain, to be frank.
<mitya57> ahayzen: thanks for the bug! I will look at it when I have more time, most probably next week.
#ubuntu-qt 2018-06-03
<lubot> <tsimonq2> FWIW, I get done with finals at the end of this week, then I go to SELF... during or after SELF, my plan is to finish up the 5.11 "transition" in Debian Experimental and get that going in Ubuntu
<valorie> tsimonq2: does this mean you are mostly done with school after this week?
<lubot> <tsimonq2> @valorie, I'm completely done with school after this week. :P
<valorie> nice!
<valorie> whatcha gonna do with your summer
<valorie> ?
<lubot> <tsimonq2> Take a guess. ð
<lisandro> stay away from your PC!
 * lisandro ducks
<lubot> <tsimonq2> ð
<lisandro> tsimonq2: knowing that you are from EEUU the only thing I can think of is one of those summer camps. Blame Hollywood.
<lubot> <tsimonq2> (I remember my Spanish teacher noting at one point that EEUU = USA, heh)
<lubot> <tsimonq2> Hah. I don't go to summer camps. :)
<lisandro> err, yeah, USA
<lisandro> bad idea, fresh air is nice ;-)
<lubot> <tsimonq2> Hehe
 * lisandro would have probably liked one of those
<lubot> <tsimonq2> (I know enough Spanish to understand common words and phrases. :))
#ubuntu-qt 2018-06-05
<lubot> <tsimonq2> Qt 5.9.6:
<lubot> - Release content in place and packages under RTA
<lubot> - If all OK we will release these packages as Qt 5.9.6 during this week
<lubot>    * Release target Wed 6.6.2018 but let's see if we can get all needed testing done early enough for that
<lubot> Qt 5.11.1:
<lubot> - Branching ongoing. Target to finalize branching Thu 7.6.2018
<lubot> - Creating initial changes files will be started later this week
<lubot> - Target to create final packages for RTA at the end of next week & put the release out 19.6.2018
<lubot>    * 4 issues open in release blocker list, see https://bugreports.qt.io/issues/?filter=19372
<lubot> <tsimonq2> Some releases coming up. :)
<lisandro> 5.11.1 already?
<lisandro> oh, wow
<lisandro> well, work to do it seems
<lubot> <tsimonq2> hehe
#ubuntu-qt 2018-06-06
<LocutusOfBorg> acheronuk, please update modemmanager-qt to fix testsuite?
<LocutusOfBorg> I did a debdiff between debian and ubuntu, probably adding A libglib2.0-dev, to build-depends and runtime-deps of -dev package is enough
#ubuntu-qt 2018-06-07
<lisandro> FWIW: https://bugreports.qt.io/projects/QTCREATORBUG/issues/QTCREATORBUG-19469?filter=allissues
<lisandro> seems ubuntu-only
<acheronuk> LocutusOfBorg: nope. that fails
<LocutusOfBorg> acheronuk, why?
<LocutusOfBorg> acheronuk, why?
<acheronuk> LocutusOfBorg: tried in a ppa, and it failed to build
<acheronuk> LocutusOfBorg: same error
<acheronuk> LocutusOfBorg: which I guess you just discovered with your ubuntu2 upload :P
<LocutusOfBorg> yep, let me fixup it
<acheronuk> LocutusOfBorg: export DEB_CXXFLAGS_MAINT_APPEND := $(shell pkg-config --cflags glib-2.0) in rules seems to work
<LocutusOfBorg> acheronuk, interestingly it doesn't ftbfs with pbuilder
<LocutusOfBorg> let me debug a little bit before pushing a fix
<LocutusOfBorg> oh picking up old momdemmanager
<acheronuk> yeah, I tried in pbuilder against proposed and it failed
<acheronuk> with that line in rules, it built. same in a ppa
<acheronuk> we are going to do debian merges with frameworks 5.47 anyway
<LocutusOfBorg> I hope to see it somewhat in sync soon :)
#ubuntu-qt 2018-06-11
<clivejo_> hi, did aix join this channel?
<lubot> <tsimonq2> No.
<clivejo_> he is having issues with scrolling dash cards in the mycroft plasmoid apparently the issue is fixed in Qt 5.11.. Would someone see if the patch could be backported?
<clivejo_> it is reverse scrolling
<clivejo_> very odd
<lubot> <tsimonq2> In 18.04 or 18.10?
<lubot> <tsimonq2> And is there a commit number we could have?
<clivejo_> he mentioned it is fixed in neon, but not sure if that is they are on Qt5.11 or backported a fix
<lubot> <tsimonq2> OK
<lubot> <tsimonq2> If he could give more details, that would be great.
<lubot> <tsimonq2> Nice to see you, Cliv. E
<lubot> <tsimonq2> *Clive
<clivejo_> well I have asked him to join this channel
<clivejo_> I'll ask him to pop in and provide more details.  He was asking of the likelihood of Ubuntu 18.04 getting Qt5.11
<lubot> <tsimonq2> @mitya57 So with 5.9.6 being released, I think we should look at SRUing it (like we discussed)
<lubot> <tsimonq2> I fly back home today, but after I get a good night's sleep tonight, I'll probably work on finishing 5.11
<lubot> <tsimonq2> Unless you want to start the process for 5.9.6 (go ahead)
<lubot> <mitya57> It will be in 18.10 anyway, and not in 18.04 unless someone makes a PPA for it.
<lubot> <tsimonq2> 5.9.6?
<lubot> <tsimonq2> (I'm talking about 5.11 for Cosmic, not Bionic :))
<lubot> <tsimonq2> I think before we can SRU a stack we need a higher version in Cosmic.
<ahayzen> mitya57, FYI, added some extra info to https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1774739   I tried using the offline .run installers TQC produce, I have found that 5.6/5.9 seem to run on Ubuntu 16.04/17.10 ... but fail on Ubuntu 18.04 with a similar stacktrace to qtcreator from the archive. So I wonder if it is a change to the system that is causing this? (eg libdbus?)
<ubottu> Launchpad bug 1774739 in qtbase-opensource-src (Ubuntu) "Running Qt apps inside a 18.04 container crashes" [Undecided,New]
<ahayzen> tsimonq2, yes IIRC you'll need a higher version in cosmic before SRU, either get 5.9.6 into cosmic or 5.11 - but you probably already know this ;-)
<lubot> <tsimonq2> @ahayzen, Yep. :)
#ubuntu-qt 2018-06-12
<mitya57> ahayzen: thanks. I donât have time to investigate so far, but my initial guess is that the containers may be blocking the syscalls that are important to Qt.
<mitya57> (Like in Debian #901062)
<ubottu> Debian bug 901062 in qtbase5-dev "qtbase5-dev: qtbase5-dev: QFil33ec:265c:71fe:e26d:2682:4ec2:aaa1:99abexists() returns false for existing files?!" [Normal,Open] http://bugs.debian.org/901062
<ahayzen> mitya57, no worries, right it's going to be something funky :-) The interesting part is that the same .run works on an older container, so something to do with the 18.04 container and it's env. Let me know if there is any additional info i can try to extract
<ahayzen> Also note that to use gdb inside docker i am passing "--security-opt seccomp=unconfined" which should not block certain syscalls, as described in the bug report you linked. And that older versions like Qt 5.6 have similar issues on 18.04
 * lisandro suspects we will be seeing more containers issues with Qt in the near future
<lisandro> it's amazing the amount of times I have seen this in the last two weeks
<acheronuk> :/
<lisandro> I think it is actually rather a good thing
<lisandro> like creating docker images from testing/sid and using them in stable
#ubuntu-qt 2018-06-13
* tsimonq2 changed the topic of #ubuntu-qt to: Ubuntu Qt Discussion Channel | https://is.gd/GIZG9E | Staging Qt 5.11.0 for Cosmic: https://bileto.ubuntu.com/#/ticket/3291 | Help remove Qt 4! https://is.gd/QXLEFW | 5.9.5 in Bionic, 5.5.1 in Xenial, 5.2.1 in Trusty | This channel is bridged to Telegram, ask us to be added | This channel is craighoward@example.net; use implies acceptance of Ubuntu IRC channel terms.
<lubot> <tsimonq2> https://bileto.ubuntu.com/#/ticket/3291
<lubot> <acheronuk> @tsimonq2, :)
#ubuntu-qt 2018-06-19
<lubot> <tsimonq2> @mitya57 Is qtwebkit-opensource-src syncable? I'll try a test build tonight, but if it is, I'd like to sync it :)
<lubot> <tsimonq2> (Along with the Qt transition I'm preparing, but still.)
<lubot> <tsimonq2> Right now I'm almost done with the bootstrapping process in the PPA, but since I'm concurrently doing Debian Experimental uploads, I can just sync packages to the PPA when the bootstrapping is done.
<lubot> <tsimonq2> irt bootstrapping, qtwebkit is building locally (just bumping build deps, I might bump debhelper and std-ver) and after that I just need qttools.
<lubot> <tsimonq2> Once both are done and uploaded, I can go quicker (because I'm not waiting for build dependencies to get done). So the slow part is almost done. :)
<lubot> <tsimonq2> I see 5.11.1 was planned for tomorrow, but seeing as there are still open blockers in the bug tracker, they'll probably push it back. If they don't push it back however, I still want to finish 5.11.0 and get it out of the way, and then the update to 5.11.1 should be craighoward@example.net.
<lubot> <tsimonq2> @mitya57, lisandro: When 5.11.1 does come out though, and when it's in Experimental (which should be in the next week or two), I'd like to plan a time to sit down with one of you to go through requesting the transition in Debian. I already commented in #ubuntu-release that I wanted to do a Qt transition, but devel-proposed is in rough shape, so there's a chance I'll have to wait (but I'll keep dialogue going).
<lubot> <tsimonq2> Hmmmmm, I see 5.11.1 tars but no announcement yet...
<lubot> <tsimonq2> @tsimonq2, Ah, so ppc64el is FTBFS. I wonder if we can upstream that patch to Debian or if it should stay in Ubuntu.
<lubot> <tsimonq2> Anyway, I'll leave that how it is for now... bed for me.
<lubot> <tsimonq2> p/
<lubot> <tsimonq2> *o/
<lubot> <mitya57> @tsimonq2, First you will need to test-build all packages depending on qt{base,declarative}-private-dev to see if they get broken. Looking at the failures in Ubuntu is usually enough, as it is a superset of Debian.
<lubot> <mitya57> Then file a transition bug (`reportbug release.debian.org`), wait for the green light. When you get it, re-upload all Qt packages with s/experimental/unstable/ (and updating symbols if needed).
<lubot> <mitya57> @tsimonq2, It wonât hurt in Debian, but the FTBFS is Ubuntu specific for some reason. Note that it's not just a patch, but also three lines in d/rules.
<lubot> <acheronuk> @tsimonq2, http://blog.qt.io/blog/2018/06/19/qt-5-11-1-released/
<lubot> <tsimonq2> Thanks @mitya57 and @acheronuk
<lubot> <tsimonq2> I think instead of continuing, now that I have the core toolchain bootstrapped, I think I'll start over with 5.11.1 and qtbase in Debian and Ubuntu.
<lubot> <tsimonq2> It shouldn't be that hard to update things now that .0 is out of the way for them.
<lubot> <tsimonq2> I think the plan of action from here is to go full speed ahead updating to .1, and land that in Ubuntu/pass that off to @acheronuk for Plasma. From there, once I know Ubuntu's completely good, I'll request a transition slot for Debian and proceed there.
<lubot> <tsimonq2> I might land in Ubuntu first with the packages from Experimental pre-transition, then as soon as that's done, do the transition in Debian and let the packages flow down via the autosyncer.
<lubot> <Santa> good afternoon
<lubot> <Santa> @tsimonq2 do you have the 5.11 ubuntu work in git?
<lubot> <tsimonq2> @Santa, Yes, in Salsa.
<lubot> <Santa> ok, I was expecting an ubuntu/bionic branch here https://salsa.debian.org/qt-kde-team/qt/qtbase/branches
<lubot> <Santa> sorry, ubuntu/cosmic
<lubot> <tsimonq2> O_o
<lubot> <tsimonq2> There should be one there.
<lubot> <acheronuk> just looked at the exact same url, and though the same
<lubot> <mitya57> @tsimonq2, +1
<lubot> <tsimonq2> Awesome
<lubot> <acheronuk> no cosmic for qtdeclarative either
<lubot> <tsimonq2> qtdeclarative gets synced
<lubot> <tsimonq2> The only things that should have Cosmic branches are qtbase and qtwebkit
<lubot> <mitya57> Note that qtdeclarative *does* have a delta in Bionic.
<lubot> <mitya57> And also qtmultimedia.
<lubot> <tsimonq2> All Qt packages have a delta in Bionic because we diverged from Debian.
<lubot> <tsimonq2> The only meaningful delta left in qtdeclarative were transitional packages that could be dropped.
<lubot> <acheronuk> I'll just pull the ci-train sources for testing backport builds then
<lubot> <tsimonq2> Am I wrong?
<lubot> <tsimonq2> @acheronuk, This isn't all of it anyway
<lubot> <tsimonq2> Just the core stuff
<lubot> <mitya57> Hm, I meant real delta :)
<lubot> qtdeclararive used to have a patch to fix breakage on arm64. Maybe it got dropped, but I donât remember that.
<lubot> qtmultimedia used to need some changes to account for OpenGL ES on arm64.
<lubot> <tsimonq2> https://launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/5.9.1-4ubuntu1
<lubot> <tsimonq2> That's Artful
<lubot> <acheronuk> @tsimonq2, meaning you won't build all in ci-train to land?
<lubot> <tsimonq2> @mitya57 Mind taking another look and seeing if I accidentally dropped meaningful qtdeclarative delta at one point? qtmultimedia is one I haven't even craighoward@example.net.
<lubot> <tsimonq2> @acheronuk, Well, not right now, but eventually
<lubot> <tsimonq2> @acheronuk Were you going to backport 5.11 to Bionic for Backports?
<lubot> <tsimonq2> Did you want me to do that?
<lubot> <acheronuk> I don't mind who does it
<lubot> <tsimonq2> OK
<lubot> <mitya57> @tsimonq2, If the whole Qt stack built fine without that patch, then dropping it was right. Looks like that is the case.
<lubot> <tsimonq2> @mitya57, Qool :)
<lubot> <mitya57> But the patch is still there :(
<lubot> https://salsa.debian.org/qt-kde-team/qt/qtdeclarative/blob/ubuntu/bionic/debian/patches/testcase_array_iteration.patch
<lubot> <mitya57> So it just was not documented as a delta.
<lubot> <tsimonq2> Ah.
<lubot> <tsimonq2> It seems to build fine without it though... ð¤
<lubot> <mitya57> qtdeclarative itself will build fine without it, but you might have problems in some other Qt modules.
<lubot> <tsimonq2> OK
<lubot> <tsimonq2> Do you think it would hurt to pull that patch into Debian?
<lubot> <tsimonq2> If not, I'll just include it there when I get to it for 5.11.1.
<lubot> <tsimonq2> Otherwise I can do a delta; it doesn't really matter to me. :)
<lubot> <mitya57> It wonât hurt, but I cannot explain why this patch helps in Ubuntu, it is a dirty workaround for some crazy bug ð±
<lubot> <tsimonq2> Ah OK :)
<lubot> <tsimonq2> I'll put it in Debian then
<lubot> <mitya57> Maybe first check if it is still needed â maybe that bug disappeared somehow
<lubot> <mitya57> According to upstream bug https://bugreports.qt.io/browse/QTBUG-61579 you need to check if qtmultimedia tests pass on s390x without that patch
<lubot> <tsimonq2> OK
<lubot> <Santa> @tsimonq2 @mitya57 it would be really helpful if we could have ubuntu/cosmic branches for all the git repositories (even if they just point to a debian branch if there's no delta)
<lubot> <tsimonq2> @Santa, I'll get to it.
<lubot> <Santa> @tsimonq2, Thank you
<lubot> <tsimonq2> yw
<lubot> <Santa> @tsimonq2 sometimes in the past you have documented the bootstrap process, have you documented somewhere the one you are just doing right now?
<lubot> <tsimonq2> @Santa, https://is.gd/GIZG9E
#ubuntu-qt 2018-06-20
<lubot> <Santa> @tsimonq2, Thanks, the following doesn't have an "experimental" branch: qtdatavis3d, qtnetworkauth, qtscxml, qtserialbus. Is that intended?
<lubot> <tsimonq2> @Santa, Yes, because they aren't released.
<lubot> <Santa> @tsimonq2, But they have tarballs of them here: https://download.qt.io/official_releases/qt/5.11/5.11.1/submodules/
<lubot> <Santa> Or you mean "not meant to be released in debian/ubuntu"?
<lubot> <tsimonq2> The packaging isn't fully complete for them yet.
<lubot> <tsimonq2> They also aren't in experimental yet.
#ubuntu-qt 2018-06-21
<lisandro> qtdatavis3d being in NEW IIRC
<lisandro> qtserialbus needs a review, sgclark was working on it
<lisandro> we've got a user asking for qtscxml
#ubuntu-qt 2018-06-22
<tsimonq2> Kay, so, round one of the bootstrap is done.
<tsimonq2> Assuming 5.11.1+dfsg-2ubuntu1 passes in Bileto, we'll be fine.
<valorie> nice
<tsimonq2> Finally. ;)
<tsimonq2> Darnit, not yet.
<tsimonq2> I forgot that I bumped ABI in this upload.
<tsimonq2> No big deal, but yet another round of uploads I have to babysit.
<tsimonq2> Oh well/
<tsimonq2> s/\//./
<lubot> <mitya57> Qt 6 news! https://tsdgeos.blogspot.com/2018/06/qt-contributor-summit-2018.html
<lubot> <tsimonq2> Ooh.
<lubot> <tsimonq2> I think we should get Qt 6 packaged (even if in Experimental) as soon as work is starting, or releases are coming if it's that quick.
<lisandro> ha, we haven't yet removed qt4 and here we go
<lisandro> mitya57, tsimonq2: we should try to avoid haveing to use qtchooser maybe
<lisandro> ie, having tools postfixed with qt6, for example
<lisandro> I also still need to check qbs
<lisandro> and if qbs is selected we need to make helmut try cross building and stuff with it
<lisandro> ;)
#ubuntu-qt 2018-06-23
<tsimonq2> So, !x86 builders are out right now due to a fire in the datacenter.
<tsimonq2> I'll work on some more Qt stuff on the Debian side tonight, but Ubuntu stuff will have to wait until they recover.
<tsimonq2> :(
<mamarley> A fireâ½  How bad was it?  Was anyone hurt?  Are the builders destroyed or just temporarily out-of-commission?
<valorie> datacenter usually means that it gets auto-locked down and filled with gas
<valorie> then they have to wait until the gas can be sucked out and everything cools
<tsimonq2> mamarley: For the first three questions you'll have to ask wgrant in #launchpad. I've heard estimates of 12-48 hours on things being back up, but as far as I can tell, no permanent damage.
<valorie> before going inside to check on the damage
<tsimonq2> valorie: You're probably right.
<valorie> I have a friend in linuxchix who used to run datacenters
<valorie> maybe still does
<tsimonq2> Ah. sarnold in #ubuntu-flavors read the incident report, perhaps you could ask him whether you're right or not.
<tsimonq2> I don't doubt it's plausible, but I'm curious as to what the full story is. :)
<lisandro> o_O
<mitya57> lisandro: letâs talk about qtchooser closer to Qt 6 release :)
<bshah> xD
<tsimonq2> .
<tsimonq2> whoops
#ubuntu-qt 2018-06-24
<tsimonq2> OK, so after that setback due to PEBKAC on my part, once things finally settle tonight, we should have a bootstrapped Qt in both Debian and Ubuntu.
<lisandro> mitya57: actually that strategy failed for qt5 exactly because of the lateness
<lisandro> Maintainers did not want to rename their tools, specially when ready to release
<lisandro> If we could get them to do it right from the start then it would really help us
<lubot> <mitya57> @lisandro, Ok, but we canât do anything until we start packaging Qt 6, can we?
<tsimonq2> hah
<tsimonq2> One more time... let's see this
<tsimonq2> WOAH. That's fast. Good. :D
<tsimonq2> oh
<tsimonq2> I'm in the completely wrong channel
<tsimonq2> We have a new bot in #lubuntu-devel :D
<lisandro> mitya57: we need to do it while they did not start qt6
<lisandro> Meaning we should start really soon
#ubuntu-qt 2018-06-25
<ktecho> Hi there. How's the upgrade of QT in bionic? I heard that it's needed for the latest kde plasma
<acheronuk> ktecho: need to do it in cosmic 1st. that is WIP
<ktecho> acheronuk: ok, understood. Thanks!
<mitya57> lisandro: What can we do right now? Announce future changes, or make changes to existing (Qt 4 / Qt 5) packaging?
<lisandro> contact upstream to ask them to please use <foo name>-qt6 or alike
<lubot> <mitya57> I donât think they will agree :(
<mitya57> lisandro: note that even for Qt 4 and Qt 5 which had more incompatibilities, upstream did not provide any official way of co-installing them.
<lisandro> and do you remember why was that?
<mitya57> (qtchooser never became official, and is mostly abandoned now)
<mitya57> No I donât, I was not working on Qt packaging at that time yet :)
<lisandro> right!
<lisandro> that was because f what I've said before: submodules maintainers did not consider the problem important enough for chaging stuff at the last minute
<lisandro> that's because we reached them a few weeks before Qt 5.0.0
<lisandro> granted, it doesn't means we are going to be successful this time
<mitya57> Ok, maybe you are right then
<mitya57> Please start a thread and I will follow it / reply if needed.
<lisandro> I'll see to talk with sune first
<lisandro> he might know better than I if it's worth the effort or no
<mitya57> Makes sense.
#ubuntu-qt 2018-06-26
<lubot> <tsimonq2> @mitya57 Can I please get a second opinion on https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3291/+build/15053268 ?
<lubot> It seems to *me* that the file is only compiled because of the differences between Debian and Ubuntu in qtbase arm64 builds. We should only have to keep an Ubuntu delta installing that on arm64, correct?
<lubot> <mitya57> @tsimonq2, Yes, you need to restore the delta.
<lisandro> tsimonq2: are you using EGL on arm64?
<mitya57> lisandro: yes
<lisandro> I see
<mitya57> lisandro: I would really like to make Debian and Ubuntu use the same variant of OpenGL on arm64, but you point out that there are arm64 devices with desktop OpenGL appearing, while in Ubuntu there are people using GL ES boards (like Raspberry Pi 3) and we donât want to break them.
<lisandro> yes, it's complicated
<lisandro> and you can't build both variants I'm afraid
<lisandro> *but* for most of the EGL cards I have seen out there you also need proprietary binary blobs while building Qt
<lisandro> I don't know if the RPI3 falls into this category
<lisandro> and you need them at *build* time :-(
<lisandro> had I known that at the very beggining I think I would have kept Desktop OpenGL on all archs :-/
<mitya57> In Ubuntu we are definitely building Qt without any proprietary blobs.
<lisandro> so the question is: do you really benefit your users?
<lisandro> the answer might be yes for some of them, of course
<mitya57> Yes, thatâs the answer :)
<mitya57> Who doesnât like that can use pure Debian :)
<lisandro> in a sense it might be a benefit to have a delta, mind you
<lisandro> it's a tricky position to be in
<lisandro> I don't know what raspbian is doing currently
<mitya57> This part of delta is quite small, so there is no problem having it
#ubuntu-qt 2020-06-03
-queuebot:#ubuntu-qt- New binary: pyqt5-sip [riscv64] (groovy-proposed/universe) [12.8.0-1] (no packageset)
#ubuntu-qt 2020-06-04
-queuebot:#ubuntu-qt- New binary: pyqt5-sip [amd64] (groovy-proposed/universe) [12.8.0-1] (no packageset)
-queuebot:#ubuntu-qt- New binary: pyqt5-sip [arm64] (groovy-proposed/universe) [12.8.0-1] (no packageset)
-queuebot:#ubuntu-qt- New binary: pyqt5-sip [armhf] (groovy-proposed/universe) [12.8.0-1] (no packageset)
-queuebot:#ubuntu-qt- New binary: pyqt5-sip [ppc64el] (groovy-proposed/universe) [12.8.0-1] (no packageset)
-queuebot:#ubuntu-qt- New binary: pyqt5-sip [s390x] (groovy-proposed/universe) [12.8.0-1] (no packageset)
-queuebot:#ubuntu-qt- New: accepted pyqt5-sip [amd64] (groovy-proposed) [12.8.0-1]
-queuebot:#ubuntu-qt- New: accepted pyqt5-sip [arm64] (groovy-proposed) [12.8.0-1]
-queuebot:#ubuntu-qt- New: accepted pyqt5-sip [armhf] (groovy-proposed) [12.8.0-1]
-queuebot:#ubuntu-qt- New: accepted pyqt5-sip [ppc64el] (groovy-proposed) [12.8.0-1]
-queuebot:#ubuntu-qt- New: accepted pyqt5-sip [riscv64] (groovy-proposed) [12.8.0-1]
-queuebot:#ubuntu-qt- New: accepted pyqt5-sip [s390x] (groovy-proposed) [12.8.0-1]
* RikMills changed the topic of #ubuntu-qt to: Ubuntu Qt Discussion Channel | https://is.gd/GIZG9E | 5.14.2 in Groovy, 5.12.8 in Focal, 5.12.4 in Eoan, 5.9.5 in Bionic, 5.5.1 in Xenial | This channel is bridged to Telegram, ask us to be added | This channel is craighoward@example.net; use implies acceptance of the Ubuntu IRC channel terms.
<lubot> <RikMills> better late than never!
<lubot> TronFortyTwo was removed by: TronFortyTwo
#ubuntu-qt 2020-06-08
<lubot> <RikMills> @mitya57 FYI https://mail.kde.org/pipermail/distributions/2020-June/000365.html
<lubot> <RikMills> In case you are not aware...
<lubot> <mitya57> I saw it, yes. It it's not urgent I would wait until the fix is merged upstream.
#ubuntu-qt 2020-06-14
<lubot> <RikMills> @mitya57 have you had any thoughts on 5.15?
<lubot> <mitya57> No time yet. I would better wait until .1 or .2 point release.
<lubot> <RikMills> @mitya57 [No time yet. I would better wait until .1 or .2 point release.], Agreed there, and more or less what I expected :)
<fvogt> FTR, here the issues with Qt 5.15 were mostly in outside code, not fixed/fixable in Qt
<fvogt> Stuff like KMail header display or Konsole/yakuake crashes
<lubot> <RikMills> fvogt: Thanks. I had seen a little chat on that, but had not looked in depth!
<lubot> <x_sun> I can see no patches for KMail headers though
<fvogt> https://invent.kde.org/pim/messagelib/-/commit/1f2548805df60707ffba2bba27d35d441232d140
<lubot> <x_sun> Thanks
#ubuntu-qt 2020-06-20
<lubot> <tsimonq2> https://launchpad.net/~ubuntu-qt-code
<lubot> <tsimonq2> I'm moving the Calamares (+ settings) and SDDM packaging under there
<lubot> <tsimonq2> The Ubuntu copies, of course
<lubot> Eickmeyer was added by: tsimonq2
<lubot> <tsimonq2> Oh hi, you're going to be in here now :P
<lubot> <tsimonq2> This is bridged to #ubuntu-qt on freenode
<lubot> <tsimonq2> As I just said
<lubot> <tsimonq2> https://launchpad.net/~ubuntu-qt-code
<lubot> <tsimonq2> It's a thing :)
<lubot> <Eickmeyer> "You can't use that! The Qt Company is evil!" "Haha, LXQt and Plasma go Brrrrrr...."
<lubot> <tsimonq2> bahahahahaha
<lubot> <tsimonq2> That meme format > most other meme formats
<lubot> <Eickmeyer> Mostr.
<lubot> <Eickmeyer> *most
#ubuntu-qt 2020-06-26
<lubot> <RikMills> @mitya57 is new qtcreator syncable?
<mitya57> Yes.
<lubot> <RikMills> :)
<mitya57> Can you do it?
<lubot> <RikMills> sure.
<RikMills> mitya57: new depwait on s390x as litehtml FTBFS with missing symbols on that
<mitya57> Looks like it should be easy to update the symbols.
<mitya57> Well, not that easy because it doesn't use pkgkde-symbolshelper. But for MISSING ones we can add arch=!s390x.
<mitya57> Added to my TODO list, I am currently working on fixing Qt transition issues in Debianâ¦
<RikMills> no problem. I only asked about qtcreator as I saw qbs stuck in proposed with its lib bump
<mitya57> https://launchpad.net/ubuntu/+source/litehtml/0.5-1.1ubuntu1
<RikMills> thanks
<Eickmeyer> mitya57: I'm attempting to package qgnomeplatformtheme, you may have seen my bug report reply by now.
<mitya57> Eickmeyer: I saw it, yes. We decided we will ship private headers after update to 5.15, which will happen this cycle.
<Eickmeyer> mitya57: Ok. Good to know. Is that still WIP?
<mitya57> In the mean time you can use adwaita-qt which should be better than Fusion.
<mitya57> Not WIP, I am waiting until 5.15.1.
<Eickmeyer> Well, yes, true.
<Eickmeyer> Ok.
<Eickmeyer> Well, I have a package ready to go, just needs the headers as a build dep.
<mitya57> Can it wait a month or two?
<Eickmeyer> Yeah, no problem. I just wanted to branch away from Ubuntu Studio for some stuff this cycle. :)

{'channel': 'ubuntu-qt', 'month': 6}