SUMMARY The kf6-core24-sdk snap is missing for the RISC-v architecture. The snap is needed to build all the other KDE snaps like kolourpaint. STEPS TO REPRODUCE On RISC-V system: snap info kf6-core24-sdk OBSERVED RESULT $ snap info kf6-core24-sdk error: no snap found for "kf6-core24-sdk" EXPECTED RESULT Snap available in latest/stable channel. SOFTWARE/OS VERSIONS n/a ADDITIONAL INFORMATION n/a
I do these snaps in my freetime. I cannot be expected to support all available architectures. Unless someone wants to sponsor me to enable more architectures this will be a WONT-FIX I am truly sorry.
(In reply to Scarlett Moore from comment #1) > I do these snaps in my freetime. I cannot be expected to support all > available architectures. Unless someone wants to sponsor me to enable more > architectures this will be a WONT-FIX I am truly sorry. Hi Scarlett, launchpad.net can be set up to build all architectures whenever you push to a Github repo. Could you, please, point me to to current repo for the kf6-core24-sdk snap so that I can check if anything is missing to build on the different architectures. Best regards Heinrich
https://snapcraft.io/docs/build-from-github describes how to build your snap on Launchpad and release it to the edge channel.
We do not use github except for read only mirrors of Applications. I know how to use github for building launchpad. This would entail creating my own repo and copying the files over, totally diverging the work to another platform ( this also breaks policy within KDE ) and linking in the store interface and I would have to then get it to build and support it. Again I am only accepting paid work at this time, I am overloaded in free work. Here is our repo https://invent.kde.org/neon/snap-packaging/kf6-core-sdk/-/tree/work.core24?ref_type=heads I am truly sorry. Scarlett
The current snap uses https://origin.archive.neon.kde.org/user as the package repository in which the riscv64 architecture is missing. So if the KDE snaps are meant to be built from Neon instead on Ubuntu this would be the first thing to fix.
Which is huge undertaking to untangle from neon. It may happen in the future. But not now. Snaps were originally maintained by the neon team and is legacy. Again funding has dried up and all snaps related to KDE is volunteer work ( mostly me ).
We do not have riscv hardware.
We are only now trying to budget so we can get arm hardware, riscv isn't even on the list yet. KDE relies solely on donations to functions, this limits our scope.
For RISC-V KDE could file a request at https://riscv.org/developers/boards/#active to receive some SiFive HiFive Premier P550 boards to support the Neon distro.
There is still the issue of no one to do the actual work. This just isn't feasible at this time.
I'd be interested in taking this on as a free-time project. I have RISC-V hardware I can build and test on (or we can use Launchpad's builders), but I'd need some ramp-up time to understand how to integrate the CI.