Apparently the package manager changed recently from opkg to apk, how can this issue be resolved?
Is there a stable version I should install? How should I do that?
In case people see this and are curious, it's part of the apk ABI-versioning saga. See details here, Owut: OpenWrt Upgrade Tool, if you wish to know more.
Not really apk specific though, opkg used the same ABI encoding into the package name. Upgrades to (e.g., but not limited to) uci, ustream, ubox cause this - and we would see the very same if we still had opkg in snapshots.
The fix is simple either way, sysupgrade to a newer base snapshot - then everything should be installable again (given the way the 2-stage buildbots are set up, it might take up to a day to get everything back into sync again).
Edit: OOPS. I was thinking this was a different thread about the same-ish issue... Below applies when doing ASU stuff, this thread is about package providers and is tangentially related, hence my confusion (that and old age).
No, this is very much due to differences in apk and opkg.
The tooling in the ASU clients uses information that we provide in the opkg package index that does not (yet) exist in the apk package index files. We use that information to strip the file names produced by the ubus call rpc-sys packagelist call so they are in their canonical form, libubus or libuci or jansson... This missing piece in apk first needs to be added (@Ansuel's issue over on the apk-tools repo, https://gitlab.alpinelinux.org/alpine/apk-tools/-/issues/11066), then propagated into the rpc call (you can see the tracks I left in the code at https://github.com/openwrt/rpcd/blob/master/sys.c#L308), so this can be resolved once apk catches up.
Ran into this too while testing the snapshot on my Fritzbox 4040, tried installing block-mount but it won't let me as it depends on libuci20250120 which isn't available via apk yet.