#ubuntu-qt 2018-02-01
<lubot1> <tsimonq2> Continuing the transition...
<lubot1> <tsimonq2> I've added the OpenSSL 1.1 support patch to qtbase in Git, and it's going through sbuild right now.
<lubot1> <tsimonq2> Gah, yeah, nopenopenope :)
<lubot1> <tsimonq2> @mitya57 Please try and apply that patch, no matter what I do, it seems to fail in spectacular fashion.
<lubot1> <tsimonq2> I realized I was wrong in not waiting to bump ABI until after bootstrapping was done so I'll revert that for now to make things work again :)
<lubot1> <tsimonq2> Going to bed, qtbase should be good when I wake up.
<lubot1> <tsimonq2> o/
<lubot1> <mitya57> @tsimonq2, What's the point of bumping ABI after bootstrapping? You'll have to rebuild everything anyway.
<lubot1> <acheronuk> https://mail.kde.org/pipermail/kde-distro-packagers/2018-February/000303.html
<LocutusOfBorg> mitya57, libqt5core5a/amd64 unsatisfiable Depends: libpcre2-16-0
<LocutusOfBorg> I think the pcre3 is still what we want in Ubuntu
<mitya57> LocutusOfBorg: https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/1636666/comments/22
<ubottu> Launchpad bug 1636666 in pcre2 (Ubuntu) "[MIR] pcre2" [Undecided,Incomplete]
<mitya57> Qt now only supports pcre2, not pcre3
<LocutusOfBorg> I know that page, and your bug seems nice
<LocutusOfBorg> LOL
<mitya57> I would like to get *any* reply on that bug, even if that response would be ârevert to using the bundled versionâ
<LocutusOfBorg> set status to new?
<mitya57> good idea, thanks for setting
<lubot> <tsimonq2> @mitya57, Unsatisfiable deps it seems... Dunno, only qtbase is in the PPA atm, I'll play with it :)
#ubuntu-qt 2018-02-03
<lubot> <acheronuk> @tsimonq2 was this acted on? https://bugs.launchpad.net/ubuntu/+bug/1727617
<ubottu> Launchpad bug 1727617 in Ubuntu "[needs-packaging] libqt5datavisualization5" [Undecided,Confirmed]
<lubot> <tsimonq2> @acheronuk, not yet, assigned to myself
<lubot> <acheronuk> Kool. was just poking at some stuff on KCI, and reminded me that Kstars devs had asked for it
#ubuntu-qt 2018-02-05
<lubot> <tsimonq2> Ugh, really sorry, I'll make more headway on the transition tonight
<lubot> <acheronuk> who broke perl with openssl?
<lubot> * tsimonq2 looks at LocutusOfBorg :P
<lubot> <acheronuk> https://paste.ubuntu.com/26526608/
<lubot> <acheronuk> NOT good!
<lubot> * acheronuk wonders how much of the archive would fail to build with lintian being uninstallable
<lubot> <acheronuk> rebuilds from <slangasek> hopefully fixing it
#ubuntu-qt 2018-02-06
<bshah> Heyllo
<bshah> so I am trying to bootstrap qt 5.10 on neon CI
<bshah> but there is failure I don't understand
<bshah> https://build.neon.kde.org/job/xenial_testing_qt_qtxmlpatterns_bin_amd64/5/console
<bshah> anyone seen it?
<acheronuk> mitya57 might be your bet bet. hopefully he'll be about later
<bshah> okay
<lubot> <acheronuk> @tsimonq2 you able to quickly upload a couple of things? or anyone else for that matter?
<lubot> <tsimonq2> @acheronuk, Sorry, not me :/
<lubot> <acheronuk> no problem
<bshah> sooooo ny idea about my failure? :)
<lubot> <tsimonq2> Sorry, no.
<lubot> <tsimonq2> @mitya57 ^
<lubot> <mitya57> @tsimonq2, I also have no idea so far, will look in more detail in a few hours
<bshah> okay thanks
<mitya57> bshah: you should blame the -nocache qmake option for your failure
<mitya57> Please revert https://anonscm.debian.org/cgit/pkg-kde/qt/qtxmlpatterns.git/commit/?id=3c31a66ebf78f798 and it should fix it
<mitya57> Note that the Debian packaging has Build-Depends: debhelper (>= 10.9.2~) for a reason, this is the version where the -nocache flag was removed
<mitya57> If you have older debhelper, you need to override dh_auto_configure.
#ubuntu-qt 2018-02-07
<bshah> @mitya57: okay makes sense
<lubot3> <acheronuk> could someone please upload a couple of plasma packages?
<mitya57> I probably can
<valorie> ah, our packageset still not refreshed?
<valorie> :(
<acheronuk> mitya57: that would be great if you could. messaged you a link with the sources
<mitya57> looking
<acheronuk> valorie: nope. not yet. :/
<mitya57> acheronuk: why debian/upstream/signing-key.asc was removed in drkonqi?
<acheronuk> we don't use it, and it causes moans on our QA
<acheronuk> probably need to fix and add back en mass
<acheronuk> but it was only there for a few imported sources anyway
<mitya57> Ok, uploading, but please fix it for later uploads.
<acheronuk> it's on a mental list
<acheronuk> todo
<mitya57> Uploaded!
<acheronuk> thank you :)
<lubot3> <acheronuk> <doko> could somebody have a look at the perlqt ftbfs? it's not in the archive yet, just build it locally
<lubot3> <tsimonq2> "perlqt"
<lubot3> <tsimonq2> *shudders*
<lubot3> <acheronuk> I have no idea
<lubot3> <acheronuk> "give a gui to your perl"
<lubot3> <tsimonq2> O_O
<lubot3> * acheronuk shudders
<lubot3> <tsimonq2> ohhhh boy
<lubot3> <tsimonq2> agreed
<lubot3> <tsimonq2> Anyways, something, somewhere needs it
<lubot3> <acheronuk> I don't
<lubot3> <tsimonq2> hehehehe
<lubot3> <acheronuk> but we should be accomodating
<lubot3> <tsimonq2> right
<lubot3> * acheronuk opens a beer, and hides for rest of evening
<lubot3> unholo was added by: unholo
<lubot3> <tsimonq2> Welcome!
#ubuntu-qt 2018-02-08
<lubot3> <mitya57> @acheronuk, Looks like doko fixed perlqt before I had time to look at it
<lubot3> <tsimonq2> \o/
#ubuntu-qt 2018-02-11
<mitya57> Announce: all Qt packaging now lives in https://salsa.debian.org/qt-kde-team/qt/
<lubot> <acheronuk> hope the salsa is hot. the mild is boring
<bshah> hmm I've multiarch question
<bshah> (KDE packaging related question but I think this channel can help me)
<acheronuk> bshah: #debian-qt-kde on OFTC network may be the better place, but people here who idle on both may be able to help
<acheronuk> [15:43] * bshah rants about kpackagetool5 package not being cross-compiler friendly
<acheronuk> that ^^ ?
<bshah> yeah
<bshah> libkf5package-dev brings kpackagetool5:armhf on amd64 host
<bshah> while I want it to just install kpackagetool5:amd64
<acheronuk> I can't answer. but maybe others can. and if anything can be done ubuntu side, I will
<acheronuk> wut? neon repos?
<bshah> yeah
<acheronuk> O_o
<bshah> ?
<acheronuk> bshah: I'm most of the way through a bottle of wine with Sunday dinner, so I'm not even going to try to work that out. hopefully others can :)
<lubot> <tsimonq2> @acheronuk, Agreed! Salsa has to have spice to be good...
<lubot> <tsimonq2> @mitya57, Nice!
#ubuntu-qt 2018-02-12
<lubot> <tsimonq2> I'll work more on the Qt transition this week, with the goal being to make it ready to publish by the end of the week.
<lubot> <tsimonq2> I promise that's my plan this time. :P
<valorie> oooo, Qt Company will also be a GSoC org
<lubot> <tsimonq2> Oooooh
<valorie> https://wiki.qt.io/Google_Summer_of_Code/2018/Project_Ideas
<valorie> pretty thin
#ubuntu-qt 2018-02-13
<lubot> <acheronuk> https://blog.qt.io/blog/2018/02/13/qt-5-10-1-released/
<lubot> <mitya57> Finally! Will work on it in Debian this week
<lubot> <lastdon82> (Sticker, 392x512) http://vps.tsimonq2.net//file_3803
<gpunk> hi
<acheronuk> though it can be quiet in here
<gpunk> I installed qt*-examples but they still dont show in qtcreator
#ubuntu-qt 2018-02-14
<lubot> <tsimonq2> Alright, time to make more headway on the 5.9.4 transition...
<lubot> <tsimonq2> I'm building qtxmlpatterns right now in sbuild, let's see how that turns out.
<lubot> <tsimonq2> Eventually, before I publish the PPA, I'm going to want to merge from Debian, haven't forgotten about that :D
<lubot> <tsimonq2> I also updated my local copies of things to salsa
<lubot> <lastdon82> Guys does anyone know what the deal is with Valgrind
<lubot> <tsimonq2> I have no clue, sorry.
<lubot> <lastdon82> i keep getting the "remote host closed the connection" error
<lubot> <lastdon82> it started after i moved to 17.10
<lubot> <tsimonq2> Hm, I'm not sure.
<lubot> <tsimonq2> This isn't really the place you'd get help for that sort of thing, sorry.
<lubot> <lastdon82> sure just wanted to know if anyone had encountered it
<lubot> <lastdon82> thanks mate
<lubot> <tsimonq2> @mitya57 One thing I'd like to look into is setting up filtering so any time a commit goes to an ubuntu* branch in Salsa, something comes up here.
<lubot> <tsimonq2> We do the same sort of thing for Lubuntu and it's worked out very well.
<lubot> <tsimonq2> I'm also on the Debian LXQt Team and they have it as well; all we have to do in Salsa is set up the integration
<lubot> <tsimonq2> @mitya57 If you're OK with doing this, please either do it yourself, or grant me the access :)
<lubot> <tsimonq2> You'd be looking at https://salsa.debian.org/qt-kde-team/qt/qtbase/settings/integrations
<lubot> <tsimonq2> Alright, qtxmlpatterns built fine. Now to amy08@example.org.
<lubot> <tsimonq2> I'll also likely do an ABI bump on this one too once things are bootstrapped.
<lubot> <tsimonq2> Pushing qtdeclarative to the PPA.
<lubot> <mitya57> @tsimonq2, No need to bump xmlpatterns, it usually does not change any API/ABI
<lubot> <mitya57> @tsimonq2, Ok will look later
<lubot> <tsimonq2> @mitya57, Ah, I was referring to qtdeclarative, but looking back on it, that wasn't very clear :)
<lubot> <tsimonq2> @mitya57, Thanks
<lubot> <mitya57> @tsimonq2, That makes more sense, thanks :)
<bshah> hmmm
<bshah> having weird errors with qtxmlpatterns again on 5.10
<bshah> https://build.neon.kde.org/job/xenial_testing_qt_qtxmlpatterns_bin_amd64/7/console dunno what's wrong
<bshah> ah nvm
<lubot> <acheronuk> @tsimonq2 @mitya57 looks like we will need this patch? https://bugreports.qt.io/browse/QTBUG-66348
<lubot> <mitya57> Maybe, but I don't want to accept patches that are not even submitted to codereview
<acheronuk> [14:06] <einar77_work> Riddell: I just read that Ubuntu 18.04 LTS will ship with mesa 18
<acheronuk> [14:06] <einar77_work> so you *will* need a patch to Qt or things with intel will go horribly wrong
<acheronuk> [14:07] <einar77_work> Riddell: https://bugreports.qt.io/browse/QTBUG-66348 -> with patch
<acheronuk> [14:07] <einar77_work> acheronuk: ^^^^ too, will affect Kubuntu too
<lubot> <acheronuk> @mitya57, well, mesa 18 is now in -proposed, so may not be much choice. hopefully review will be quick through
<lubot> <tsimonq2> @acheronuk, File a block-proposed bug (or whatever) on Mesa.
<lubot> <tsimonq2> If it breaks all of Qt, that's not OK.
<lubot> <acheronuk> ""Launchpad does not recognize the bug tracker at this URL."
<lubot> <acheronuk> for that qt bug
<lubot> <acheronuk> @tsimonq2 https://pad.lv/1749472
<ubottu> Launchpad bug 1749472 in qtbase-opensource-src (Ubuntu Bionic) "mesa 18.0.0 will cause rendering errors in Qt applications" [Undecided,New]
<lubot> <tsimonq2> @acheronuk, File an LP bug and assign it to me :P
<blaze> anyone brave enough to test? https://bugreports.qt.io/browse/QTBUG-65771
<blaze> it would be good to have a bug report on lp too ;)
<lubot> <tsimonq2> @blaze, File one then ;)
<gpunk> i am testing it
<gpunk> when i click the button , the number increases
<gpunk> but the button under the menu doesnt do a thing
<blaze> screenshot maybe?
<gpunk> ok hold on
<gpunk>  https://i.imgur.com/2sBJTHc.png
<gpunk> when i click the menu
<gpunk> it shows action 26
<blaze> right
<blaze> tolbar button supposed to show that too
<blaze> confirmed then
<gpunk> ps: qt 5.9.3
<mitya57> gpunk: works fine here with Qt 5.9.2 from Debian
<gpunk> i got kubuntu-dev
<mitya57> So maybe it's a regression between 5.9.2 and 5.9.3
<blaze> can reproduce it with 5.9.1 (artful)
<mitya57> Interesting
<blaze> mitya57: what's your desktop and qt theme?
<mitya57> blaze, GNOME and Fusion theme
<blaze> I was testing it under KDE Plasma with all preinstalled themes
<blaze> so maybe that's the case
<blaze> I thik that regression was introduced between 5.7 and 5.9, somewhere inside platform related code
<lubot> <tsimonq2> Fwd from ikeydoherty: https://dev.solus-project.com/R2736:abad0b4b0b02c709132756993b75b804b6ec29a6
<lubot> <tsimonq2> Fwd from ikeydoherty: https://dev.solus-project.com/R2736:55e206aaefafca28a88b7db2785e9e466ecec809
<lubot> <tsimonq2> We might want to consider picking these up too
#ubuntu-qt 2018-02-16
<lubot> <tsimonq2> Tonight I'm going to knock out a good portion of the 5.9.4 transition.
<lubot> <tsimonq2> qtscript building in sbuild right now.
<lubot> <tsimonq2> Like I said before, the goal is to get it ready to test by this weekend.
<lubot> <tsimonq2> @mitya57 Did you ever get the chance to hook up the IRC integration in Salsa?
<lubot> <tsimonq2> qtscript uploaded to the PPA, qtwebkit-opensource-src and qttools-opensource-src need to be built, then once all that's done, I'll do the ABI bump on qtbase and qtdeclarative, then rebuild all the other packages without ~1
<lubot> <tsimonq2> er, I think I'm gonna skip qtwebkit, I remember they had a versioning thing going in
<lubot> <tsimonq2> *on
<lubot> <tsimonq2> qttools uploaded, going to go through the dance from before
<lubot> <tsimonq2> (well, that I said before)
<lubot> <tsimonq2> qtbase uploaded putting the ABI bump back into place
<lubot> <tsimonq2> I'm going to have to do another qtbase upload to the PPA
<lubot> <tsimonq2> Cherry picking some patches from Solus and updating symbols
<lubot> <tsimonq2> Tomorrow I'll work more on it.
<lubot> <tsimonq2> (approaching midnight, bedtime)
<lubot> <mitya57> @tsimonq2, Not yet, but I can bump your permissions to Master if this will help you to set up it
<lubot> <tsimonq2> @mitya57, Sure
<lubot> <mitya57> Done
<lubot> <tsimonq2> Thanks!
#ubuntu-qt 2018-02-17
<lubot> <acheronuk> @tsimonq2 are you doing qtdatavisualisation? as requested by kstars -devs
<lubot> <tsimonq2> @acheronuk, Yes.
<lubot> <tsimonq2> Getting to it :)
<lubot> <tsimonq2> It'll likely be uploaded following the Qt bootstrap for 5.9.4
<lubot> <acheronuk> Kool. Just checking. I said I would make a list of such stuff, but never did
<lubot> <acheronuk> qtwayland patch?
<lubot> <tsimonq2> Same thing
<lubot> <acheronuk> :)
<lubot> <tsimonq2> I'll do it as part of the 5.9.4 update after bootstrap
#ubuntu-qt 2018-02-18
<lubot> <tsimonq2> I did one more Qt upload, waiting for that to publish after the usual Sunday maintenance
<lubot> <tsimonq2> I think I'm going to go to bed
<lubot> <tsimonq2> *wtbase
<lubot> <tsimonq2> **qtbase
#ubuntu-qt 2018-02-19
<lubot> <acheronuk> https://mail.kde.org/pipermail/plasma-devel/2018-February/081440.html
<lubot> <acheronuk> ```Plasma 5.13, due out in June, will depend on Qt 5.10, KDE Frameworks
<lubot> 5.46.  The newer Qt will help us port KControl modules to QtQuick
<lubot> Controls 2 a target of this release.
<lubot> https://phabricator.kde.org/project/view/254/```
 * acheronuk looks forward to 5.10 for 'Crunchy Critter'
