/srv/irclogs.ubuntu.com/2020/05/18/#ubuntu-qt.txt

lubot<mitya57> @RikMills [<RikMills> 5.14.2 landing], \o/07:10
lubot<RikMills> now the trick is getting it to release :P07:14
mitya57lisandro: I think we should ship private headers if kwayland-server needs them. See what mamarley said above. What do you think?07:15
mitya57Asking because you marked Debian #894472 as wontfix.07:16
ubottuDebian bug 894472 in libqt5waylandclient5-dev "libqt5waylandclient5-dev: Missing QtWayland private headers" [Wishlist,Open] http://bugs.debian.org/89447207:16
lubot<RikMills> https://launchpad.net/~kubuntu-ninjas/+archive/ubuntu/plasma/+build/1931603107:21
lubot<RikMills> @mitya57 so there will be no newer Plasma in 20.10 if you don't07:26
lubot<mitya57> Ack07:38
lubot<mitya57> But we can wait until the current transition lands, right?07:39
lubot<RikMills> Yes, I think so. I can shove a qtwayland build with the headers in my plasma staging ppa in the meantime07:42
lubot<RikMills> Sorry. I did not know about this, as I have not been able to try to build the new plasma without 5.1407:44
lubot<mitya57> No problem07:44
lubot<RikMills> I will also double check the requirement if I can. I have asked in Neon channel07:45
lubot<RikMills> They added the package there, but the git log is not very informative07:46
lubot<RikMills> maybe it is needed for some plasma-mobile stuff which we do not build at the moment07:47
lubot<RikMills> so far just building kwayland-server seems not to need private headers, but building the tests seems to need qtbase private. opensuse do not build with them or the tests08:28
lubot<mitya57> qtbase private headers are all there :)08:29
lubot<RikMills> indeed. when the right people from Neon show up today, I will try to clarify why they wanted the qtwayland private things and put a build depend on them08:31
lubot<RikMills> https://launchpad.net/~kubuntu-ninjas/+archive/ubuntu/plasma/+build/1931832408:32
lubot<RikMills> that builds ok with no private anything and tests disabled08:32
lubot<x_sun> (Photo, 977x171) https://i.imgur.com/zvWpQui.jpg09:54
lubot<x_sun> (Photo, 1061x175) https://i.imgur.com/j5HAGWR.jpg Launchpad build fails where my local build works just fine. I hate this stuff 🙄09:54
lubot<tsimonq2> @x_sun [<reply to image>], How are you building it locally?10:17
lubot<x_sun> Clean vm10:18
lubot<tsimonq2> Cross ref build deps and versions pulled in by infra vs local copy10:18
lubot<tsimonq2> There's a file that tells you this, hmm..10:18
lubot<tsimonq2> Alright wtf LP10:24
lubot<tsimonq2> LP builders build the buildinfo file10:24
lubot<tsimonq2> But don't actually publish it10:25
lubot<tsimonq2> That can't be right...10:25
lubot<tsimonq2> @x_sun [Clean vm], In any case, since I'm done going down that rabbit hole, try sbuild10:30
lubot<tsimonq2> So a very very very minimal install10:30
lubot<x_sun> It was on my radar, yeah10:34
lubot<tsimonq2> Cool10:34
lubot<RikMills> @mitya57 I am now told by kde devs that the qtwayland private headers are not needed for kwayland-server, which just conforms what experimentation already showed10:36
lubot<RikMills> No idea why Neon added that build dep10:36
lubot<x_sun> But I think that the reason Ninja fails here can be that `<<BUILDDIR>>` path10:40
lubot<mitya57> @RikMills [@mitya57 I am now told by kde devs that the qtwayland private headers are not ne …], Ok, private headers can wait then. (Lisandro prefers we wait until 5.15)10:54
lubot<mitya57> @x_sun [But I think that the reason Ninja fails here can be that <<BUILDDIR>> path], <<BUILDDIR>> is not an actual build directory, it's what it is replaced with in the log.10:56
lubot<x_sun> @mitya57 [<<BUILDDIR>> is not an actual build directory, it's what it is replaced with in …], Yeah, but I'm 99% sure there's something wrong with the path just looking at the problematic line of `toolchain.ninja`11:57
lubot<x_sun> My guess is that tilde `~` is not allowed there 🤷12:13
lubot<x_sun> Is there a way to hack a LP builddir location without changing the package version?12:23
lubot<x_sun> Guess what, I've managed to reproduce the issue on a local vm12:39
lubot<x_sun> (Photo, 1089x117) https://i.imgur.com/TvXe9u6.jpg12:40
lisandromitya57: wrt private headers: (1) considering the null amount of time I have been able to put into Qt it's really up to you (2) whatever KDE is part of the Debian Qt/KDE team's responsability, so yes, if I where to make the decistion I would go forward13:51
lisandroI guess that if I could really put all the necessary effort into Qt packaging I would certainly try to ship all private headers. But IMPOV that's nealy a paid job thing13:53
lisandro*nearly13:53
mitya57lisandro: looks like KDE actually doesn't need it right now, and it can wait until 5.15.15:21
lubot<RikMills> The KDE person who wanted it could not remember why they wanted the headers in Neon Qt.15:22
lubot<mitya57> @RikMills [thanks. I have not checked through yet, but anything in sync with debian do you …], Bugs filed at https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-qt-kde@lists.debian.org;tag=qt5.1418:04
lubot<mitya57> vorlon deleted qtwebengine from proposed. “disentangle Qt from protobuf” 🤔20:08
mamarleyYeah, and completely wreck the dependencies for KDE…20:19

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