apk: a few transitional issues

[stangri]

Describe the bug

Sorry @aparcar if there's a master issue for all transitional problems I couldn't find it when I searched open issues for apk.

I'm facing a few issues:

1. Sorry, figured out a problem, was my fault.

2. The apk binaries produced by SDK do not contain arch in the filename like the ipk binaries did. For example, a filename for the binary produced by the APK-enabled SDK is: https-dns-proxy-2023.12.26-r1.apk, while ipk binary is called https-dns-proxy_2023.12.26-1_x86_64.ipk. Is it by design or is this an oversight which needs to be addressed?

3. For ipk binaries there's a ./scripts/ipkg-make-index.sh which I use to create the manifest file and set up a 3rd-party repository with the binaries I produce, can you point me in the direction of the script/code I could use to achieve the same for apk?

Thanks!

OpenWrt version

snapshots

OpenWrt release

snapshots

OpenWrt target/subtarget

x86_64

Device

Dell Edge 620

Image kind

Official downloaded image

Steps to reproduce

No response

Actual behaviour

No response

Expected behaviour

No response

Additional info

No response

Diffconfig

No response

Terms

• I am reporting an issue for OpenWrt, not an unsupported fork.

[github-actions]

Invalid Version reported. snapshots
Is this from a clean repository?

[github-actions]

Invalid Release reported. snapshots
Is this from a clean repository?

[github-actions]

Invalid Target/Subtarget reported. x86_64
Is this from a supported device?

[aparcar]

1. Curious issue, I haven't witnessed this yet. I'm guessing it's a problem how SDK combine RELEASE/VERSION, it's obvious that the r is missing right? Do you mind having a look?
2. Yes historically the architecture is missing from the APK packages. Also the packages use dashes instead of underscores, not sure why they decided on that. Somewhere is already an issue to have a more flexible naming design, however what's special is that APK doesn't store filenames in the index but concatenates metadata to figure out the filename. Such custom schema could be done on a per index basis, but then again is it really worth it? Do you face any troubles at this point not having the architecture in the name?
3. I'd suggest to use make package/index V=s, if you have to do it outside of build root or SDK, use apk mkndx. There is no script needed, APK itself does the magic. After als it's a binary file and not just a bunch of strings written, so a simple shell script doesn't cut it anymore

[aparcar]

I think it has to be noarch and not "all"

[hnyman]

ERROR: unable to select packages:
  6in4-29:
    error: uninstallable
    arch: all

I think it has to be noarch and not "all"

alternative to "noarch"(? ) might be to add "all" to the allowed architectures in /etc/apk/arch file.
See that mentioned in forum:
https://forum.openwrt.org/t/the-future-is-now-opkg-vs-apk/201164/78

I checked the /etc/apk/arch file, and it was set to x86_64, which is not the architecture of the my BPI R4. I changed the contents to

aarch64_cortex-a53
all

and now it works as expected. The all line is essential, since without it, some packages, like wireless-regdb will not be satisfied

[GlebChili]

Here is the issue for the forum discussion mentioned by @hnyman: #16953

[vincejv]

may i suggest that, just like with iptables to nftables transition/migration we maintain a list of packages that needs to be updated, just like this issue: openwrt/packages#16818 and pin them, since they somehow depend on the old opkg functionality?

For example:

• strongswan: strongswan-ipsec (5.9.14-r4) post-install script will not work after apk transition packages#25378
• [BanIP]: user.err banIP: no download utility with SSL support packages#25376
• apk: strongswan-mod-kernel-netlink (no such package) on SNAPSHOT #16968

[ynezz]

Please, don't mix multiple issues in one, always create a separate issue for every problem you face. Otherwise its very hard to keep track of anything that way, you can't use Fixes: XXXX tag to close such multi issues etc. Not to mention, that nobody wants to go through wall of texts just to get to the root of the problem.

That being said, please split this up into separate issues, ideally prefixed with apk: if you think, that its related to the opkg->apk transition, thanks!

[stangri]

As per suggestion from @ynezz I'm closing this in favour of individual issues.