package names under 25.12.1

[alfredganz]

Although the packages that had fixed names and required special handling under 25.12.0 like libubox are the proper packages under 25.12.1 they are
still reported by apk as they were under 25.12.0 like llibubox20260213.
Shouldn't that mapping be cleared with 25.12.1?

[efahl]

The ABI-versioned names like llibubox20260213 are the actual package names. Only the ASU server and clients deal with the sanitized versions, so any apk ... commands will always show the full name.

What specifically are you seeing that is a concern? This all looks correct to me.

$ apk query --available 'libubox*'
Name: libubox20260213
Version: 2026.03.13~81563384-r2
Description: Basic utility library
Arch: x86_64
License: ISC
Origin: feeds/base/libs/libubox
File-Size: 29529
Tags: openwrt:abiversion=20260213

$ owut check | grep libubox
  libubox       2026.02.13~1aa36ee7-r1    2026.03.13~81563384-r2

[alfredganz]

efahl, Date: Fri, 03 Apr 2026 12:07:57 -0700 Subject: Re: [efahl/owut] package names under 25.12.1 (Issue #69) The ABI-versioned names like `llibubox20260213` are the actual package names. Only the ASU server and clients deal with the sanitized versions, so any `apk ...` commands will always show the full name. What specifically are you seeing that is a concern? This all looks correct to me. My misunderstanding of how ABI-versioned works! I assumed that the ABI-versioned names would change quicker than they do. Thanks for your answer and sorry for the noise, AG

…

-- ---------------------------------------------------------------------- Alfred Ganz alfred-ganz:at:agci.com AG Consulting (203) 481-9776 88 Notch Hill Road, # 222 North Branford, CT 06471 ----------------------------------------------------------------------

[efahl]

My misunderstanding of how ABI-versioned works! I assumed that the ABI-versioned names would change quicker than they do.

Aha, I'm seeing what cause your concern now (sorry, I sort of missed that on first pass).

Your expectations were no doubt set by all previous builds where the package version and ABI version tracked exactly. With this libubox update, the actual-code-level-ABI didn't change, but the version and name did, so when the package was built with a new ABI-versioned name, it caused all sorts of havoc. In this rare case, the ABI version was reverted and hard-coded to match the previous release. This is causing other issues, but shouldn't hurt apk (which works from the package name and ignores ABI), or owut (which, like all of ASU - server and client alike - strips out ABI info and carries on without it).

We should really get rid of the ABI versioned names (ongoing discussion for years now), or manually separate/distance the ABI version from the package version number, like external packages do:

$ apk query --fields name,version,tags --format yaml jansson4 libgcc1
# 2 items
- name: jansson4
  version: 2.15.0-r1
  tags: # 1 items
    - openwrt:abiversion=4
- name: libgcc1
  version: 14.3.0-r5
  tags: # 1 items
    - openwrt:abiversion=1

[alfredganz]

efahl, Date: Fri, 03 Apr 2026 15:05:08 -0700 Subject: Re: [efahl/owut] package names under 25.12.1 (Issue #69) My misunderstanding of how ABI-versioned works! I assumed that the ABI-versioned names would change quicker than they do. Aha, I'm seeing what cause your concern now (sorry, I sort of missed that on first pass). .... We should really get rid of the ABI versioned names (ongoing discussion for years now), or manually separate/distance the ABI version from the package version number, like external packages do: .... This is obviouysly more complex a story than I thought it was! Thanks for taking the time to explain! AG

…

-- ---------------------------------------------------------------------- Alfred Ganz alfred-ganz:at:agci.com AG Consulting (203) 481-9776 88 Notch Hill Road, # 222 North Branford, CT 06471 ----------------------------------------------------------------------