Alrighty then! 
Another example of SNAPSHOT builds "doing things" which will happen with a much higher frequency right now around the release window. If you're curious about the root cause of that (I know I would be 
), I'd look at the kmods and see if any appeared or disappeared, and look in the kernel patch changes between .56 and .58...
Today's SNAPSHOT includes an updated attendedsysupgrade-common with the fix applied!
However, your attendedsysupgrade-owut file hasn't been renamed yet.
Yeah, I saw that. That means that you can get rid of the
. /rom/blah blah blah
line in your init script (which is the truly hacky bit we added), but keep the
uci set attendedsysupgrade.owut=owut
and it should work just fine. That latter uci set is sort of benign insurance, it basically does nothing if the ASU config exists, and is safe in any case (I added it to the wiki example a couple days ago, "just in case").
Huh, on both of my RT3200s the r27981 had the updated attendedsysupgrade-common package (v9), but the same release on my TL-WDR4300 still have the old (v8). I'll guess I'll wait another day to test a new SNAPSHOT.
Maybe some delay in the ASU server?
Looks like the ath79/mips24kc stuff is lagging behind on the buildbots:
https://downloads.openwrt.org/snapshots/packages/mips_24kc/packages/
I see it's still on version 8, last date stamp is "Wed Oct 30 10:55:27 2024"
Bah! I was hoping it would get that in before 24.10 was branched, but I missed the cutoff. I'll probably have to manually backport it...
Yes, please! 
Good to know, so upgrading my dumbaps from 23 to 24 when that lands (unlike my bpir4, those have no simple way to fix broken images) should probably be done with firmware selector.
@efahl, I see the 24.10-Snapshot images have landed. I was thinking about going to this from the Development SNAPSHOT to these.
The migration to apk is making me a little nervous.. has anyone tried owut on 24.10-Snapshot yet?
If you already have owut installed, that should also work safely, too, but you'll need to do the "double upgrade" as outlined above, so FS is probably easier. (And make sure on FS to verify that opkg is explicitly included, and as added insurance if you add owut there, you'll have another avenue for installing missing packages in case opkg fails in some way.)
Don't get ahead of yourself here! The 24.10 builds are only about halfway done, look like the packages will take another day or so at this rate (https://downloads.openwrt.org/releases/24.10-SNAPSHOT/packages/). In any case, they are probably going to be pretty unstable for a while, so if you feel like going to 24.10, I'd at least wait for 24.10.0-rc1.
That being said, I will be installing 24.10-SNAPSHOT (probably on an x86 vm) as soon as the packages are done building. My intended use is to debug and do QA on owut and my local ASU server, feeding any fixes back into the release branch. So, unless you have a need to do such specific testing, I'd recommend against it. (But, if you want to help with the QA, definitely jump in! The more the merrier.)
Right now, owut should work exactly the same on both the 24.10- and main-snapshots, there's no differences in the code yet.
And 24.10 is going to be using opkg for the time being, so no worries there. The plan is to make 24.10 stable work, then switch to apk on main SNAPSHOT. If the switchover is smooth and things work well, then the devs will decide whether to switch from opkg to apk during the 24.10 RC builds.
Oh, should have mentioned that you can monitor the build progress for your platform like this, watching that missing packages line.
$ owut check -V 24.10-snapshot
...
191 packages missing in target version, cannot upgrade
267 packages are out-of-date
...
OOPS. That only works for me, as I've got https://github.com/openwrt/asu/pull/1066 running on my ASU server. Sorry for the false (for now) info.
On my main and other APs running owut, I'm getting the below mentioned error. I understand that it says that the update server lagging behind, but it is same from last two days.
Also, due to this, I'm unable to install opkg on my main x86 router.
Request:
Version r28022-6691ff86b7 (kernel 6.6.59)
Request hash:
012b6cb617ce36334c661a9cac6b4ae9
--
Status: init
Progress: 0s total = 0s in queue + 0s in build
Build failed in 0s total = 0s in queue + 0s to build:
ASU server error =
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/rq/worker.py", line 1430, in perform_job
rv = job.perform()
^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/rq/job.py", line 1280, in perform
self._result = self._execute()
^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/rq/job.py", line 1317, in _execute
result = self.func(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/asu/build.py", line 176, in build
version_code = re.search('Current Revision: "(r.+)"', job.meta["stdout"]).group(1)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'group'
ASU server stderr =
make: *** No rule to make target 'info'. Stop.
ERROR: Build failed with status 500
The above errors are often due to the upgrade server lagging behind the
build server, first suggestion is to wait a while and try again.
Getting the same error for the last 24 hours on my BananaPi BPI r4.
I can download a new SDcard firmware, but the "request build" option of the 'Firmware Selector' fails when I try to include OWUT. (I have not tried it with another package.)
It was worse than that, snaphots stopped working on Saturday when the docker images were changed.
But, good news! The fix has been in place for about 4 hours now, I've just spent the last half hour running various tests to confirm everything works. You should be able to build snapshots with any of the ASU clients now.
Yeah, I updated my two RT3200s to the r28021 SNAPSHOT and it's working great!
I'm curious if anyone wants to test out 24.10-SNAPSHOT builds? (Not working on ASU server yet, so don't bother trying; I'm just gauging interest.)
I would, but I'm confused about these snapshots.
The Main snapshots are for new features overall? Like a canary release?
And the 24.10-snapshot for new features for the upcoming 24.10?? Like a Beta??
I had the r28010 SNAPSHOT and on Luci said "24.10 branch". Now, the r28021 says "Luci Master".
In the end, maybe I'll stay on snapshot until 24.10-rc arrives.
I would do on my dumbaps (mt3000 and Xiaomi ax6), possibly on the bpir4 too (tho that one runs snapshot by necessity anyhow).