[05:29] <RikMills> santa_: not yet
[12:46] <santa_> RikMills: if you haven't started already, do you mind if I proceed?
[12:47] <RikMills> santa_: fine with me
[12:47] <santa_> RikMills: ack, I will start in the next hour
[12:48] <santa_> I have a change here to make the blue color of ka_print_info a bit easier to read on dark backgrounds
[13:50] <BluesKaj> Hi all
[19:03] <RikMills> santa_: please let me know when fw packing is done. I need to do a build for riscv64 in a ci-train ppa due to some apparent issues on that arch for kde things
[19:04] <santa_> RikMills: ack, by the way is the ppa-build-status thing working fine for you latetly?
[19:04] <santa_> * lately
[19:04] <RikMills> i.e. repeatable FTBFS segfaults during builds
[19:04] <RikMills> santa_: no, it was broken last time I tried it
[19:04] <santa_> ahhhh
[19:05] <santa_> it's not working for me either and I am trying to figure it out
[19:05] <santa_> it doesn't download the build logs properly
[19:05] <RikMills> yes, I found that
[19:06] <santa_> it's because of the TLS version used in https
[19:06] <RikMills> santa_: also what release are you running it on?
[19:06] <santa_> I don't know yet how to fix it, but I have been investigating it
[19:07] <santa_> RikMills: ** suspense music **
[19:07] <santa_> RikMills: 18.04
[19:07] <RikMills> santa_: makes sense. it is also broken on newer python for other reasons
[19:07] <santa_> I suspected it was because of the old version but I was going to try in noble
[19:08] <santa_> what other reasons?
[19:08] <RikMills> so I have been running it in a 18.04 container for a while
[19:08] <RikMills> santa_: some depreciated/removed python things that I forget what they were right now
[19:09] <RikMills> url *something*
[19:09] <RikMills> maybe.....
[19:09] <santa_> aha, well I will have a look
[19:09] <RikMills> I had been meaning to mention that breakage for some while, but kept forgetting
[19:14] <RikMills> fyi, the riscv64 issue is this: https://launchpad.net/ubuntu/+source/krdc/4:23.08.3-1ubuntu1/+build/27040377
[19:15] <RikMills> same issue in several KDE packages in proposed
[19:16] <RikMills> so I wouldn't want to upload fw without seeing that the whole stack builds on riscv64
[19:23] <RikMills> I have several ideas that might be a fix, but yet to test much
[19:40] <santa_> so it's a segfault on /usr/lib/libexec/kf5/kconfig_compiler_kf5
[19:40] <santa_> so many things at the same time
[19:41] <santa_> I got the ppa-build-status thing working in noble
[19:41] <santa_> I guess I will push the patch today at some point to master
[20:55] <santa_> RikMills: FYI I have pushed 3 commits to KA's master branch, one of them is the one that fixes ppa-build-status at least for noble, one question: do you know if update-symbols-ppa works with private PPAs?
[20:57] <RikMills> santa_: never tried it, but I would be very surprised if it did
[20:58] <santa_> RikMills: why?
[20:58] <santa_> because it doesn't have all the archs?
[20:58] <santa_> or because of something else? :)
[20:58] <RikMills> auth to get the build logs
[21:00] <santa_> ah, it logs in anonymously
[21:00] <RikMills> I thought so
[21:00] <RikMills> could be wrong
[21:02] <RikMills> only ever tried it with normal and ci-train ppas. which it works with
[23:32] <mmikowski> Hey Kubuntu Development Strike Force! I've got one for you. On 22.04.3 LTS, using the backports-extra repo and Plasma 5.27.9, Discover is showing [X] for images like so: https://www.reddit.com/r/Kubuntu/comments/17zguut
[23:32] <mmikowski> https://www.reddit.com/r/Kubuntu/comments/17zguut
[23:33] <mmikowski> whoops, sorry about the dup. Here's the image: https://i.imgur.com/E0xrzSk.png
[23:33] <mmikowski> This was confirmed with arraybolt3 too.