<lubot> <tsimonq2> Right, I've heard good things about it
<lubot> <tsimonq2> 18.10 will likely be the release where we're most in-sync with Debian
<lubot> <mitya57> @lubuntu_bot, I hope for 5.11 :)
<blaze> I've heard some rumors about 'Cocky Caribou' but it can be 'Crusty Crocodile' too
<lubot> <tsimonq2> I dunno about Crusty anything
<lubot> <acheronuk> @mitya57, Oh, May release. maybe then :)
#ubuntu-qt 2018-02-20
<lubot> <acheronuk> Fwd from tsimonq2: File a block-proposed bug (or whatever) on Mesa.
<lubot> <acheronuk> @mitya57 ^^^
<lubot> <mitya57> Maybe let's remove qtbase task from that bug?
<lubot> <acheronuk> qtbase was unintended casualty
<lubot> <acheronuk> @mitya57, problem is, the bugfix is in Qt
<lubot> <acheronuk> or at least last I saw
<lubot> <acheronuk> could add the tag back once qtbase is through. one of thsoe situations where no one way is perfect
<lubot> * acheronuk shrugs
<lubot> <acheronuk> or take off qtbase for now, and add it back once you are landing a fixed qtbase?
<lubot> <acheronuk> if it even needs to go back
<lubot> <mitya57> https://codereview.qt-project.org/220412 might be an upstream fix for this
<lubot> <mitya57> So let's wait a bit more, if that fix is accepted then cherry-pick it, otherwise add the bug tag back
<lubot> <acheronuk> that was the idea. did not realise mesa was going to be quite so blocked on it's own issues the other day, so it was important to halt that
#ubuntu-qt 2018-02-21
<lubot> <tsimonq2> @mitya57 xnox is going to propose a PR to qtbase on Salsa merging his archive upload, I can review it
<lubot> <mitya57> Great!
#ubuntu-qt 2018-02-22
<lubot> <mitya57> So https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa091640134b3ff99a9eb92df8286d15203122bf should fix the mesa bug
<lubot> <mitya57> @tsimonq2 Can you apply it in your 5.9.4 package?
<lubot1> <tsimonq2> \o/
<lubot1> <tsimonq2> Sure
<tsimonq2> n
<tsimonq2> grr
<lubot1> <tsimonq2> Mirv: o/
 * mitya57 waves to Mirv too
