Bit weird, auc advises snapshot r23102 is available but sends r23104.
Firmware selector shows r23104 so taken that but auc still incorrect.
Not causing me any trouble but if anyone is using attended sysupgrade you may run into this.
FWIW same issue here. Happening here at least since yesterday (i update stuff at weekends).
root@AP_S:~# auc -n -y
auc/0.3.2-1
Server: https://sysupgrade.openwrt.org
Running: SNAPSHOT r22866-4e5aac4729 on ipq807x/generic (dynalink,dl-wrx36)
Available: SNAPSHOT r23097-86e7614e0d
Requesting package lists...
iwinfo: 2023-02-06-c7eb8ebe-1 -> 2023-05-17-c9f5c3f7-1
kmod-crypto-gf128: 5.15.110-1 -> 5.15.113-1
kmod-usb-core: 5.15.110-1 -> 5.15.113-1
kmod-crypto-manager: 5.15.110-1 -> 5.15.113-1
busybox: 1.36.0-1 -> 1.36.1-1
kmod-crypto-ctr: 5.15.110-1 -> 5.15.113-1
ipq-wifi-dynalink_dl-wrx36: 2023-04-12-b22487d7-1 -> 2023-05-22-0f73d32e-1
kmod-nft-fib: 5.15.110-1 -> 5.15.113-1
kmod-nfnetlink: 5.15.110-1 -> 5.15.113-1
kmod-ath11k: 5.15.110+6.1.24-1 -> 5.15.113+6.1.24-4
umdns: 2021-05-13-b777a0b5-5 -> 2023-01-16-65b3308d-5
kmod-crypto-hash: 5.15.110-1 -> 5.15.113-1
kmod-nf-reject6: 5.15.110-1 -> 5.15.113-1
kmod-crypto-aead: 5.15.110-1 -> 5.15.113-1
kmod-usb-dwc3: 5.15.110-1 -> 5.15.113-1
kmod-nf-flow: 5.15.110-1 -> 5.15.113-1
kmod-lib-crc-ccitt: 5.15.110-1 -> 5.15.113-1
ucode-mod-ubus: 2023-02-13-ab2f3f70-1 -> 2023-04-03-51638672-1
kmod-phy-aquantia: 5.15.110-1 -> 5.15.113-1
kmod-pppoe: 5.15.110-1 -> 5.15.113-1
kmod-pppox: 5.15.110-1 -> 5.15.113-1
kmod-nf-reject: 5.15.110-1 -> 5.15.113-1
base-files: 1530-r22866-4e5aac4729 -> 1531-r23097-86e7614e0d
kmod-nf-nat: 5.15.110-1 -> 5.15.113-1
kmod-crypto-crc32c: 5.15.110-1 -> 5.15.113-1
ucode-mod-uci: 2023-02-13-ab2f3f70-1 -> 2023-04-03-51638672-1
kmod-usb-dwc3-qcom: 5.15.110-1 -> 5.15.113-1
kmod-usb-xhci-hcd: 5.15.110-1 -> 5.15.113-1
kmod-crypto-hmac: 5.15.110-1 -> 5.15.113-1
kmod-crypto-sha256: 5.15.110-1 -> 5.15.113-1
kmod-crypto-acompress: 5.15.110-1 -> 5.15.113-1
ucode-mod-math: 2023-02-13-ab2f3f70-1 -> 2023-04-03-51638672-1
kmod-lib-crc32c: 5.15.110-1 -> 5.15.113-1
kmod-qca-ssdk: 5.15.110+2022-09-12-628b22bc-1 -> 5.15.113+2022-09-12-628b22bc-2
kmod-crypto-sha512: 5.15.110-1 -> 5.15.113-1
kmod-crypto-seqiv: 5.15.110-1 -> 5.15.113-1
kmod-nft-nat: 5.15.110-1 -> 5.15.113-1
kmod-usb3: 5.15.110-1 -> 5.15.113-1
kmod-thermal: 5.15.110-1 -> 5.15.113-1
kmod-crypto-ghash: 5.15.110-1 -> 5.15.113-1
ucode-mod-fs: 2023-02-13-ab2f3f70-1 -> 2023-04-03-51638672-1
kmod-hwmon-core: 5.15.110-1 -> 5.15.113-1
kmod-qrtr-smd: 5.15.110-1 -> 5.15.113-1
libiwinfo-data: 2023-02-06-c7eb8ebe-1 -> 2023-05-17-c9f5c3f7-1
ucode: 2023-02-13-ab2f3f70-1 -> 2023-04-03-51638672-1
kmod-crypto-ccm: 5.15.110-1 -> 5.15.113-1
kmod-nf-log: 5.15.110-1 -> 5.15.113-1
kmod-leds-gpio: 5.15.110-1 -> 5.15.113-1
kmod-gpio-button-hotplug: 5.15.110-3 -> 5.15.113-3
kmod-qrtr: 5.15.110-1 -> 5.15.113-1
kmod-nf-log6: 5.15.110-1 -> 5.15.113-1
kmod-mac80211: 5.15.110+6.1.24-1 -> 5.15.113+6.1.24-4
libbpf: 7.1.0-b01941c8-1 -> 1.2.0-1
kmod-qca-nss-dp: 5.15.110+2022-04-30-72e9ec41-1 -> 5.15.113+2022-04-30-72e9ec41-1
kmod-crypto-michael-mic: 5.15.110-1 -> 5.15.113-1
kmod-libphy: 5.15.110-1 -> 5.15.113-1
kmod-nft-offload: 5.15.110-1 -> 5.15.113-1
kmod-ppp: 5.15.110-1 -> 5.15.113-1
kmod-crypto-null: 5.15.110-1 -> 5.15.113-1
libjson-c: 0.16-2 -> 0.16-3
kmod-nf-conntrack: 5.15.110-1 -> 5.15.113-1
libiwinfo: 2023-02-06-c7eb8ebe-1 -> 2023-05-17-c9f5c3f7-1
kmod-crypto-gcm: 5.15.110-1 -> 5.15.113-1
kmod-crypto-cmac: 5.15.110-1 -> 5.15.113-1
kmod-crypto-rng: 5.15.110-1 -> 5.15.113-1
kmod-nf-conntrack6: 5.15.110-1 -> 5.15.113-1
libucode: 2023-02-13-ab2f3f70-1 -> 2023-04-03-51638672-1
kmod-ath11k-ahb: 5.15.110+6.1.24-1 -> 5.15.113+6.1.24-4
kmod-lib-lzo: 5.15.110-1 -> 5.15.113-1
kmod-ath: 5.15.110+6.1.24-1 -> 5.15.113+6.1.24-4
kmod-nft-core: 5.15.110-1 -> 5.15.113-1
kmod-nls-base: 5.15.110-1 -> 5.15.113-1
kmod-slhc: 5.15.110-1 -> 5.15.113-1
kmod-cfg80211: 5.15.110+6.1.24-1 -> 5.15.113+6.1.24-4
arp-scan: 1.9.8-1 -> 1.10.0-2
Error: Received inncorrect version r23110-dc2d4d7393 (requested r23097-86e7614e0d)
Bad message (74)
Perhaps, just flagging in case anyone runs scripted updates over the weekend.
Most likely the new buildbot is crunching builds faster than the auc updates its database of builds. A new build got ready after the list was refreshed.
See the recent build frequency of ipq807x
(I remember a recent discussion that said that auc updated its database every eight(?) hours: At what hours is firmware selector updated? )
1 Like
Im seeing it on mt7622, netgear wax206 to be precise.
FWIW auc's backend seems stuck at r23097-86e7614e0d since saturday. so definitively it seems that definitively something stopped updating.
1 Like
It did, sorry. The new implementation should be less flaky and will be deployed some day soon! Sorry for the inconvenience.
3 Likes
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.