[12:34] <santa_> good afternoon everyone
[12:34] <santa_> RikMills: fw 5.113 completed, at the moment, I don't plan to change more things in the packaging
[12:35] <santa_> so please go ahead with the riscv experiments
[12:35] <santa_> also, misc news/info:
[12:36] <santa_> - oxygen-icons tarball was renamed, just updating one file ka-metadata made KA work fine; the metadata is in the frameworks_staging branch btw
[12:37] <santa_> - I have pushed another fix for ppa-build-status, now it should work both with recent and ancient versions of Ubuntu
[12:38] <santa_> - for breeze-icons, I changed the package to not install arch specific cmake files, we were having a lintian warning for a while; if these files are actually needed for anything, they should go to a separate arch-specific package
[12:39] <RikMills> santa_: I have conformed it is the riscv64 builder change, rather than any other change in noble, by no change rebuidling the manic kconfig package
[12:39] <RikMills> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4979/+sourcepub/15413039/+listing-archive-extra
[12:39] <RikMills> it fails in the same way
[12:40] <santa_> ah, I get it, I was going to ask about that
[12:40] <RikMills> santa_: ack on breeze-icons
[12:40] <RikMills> I will have to open a ticket with LP admins to get this looked at
[12:40] <santa_> have you tried the new fw 5.113 package on riscv, does it fail in the same way?
[12:41] <RikMills> santa_: not yet. I will try in the next few days when I can free up a PPA
[12:42] <RikMills> or I gues I could pathc in the the 5.113.0 changes to a 5.112.0 build
[12:42] <RikMills> *patch
[12:43] <santa_> sure, but imagine the segfault comes from one of the deps
[12:43] <santa_> but it's a good start if you don't have a proper PPA available yet, so please go ahead and experiment
[12:45] <RikMills> ci-train PPAs cannot be created now since bileto seems dead. but there are dozens on existing PPAs that the creators don't look to be using. so what I need to do is find one that I am sure I can steal ;)
[12:45] <RikMills> s/steal/re-purpose/
[12:46] <RikMills> santa_: and yes, rebuilding the fw stack is the best test
[12:46] <santa_> hahah
[12:46] <santa_> ok
[12:48] <RikMills> hopefully will get to that by the end of the week
[12:50] <santa_> so the change in the buildds was:
[12:50] <santa_> qemu buildds -> non-qemu buildds
[12:50] <santa_> ?
[12:50] <RikMills> looks that way
[12:51] <RikMills> I recall seeing something about them getting real boards etc a while back
[12:53] <RikMills> idea is to get riscv64 towards a real release architecture
[12:54] <RikMills> if you are going to do that, then you can't acre flavours who use KDE things
[12:55] <RikMills> s/acre/screw
[12:55] <RikMills> sigh
[12:57] <santa_> ack, I have seen now all the #launchpad messages
[12:57] <santa_> in case the issue persists, things interesting in case we request help from KDE fellows
[12:58] <santa_> - confirm if the change in the buildds is non-qemu -> quemu
[12:58] <santa_> - a shell in a riscv server where someone can reproduce the issue, rebuild and try to fix
[13:01] <RikMills> indeed
[13:23] <BluesKaj> Hi all
 so far so good upgraded fw 5.113 (re @IrcsomeBot: <santa_> RikMills: fw 5.113 completed, at the moment, I don't plan to change more things in the packaging)
[15:59] <santa_> ack, thanks for testing