[00:06] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #1049: SUCCESS in 6 min 31 sec: https://kci.pangea.pub/job/mgmt_merger/1049/
[00:10] <valorie> mparillo: <3
[00:10] <valorie> I see you already did the beta 1 release notes
[00:10] <valorie> just made of a draft of the news story for it
[00:10] <valorie> thank you
[00:29] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #106: STILL FAILING in 21 min: https://kci.pangea.pub/job/bionic_unstable_ruqola/106/
[00:35] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdenetwork-filesharing build #61: STILL UNSTABLE in 27 min: https://kci.pangea.pub/job/bionic_unstable_kdenetwork-filesharing/61/
[00:43] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdeplasma-addons build #87: STILL FAILING in 35 min: https://kci.pangea.pub/job/bionic_unstable_kdeplasma-addons/87/
[00:51] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kdenetwork-filesharing build #21: STILL UNSTABLE in 43 min: https://kci.pangea.pub/job/bionic_stable_kdenetwork-filesharing/21/
[00:52] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kolourpaint build #57: FAILURE in 1 min 2 sec: https://kci.pangea.pub/job/bionic_stable_kolourpaint/57/
[01:00] <mparillo> My pleasure.
[01:01] <mparillo> I should be able to update the screenshots and version numbers in late February / early March.
[01:01] <valorie> that's the thing, it's the 22nd already!
[01:01] <valorie> time marches on
[01:01] <mparillo> I do not believe any bugs are tagged with Bionic, but I could be wrong. IIRC, only certain people could do it.
[01:01] <valorie> but we've go the new plasma in the archive so my heart is light
[01:02] <mparillo> Beta is early March, correct?
[01:02] <valorie> it drops the 8th
[01:02] <valorie> so it will be testing from the 3rd on or so
[01:02] <valorie> but dinner time now!
[01:03] <mparillo> Maybe more of a question for acheronuk, but do you think we will still have Plasma .2 and no substantial upgrades to Apps.
[01:03] <valorie> not sure
[01:03] <valorie> I hope for .2 and hope for upgraded apps
[01:03] <valorie> and a new falkon release!
[01:03] <valorie> Any Day Now
[01:04] <mparillo> That is why I was holding off on screen shots and updating theversion numbers in the descriptions. We already have Plasma .2. Santa's iron hand is back and shows it entirely landed.
[01:04] <valorie> coolio
[01:04] <mparillo> Did we decide to ship Falkon? 
[01:04] <valorie> we're going to ship it if it is ready
[01:05] <valorie> but not make it The Browser
 Lubuntu Next is shipping it
 :P
[01:05] <valorie> it's gotta be released
[01:05] <valorie> anyway, ciao
[01:05] <mparillo> Hi Simon. Does Lubuntu Next allow for WEP passwords in its network manager.
 @mparillo, I'm not entirely sure if nm-tray does that.
[01:06] <mparillo> It did not last time I tested it.
[01:06] <wxl> i bet it does
 But WEP is insecure and you should upgrade
 Maybe it's a sign XD
[01:07] <mparillo> Funny story (maybe -offtopic), but I got a new router that supports a more secure protocol, but when I thought about chagnging maybe 20 devices, including a printer, where you use arrow keys to select the passwords, I said not thanks. In the suburbs I only see maybe three neighbor's wifi anyway, and none have a strong signal.
[01:08] <mparillo> arrow keys to select the passwords, character by character!
[01:09] <mparillo> In any case, I try to test Lubuntu Next at least once per twice-annual cycle.
 OK, cool