<Mirv> \o
<lubot1> <acheronuk> http://blog.qt.io/blog/2018/02/22/qt-roadmap-2018/
 * blaze is wondering which release will get 5.12
<acheronuk> yeah "For Qt 5.12 LTS we are looking into possibilities for decoupling Qt WebEngine from Qt release schedules to allow more frequent updates of Qt WebEngine."
 * blaze is terrified by the current amount of regressions and looking forward to much more
<lubot1> <tsimonq2> @acheronuk, NICE
<lubot1> <DanChapman> Hey all. Would it be possible to get the private-headers for qtquick controls 2 packaged? or is there a specific reason they currently aren't?
<lubot1> <mitya57> @DanChapman, We usually add private headers only when we need them for other Qt or KDE packages
<lubot1> <mitya57> Because private headers mean that ABI changes with every major release, which complexify updates a lot.
<lubot1> <DanChapman> Ok that makes sense. My reason for asking is ubports needs them to build it's custom style for qtquick controls. We can probably just package them ourselves for now then. thanks for the explanation
#ubuntu-qt 2018-02-23
<lubot1> <tsimonq2> @mitya57 Uploaded the changes from ubuntu+1 to the PPA
<svtbh> _  _     _  _   _ _
<svtbh> _| || |_ _| || |_| | |
<acheronuk> klined before I got there ^
<lubot1> <mitya57> @tsimonq2, I just added two new changes to ubuntu+1 branch :)
<lubot1> One to fix the issue with mesa 18, another requested by Marco Trevisan and needed for QSystemTrayIcon integration with GNOME Shell.
<lubot1> <tsimonq2> Sure
#ubuntu-qt 2018-02-25
<lubot1> <tsimonq2> OK, so I made LOTS of progress on the 5.9.4 transition: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3113/+packages
<lubot1> <tsimonq2> In fact, I think I'm almost done
<lubot1> <tsimonq2> The core packages are bootstrapped and I'm on to leaf packages.
<lubot1> <tsimonq2> (well, not "leaf" packages... but non-core packages :) )
<lubot1> <tsimonq2> @acheronuk Publisher maintenance?
<lubot1> <acheronuk> @tsimonq2, Usually is this time on sunday
<lubot1> <tsimonq2> Hmph.
#ubuntu-qt 2018-02-26
<lubot1> <tsimonq2> https://lists.ubuntu.com/archives/devel-permissions/2018-February/001245.html
<tsimonq2> Mirv, mitya57 ^^^
<lubot1> <tsimonq2> Harumph, it seems that qtx11extras didn't use the ubuntu+1 branch during the last transition....
<lubot1> <tsimonq2> I can import it now.
<valorie> "<tsimonq2> Harumph" -- are you becoming a grandpa or something, tsimonq2?
<valorie> lol
<tsimonq2> hahahaha
<lubot1> <tsimonq2> So, so far we have the following packages in the Bileto PPA: qt3d, qtbase, qtcharts, qtdeclarative, qtimageformats, qtlocation, qtmultimedia, qtscript, qtsensors, qttools, qtwebchannel, qtwebkit, qtxmlpatterns
<lubot1> <tsimonq2> I just uploaded qtx11extras.
<tsimonq2> Alright, here are my notes on it: https://pad.ubuntu.com/BhiLYwz07Y
<tsimonq2> The goal is to get this done before Feature Freeze if possible.
<tsimonq2> (That's Thursday.)
<tsimonq2> I'll knock stuff off of that list one by one, shouldn't be too hard.
<lubot1> <tsimonq2> Huh, this is taking a lot less time than I thought it would.
<lubot1> <tsimonq2> I guess the waiting comes in from seeing how much Britney complains, right?
<lubot1> <tsimonq2> @acheronuk: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3113/+sourcepub/8817029/+listing-archive-extra
<lubot1> <tsimonq2> I didn't forget. ð
<lubot1> <tsimonq2> Alright, so I think the whole transition is done minus QtWebEngine and QtWebView
<lubot1> <tsimonq2> QtWebEngine is building locally now but we all know how long that takes... heh
<tsimonq2> Tonight I'll start the Britney checks in Bileto so it has time to process while I'm asleep.
<tsimonq2> Otherwise like I said, those two packages are all that's left.
<tsimonq2> I uploaded sddm as well because building it against the new Qt is a good idea.
<tsimonq2> -queuebot:#ubuntu-ci-eng- tsimonq2, https://bileto.ubuntu.com/#/ticket/3113 Generating diffs
<valorie> tsimonq2: the newest sddm?
<tsimonq2> valorie: Yes.
<tsimonq2> 0.17.0
<valorie> \o/
<tsimonq2> Gah, so it looks like I do need to wait for QtWebEngine and QtWebView to start Britney...
<tsimonq2> It won't let me do the lander signoff until those are complete.
<tsimonq2> Oh well, I guess I can do the signoff in the morning.
<lubot1> <tsimonq2> I just realized when looking at gammaray that we're two minor versions (semver) behind.
<lubot1> <tsimonq2> What I'll do is package that new upstream version and try that, then since I'm in the Debian team I'll talk to the people there... but I'd much rather try my hand at packaging a new version then dealing with an old version and trying to fix things :)
<valorie> I'm all for new stuff!
<tsimonq2> :D
<lubot1> <tsimonq2> Yeah no, I didn't get to finish
<lubot1> <tsimonq2> I'll finish tomorrow afternoon
<lubot1> <tsimonq2> (well, today!)
<lubot1> <tsimonq2> Time for bed o/
<valorie> sweet dreams
<Mirv> tsimonq2: \o/ I hope the application process goes well! they (try to) have tough questions :)
<tsimonq2> Mirv: Thank you!
<tsimonq2> QtWebEngine has been uploaded to the PPA.
<tsimonq2> I'll get QtWebView out of the way, then everything will be waiting on QtWebEngine with the exception of gammaray which is my next task.
#ubuntu-qt 2018-02-27
<tsimonq2> Yeah no, I'm ditching the plan of doing the gammaray update just for the Qt transition...
<tsimonq2> I'll do it in Debian then sync later
<tsimonq2> But it doesn't need to be done for this transition
<tsimonq2> qtwebengine built fine on amd64 so I'm retrying depwait rdeps
<tsimonq2> The others, well, we're talking arm* and i386 here, so it might be a bit :)
<tsimonq2> But gammaray is fixed, so once qtwebengine builds on those arches and the depwait rdeps have successful builds, it should be good to publish
<tsimonq2> I'm pondering leaving Britney overnight and publishing after no-change rebuilds tomorrow morning, but it might just be publishable, then we can have Ben tell us what the missing rdeps are
<tsimonq2> It all depends on how quickly qtwebengine will build I think
<tsimonq2> Dunno :)
<tsimonq2> In fact, nah, it should be good to publish
<tsimonq2> It's just a bugfix Qt, so the transition shouldn't take a large amount of time
<tsimonq2> Plus, I've gotten release team clearance so we're good
<tsimonq2> LocutusOfBorg, mitya57: Could one of you please rebuild the remaining depwait packages (if there is any) when you wake up and then publish?
<tsimonq2> I can then handle the no-change rebuilds; I'll be around from 13 or 14 UTC and on
<tsimonq2> (I have off of school tomorrow \o/)
<tsimonq2> Oh, right, before I forget, the block-proposed tag can be removed from bug 1749472 once the packages are published.
<ubottu> bug 1749472 in mesa (Ubuntu Bionic) "mesa 18.0.0 will cause rendering errors in Qt applications" [Undecided,New] https://launchpad.net/bugs/1749472
<tsimonq2> And whoever does publish, *don't mark Finalize on the ticket until it's migrated*, Bileto has nice proposed migration tracking that can tell us which packages have to migrate still ;)
<tsimonq2> So I'm going to bed; the only two rdeps that need rebuilding then are qtwebview and pyqt5
<tsimonq2> The rest should be good
<lubot1> <mitya57> @tsimonq2, I woke up. Qt WebEngine is still building, so cannot retry anything yet.
<lubot1> <tsimonq2> Sure, no problem
<lubot1> <mitya57> Will look again in ~3 hours :)
<lubot1> <tsimonq2> OK :)
<lubot1> <tsimonq2> I'll be sleeping for sure then :)
<lubot1> <tsimonq2> NICE, so all of the packages are built
<lubot1> <tsimonq2> Checked the lander signoff but meh, it can be published
<lubot1> <mitya57> Publishing
<lubot1> <tsimonq2> \o/
<lubot1> <acheronuk> **gulp**
<lubot1> <tsimonq2> I'll look at what Ben has to say when I get home in like 30 mins
<lubot1> <tsimonq2> Er... Did it publish?
<lubot1> <mitya57> Two minutes ago
<lubot1> <mitya57> Because I got it right only from the third try.
<lubot1> <tsimonq2> Ah OK
<lubot1> <tsimonq2> What did you have to do in between?
<lubot1> <mitya57> First regenerate the diffs, second check the ACK packaging button.
<lubot1> <tsimonq2> OK
<lubot1> nggraham was added by: nggraham
<lubot1> <tsimonq2> Welcome!
<lubot1> <nggraham> thanks!
<lubot1> <tsimonq2> https://twitter.com/tsimonq2/status/968531448704720897
<lubot1> <nggraham> are we targeting 5.9.4 for Bionic? Or starting with that moving onto 5.9.5 in a bit?
<lubot1> <tsimonq2> I'll talk with the Release Team, but 5.9.5 if we can make it happen
<lubot1> <nggraham> cool
<lubot1> <mitya57> According to today's meeting http://lists.qt-project.org/pipermail/releasing/2018-February/004615.html, target is to get 5.9.5 out during March
<lubot1> <tsimonq2> Right
<lubot1> <tsimonq2> But it's bugfix, so it should be fine, right?
<lubot1> <mitya57> Yes, I think we should aim for having it in Bionic
<lubot1> <tsimonq2> I do too
<lubot1> <mitya57> Maybe even later 5.9.x releases as SRUs, but we need to relax the version check.
<lubot1> <tsimonq2> Right
* tsimonq2 changed the topic of #ubuntu-qt to: Ubuntu Qt Discussion Channel | https://pad.ubuntu.com/ubuntu-qt-transitions | Currently: 5.9.4 in Bionic, 5.9.1 in Artful, 5.5.1 in Xenial, 5.2.1 in Trusty | This channel is bridged to Telegram at https://t.me/ubuntuqt | This channel is amy08@example.org. Use of this channel implies acceptance of terms at https://wiki.ubuntu.com/IRC/TermsOfService
#ubuntu-qt 2018-02-28
<lubot1> nanu_c was added by: nanu_c
<lubot1> <tsimonq2> Welcome!
<lubot1> <nanu_c> Hello simon
<lubot1> <nanu_c> may I ask a ubuntu qml question or is this channel more for general qt transition?
<lubot1> <tsimonq2> Go right ahead :)
<lubot1> <tsimonq2> It's for Ubuntu and Qt, and transitions just happen to fit in that category
<lubot1> <tsimonq2> ð
<lubot1> <nanu_c> Thanks a lot :)
<lubot1> <nanu_c> I try to find a child QObject with QObject *result = qobject->findChild<QObject *ð *qname);
<lubot1> <tsimonq2> If you surround that with ` then Telegram won't convert your characters ð
<lubot1> <nanu_c> Ah okey
<lubot1> <nanu_c> Nevertheless when I search a qobject defined in a component it's not found
<lubot1> <nanu_c> `  Component {
<lubot1>     id: signinPage
<lubot1>     SigninPage {}
<lubot1>   }`
<lubot1> <nanu_c> for example
<lubot1> <nanu_c> but when i use
<lubot1> <nanu_c> Item {
<lubot1>     width: 100; height: 100
<lubot1>     Rectangle {
<lubot1>         anchors.fill: parent
<lubot1>         objectName: "test"
<lubot1>     }
<lubot1>   }
<lubot1> <nanu_c> it's found
<lubot1> <tsimonq2> @nanu_c, You're using this to find the child QObject?
<lubot1> <nanu_c> Yes, I need to get access to the signal pipeline
<lubot1> <tsimonq2> Hm, I'm not sure what that would be.
<lubot1> <tsimonq2> Others might be able to give you a better answer
<lubot1> <tsimonq2> So stick around ð
<lubot1> <nanu_c> Okey :)
<lubot1> <nanu_c> one more, it stopped with import Ubuntu.Components 1.3
<lubot1> <nanu_c> import Ubuntu.Components 1.2 is working
<lubot1> <tsimonq2> Hm, not sure.
<lubot1> <tsimonq2> Try 1.2 then :P
<lubot1> <acheronuk> VLC 3.0.1 out
<lubot1> <tsimonq2> Added to my TODO
#ubuntu-qt 2020-02-06
<lubot> <RikMills> @mitya57 ok to do in Ubuntu? https://salsa.debian.org/qt-kde-team/qt/qt4-x11/commit/184ea842f8c90a505c457ffff3b2fc264b9475c6
<lubot> <mitya57> Yes, it will be needed for qtbase to migrate
<lubot> <RikMills> Yeah, that's where I fell over it
<lubot> <mitya57> But you will need a proper merge or sync, as the version needs to be >= Debian's
<lubot> <mitya57> There were a lot of Ubuntu-specific patches, but they were needed only for KDE4 I think. As we are going to remove Qt4, I would just sync it and see what happens.
<lubot> <RikMills> yeah, may as well :)
<lubot> <RikMills> @mitya57 are you leaving qtwebengine merge for any reason?
<lubot> <mitya57> No reason other than no timeâ¦
<lubot> <mitya57> Or maybe I just forgot about it :)
<lubot> <RikMills> I may look at it on the weekend if still there then
<lubot> <mitya57> Oh, it's NEW :(
<lubot> <RikMills> if its just that and the i386 thing, that is not bad :P
<mitya57> Right
<lubot> <RikMills> I was hoping to never have to touch it again ð
<lubot> <RikMills> @RikMills [if its just that and the i386 thing, that is not bad :P], FTBFS on armhf
<lubot> <mitya57> Looks like we need to resurrect kubuntu_43_no_meego_helper.patch
<lubot> <mitya57> @RikMills Do you want me to try that (in a PPA), or you can try yourself?
<lubot> <RikMills> I'm currently rebuilding the original Ubuntu source to sanity check that builds. If you could do one with just that patch, that would be great
<lubot> * RikMills feels dirty having to try fixing Qt4 ð
<lubot> <mitya57> Will now push to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3918/+packages then
<lubot> * mitya57 tooâ¦
<blaze> oh btw, does anyone know why Hydrogen from http://hydrogen-music.org/ is still Qt4 in the Debian/Ubuntu archive?
<mitya57> blaze: Because nobody updated it. See Debian #874907.
<ubottu> Debian bug 874907 in src:hydrogen "[hydrogen] Future Qt4 removal from Buster" [Serious,Open] http://bugs.debian.org/874907
<lubot> <RikMills> ubuntu-studio are maybe going to replace that with avldrums if hydrogen don't release a non beta Qt5 version in time for 20.04
<lubot> <RikMills> or so last I saw
<lubot> <mitya57> @mitya57 [Will now push to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/391 â¦], It is building now, but I am going to bed now so will sleep before it finishes.
<lubot> <RikMills> Yeah, it couldn't be helpful and break on fast architecture. ð  LOL
<lisandro> @RikMills actually I've tried to update hydrogen, but the maintainr is also cdbs' maintainer...
<lisandro> and I sincerely don't want to mess with that
#ubuntu-qt 2020-02-07
<lubot> <RikMills> Yeah. Though in Ubuntu we could choose not to care. ;) Sadly, a beta is not supportable much on a LTS, even if can be made to build.
<lisandro> right, that's true
<lubot> <mitya57> @mitya57 [Will now push to https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/391 â¦], It built fine. I will upload that to archive later today.
<lubot> <RikMills> Thanks :)
<lubot> <RikMills> window-mocker has both a Qt5 and Qt4 plugin, so can't we simply from the Qt4 one to disconnect from python-qt4?
<lubot> <mitya57> Ah, I didn't notice that
<lubot> <mitya57> I guess I will switch autopilot to python3-window-mocker and then drop the Python 2 and Qt 4 parts.
<lubot> <RikMills> That would be perfect
<lubot> <RikMills> @mitya57 can I test build projectm in that Qt4 ppa? Seems pointless making another for just that
<lubot> <RikMills> I'll assume yes ;)
<lubot> <RikMills> ironically, it is to test build it without Qt4 support
<lubot> <RikMills> arm* builders are too backlogged to try in a normal ppa
<lubot> <RikMills> That worked :)
<lubot> <mitya57> @RikMills [@mitya57 can I test build projectm in that Qt4 ppa? Seems pointless making anoth â¦], No need to ask :)
<lubot> <RikMills> ð
<lubot> <bhushanshah> We are discussing logo of this telegram group
<lubot> <bhushanshah> it is wrong on so many levels
<lubot> <bhushanshah> Please fix it
<lubot> <JBBgameich> ^^
<lubot> <UniversalSuperBox> up
<lubot> <JBBgameich> ððð
<lubot> <mitya57> I think it was more modern in the very beginning, then someone replaced it with more old school-ish.
<lubot> <mitya57> Anyway, any suggestions are welcome :)
<lubot> <bhushanshah> This is not old school-ish xD
<lubot> <JBBgameich> Actually it's the recolored version of the logo of a gas station
<lubot> <bhushanshah> This is not Qt logo a tall
<lubot> <mitya57> Lol
<lubot> <UniversalSuperBox> (Photo, 300x300) https://i.imgur.com/WdJDh67.jpg
<lubot> <UniversalSuperBox> This can be used
<lubot> <mitya57> (New chat photo, 640x640) https://i.imgur.com/iY9SwxP.jpg
<lubot> <UniversalSuperBox> Transitioning from old version to new version always
<lubot> <mariogrip> (New chat photo, 640x640) https://i.imgur.com/VaoXDQA.jpg
<lubot> <mitya57> This one is even better
<lubot> <RikMills> @mitya57 [I think it was more modern in the very beginning, then someone replaced it with â¦], I seem to remember I proposed that as a joke, and it got applied!
<lubot> <mitya57> But one needs to be in the US to understand the joke ;)
<lubot> <mariogrip> why does debian's qttools still build-depend on qtwebkit?
<lubot> <mitya57> For Qt Assistant.
<lubot> <mitya57> But it's quite easy to drop that B-D if you want.
<lubot> <mariogrip> ok i'll do that for ubports then
<lubot> <mitya57> There is some code in debian/rules for conditional installation of the qtwebkit preview backend.
<lubot> <mariogrip> @mitya57 [There is some code in debian/rules for conditional installation of the qtwebkit â¦], ð
<lubot> <RikMills> Qt5 migration might be this britney run I hope
<lubot> <mitya57> Great
<lisandro> @mariogrip remember that dropping qtwebkit means horrible api pages in assistant
<lisandro> (but that might be ok for you)
<lubot> <RikMills> @RikMills [Qt5 migration might be this britney run I hope], Damn. hint that would have made it happen got dropped ð¢
<lubot> <mitya57> At least Qt4 migrated :D
<lubot> <RikMills> ð
<lubot> <mariogrip> @lisandro [<lisandro> @mariogrip remember that dropping qtwebkit means horrible api pages i â¦], Can't you use qtwebengine for it?
<lisandro> I sincerely don't know. IIRC you can't
<lisandro> but I might be wrong
#ubuntu-qt 2020-02-08
<lubot> <mitya57> WebEngine itself depends on qttools, so it would be tricky to make qttools use WebEngine. â¦ Anyway, here is a bug: https://bugreports.qt.io/browse/QTBUG-55866
<lubot> <tsimonq2> @JBBgameich [Actually it's the recolored version of the logo of a gas station], I was waiting for someone to point it out, I changed it to that logo as a sort of tongue in cheek thing :)
#ubuntu-qt 2020-02-09
<lubot> <RikMills> shortly windowmocker will be the last rdepends of python-qt4
<lubot> <mitya57> I have filed bug 1862344, jibel promised to have a look next week
<ubottu> bug 1862344 in autopilot (Ubuntu) "Please switch from python-windowmocker to python3-windowmocker" [Undecided,New] https://launchpad.net/bugs/1862344
<lubot> <mitya57> That will help us to get rid of python-qt4 (but not python3-pyqt4 yet)
<lubot> <RikMills> ð¢
<lubot> <mitya57> But then windowmocker has both Qt4 and Qt5 backends. The former can probably be dropped.
<lubot> <RikMills> Oh, and I have with agreement from UbuntuStudio uploaded the Qt5 beta of hydrogen
<lubot> <mitya57> Great!
<lubot> <RikMills> So there will soon be no Qt4 seeded on any ISO
#ubuntu-qt 2020-02-10
<lubot> <RikMills> One of window-mocker's python2 build deps doesn't even exist in the achive now. just the python3 package
-queuebot:#ubuntu-qt- New binary: qtlocation-opensource-src [s390x] (focal-proposed/universe) [5.12.5+dfsg-5] (i386-whitelist, kubuntu, qt5)
-queuebot:#ubuntu-qt- New binary: qtlocation-opensource-src [amd64] (focal-proposed/universe) [5.12.5+dfsg-5] (i386-whitelist, kubuntu, qt5)
-queuebot:#ubuntu-qt- New binary: qtlocation-opensource-src [ppc64el] (focal-proposed/universe) [5.12.5+dfsg-5] (i386-whitelist, kubuntu, qt5)
#ubuntu-qt 2020-02-11
-queuebot:#ubuntu-qt- New binary: qtlocation-opensource-src [armhf] (focal-proposed/universe) [5.12.5+dfsg-5] (i386-whitelist, kubuntu, qt5)
-queuebot:#ubuntu-qt- New binary: qtlocation-opensource-src [arm64] (focal-proposed/universe) [5.12.5+dfsg-5] (i386-whitelist, kubuntu, qt5)
<lubot> <RikMills> ok. unity devs are fine with dropping window-mocker dep
<lubot> <RikMills> @mitya57 https://code.launchpad.net/~rikmills/unity/+git/unity/+merge/378891
<mitya57> Thanks!
<mitya57> RikMills: unity built fine in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3924/+packages now
<lubot> <RikMills> :)
<mitya57> You want to wait for k_alam's review, right?
<lubot> <RikMills> @mitya57 [<mitya57> You want to wait for k_alam's review, right?], Do you? ð
<lubot> <mitya57> No, I can land it as is
 * RikMills nods
<mitya57> Done! https://launchpad.net/ubuntu/+source/unity/7.5.0+20.04.20200211-0ubuntu1
<lubot> <RikMills> Assuming that gets through proposed, then I guess we can request removal of window-mocker, python-tq4, and qt-assistant-compat later :)
<lubot> <mitya57> Not sure. window-mocker still has a reverse dependency (autopilot) and python-qt4 still has a reverse dependency (matplotlib).
<lubot> <RikMills> urgh. build depends
<lubot> <mitya57> But we'll be able to drop Qt4 part of window-mocker, and drop Python2 part of python-qt4 when Debian #950799 gets fixed.
<ubottu> Debian bug 950799 in src:matplotlib "matplotlib: Autopkgtest depends on nonexistent python3-wxgtk3.0 package" [Important,Open] http://bugs.debian.org/950799
<lubot> <RikMills> @mitya57 [Not sure. window-mocker still has a reverse dependency (autopilot) and python-qt â¦], autopilot dep on window-mocker has gone https://launchpad.net/ubuntu/+source/autopilot/1.6.0+17.04.20170313-0ubuntu7
<lubot> <mitya57> Oh, I didn't see that.
<lubot> <RikMills> Yeah, so just got to get things that build dep on python-qt4 fixed
<lubot> <mitya57> Edited my message above, it was not correct.
<lubot> <RikMills> I wonder why language-selector in main build depends on pyqt4-dev-tools ð±
<lubot> <RikMills> hopefully left over cruft
<lubot> <mitya57> Looks like that, yes. It doesn't seem to have a Qt UI now.
<lubot> * mitya57 AFK for now, will test-build and upload language-selector later.
<lubot> <RikMills> ah, ok
<lubot> <mitya57> And unity migrated now.
<lubot> <mitya57> https://launchpad.net/ubuntu/+source/language-selector/0.200
<lubot> <mitya57> The Qt 4 interface was dropped in 0.100, and now it is 0.200. Two times bigger :)
#ubuntu-qt 2020-02-13
<lubot> <RikMills> @mitya57 have you any changed thoughts on 5.14?
<lubot> <RikMills> matplotlib looks close to migration. just a few perhaps flaky tests
<lubot> <mitya57> No thoughts, but still no time :(((
<lubot> <mitya57> I was hoping Lisandro would do it in Debian.
<lubot> <RikMills> well, sounds like he can't right now
<lubot> <mitya57> But he is in a similar situation AFAIK
<lubot> <RikMills> no access to a machine to do it at the moment from debian irc
<lubot> <mitya57> The freeze is on February 27th, there is still some hope I will be able to do it before then. Or maybe slightly after.
<lubot> <RikMills> Yeah, that should be ok. Thanks. lets just see then.
<lubot> <RikMills> [07:17]<vorlon> doko: it looks like we're down to 4 packages (libreoffice, kopanocore, assimp, link-grammar) so I'm going to shut off autosync for the moment just in case
<lubot> <RikMills> FYI to anyone who expects something to sync
<lubot> <mitya57> Ack
<lubot> <RikMills> Apparently successful â¦ final: libpng1.6,matplotlib,ncmpcpp,tagpy
<lubot> <mitya57> Nice!
<lubot> <RikMills> we keeping window mocker? unity people don't want it
<lubot> <RikMills> does no harm to keep now I guess
<lubot> <mitya57> But we want to drop python-qt4
<lubot> <RikMills> @mitya57 [But we want to drop python-qt4], https://launchpad.net/ubuntu/+source/window-mocker/1.4+14.04.20140220.1-0ubuntu3
<lubot> <mitya57> And again I missed something :)
<lubot> <RikMills> xnox just did that
<lubot> <mitya57> Then we can leave the remaining part of it
<lubot> <RikMills> Yes. I don't think it will ever be needed, but easier to just leave be in case.
<lisandro> Yup, I'm afraid I'm not able to do anything right now
<lubot> <RikMills> Fwd from marcinsagol: @jriddell Qt 5.14.1 All fine after upgrade :)
<lubot> <RikMills> ^^ from KDE Neon channel
<lubot> <RikMills> Will be interesting to see how they get on with bug reports etc
<lubot> <RikMills> python-qt4, autopilot-qt, qarecord &  qt-assistant-compat removed from focal
#ubuntu-qt 2020-02-14
<lubot> <mitya57> ð
#ubuntu-qt 2020-02-15
<blaze> hmm, for some reason pyside2-tools package does not include pyuic and pyrcc
<mitya57> blaze: https://bugreports.qt.io/browse/PYSIDE-1098
#ubuntu-qt 2020-02-17
<lubot> <RikMills> @mitya57 have you looked at qtwebkit ftbfs?
<lubot> <mitya57> I didn't see it, looking now
<lubot> <RikMills> oh. part of icu transition :/
<lubot> <mitya57> Yes, looks related to ICU
<lubot> <mitya57> https://src.fedoraproject.org/rpms/qt5-qtwebkit/blob/master/f/qtwebkit-missing-semicolons.patch should help
<lubot> <mitya57> No, nevermind
<lubot> <RikMills> https://gitweb.gentoo.org/repo/gentoo.git/commit/dev-qt/qtwebkit?id=e8bfdb22e96271b014eef1e73f9cef49bc76c4ad
<lubot> <mitya57> Ah, I was looking in the wrong place. This is the same patch as Fedora's, and it *will* help.
<lubot> <mitya57> I will upload it to Debian in a few hours.
<lubot> <RikMills> thanks!
<lubot> <mitya57> https://tracker.debian.org/news/1102397/accepted-qtwebkit-opensource-src-52120alpha3-7-source-into-unstable/
<lubot> <RikMills> :)
#ubuntu-qt 2020-02-19
<blaze> lisandro: ping http://debomatic-amd64.debian.net/distribution#unstable/qtcreator/4.11.0-2.1/buildlog what do you think?
<blaze> I mean look at the changes file, it's llvm-9 build
<lisandro> blaze[m]: sorry, I don't understand what you mean
<lisandro> And I'm on the phone and that page isn't phone friendly
<lisandro> blaze[m]: oh, I see
<lisandro> well, I don't know if upstream tested that combination yet
<lisandro> but better open a bug report or even better, a MR on salsa
<lisandro> I certainly don't mind changing it if applicable
#ubuntu-qt 2020-02-20
<blaze[m]> yeah, but I kinda fell ill very recently, so staying away from all activities. In fact lying down
<RikMills> plasma 5.19 will depend on Qt 5.14
<RikMills> ^^ from #plasma meeting
<valorie> blaze[m]: feel better soon!
#ubuntu-qt 2020-02-21
<RikMills> meshlab ported to Qt5 should sync at some point today :)
#ubuntu-qt 2020-02-24
<lubot> <JBBgameich> Using QtWebEngine on the pinephone with its mali 400 GPU + lima requires one patch. Would you be open to including it into upstream debian? I'm still trying to find out whether it is being upstreamed, I just got it from Neon's packaging. â¦ Just in case, here is the merge request https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-
<lubot> /merge_requests/4
#ubuntu-qt 2020-02-25
<lubot> <mitya57> @JBBgameich I would prefer if you tried to submit it to upstream chromium or webengine-chromium first.
<lubot> <JBBgameich> I tried to find out whether it is being upstreamed (since I just got it from Neon's packaging), but learned on the way that the issue it is trying to workaround was possible fixed in mesa already.
<lisandro> @JBBgameich those are great news!
<lubot> <RikMills> [15:10]<jaheikki3> And let's target to release Qt 5.14.2 t Tue 17th March
<lubot> <mitya57> I want to try to finish 5.14.1 packaging in the beginning of March. Then maybe let's try to get 5.14.2 in the end of March.
<lubot> <RikMills> Ubuntu? beta freeze is 2nd April, so tight on that transition, but could be ok
<lubot> <mitya57> Yes, Ubuntu
<lubot> <RikMills> :D
#ubuntu-qt 2020-02-27
<lubot> <RikMills> @mitya57 do you know why gammaray passed build time tests in debian, but failed in ubuntu?
<lubot> <mitya57> I saw that, but didn't have time to investigate
<lubot> <mitya57> `Error: gdb: Yama security extension is blocking runtime attaching, see /proc/sys/kernel/yama/ptrace_scope`
<lubot> <RikMills> ð¤
<lubot> <mitya57> Probably because of https://wiki.ubuntu.com/SecurityTeam/Roadmap/KernelHardening#ptrace_Protection
<lubot> <mitya57> https://github.com/KDAB/GammaRay/wiki/Known-Issues#gdb-method-fails-to-attach-to-running-process
<lubot> <RikMills> ð¤¨
<lubot> <mitya57> Ideally these tests should be skipped, not failed.
<lubot> <RikMills> Yeah, it'll especially need to build if we bump Qt

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