Owut: OpenWrt Upgrade Tool

Community Builds, Projects & Packages
610

It was an issue with the downloads site, https://downloads.openwrt.org/.versions.json was missing... Broke all the ASU clients.

1 Like
611

I think I found a bug in owut or perhaps the packages (on 24.10):

$ owut check -v

[...]
Default package analysis:
  Default                             Provided-by
  dnsmasq                             dnsmasq-full
  nftables                            nftables-json
  ppp                                 not installed
  ppp-mod-pppoe                       not installed
  wpad-basic-mbedtls                  not installed

[...]

While this is mostly correct, it is wrong about wpad-basic-mbedtls. I have the full wpad-mbedtls installed, which provides that functionality (plus additional WPA2 EAP functionality that I use).

This is with OpenWRT 24.10 on a GL.INet MT-6000 (Flint 3). Owut version is 2025.03.14~52e7d44c-r1 apparently.

612 
wpad-basic-mbedtls != wpad-mbedtls
613

Indeed, but dnsmasq isn't dnsmasq-full either. Clearly it is in that case detecting that I have a replacement package. Same for nftables. But not for wpad.

614

Seeing the same with wpad-mbedtls.

I'd say it's a bug - it does not actually hurt upgrades in any way but the warning might scare people.

615

I do not know if it's due to the build server lagging behing, or something else, but 24.10.1 is missing from https://sysupgrade.openwrt.org/json/v1/overview.json

616

Both of those packages provide the hostapd and wpa-supplicant capabilities (see opkg whatprovides hostapd for example), but since neither of those is a default package and neither is mentioned anywhere in the packages lists reported by the rpc-sys packagelist call, there's no way for owut to know how to associate them.

This is an issue with packaging, but there's nothing owut can do about it, you'd need to dig into the target and package Makefiles, and see if you could resolve it there.

2 Likes
617

Yeah, saw that, too. https://github.com/openwrt/asu/issues/1327

I might dig into sometime when I recover from travel. blarg...

618

Looks like large number packages out of date after upgrade to 24.10.1. Is it safe to force package upgrades with - - f?

IMG_0038
IMG_00381290×2796 371 KB

619

I’ve upgraded all packages directly within Luci but now says 48 packages out of date. Surely this is not correct?

620

Hi,

I would not do anything at present, correct process is owut upgrade to update all packages.

1 Like
621

Thanks @hecatae hopefully we get clarification on this soon. Even when all up to date in Luci package manager , Owut says 48 packages are out of date!

622

If you look at the version-to line of the screenshot you posted it looks like owut wants to downgrade you to 24.10.0. I’d guess this is a symptom of the sysupgrade servers not being updated as previously noted in this thread.

1 Like
623

Thanks @foggygray, yep that makes sense!

1 Like
624

Spot on. :+1:t3:

I'm working on a PR for the issue (redis permanent caching of the version/target/subtarget info), should be submitted sometime today.

5 Likes
625

hi. I use zapret. this is external package. is it possible to use owut with external packages? I want to add some ipk files.

626

No, there is no mechanism in place to supply the ASU server with external packages to link into the image. You may be able to accomplish your goal with a two-step:

owut upgrade --remove zapret
< fix feeds to point to wherever zapret lives >
opkg install zapret
1 Like
627

thank you very much ...

628

I have a couple of quetions before I upgrade my router to 24.10.1.

  1. I use "owut upgrade" tool, do I keep all my settings and all intalled packages?
    (Not wanted to reconfigure all again)

  2. If I want to only update my outdated packages what commad do I use then?
    1 packages were downgraded
    70 packages are out-of-date

629

Yes! That was the principal goal of the ASU system: retain all of your packages across upgrades. The original sysupgrade system that attended sysupgrade built upon already retained configuration settings across an upgrade. All of the device-based ASU clients (auc, owut and LuCI Attended Sysupgrade) accomplish this.

The image created by ASU is complete, i.e., it contains the OS image and all packages in one binary, so when installed, it overwrites everything on the device. So, there's no notion of "selective upgrade", it's an all or nothing process. If you are accustom to doing selective updates on, say, your workstation (apt upgrade nmap), this isn't like that. On an embedded device, you typically wipe it down completely and start from scratch.

1 Like