[01:11] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #84: FAILURE in 1 min 8 sec: https://kci.pangea.pub/job/bionic_stable_cantor/84/
[01:15] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ruqola build #107: STILL FAILING in 40 min: https://kci.pangea.pub/job/bionic_unstable_ruqola/107/
[01:28] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_ark build #72: STILL UNSTABLE in 1 hr 20 min: https://kci.pangea.pub/job/bionic_stable_ark/72/
[01:30] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ark build #83: STILL UNSTABLE in 1 hr 22 min: https://kci.pangea.pub/job/bionic_unstable_ark/83/
[01:30] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kalzium build #53: STILL UNSTABLE in 1 hr 22 min: https://kci.pangea.pub/job/bionic_unstable_kalzium/53/
[01:31] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_peruse build #52: STILL UNSTABLE in 1 hr 23 min: https://kci.pangea.pub/job/bionic_unstable_peruse/52/
[01:32] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kalgebra build #85: FAILURE in 1 min 3 sec: https://kci.pangea.pub/job/bionic_unstable_kalgebra/85/
[01:32] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktp-common-internals build #81: FAILURE in 1 min 11 sec: https://kci.pangea.pub/job/bionic_unstable_ktp-common-internals/81/
[01:33] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kolf build #80: FAILURE in 2 min 10 sec: https://kci.pangea.pub/job/bionic_unstable_kolf/80/
[01:33] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_lskat build #84: FAILURE in 2 min 12 sec: https://kci.pangea.pub/job/bionic_unstable_lskat/84/
[01:38] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktp-common-internals build #82: STILL FAILING in 56 sec: https://kci.pangea.pub/job/bionic_unstable_ktp-common-internals/82/
[01:44] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[01:44] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kolourpaint build #58: FIXED in 46 min: https://kci.pangea.pub/job/bionic_stable_kolourpaint/58/
[01:45] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_ktorrent build #74: FAILURE in 1 min 5 sec: https://kci.pangea.pub/job/bionic_stable_ktorrent/74/
[01:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_gwenview build #90: FAILURE in 53 min: https://kci.pangea.pub/job/bionic_unstable_gwenview/90/
[01:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_amarok build #27: STILL UNSTABLE in 1 hr 38 min: https://kci.pangea.pub/job/bionic_unstable_amarok/27/
[01:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_discover build #87: FAILURE in 1 hr 38 min: https://kci.pangea.pub/job/bionic_unstable_discover/87/
[01:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_konqueror build #40: STILL UNSTABLE in 1 hr 38 min: https://kci.pangea.pub/job/bionic_unstable_konqueror/40/
[01:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kblog build #30: FAILURE in 1 hr 38 min: https://kci.pangea.pub/job/bionic_unstable_kblog/30/
[01:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kstars build #79: STILL UNSTABLE in 1 hr 38 min: https://kci.pangea.pub/job/bionic_unstable_kstars/79/
[01:52] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_gwenview build #91: STILL FAILING in 56 sec: https://kci.pangea.pub/job/bionic_unstable_gwenview/91/
[02:00] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_cantor build #85: NOW UNSTABLE in 43 min: https://kci.pangea.pub/job/bionic_stable_cantor/85/
[02:01] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_purpose build #84: STILL FAILING in 57 sec: https://kci.pangea.pub/job/bionic_unstable_purpose/84/
[02:01] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:01] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_lskat build #85: FIXED in 22 min: https://kci.pangea.pub/job/bionic_unstable_lskat/85/
[02:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:02] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kolf build #81: FIXED in 23 min: https://kci.pangea.pub/job/bionic_unstable_kolf/81/
[02:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:02] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kalgebra build #86: FIXED in 25 min: https://kci.pangea.pub/job/bionic_unstable_kalgebra/86/
[02:02] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kdeplasma-addons build #88: STILL FAILING in 1 hr 14 min: https://kci.pangea.pub/job/bionic_unstable_kdeplasma-addons/88/
[02:03] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libksysguard build #51: FAILURE in 1 min 10 sec: https://kci.pangea.pub/job/bionic_unstable_libksysguard/51/
 Wow, 18.04 is shaping up quite nicely well ahead of beta!
[02:04] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_breeze build #84: FAILURE in 1 min 48 sec: https://kci.pangea.pub/job/bionic_unstable_breeze/84/
 I agree :D
[02:08] <valorie> upgrading my travel laptop next week as part of testing
[02:08] <valorie> :-)
[02:08] <tsimonq2> :D
[02:09] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libksysguard build #52: STILL FAILING in 57 sec: https://kci.pangea.pub/job/bionic_unstable_libksysguard/52/
 4.15 kernel, libinput 1.10, plasma 5.12.2, fw 5.43, xorg 1.19.6
 Not to forget.... apps 17.12.2
[02:12] <valorie> yes
[02:12] <valorie> are we up-to-date on appls that aren't part of kdeapps?
 vlc is v. 3.0 :)
 which apps did you have in mind?
[02:14] <valorie> not sure what's in and what's out
 repos have wine-64 dev v. 3.3
[02:15] <valorie> vlc isn't a KDE application at all
 But we have it by default...
[02:15] <valorie> buddies, but not us
[02:15] <valorie> yes
[02:15] <valorie> how about sddm?
[02:15] <valorie> isn't there a new version lately?
 Funny enough, I'm working on that right now
 that's why I put a smiley face.
[02:15] <valorie> coolio
 We have 0.14 in Ubuntu, 0.15 in Debian, and I'm working on 0.17 now for both.
 sddm is still 0.14...
 Right
[02:16] <valorie> \o/
 ^what simon said
 :)
 Do you think you will have 0.17 ready before beta?
[02:17] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:17] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_ktorrent build #75: FIXED in 27 min: https://kci.pangea.pub/job/bionic_stable_ktorrent/75/
[02:17] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_discover build #88: STILL FAILING in 26 min: https://kci.pangea.pub/job/bionic_unstable_discover/88/
[02:18] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kreport build #23: FAILURE in 1 min 2 sec: https://kci.pangea.pub/job/bionic_stable_kreport/23/
[02:18] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kblog build #31: STILL FAILING in 26 min: https://kci.pangea.pub/job/bionic_unstable_kblog/31/
[02:18] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_cantor build #52: STILL UNSTABLE in 47 min: https://kci.pangea.pub/job/bionic_unstable_cantor/52/
[02:19] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_syndication build #76: FAILURE in 1 min 1 sec: https://kci.pangea.pub/job/bionic_unstable_syndication/76/
[02:25] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_syndication build #77: STILL FAILING in 1 min 0 sec: https://kci.pangea.pub/job/bionic_unstable_syndication/77/
 Do you dl sddm straight from github to start the packaging (https://github.com/sddm/sddm/) ?
 @DarinMiller, Oh yeah, should be no issue
 @DarinMiller, No, I use the existing package, bump the changelog, use uscan to grab the new tar from GitHub, then try to run it through sbuild and tackle issues from there.
 i.e. sometimes quilt patches need updating
 Sometimes Lintian starts whining
 makes sense.
 etc.
 sddm has a lintian dep?
 All packages are ran through Lintian
 Lintian is not something to depend on, really
 Oh, OK.
 It's a tool to check your package
 Right
 :)
 I knew "dep" was the wrong word, but I thought Lintian was the language checker portion of packaging tools.... googling....
 https://lintian.debian.org/
 Oh, lintian does many things....
 Right :)
 yep, that's zactly where good took me...
 google
