Moved to 24.10-SNAPSHOT with a sysupgrade.
Let me know when owut supports.
There are two blockers that I know of: List of blockers move to top.
I've had owut working on 24.10-SNAPSHOT with my local ASU server for I think 8 days now, but only because I can hack-force the existence of 24.10 manually (and I'm running all my PRs for testing to stay ahead of the game). The data is all there, it's just the pipes connecting the pieces are not in place.
can you run the ASU server on docker?
@efahl you can install owut on 24.10-SNAPSHOT but it complains.
Maybe. I run bare metal in an Ubuntu 24.04 VM, as it needs a bunch of basic infrastructure that's missing in smaller pieces. The server itself runs as 3-4 podman containers. Docs at https://github.com/openwrt/asu/pull/1032
What does it say? I haven't tried it for a few days, been busy trying to work through getting the rpc packagelist figured out.
OpenWrt 24.10-SNAPSHOT, r28018-d83ae23d08
-----------------------------------------------------
root@OpenWrt:~# owut check
owut - OpenWrt Upgrade Tool 2024.10.25~8c8907c6-r2 (/usr/bin/owut)
Available 'version-to' values:
21.02 release branch
21.02-SNAPSHOT
22.03 release branch
22.03.5
22.03.6
22.03.7 (latest)
22.03-SNAPSHOT
23.05 release branch
23.05.0
23.05.2
23.05.3
23.05.4
23.05.5 (latest)
23.05-SNAPSHOT
SNAPSHOT main branch
SNAPSHOT (latest)
Your specified version-to '(null)' is not available. Pick one from above.
Ah, got it! Yes, that requires the items I mention just above. After those are done, you'll see this:
$ owut versions
owut - OpenWrt Upgrade Tool %%VERSION%% (/root/bin/owut)
Available 'version-to' values:
21.02 release branch
21.02-SNAPSHOT
22.03 release branch
22.03.5
22.03.6
22.03.7 (latest)
22.03-SNAPSHOT
23.05 release branch
23.05.0
23.05.2
23.05.3
23.05.4
23.05.5 (latest)
23.05-SNAPSHOT
24.10 release branch
24.10-SNAPSHOT
SNAPSHOT main branch
SNAPSHOT (latest,installed,requested)
Just checking, are most errors still because of the OPKG transition? I'm getting an error about 35 missing packages in target version.
Yes, the ASU package indexes are currently delivered with ABI-versioned names, but that is contrary to how it was done prior to apk. So, for example, if you had jansson4 installed, it was called just jansson everywhere, but now it's all mixed up and some places (on device) use one name and others (ASU server's index.json) use the other, those account for most of the "missing packages".
Makes sense, is there any intervention I can/should take or is that an issue that will sort/be resolved in due time?
The only thing you can do right now is move off of snapshot, things are moving slowly there. Maybe install 24.10-SNAPSHOT for the time being?
In order to be able to transition from SNAPSHOT to 24.10-SNAPSHOT, we need to wait for your "blockers" to be resolved, correct? So, at this point, best strategy is to sit tight and wait for the PR to be merged, and new tags to be created?
Yeah, pretty much. And a new issue popped up today (https://github.com/openwrt/openwrt/issues/17036).
I moved the blockers list to the very top for easy reference.
3 Likes
Good progress, 24.10-SNAPSHOT is now visible to OWUT.
For my GL.iNet GL-MT6000, I get:
`root@mt6000:~# owut check
~
~
Package version changes:
~
~
nftables-json 1.0.9-r1 1.1.1-r1
61 packages missing in target version, cannot upgrade
82 packages are out-of-date
Default package analysis:
Default Provided-by
nftables nftables-json
There are currently package build failures for 24.10-SNAPSHOT aarch64_cortex-a53:
Feed: packages
kadnode Mon Nov 25 22:52:59 2024 - not installed
micropython-lib Mon Nov 25 23:00:56 2024 - not installed
umurmur Mon Nov 25 23:03:49 2024 - not installed
Feed: telephony
freetdm Mon Nov 25 23:29:07 2024 - not installed
Failures don't affect this device, details at
https://downloads.openwrt.org/releases/faillogs-24.10/aarch64_cortex-a53/
ERROR: Checks reveal errors, do not upgrade
root@mt6000:~# exit`
Thanks
1 Like
I noticed that, too. But it also seems not reliable because I can't find the versions of the new packages, so it complains about it.
We're getting there! 
I'm guessing your "missing list" is probably mostly kmod-*? That's tied to getting this resolved: https://github.com/openwrt/openwrt/pull/17042 (then all of its follow-up in the ASU server...).
Is it advisable going from 23.x to 24.10 using this tool?
Not mostly, but entirely kmod-*!
I think that the BPI-R4 was the same.
1 Like
No, you can't run owut on 23.05, it's 24.10-and-later only. You would use auc on 23.05, which will be auto-replaced by owut when you do the upgrade.
But, don't go to 24.10 unless you have a good reason, and are willing to live with some rough bits. 24.10 is not as fraught with issues as the apk-based main snapshots, but it still has it's own set of lingering issues (see that post a couple above about the missing packages).
Heh, yeah, that's a problem. Made some progress on it today, @ynezz got the kernel version info into the profiles.json file for the build (still need for it to filter through the buildbots before we actually see it). Just submitted a PR to use that data to retrieve and populate the returned index.json with the kmods. (Details in my issues list at the very top; let me know if I've missed anything up there, I'm shooting in 10 directions right now and it's confusing as hell.)
This one should be knocked off in a day or two, only a billion or so remaining... 
2 Likes
The buildbots are updating nicely.
My GL.iNet GL-MT6000, and BananaPi BPI-R4 (both running 24.10-SNAPSHOT) have successfully upgraded using owut.
Thank you
Indeed, "only" n-1 tasks to go...
2 Likes