Sysupgrade 24.10.4 -> 24.10.5

[bcookatwrt]

Hey there..

(attended sysupgrade is used for flashing / re-partitioning )
Was doing updates last night for devices as a Holiday break is coming up..

It seems this AM 10.5 is available and sysupgrade builders is/are failing

Is there a way to use one of the other images build last night?

Or can I force attended sysupgrade to 10.4 somehow?

If I sysupgrade flash the ‘last night built’ image it should rerun the partitioning (I’ve just not done without attended sysupgrade in a few years.. )

Thank you in advance.

[dave14305]

Since 24.10.5 hasn’t been announced yet, it is safe to assume the backend tools are not yet ready to support it.

[brada4]

You can always switch to 24.10-SNAPSHOT for ahead of time upgrades.

[badulesia]

Yes, and it won't until the official announcement has occured, as always. Sometimes it even takes a few extra days for the server to update.

[dave14305]

Took a while for me to find this useful post:

A note about using new stable releases before they are announced

There is always an excitement and enthusiasm as new stable releases start showing up on the downloads page -- and that is great! As of this moment, 21.02.3 and 19.07.10 are currently building, but they are not complete nor are they announced (current versions are still 21.02.2 and 19.07.9). Over time, the 'current' and upcoming versions will be different, but the same principles apply. A few things to know before you try to install new versions prior to the official announcement: The build s…

[bcookatwrt]

Sorry if this wasn’t clear possibly this might help..

Then I get this:

I understand the 10.5 is coming.. but I would like to keep going with my 10.4 from literally 12 hours ago..

Is there anyway to ‘tell this’ to use 10.4 and not 10.5

(second part)

If I just upload my sysupgrade image from previous builds.. will that engage the rootpt-resize and rootfs-resize?

Thank you (again) in advance.

[bcookatwrt]

seems as if auc was replaced with owut..

reading..

[bcookatwrt]

owut upgrade --version-to 24.10.4

[bcookatwrt]

well that was scary..

```
owut upgrade --version-to 24.10.4
ASU-Server https://sysupgrade.openwrt.org
Upstream https://downloads.openwrt.org
Target x86/64
Profile generic
Package-arch x86_64
Version-from 24.10.2 r28739-d9340319c6 (kernel 6.6.93)
Version-to 24.10.4 r28959-29397011cc (kernel 6.6.110)
148 packages are out-of-date
WARNING: There are 3 missing default packages, confirm this is expected before proceeding
Request hash:
6293d5b1210d9836cb325bda10e463493ae88d47d93e240f58dcc7cd9b13008f

Status: queued - 0 ahead of you

Progress: 0s total = 0s in queue + 0s in build

Status: init

Progress: 1s total = 0s in queue + 1s in build

Status: container_setup

Progress: 4s total = 0s in queue + 4s in build

Status: validate_manifest

Progress: 26s total = 0s in queue + 26s in build

Status: building_image

Progress: 145s total = 0s in queue + 145s in build

Status: done
Progress: 148s total = 0s in queue + 148s in build

Build succeeded in 148s total = 0s in queue + 148s to build:
Image saved : /tmp/firmware.bin
Installing /tmp/firmware.bin and rebooting...
```

[bcookatwrt]

Looks like this works..

No –are-you-sure flag.. +1

[OpenWrt Wiki] owut: OpenWrt Upgrade Tool

[efahl]

Best practice is to run (with the other options you're going to use, like --version-to whatever)

owut check --verbose

and check out what's going on prior to doing an upgrade.