[02:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_breeze build #85: FIXED in 26 min: https://kci.pangea.pub/job/bionic_unstable_breeze/85/
[02:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kcontacts build #78: STILL FAILING in 33 min: https://kci.pangea.pub/job/bionic_unstable_kcontacts/78/
[02:36] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kmailtransport build #57: FAILURE in 1 min 5 sec: https://kci.pangea.pub/job/bionic_unstable_kmailtransport/57/
[02:37] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libkipi build #84: FAILURE in 1 min 1 sec: https://kci.pangea.pub/job/bionic_unstable_libkipi/84/
[02:37] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kpimtextedit build #66: FAILURE in 1 min 8 sec: https://kci.pangea.pub/job/bionic_unstable_kpimtextedit/66/
 new pulseaudio (v 1.11) fixes the audio auto switch crash (as promised in the bug report last fall).
 As far as I can tell, this release has very few papercuts.  In fact, I can't think of any for the Xorg side.
[02:39] <valorie> do we have this in a PPA somewhere?
 On the wayland side.... that's another (longer) story, but it is  nearly usable. :)
 ppa?
[02:40] <valorie> so it could be easily tested
[02:40] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_purpose build #85: STILL FAILING in 33 min: https://kci.pangea.pub/job/bionic_unstable_purpose/85/
 sorry, I don't understand what needs tested.
[02:40] <valorie> the new pulseaudio
 sddm ppa?
 18.04 has pa v  1.11 already in the repos.
 Right
[02:41] <valorie> ah, OK
 All of what he's saying valorie is already there :)
[02:41] <valorie> cool, I didn't understand that
 That's the excitement, all of this stable stuff is landing before beta!
[02:43] <valorie> that is indeed different from the past
[02:43] <valorie> at least since I've been involved
[02:43] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kpimtextedit build #67: STILL FAILING in 55 sec: https://kci.pangea.pub/job/bionic_unstable_kpimtextedit/67/
 I have been using *buntu since 7.10 and this is release is incredibly awesome--the best by far.
[02:50] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[02:50] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_kreport build #24: FIXED in 26 min: https://kci.pangea.pub/job/bionic_stable_kreport/24/
[03:01] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kcontacts build #79: STILL FAILING in 20 min: https://kci.pangea.pub/job/bionic_unstable_kcontacts/79/
[03:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:02] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kmailtransport build #58: FIXED in 20 min: https://kci.pangea.pub/job/bionic_unstable_kmailtransport/58/
[03:02] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[03:02] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_libkipi build #85: FIXED in 19 min: https://kci.pangea.pub/job/bionic_unstable_libkipi/85/
[03:14] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kwin build #92: FAILURE in 1 min 9 sec: https://kci.pangea.pub/job/bionic_unstable_kwin/92/
 \o/
[03:31] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_krita build #77: STILL UNSTABLE in 3 hr 23 min: https://kci.pangea.pub/job/bionic_unstable_krita/77/
 is krunner K-runner or crun-ner?
[03:39] <valorie> I say k runner in my head
[03:40] <valorie> but my fingers say alt space
[03:40] <valorie> :-)
 same I've always said k runner but never bothred to ask before lol
[03:41] <valorie> otoh I say koo buntu
[03:41] <valorie> while some say K ubuntu
 @DarinMiller, I agree this is great thus far. I am so excited to see I have actually contributed to a distro release. . . weird I havent done that before for Kubuntu
[03:42] <valorie> it's great to have you on the team, @MichaelTun
 @valorie, it should be koo-boon-too, just makes sense. Xubuntu and Lubuntu are done the same way
[03:42] <valorie> agreed
 @valorie, You also say Daybian so idk ;)
 @tsimonq2, fair enough lol
[03:42] <valorie> I say deb ian
[03:43] <valorie> 'cause it was deb and ian
[03:43] <valorie> RIP Ian
 deb-ian and debian sound so similar that even if said with a slight pause it still works
 and yea rip ian
 @valorie, Nonono … You say DAY bien … Emphasis on the A in the middle :P
 :D
[03:44] <valorie> and you say?
 RIP Ian
 dehb
 Dehb ee an
[03:45] <valorie> well, that's how Deb is said
 short sound e
[03:45] <valorie> fight!
[03:45] <valorie> lol
 Lol
 I am confused do you say dayborah?
[03:45] <valorie> nope
[03:45] <valorie> lo;
[03:45] <valorie> l
[03:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kxmlrpcclient build #60: FAILURE in 33 min: https://kci.pangea.pub/job/bionic_unstable_kxmlrpcclient/60/
 can IRC get voice clips?
[03:46] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_messagelib build #133: STILL FAILING in 44 min: https://kci.pangea.pub/job/bionic_unstable_messagelib/133/
 (Voice, 2s)https://irc-attachments.kde.org/qbiAtwnE/file_4872.oga
[03:47] <valorie> not directly
[03:47] <valorie> but via matrix or telegram, yeah
[03:47] <valorie> worked
 (Voice, 1s)https://irc-attachments.kde.org/NFtvPFRg/file_4873.oga
[03:50] <valorie> that's how I saw it too, at least in my imagination....
 (Voice, 4s)https://irc-attachments.kde.org/eATzN2ej/file_4874.oga
[03:53] <valorie> same, but not with the accent!
 The accent might be weird from me as well :)
 the KDE documentation is so weird sometimes, for example:
 KWin (pronounced "kwin" in one word)
 that is not helpful because k-win or qwin are both 1 word.
[04:02] <valorie> yup -- I say quin
 Whaaat
 I say Kay Win
[04:03] <valorie> it is KDE's windowing system
[04:04] <valorie> so you are probably more correct on that
[04:07] <ahoneybun> xD
[04:10] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kxmlrpcclient build #61: STILL FAILING in 18 min: https://kci.pangea.pub/job/bionic_unstable_kxmlrpcclient/61/
[04:10] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kjs build #78: FAILURE in 1 min 4 sec: https://kci.pangea.pub/job/bionic_unstable_kjs/78/
 I say k-win but I think Riddell says quin but I might be imagining that
[04:14] <valorie> Martin says quin
[04:14] <valorie> and since he's the maintainer, I just copied him
 martin was the original dev right? I suppose that answers it then
[04:22] <valorie> not sure if he was the original maintainer or not, but I met him a loooong time ago
[04:22] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_messagelib build #134: STILL FAILING in 31 min: https://kci.pangea.pub/job/bionic_unstable_messagelib/134/
 oh ok
