Let’s prepare some devices to test.
6 Likes
https://downloads.openwrt.org/releases/25.12-SNAPSHOT/ - and those are the builds.
4 Likes
Yes. It’s still compiling, mediatek isn’t here for now.
In case you are looking for any feedback: I downloaded the image glinet_gl-ax1800-squashfs-sysupgrade.bin and installed to my spare router, which had last been upgraded and tested with an OpenWrt snapshot several months ago. sysupgrade -c -u /tmp/sysupgrade.bin preserved all settings. However, apk upgrade failed:
root@OpenWrt:~# apk update
[https://downloads.openwrt.org/releases/25.12-SNAPSHOT/targets/qualcommax/ipq60xx/packages/packages.adb]
[https://downloads.openwrt.org/releases/25.12-SNAPSHOT/packages/aarch64_cortex-a53/base/packages.adb]
[https://downloads.openwrt.org/releases/25.12-SNAPSHOT/targets/qualcommax/ipq60xx/kmods/6.12.60-1-52e9e309075585cd6b3b8e9d302f2cb2/packages.adb]
[https://downloads.openwrt.org/releases/25.12-SNAPSHOT/packages/aarch64_cortex-a53/luci/packages.adb]
[https://downloads.openwrt.org/releases/25.12-SNAPSHOT/packages/aarch64_cortex-a53/packages/packages.adb]
[https://downloads.openwrt.org/releases/25.12-SNAPSHOT/packages/aarch64_cortex-a53/routing/packages.adb]
[https://downloads.openwrt.org/releases/25.12-SNAPSHOT/packages/aarch64_cortex-a53/telephony/packages.adb]
[https://downloads.openwrt.org/releases/25.12-SNAPSHOT/packages/aarch64_cortex-a53/video/packages.adb]
OK: 11018 distinct packages available
root@OpenWrt:~# apk upgrade
ERROR: unable to select packages:
libblobmsg-json20241219 (no such package):
required by: world[libblobmsg-json20241219]
libjson-script20241219 (no such package):
required by: world[libjson-script20241219]
libubox20241219 (no such package):
required by: world[libubox20241219]
libubus20250516 (no such package):
required by: world[libubus20250516]
libc-1.2.5-r5:
breaks: world[libc=1.2.5-r4]
…
This is something that I would expect from a snapshot of the main branch. I understand that this release branch was just forked, and the package selection would stabilize closer to the actual release candidates.
It is about buildbot having time to build packages for all possible target architectures...
(First build rounds largely failed due to missing SDKs from phase1 images buildbot. Now they are largely there, except the few that failed for annoying git server reasons. Check the 25.12 builders here on page 3/4... https://buildbot.openwrt.org/images/#/builders )
9 Likes
Just tried it on an „MR70X“ with it’s unique image, and it does seem to work stabilish-y. The biggest bugs are with apk though, installing and ironically uninstalling causes errors, in case of uninstalling is worse, since it phantom uninstalls the package (learned this the hard way with „wpad-basic“, completely broke Wi-Fi), in short everything has to be done with --allow-untrusted, which is not ideal. But everything else seems to work.
Better wait for the official announcement which should show up in: https://forum.openwrt.org/c/announcements/14, it can take a few days before everything has been build and is ready
2 Likes
25.12 can be built quite normally from sources with the full toolchain, and all required packages included.
But the image cook-up solutions, like owut, attendedsysupgrade etc. do not yet have the full normal package selection available, as buildbot is still ramping up.
Ps. Good to understand that the 25.12 source code is in practice the main/master development snapshot codebase from two days ago. There is nothing special in 25.12 compared to development snapshots, yet, except the version string... Main/master continues to get developed, and 25.12 will be polished via release candidate testing by wider populace to the final release.
9 Likes
I already switched 3 of my routers to 25.12 x86,filogic,ipq806x. Only had minor issues with the package config. E.g. ddns für my provider did not work because by default libcurl is configured without the needed http auth support.
Here's a more specific link: https://buildbot.openwrt.org/images/#/builders?tags=%2Bopenwrt-25.12
Which DDNS provider are you using if I may ask?
Now buildbot seems to have built all targets (main images, SDKs and imagebuilders) into https://downloads.openwrt.org/releases/25.12-SNAPSHOT/targets/ , and also almost all packages architectures (except mipsel_mips32 and arm_cortex-a9_neon) into https://downloads.openwrt.org/releases/25.12-SNAPSHOT/packages/
So, the downloadable imagebuilder should already work ok for most routers.
(But no idea about the online build tools. Likely not yet.)
6 Likes
working on Linksys MR7350
Right. ASU for 25.10-SNAPSHOT will not appear until there's an actual release on that branch, due to the way the metadata files are generated (they never mention snapshots, that's interpolated from release branches).
Currently missing are
-
Any mention of
25.12*in https://downloads.openwrt.org/.versions.json -
https://downloads.openwrt.org/releases/25.12-SNAPSHOT/.targets.json
-
https://downloads.openwrt.org/releases/25.12-SNAPSHOT/.overview.json. ASU doesn't use that one directly, instead it's needed by the Firmware Selector (I had forgotten about that until I re-read my notes).
I don't have any idea where the generation of any of these occurs, I've scoured the o/openwrt, o/buildbot and o/docker repos to no avail.
3 Likes
What a shame, another 15 days and it could have joined in on Apple’s bandwagon and also skipped to v26.
Silliness aside (yes, I know the year-based naming predates Apple’s re-versioning), will 25.12 be including the new package manager, apk or (like v24) will opkg be backported into the snapshot code?
Will we not know until the official release announcement?
Also, looking at the timeline, 24.10 rc1 in 2024-12, release in 2025-02 is it normal to expect the final release in 3+ months?
apk has been the default package manager on main for a while now (https://github.com/openwrt/openwrt/commit/40b8fbaa9754c86480eefc3692c9116a51a64718). It is the package manager for this and future releases until something better (which is a pretty tall task). opkg has been abandoned, as no one has maintained it for years, and there's no reason to try to keep it alive.
1 Like
From what I read, apk was already the default when 24.10 was branched from snapshot, but it was reverted to opkg.
I do not remember what was the reason at the time, or if it has changed; maybe that was why 24.10 took several months from branch to release?
I do not know what the typical release timeframe is.
I ask because typical times from branch to release and confirmation of apk as package manager are the most common questions I expect new or casual users OpenWRT to have when hearing this news.
Edit: Based on this comment, maybe it was not quite in Snapshot at the time, but it was definitely a strong possibility for 24.10:
@efahl Did I miss this, or did you recently edit this in:
Right, apk still had some major issues, especially with the ABI versioning which took some months after that to get resolved. It was pretty obvious at the time that apk was not ready, so the call to stay on opkg was pretty easy.
Yeah, I've been updating posts and wiki articles as I run across them over the past week or so since the 25.12 branch was created; if you think something change, it likely did...
2 Likes
25.12.0-rc1 is near:
4 Likes
Jenkins releases have a simple sun/rain icon where you can vote whether a particular release worked or not. It would be useful to have something like that for OpenWrt too, preferably builtin as a form of optional telemetry.