 The installation above worked
 good night everyone, see you tomorrow
[02:57] <krytarik> As a follow-up, this is how my suggestion for an overhauled Kubuntu CD Image design looks like currently: https://i.imgur.com/6JuajGF.png
 @RikMills, Yes, install worked great over wifi and the wifi connection password was retained upon reboot.  The retention has not always worked in the past, but it worked today.  Maybe the connection is only retained if connect during install and I typically live test before install, connect to wifi in the panel, so I suspect that's the difference... Also, my timezone was correctly detected.
 (Photo, 444x141) https://irc-attachments.kde.org/MOzJlTbW/file_43206.jpg Classic LP
 Classic QtWebEngine being a pain in the ****
 @DarinMiller, Great. Yes, that sounds likely.
 To be honest I see a thing like that for the first time. Usually it takes 3 to 7-ish hours
 @X, Have you not done a build since this? https://launchpad.net/ubuntu/+source/qtwebengine-opensource-src/5.15.3+dfsg-3ubuntu1
 Ha `-j2`, I see
[10:41] <mparillo> TZ fix works for me: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1916331/comments/4
[10:44] <RikMills> mparillo: great. thanks :)
[12:23] <santa_> hi everyone
[12:23] <santa_> RikMills: I have zsynced the daily iso and tested an installation this morning, the bug is gone already
 \o/
[12:24] <santa_> RikMills: anything else being urgent?
 I don't think so. Thanks for taking the time :)
[12:25] <santa_> one million thanks for fixing it, small news from my front:
[12:26] <santa_> - I have been assembling a new server, the new one has 16 hard disks
[12:27] <santa_> - I hope to do some test rebuilds, test upgrades this afternoon
[12:27] <santa_> what about KA? have you experienced any bug since the last beta?
[12:38] <RikMills> santa_: gbp-ppa didn't handle the 'v' in the newest tar here very well: https://download.kde.org/stable/plasma-wayland-protocols/
[12:38] <RikMills> that is about it I think
[12:40] <santa_> ugh
[12:40] <RikMills> that was a mistake by the upstream dev, so should not occur much
[12:41] <RikMills> I worked around it somehow
[12:49] <BluesKaj> Hi folks
[13:28] <santa_> RikMills: ack, I have been thinking about it and tested a number of debian/watch modifications of plasma-wayland-protocols, none of them worked XD
[13:29] <santa_> I see no other way to fix this than adding a shoddy thing in the KA code lie "if source_package_name == ..."
[13:30] <santa_> since you mention it was a temporary mistake maybe we could simply ignore it and hope they don't add the extra '-v' in the future
[13:31] <RikMills> yep, hopefully this is a one off thing
 Santa, any reason not to update the KA code with something like: … package_name = "plasma-wayland-protocols-v1.2.1.tar.xz" … version = package_name.split('-')[-1].split('.tar')[0].replace('v','')
[17:39] <santa_> @DarinMiller that kind of solution would just work for that plasma-wayland-protocols package, and that style of if's is a bit like embedding ka-metadata into the code :|
[17:40] <santa_> also you have to take into account the problem is not the version but the tarball name
[17:40] <santa_> plasma-wayland-protocols is of release type "other"
[17:41] <santa_> therefore the tarball is downloaded with uscan, then symlinked in build-area/plasma-wayland-protocols_version.orig.tar.gz
[17:42] <santa_> and the build-area/ symlink would point to <path>/plasma-wayland-protocols-1.2.1.tar.gz
[17:44] <santa_> while it should point to <path>/plasma-wayland-protocols-v1.2.1.tar.gz (which is the tarball name as downloaded by uscan)
[17:45] <santa_> and as far as I can see there is no way to alter the tarball as downloaded by uscan
[17:51] <santa_> * to alter the tarball name
 ah, OK makes sense.