[04:25] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[04:25] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kwin build #93: FIXED in 1 hr 6 min: https://kci.pangea.pub/job/bionic_unstable_kwin/93/
[04:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[04:34] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kjs build #79: FIXED in 18 min: https://kci.pangea.pub/job/bionic_unstable_kjs/79/
[05:10] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_sonnet build #62: FAILURE in 1 min 5 sec: https://kci.pangea.pub/job/bionic_unstable_sonnet/62/
 Kdenlive announced a Cafe . . . a few hours before doing it. That marketing is so stellar
[05:33] <Perigee> Hah I noticed that too
[05:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[05:34] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_sonnet build #63: FIXED in 18 min: https://kci.pangea.pub/job/bionic_unstable_sonnet/63/
[08:16] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-framework build #71: FAILURE in 1 min 19 sec: https://kci.pangea.pub/job/bionic_unstable_plasma-framework/71/
[08:57] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:57] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_konqueror build #139: FIXED in 36 min: https://kci.pangea.pub/job/xenial_stable_konqueror/139/
[08:57] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:57] -kubuntu-ci:#kubuntu-devel- Project artful_stable_konqueror build #133: FIXED in 37 min: https://kci.pangea.pub/job/artful_stable_konqueror/133/
[08:57] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:57] -kubuntu-ci:#kubuntu-devel- Project bionic_stable_konqueror build #51: FIXED in 37 min: https://kci.pangea.pub/job/bionic_stable_konqueror/51/
[09:01] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:01] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_konqueror build #41: FIXED in 40 min: https://kci.pangea.pub/job/bionic_unstable_konqueror/41/
[09:01] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_konqueror build #249: FIXED in 40 min: https://kci.pangea.pub/job/xenial_unstable_konqueror/249/
[09:01] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:01] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-framework build #72: FIXED in 40 min: https://kci.pangea.pub/job/bionic_unstable_plasma-framework/72/
[09:01] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[09:01] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_konqueror build #109: FIXED in 41 min: https://kci.pangea.pub/job/artful_unstable_konqueror/109/
[09:56] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kbookmarks build #55: FAILURE in 1 min 4 sec: https://kci.pangea.pub/job/bionic_unstable_kbookmarks/55/
[10:02] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kbookmarks build #56: STILL FAILING in 58 sec: https://kci.pangea.pub/job/bionic_unstable_kbookmarks/56/
[10:03] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kirigami2 build #76: FAILURE in 1 min 4 sec: https://kci.pangea.pub/job/bionic_unstable_kirigami2/76/
[10:31] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:31] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kirigami2 build #77: FIXED in 23 min: https://kci.pangea.pub/job/bionic_unstable_kirigami2/77/
 @nggraham @MichaelTun https://cgit.kde.org/plasma-desktop.git/commit/?id=b2588104cc562a0500b32c186aa11a6b8affddc4
