 @RikMills [<RikMills> 5.14.2 landing], \o/
 now the trick is getting it to release :P
[07:15] <mitya57> lisandro: I think we should ship private headers if kwayland-server needs them. See what mamarley said above. What do you think?
[07:16] <mitya57> Asking because you marked Debian #894472 as wontfix.
 https://launchpad.net/~kubuntu-ninjas/+archive/ubuntu/plasma/+build/19316031
 @mitya57 so there will be no newer Plasma in 20.10 if you don't
 Ack
 But we can wait until the current transition lands, right?
 Yes, I think so. I can shove a qtwayland build with the headers in my plasma staging ppa in the meantime
 Sorry. I did not know about this, as I have not been able to try to build the new plasma without 5.14
 No problem
 I will also double check the requirement if I can. I have asked in Neon channel
 They added the package there, but the git log is not very informative
 maybe it is needed for some plasma-mobile stuff which we do not build at the moment
 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 tests
 qtbase private headers are all there :)
 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 them
 https://launchpad.net/~kubuntu-ninjas/+archive/ubuntu/plasma/+build/19318324
 that builds ok with no private anything and tests disabled
 (Photo, 977x171) https://i.imgur.com/zvWpQui.jpg
 (Photo, 1061x175) https://i.imgur.com/j5HAGWR.jpg Launchpad build fails where my local build works just fine. I hate this stuff 🙄
 @x_sun [<reply to image>], How are you building it locally?
 Clean vm
 Cross ref build deps and versions pulled in by infra vs local copy
 There's a file that tells you this, hmm..
 Alright wtf LP
 LP builders build the buildinfo file
 But don't actually publish it
 That can't be right...
 @x_sun [Clean vm], In any case, since I'm done going down that rabbit hole, try sbuild
 So a very very very minimal install
 It was on my radar, yeah
 Cool
 @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 showed
 No idea why Neon added that build dep
 But I think that the reason Ninja fails here can be that `<<BUILDDIR>>` path
 @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)
 @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.
 @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`
 My guess is that tilde `~` is not allowed there 🤷
 Is there a way to hack a LP builddir location without changing the package version?
 Guess what, I've managed to reproduce the issue on a local vm
 (Photo, 1089x117) https://i.imgur.com/TvXe9u6.jpg
[13:51] <lisandro> mitya57: 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 forward
[13:53] <lisandro> I 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 thing
[13:53] <lisandro> *nearly
[15:21] <mitya57> lisandro: looks like KDE actually doesn't need it right now, and it can wait until 5.15.
 The KDE person who wanted it could not remember why they wanted the headers in Neon Qt.
 @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.14
 vorlon deleted qtwebengine from proposed. “disentangle Qt from protobuf” 🤔
[20:19] <mamarley> Yeah, and completely wreck the dependencies for KDE…