[10:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:52] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_ktp-common-internals build #83: FIXED in 31 min: https://kci.pangea.pub/job/bionic_unstable_ktp-common-internals/83/
[10:52] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kpimtextedit build #68: FIXED in 33 min: https://kci.pangea.pub/job/bionic_unstable_kpimtextedit/68/
[10:52] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[10:52] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_syndication build #78: FIXED in 32 min: https://kci.pangea.pub/job/bionic_unstable_syndication/78/
[10:52] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_gwenview build #92: STILL FAILING in 32 min: https://kci.pangea.pub/job/bionic_unstable_gwenview/92/
[11:29] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_gwenview build #93: STILL FAILING in 31 min: https://kci.pangea.pub/job/bionic_unstable_gwenview/93/
[12:10] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2078: SUCCESS in 53 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2078/
[12:10] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2078: SUCCESS in 1 min 4 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2078/
[12:13] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2078: SUCCESS in 3 min 47 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2078/
[12:28] <gpunk> plasma is very slow since this morning update
[12:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[12:33] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_kbookmarks build #57: FIXED in 20 min: https://kci.pangea.pub/job/bionic_unstable_kbookmarks/57/
[14:08] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-desktop build #91: FAILURE in 1 min 31 sec: https://kci.pangea.pub/job/bionic_unstable_plasma-desktop/91/
[14:09] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-desktop build #92: STILL FAILING in 1 min 7 sec: https://kci.pangea.pub/job/bionic_unstable_plasma-desktop/92/
[14:11] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-desktop build #93: STILL FAILING in 48 sec: https://kci.pangea.pub/job/bionic_unstable_plasma-desktop/93/
[14:16] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-desktop build #94: STILL FAILING in 31 sec: https://kci.pangea.pub/job/bionic_unstable_plasma-desktop/94/
[14:21] <acheronuk> yofel: linode seems to be the main culprit for failing on adding the PPA. racy condition as it is just very fast?
[14:22] -kubuntu-ci:#kubuntu-devel- Project artful_stable_plasma-desktop build #223: FAILURE in 3 min 49 sec: https://kci.pangea.pub/job/artful_stable_plasma-desktop/223/
[14:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-desktop build #345: STILL FAILING in 3 min 49 sec: https://kci.pangea.pub/job/xenial_unstable_plasma-desktop/345/
[14:23] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-desktop build #229: FAILURE in 5 min 8 sec: https://kci.pangea.pub/job/artful_unstable_plasma-desktop/229/
[14:24] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-desktop build #158: STILL FAILING in 5 min 54 sec: https://kci.pangea.pub/job/xenial_stable_plasma-desktop/158/
 (Sticker, 512x512) https://irc-attachments.kde.org/FcfcNTqJ/file_4889.webp
[14:31] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-desktop build #346: STILL FAILING in 3 min 44 sec: https://kci.pangea.pub/job/xenial_unstable_plasma-desktop/346/
[14:31] -kubuntu-ci:#kubuntu-devel- Project artful_stable_plasma-desktop build #224: STILL FAILING in 3 min 44 sec: https://kci.pangea.pub/job/artful_stable_plasma-desktop/224/
[14:32] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_plasma-desktop build #230: STILL FAILING in 3 min 42 sec: https://kci.pangea.pub/job/artful_unstable_plasma-desktop/230/
[14:33] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_plasma-desktop build #159: STILL FAILING in 3 min 41 sec: https://kci.pangea.pub/job/xenial_stable_plasma-desktop/159/
[15:21] -kubuntu-ci:#kubuntu-devel- Project bionic_unstable_plasma-desktop build #95: NOW UNSTABLE in 1 hr 2 min: https://kci.pangea.pub/job/bionic_unstable_plasma-desktop/95/
[15:45] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #2079: SUCCESS in 46 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/2079/
[15:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #2079: SUCCESS in 1 min 5 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/2079/
[15:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #2079: SUCCESS in 3 min 44 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/2079/
[16:50] <yofel> hm maybe... but speed wise I would assume that master would also fail on occasion
[16:50] <yofel> I'll look into it later
[16:51] <acheronuk> I was slightly clutching at straws there
[16:51] <acheronuk> thanks
 Neon has added Qt 5.10
 @MichaelTun, Yes
[18:04] <blaze> aaand… guess what, it's bad
 Huh?
 @acheronuk Are these Phonon releases something we should pick up?
 @tsimonq2, Possibly
 Nice. Looks like building against the new mesa and/or libglvnd in proposed has screwed our desktop opengl rendering
 now we default to llvmpipe on intel
 ick
[18:50] <mamarley> acheronuk: I don't think that is happening on my system.  How are you checking?
 if you purge libglvnd0 and libegl you get full opengl back
 @mamarley, Live system on kabylake
 renders only with llvmpipe
[18:52] <blaze> glxinfo | grep renderer
 remove those and you get it back (losing kinfocentre which oddly now depends on them)
[18:52] <mamarley> I see "OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2)" in glxinfo on this bionic-proposed system.
 mamarly it could well be -release only, caused by building against proposed
 blaze. yep, that is how I checked.
[18:54] <mamarley> Ah, yes, that sounds correct.
 also have several reports from users of bionic of the same.
[18:57] <mamarley> It is probably worth reporting in #ubuntu-x.
[19:00] <acheronuk> just doing
[19:59] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop amd64 [Xenial 16.04.4] (20180223.1) has been added
[19:59] -queuebot:#kubuntu-devel- Builds: Kubuntu Desktop i386 [Xenial 16.04.4] (20180223.1) has been added
[20:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kinfocenter build #478: STILL FAILING in 3 min 42 sec: https://kci.pangea.pub/job/xenial_unstable_kinfocenter/478/
[20:15] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kinfocenter build #62: STILL FAILING in 5 min 44 sec: https://kci.pangea.pub/job/xenial_stable_kinfocenter/62/
[20:22] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kinfocenter build #479: STILL FAILING in 4 min 32 sec: https://kci.pangea.pub/job/xenial_unstable_kinfocenter/479/
[20:24] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kinfocenter build #63: STILL FAILING in 4 min 33 sec: https://kci.pangea.pub/job/xenial_stable_kinfocenter/63/
[20:50] <yofel> [Errno 2] No such file or directory: 'S.gpg-agent.ssh'
[20:50] <yofel> kind of good thing: I can reproduce it. bad thing: that error really doesn't tell much about that's wrong -_-
[20:50] <yofel> hm, could also be LXC interfering..
[21:12]  * yofel wonders why apt is doing everything in /tmp these days
 @nggraham https://launchpad.net/ubuntu/+source/network-manager/1.10.4-1ubuntu2
 c'est magnifique
 lets hope it really works!
 seriously
 I'll be able to test sometime this weekend, if nobody beats me to it
 with default settings, it only manifests in the live session, not during an actual install
 I can try on the latop I just borrowed to test that opengl issue as well
 I had the bug on today's iso, so that is a good comparison :)
 So this isn't limited to Kubuntu, but it's a major papercut: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1639863
 because of this, Firefox and Thunderbird don't show up in KDE Discover
 wow. that sat dorment for a bit!
 yes, sadly
[21:43] <acheronuk> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1447144
[21:43] <acheronuk> I REALLY want to get that sorted!
[21:48] <valorie> props to you two for getting this stuff DONE
 While we're at it, if you open Discover on Kubuntu (any version), you'll notice that the app icons are all ugly and pixellated. This is apparently a packaging issue, but in Neon, they're crisp and sharp. I don't know what Neon is doing differently, but we might want to copy it, if possible. Might wanna ask Jonathan Riddell or Harald Sitter?
[21:55] <valorie> they are indeed pixely
[21:55] <valorie> in artful
 yeah, hideous
 it's a really poor user experience, but apparently it's possible to somehow change because every single icon in KDE Neon is pretty, and that's based on 16.04 and I'm pretty sure they didn't re-package *everything*
[21:57] <yofel> hm, this really seems to be a race condition of some sort
[21:59] <yofel> software-properties creates a keyring in a temporary folder, gnupg launches an agent to manage it, software-properties tries to delete the folder to clean up after itself... and fails, leaving a random set of files behind, e.g. the dirmngr socket etc.
[22:09] <valorie> any ideas about those icons acheronuk, simon, or yofel
[22:09] <valorie> nate -- they literally DO repackage everything, even if they use our packaging
[22:10] <valorie> all built by machine, basically
 oh hmm
 for example see https://bugs.kde.org/show_bug.cgi?id=370350
[22:12] <valorie> but somehow we are using the small icon and blowing them up or something instead of using the bigger version?
 and https://bugs.kde.org/show_bug.cgi?id=388253
[22:12] <yofel> hm, could be that we don't ship the appropriate size by default? I don't think we split that these days, but we did in the past
[22:12] <yofel> I doubt that optipng would be messing with the quality..
 @valorie, Exactly, the Ubuntu packaging provides small icons, and in Discover we display them larger then that, so they get blown up and pixellated
[22:13] <valorie> sounds like a packaging bug then
 yes, but for every single package
[22:13] <valorie> perhaps we're not pulling in the proper SVGs
[22:13] <valorie> somewhere along the line
 it seems to be a systemic issue or a policy decision or something
[22:14] <yofel> let me install discover......
 the Plasma 5.12 version is getting better, in case you hated it before
[22:15] <yofel> yeah, I rage-uninstalled it some 2 years ago
 I'm on a mission to make it not suck
[22:18] <yofel> nate++
 because having a good software center is really important
 in one year, you will love it
 hopefully by now, you at least no longer hate it, and are only merely annoyed by it :)
 Check out https://pointieststick.wordpress.com/category/discover/
 (just published this week's post)
[22:21] <acheronuk> we inherited this from debian: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/discover/tree/debian/extra/60plasma-discover?h=kubuntu_bionic_archive
[22:21] <acheronuk> but it should be fetching hi and low res
[22:21] <yofel> that looks right..
[22:21] <acheronuk> though not sure ppa builds generate them
 hmm, I can confirm that they look bad even without using the Backports PPA
[22:22] <yofel> the bug report has gedit as example, so I don't think the PPA matters here
[22:26] <valorie> wow, the icons are so crisp and clear in your blogpost, nate
[22:26] <valorie> now I really see what you mean
 yeah, all my screenshots are from Neon
[22:26] <valorie> getting this fixed for the LTS would be Good
 (I do my dev work in a Neon VM)
[22:28] <yofel> ouch, this really looks horrible
[22:28] <valorie> sitter, sgclark, Riddell -- any of you recall what you did differently for icons in neon than you used to do in Kubuntu?
 yeah, and people blame Discover :(
[22:28] <yofel> *headscratch*
[22:28] <wxl> did they just suddenly go bad?
[22:28] <valorie> to be fair, it was easy to blame discover for lots of things
 no, they've been bad for years apparently
[22:28] <valorie> dunno how long they have been bad
[22:29] <wxl> THAT's a problem.
[22:29] <yofel> let's say there's a historic incentive for that
[22:29] <valorie> yes
 yeah, Discover has been not-so-great for a long time
[22:29] <wxl> wait, this is only in discover?
 But I'm really trying to turn the ship around
[22:29] <wxl> (sorry didn't read all the backlog)
 yes
 it doesn't show up in GNOME Software because they use smaller icons by default
 they use 64x64 IIRC, which is considered the "small" size. We use 80x80 and bigger
[22:31] <wxl> and these are the category icons, right? or all icons?
[22:31] <yofel> hm, according to strace, discover isn't trying to open anything but the 64x64 img
 https://i.imgur.com/3MHSrdD.png
 @wxl, the actual app icons
 Can we use the size provided by the package without upscaling it if it’s smaller than needed ?
[22:31] <sgclark> valorie: I have no clue sorry :(
 Just center it on the rect
 @acheronuk, that is a VM seems to only be fetching the 64x64
[22:32] <wxl> it looks like SOME of them are bad
[22:32] <wxl> like Guake looks like garbage, but VirtualBox looks sharp
 @acheronuk, so there are higher-resolution icons that we're simply not fetching?
 @wxl, Make sure Virtualbox is coming from Ubuntu packaging and not Flathub for example; all their icons are good
 @nggraham, http://archive.ubuntu.com/ubuntu/dists/bionic/main/dep11/
[22:33] <wxl> fwiw i'm running this on trusty.
 Hmm, feels like a packaging or config issue then. Again, Discover succeeds at fetching and displaying high-rec icons in all other distros that I've seen and used
 It's good in Neon, Arch (and derivatives), Fedora, and openSUSE
 @wxl, Without the backports PPA, the version of discover you're using is hideously old then
[22:34] <wxl> yeah, well, i never use discover anyways :)
[22:35] <valorie> that was interesting -- tried to expand the panel way up to see how the icons scaled, and it froze the desktop
[22:35] <valorie> had to restart
 (Photo, 844x648) https://irc-attachments.kde.org/GeKRZlVV/file_4905.jpg
 is that other apt config file overriding discover's?
 @acheronuk, that looks like it's a problem
 where does that file live?
[22:37] <valorie> thanks sgclark
[22:37] <yofel>  /etc/apt/apt.conf.d/50appstream
 does lower or higher number have priority? I forget!
[22:38] <yofel> the discover config file should override that though
[22:39] <yofel> I *think* lower, as in they're read in the file listing order
[22:39] <yofel> erm, higher
[22:40] <yofel> wait a moment
[22:41] <yofel> deb::DEP-11-icons-hidpi is not 128, that's $(COMPONENT)/dep11/icons-64x64@2.tar
[22:41] <yofel> 128 is deb::DEP-11-icons-large and deb::DEP-11-icons-large-hidpi
[22:43] <yofel> hm, now apt is at least downloading the 128 images, but discover isn't actually loading them
 If you discover any bugs with Discover 😜 let me know and I'll fix them
[22:45] <acheronuk> yofel: oh, so that whole 60discover is the 64x ones, and 12 are turned off in 50appstream?
[22:45] <yofel> right
[22:45] <acheronuk> *128 are
[22:45] <yofel> Get:33 http://de.archive.ubuntu.com/ubuntu bionic/universe DEP-11 128x128 Icons [19,2 MB]                                             
[22:45] <yofel> but where did it actually put them.....
[22:45] <acheronuk> duh, I misread that for a long time then
[22:46] <yofel> I only realized that too when I wondered why 50 appstream had 4 config blocks and actually read them..
[22:47] <yofel> well duh
[22:47] <acheronuk>  /var/lib/app-info/icons/
[22:47] <yofel> after enabling that you need to FORCE an appstream cache update for it to pick it up
[22:47] <valorie> :(
[22:48] <yofel> hey, my icons look pretty. Yay....
 holy crap they're pretty now
[22:48] <yofel> well. *some* of them
[22:48] <yofel> like krita, digikam, kmymoney, gcompris are pretty. Kdenlive and ktorrent are ugly o.O
 that might be an issue with those individual packages
[22:49] <yofel> true
[22:49] <acheronuk> mine are all pretty as well!
[22:49] <acheronuk> *mostly
 ok, so this is fantastic. Is there a Discover bug here, or is it all Debian packaging?
[22:50] <yofel> packaging
[22:50] <yofel> well, appstream configuration really
[22:50] <yofel> I guess debian decided that users don't need to waste network bandwidth on a bit prettier icons
[22:51] <yofel> a bit annoying that there's no way to make that decision based on connection type
 booooo
 this is 2018
[22:51] <yofel> yeah, where many people use they notebooks over mobile connections with limited monthly bandwidth
[22:51] <yofel> welcome in the 21st century
[22:51] <yofel> *their
 so what's the path forward here? Can we override it in Ubuntu or Kubuntu, or so we have to/should we go to Debian instead?
[22:52] <yofel> we can override it if wanted. That config file is shipped by the discover package
[22:52] <acheronuk> can't change the 50appstream I assume
[22:52] <acheronuk> so we match the appstream one, but enable 128?
[22:52] <acheronuk> if we want users to have these
[22:53] <yofel> I enabled 128 in /etc/apt/apt.conf.d/60plasma-discover, and that works for me
[22:53] <yofel> just the auto-cache-refresh didn't work
[22:54] <acheronuk> no? damn
[22:54] <yofel> "AppStream cache update is not necessary." is what I got
[22:54] <yofel> worked after --force
[22:54] <yofel> sounds like some kind of appstream apt integration bug to me
[22:55] <yofel> where's matthias when you need him..
[22:55] <yofel> hm, missed him by half an hour
 looks like Discover doesn't actually ship that file, or at least I can't find it in our repo
 maybe it's provided by Debian or Ubuntu packagers?
[22:55] <yofel> huh?
[22:55] <yofel> $ dpkg -S /etc/apt/apt.conf.d/60plasma-discover 
[22:55] <yofel> plasma-discover: /etc/apt/apt.conf.d/60plasma-discover
[22:55] <acheronuk> it's debian
[22:56] <yofel> well yes, it's part of the packaging
[22:56] <acheronuk> was added by debian
[22:56] <yofel> not the upstream source
[22:56] <acheronuk> in debian/extras/
 yeah, looks like we need Matthias then
[22:57] <yofel> anyway, this works for me: http://paste.ubuntu.com/p/T3mzCnXvg3/
[22:57] <yofel> and should do the jobs for fresh installs at least
[22:57] <yofel> or whenever appstream decides to refresh the cache itself
[22:57] <acheronuk> that is 90% better than we had
 yep yep yep
 thanks so much guys for this investigation
 if anyone here is familiar with the Debian bug tracker, could you file a bug? I've never been able to get their procrustean email-based bug tracker to actually work for me
[22:59] <acheronuk> haha. 90% of the time the debian BTS eats my bug emails without trace!
[23:00] <yofel> 90% of the time their bts just annoys me and I stop bothering. Guess it works as intended
 I cannot imagine how that project manages with such a crude tool
[23:01] <yofel> well, they don't need a spam filter by requring people to actually know what they're doing. And as long as you can use email it works rather well
[23:01] <acheronuk> I think it perfectly matches the prevailing attitude there
[23:01] <yofel> and heck, they use emails for internal server communication. So it does feel very like debian
 can anyone provide a link to a web page that shows the file in the debian packaging repo?
 https://salsa.debian.org/qt-kde-team/kde/plasma-discover/blob/master/debian/extra/60plasma-discover
 lurvley, thank you!
[23:05] <acheronuk> so shall I change that? or we want to do some more tests first?
[23:07] <yofel> I guess people can live with some 20MB more for a package cache refresh, so I'll +1 it
 wow, @ximion just fixed it
 https://salsa.debian.org/qt-kde-team/kde/plasma-discover/commit/ead46cbea3335f9eaeb37302cdfa2020d3d00c32
 Thanks! Can we also get the -hidpi versions of them, too?
 tired of playing telephone here :)
 Oh heyyyy
 :D
[23:10] <yofel> o/
 LOL
 so just icons-large not icons-large-hidpi?
 yes, he is objecting to that
[23:12] <ximion> ideally sync the whole package with Debian...
 we might have to do that ourselves if Debian doesn't want to make that change
[23:13] <ximion> I just looked at it, and the Ubuntu version is quite different from what we have in Debian, even shipping differently named packages for backends
[23:13] <yofel> what's the problem with hidpi?
[23:13] <ximion> yofel: it gets downloaded unconditionally, and people complain hard about that
[23:16] <yofel> hm, either we don't have those in ubuntu, or my apt config is just ignoring the hidpi setting
 so uh, looks like it's gonna be up to us if we want Discover to show nice icons for people using HiDPI displays
 @nggraham, it usually is us 🙄
 This is why I'm here instead of Debian :p
[23:19] <yofel> ximion: one more thing, shouldn't changing this trigger an appstream cache refresh? Here (0.11.8), it doesn't and I need --force for the icon size to get deployed
 Things have different names, as debian is so late to the party and then decide to be the oddball
[23:19] <ximion> Ubuntu has no HiDPI icons, as far as I know
[23:20] <ximion> it's appstream-generator is too old or has this feature disabled
 right
[23:20] <yofel> okay, so we can save us the trouble for that
[23:21] <valorie> I have hidpi and I vote for having hidpi icons everywhere possible
[23:21] <ximion> looking at the times, Debian was faster on updating this than Ubuntu, and blaming someone as oddball really doesn't help collaboration
[23:21] <valorie> thanks for your help on this ximion
[23:22] <valorie> I think we're frustrated that this bug crept in and kept things ugly for so long
[23:22] <yofel> no, but merging is so much effort that it doesn't make sense to do this all the time. And debian deciding how to name things whenever they want doesn't help.
[23:22] <yofel> but now I'm rambling agian. I'll shut up
[23:22] <ximion> valorie: for that you would first need to have hiDPI icon tarballs in Ubuntu, they don't exist there at all
[23:23] <valorie> ximion: we've got an LTS looming, and want to polish it as much as possible
[23:23] <yofel> but yes, thanks a lot for poking in and helping!
[23:23] <ximion> valorie: ask Laney for an appstream-generator update, I would like that as well ;-)
[23:23] <valorie> ximion: boo on that, but i've been living without it I guess
 wee added the backend packages nearly a year ago. debian a month ago. I was refering to that
 and I didn't mean to offend
[23:24] <valorie> ximion: will do
[23:24] <ximion> (it's difficult though, because I didn't have time to work on this for Ubuntu, and Laney might not have time either, especially since asgen will likely require a newer version of Ubuntu - more recent versions don't run on Xenial anymore)
 fwiw, it looks a million time better here already. so I count that a win
 thank you
[23:26] <ximion> in any case, sorry that I can help more, I am in the middle of packing my stuff to leave for skiing tomorrow
[23:26] <valorie> oooo, fun!
[23:26] <yofel> enjoy the trip
 ximion: lucky you!
[23:27] <valorie> do we have to ask Laney or can we just do this?
[23:27] <valorie> tsimonq2: ^^^
[23:27] <ximion> also, this is the perfect example of why centralizing this apt snippet in a package makes sense, I think I'll go ahead with that plan later (beginning of March), so no package falls out of sync
[23:27] <tsimonq2> huh
[23:27] <tsimonq2> what
 thanks again for your help!
 I'm so happy we won't ship 18.04 with ugly icons
[23:27] <valorie> read up a bit re  appstream-generator update
[23:27] <valorie> oooo, snowing here again
 @valorie, that is ubuntu
[23:28] <ximion> valorie: ask Laney, unless you want to do really dirty things like injecting data (eww!)
[23:28] <ximion> yofel: thanks! Btw, I haven't seen you a loong time! Nice to know you're still there :-)
[23:28] <valorie> lol
[23:29] <tsimonq2> valorie: name of the source package?
[23:29] <yofel> yeah, being just fed up with IRC for a couple months didn't really work out. So I'm back for the time being ^^
[23:30] <acheronuk> we are very pleased you are back as much as you are now
[23:30] <ximion> valorie: asgen is a server-side service running somewhere at Canonical infrastructure. The package for the service itself in Bionic is fully up2date
[23:30] <valorie> !info  appstream-generator
[23:31] <valorie> tsimonq2: ^^^
[23:31] <valorie> needs updating
[23:32] <valorie> yofel: recently I decided to just set myself away when I was tired of reading IRC, and it makes a big difference
[23:33] <tsimonq2> valorie: That's in-sync with Debian.
[23:33] <valorie> ximion: ^^^
[23:34] <yofel> I just don't open IRC at all. Which is why I'm not reachable at all then. Not quite sure yet whether I want Telegram back..
[23:34] <ximion> [00:30] <ximion> valorie: asgen is a server-side service running somewhere at Canonical infrastructure. The package for the service itself in Bionic is fully up2date
[23:34] <tsimonq2> The *only* difference is that it was no-change rebuilt for a transition.
[23:34] <yofel> btw. what's the intended release date for 16.04.04? The schedule says 15th, but I'm seeing images popping up?
[23:34] <valorie> Monday I think
[23:34] <ximion> the package doesn't need updating in Bionic, but the service needs updating at Canonical
[23:34] <tsimonq2> yofel: March 1st
[23:34] <yofel> thanks
[23:35] <valorie> ah, thanks for the enlightenment
[23:35] <tsimonq2> ximion: Mind emailing rt@ubuntu.com with that, or telling me what to write?
[23:35] <valorie> so that's why Laney needs pinging then
 @acheronuk tritemio is about to be fully restored, it has been building everything for a while
[23:35] <ximion> I can only email stuff in after a week - I won't touch a computer the next week, if I am lucky :P
[23:36] <ximion> the problem with updating asgen is that newer versions require a newer GLib that's not available on Xenial, which is what's running on the server composing the data
[23:36] <ximion> as far as I know
[23:36] <tsimonq2> OK
[23:37] <ximion> btw, the service in question produces this: http://appstream.ubuntu.com/
[23:37] <ximion> (additional to the actual data, that is part of archive.ubuntu.com)
[23:38] <valorie> appstream becomes more and more important
[23:38] <valorie> @Santa that's good news
[23:39] <valorie> without good appstream info we don't get up-to-date info and images for apps
 ...and then people blame Discover for it
 @Santa, great. with tests?
 ^
[23:40] <tsimonq2> ximion: So wait, discover pulls from appstream.ubuntu.com?
[23:41] <ximion> nope, from archive.ubuntu.com
[23:41] <acheronuk> no
[23:41] <ximion> and Discover doesn't pull anything, APT does
[23:41] <tsimonq2> I'm confused then, what's the problem?
[23:41] <ximion> AppStream data is part of the archive metadata, just like Packages and Sources and Contents files
[23:42] <ximion> that apparently people want hidpi icons, which the older version of asgen that Ubuntu uses to generate the data doesn't support
[23:42] <acheronuk> but an external service has to make it?
[23:42] <acheronuk> and not the normal LP builders
[23:42] <tsimonq2> Maybe it's part of the archive tooling itself?
[23:43] <acheronuk> tsimonq2: look at neon CI. It has it's own appstream jobs
 @acheronuk, Yep http://gpul.grupos.udc.es/build-status/buildstatus_ubuntu-exp3/
[23:44] <tsimonq2> acheronuk: Right, but we don't share archive tooling with them
[23:44] <acheronuk> which is one reason why they have had better data than us for the things they do generate for
[23:44] <acheronuk> tsimonq2: but the idea is the same
[23:44] <valorie> and prettier icons!
[23:44] <ximion> a server running asgen downloads data from the internet, which builders can not. It also does some operations like rendering SVGs and scaling images from 3rd-party sources, which are potentially a security risk and therefore are usually isolated on a separate machine
 \o/
[23:45]  * ximion now really needs to get to packing his luggage
 uploaded that small change anyway for now. lets see how that changes real installs :)
[23:51] <valorie> have a great week ximion
[23:51] <valorie> thanks again for the information and collaboration
[23:56] <ximion> :-)
[23:58] <valorie> tsimonq2: are you writing that email or talking to Laney about this issue?
 so do we need to do anything to pick up that change that ximion just made?
[23:58] <tsimonq2> valorie: I'm waiting on ximion ;)
[23:59] <valorie> that is the easiest but it would be good to get this done before the LTS
[23:59] <valorie> if possible
 @nggraham, To 60discover?