Auc acting strangely

Hello,

I saw some updates being made to the latest snapshot and wanted to update. I like using the auc command to do this because you can get a listing of what's changing before updating, but it wasn't seeing the most-recent update. I then updated using attended sys update and that worked, but when I checked auc again it displayed the following:

auc (0.2.4-8)
Server:    https://sysupgrade.openwrt.org
Running:   SNAPSHOT r19160-7ea2f3d6e2 on mediatek/mt7622 (linksys,e8450-ubi)
Available: SNAPSHOT r19138-4ecf8346c0
Requesting package lists...
 kmod-usb-storage: 5.10.107-1 -> 5.10.104-1
 terminfo: 6.3-1 -> 6.2-3
 iwinfo: 2022-03-01-90bfbb9a-1 -> 2021-07-11-a0a0e02d-1
 kmod-crypto-gf128: 5.10.107-1 -> 5.10.104-1
 kmod-usb-core: 5.10.107-1 -> 5.10.104-1
 kmod-usb-storage-uas: 5.10.107-1 -> 5.10.104-1
 kmod-crypto-manager: 5.10.107-1 -> 5.10.104-1
 kmod-crypto-ctr: 5.10.107-1 -> 5.10.104-1
 kmod-crypto-hash: 5.10.107-1 -> 5.10.104-1
 kmod-nf-reject6: 5.10.107-1 -> 5.10.104-1
 kmod-tun: 5.10.107-1 -> 5.10.104-1
 kmod-crypto-aead: 5.10.107-1 -> 5.10.104-1
 libiwinfo-lua: 2022-03-01-90bfbb9a-1 -> 2021-07-11-a0a0e02d-1
 kmod-nf-flow: 5.10.107-1 -> 5.10.104-1
 kmod-lib-crc-ccitt: 5.10.107-1 -> 5.10.104-1
 libiptext: 1.8.7-6 -> 1.8.7-5
 kmod-pppoe: 5.10.107-1 -> 5.10.104-1
 kmod-pppox: 5.10.107-1 -> 5.10.104-1
 kmod-ipt-conntrack: 5.10.107-1 -> 5.10.104-1
 kmod-nf-reject: 5.10.107-1 -> 5.10.104-1
 procd-ujail: 2022-02-19-ad652490-3 -> 2022-02-19-ad652490-2
 base-files: 1472-r19160-7ea2f3d6e2 -> 1470-r19138-4ecf8346c0
 kmod-lib-crc16: 5.10.107-1 -> 5.10.104-1
 kmod-nf-nat: 5.10.107-1 -> 5.10.104-1
 kmod-crypto-crc32c: 5.10.107-1 -> 5.10.104-1
 kmod-mt7615e: 5.10.107+2022-03-15-053668ac-4 -> 5.10.104+2022-03-15-053668ac-4
 uboot-envtools: 2022.01-15 -> 2022.01-14
 kmod-usb-xhci-hcd: 5.10.107-1 -> 5.10.104-1
 procd: 2022-02-19-ad652490-3 -> 2022-02-19-ad652490-2
 kmod-crypto-hmac: 5.10.107-1 -> 5.10.104-1
 kmod-crypto-sha256: 5.10.107-1 -> 5.10.104-1
 kmod-mt7615-common: 5.10.107+2022-03-15-053668ac-4 -> 5.10.104+2022-03-15-053668ac-4
 kmod-iptunnel: 5.10.107-1 -> 5.10.104-1
 libxtables: 1.8.7-6 -> 1.8.7-5
 kmod-mt76-connac: 5.10.107+2022-03-15-053668ac-4 -> 5.10.104+2022-03-15-053668ac-4
 kmod-crypto-seqiv: 5.10.107-1 -> 5.10.104-1
 kmod-fs-vfat: 5.10.107-1 -> 5.10.104-1
 kmod-usb3: 5.10.107-1 -> 5.10.104-1
 kmod-fs-exfat: 5.10.107-1 -> 5.10.104-1
 kmod-thermal: 5.10.107-1 -> 5.10.104-1
 kmod-nf-ipt: 5.10.107-1 -> 5.10.104-1
 kmod-ip6tables: 5.10.107-1 -> 5.10.104-1
 kmod-crypto-ghash: 5.10.107-1 -> 5.10.104-1
 iptables-mod-ipopt: 1.8.7-6 -> 1.8.7-5
 kmod-fs-ext4: 5.10.107-1 -> 5.10.104-1
 ip6tables-legacy: 1.8.7-6 -> 1.8.7-5
 libip4tc: 1.8.7-6 -> 1.8.7-5
 kmod-hwmon-core: 5.10.107-1 -> 5.10.104-1
 kmod-nls-utf8: 5.10.107-1 -> 5.10.104-1
 kmod-nls-cp437: 5.10.107-1 -> 5.10.104-1
 procd-seccomp: 2022-02-19-ad652490-3 -> 2022-02-19-ad652490-2
 libiwinfo-data: 2022-03-01-90bfbb9a-1 -> 2021-07-11-a0a0e02d-1
 kmod-mt7915e: 5.10.107+2022-03-15-053668ac-4 -> 5.10.104+2022-03-15-053668ac-4
 iptables-legacy: 1.8.7-6 -> 1.8.7-5
 kmod-crypto-ccm: 5.10.107-1 -> 5.10.104-1
 kmod-leds-gpio: 5.10.107-1 -> 5.10.104-1
 kmod-gpio-button-hotplug: 5.10.107-3 -> 5.10.104-3
installed package xtables-legacy cannot be found in remote list!
 kmod-mac80211: 5.10.107+5.15.8-1-2 -> 5.10.104+5.15.8-1-2
 libip6tc: 1.8.7-6 -> 1.8.7-5
 libiptext6: 1.8.7-6 -> 1.8.7-5
 kmod-sit: 5.10.107-1 -> 5.10.104-1
 kmod-ipt-core: 5.10.107-1 -> 5.10.104-1
 kmod-ppp: 5.10.107-1 -> 5.10.104-1
 kmod-fs-f2fs: 5.10.107-1 -> 5.10.104-1
 libncurses: 6.3-1 -> 6.2-3
 kmod-crypto-null: 5.10.107-1 -> 5.10.104-1
 libiwinfo: 2022-03-01-90bfbb9a-1 -> 2021-07-11-a0a0e02d-1
 kmod-mt7615-firmware: 5.10.107+2022-03-15-053668ac-4 -> 5.10.104+2022-03-15-053668ac-4
 kmod-iptunnel4: 5.10.107-1 -> 5.10.104-1
 kmod-nf-conntrack: 5.10.107-1 -> 5.10.104-1
 kmod-nf-ipt6: 5.10.107-1 -> 5.10.104-1
 kmod-crypto-gcm: 5.10.107-1 -> 5.10.104-1
 kmod-fs-autofs4: 5.10.107-1 -> 5.10.104-1
 kmod-nls-iso8859-1: 5.10.107-1 -> 5.10.104-1
 kmod-crypto-cmac: 5.10.107-1 -> 5.10.104-1
 kmod-ipt-ipopt: 5.10.107-1 -> 5.10.104-1
 kmod-crypto-rng: 5.10.107-1 -> 5.10.104-1
 kmod-nf-conntrack6: 5.10.107-1 -> 5.10.104-1
 kmod-mt76-core: 5.10.107+2022-03-15-053668ac-4 -> 5.10.104+2022-03-15-053668ac-4
 kmod-sched-cake: 5.10.107-1 -> 5.10.104-1
 kmod-crypto-crc32: 5.10.107-1 -> 5.10.104-1
 kmod-ifb: 5.10.107-1 -> 5.10.104-1
 kmod-nls-base: 5.10.107-1 -> 5.10.104-1
 kmod-ipt-offload: 5.10.107-1 -> 5.10.104-1
 kmod-scsi-core: 5.10.107-1 -> 5.10.104-1
 kmod-slhc: 5.10.107-1 -> 5.10.104-1
 kmod-cfg80211: 5.10.107+5.15.8-1-2 -> 5.10.104+5.15.8-1-2
 kmod-ipt-nat: 5.10.107-1 -> 5.10.104-1
 kmod-sched-core: 5.10.107-1 -> 5.10.104-1
Are you sure you want to continue the upgrade process? [N/y] 

Looks like it still wants SNAPSHOT r19138-4ecf8346c0?

Thanks!

Just a head's up that I saw errors again in auc after flashing the latest snapshot today:

auc (0.2.5-2)
Server:    https://sysupgrade.openwrt.org
Running:   SNAPSHOT r19183-e89c85249e on mediatek/mt7622 (linksys,e8450-ubi)
Available: SNAPSHOT r19183-e89c85249e
Requesting package lists...
installed package openssh-sftp-server cannot be found in remote list!
installed package openssl-util cannot be found in remote list!
installed package libustream-openssl cannot be found in remote list!
installed package unbound-daemon cannot be found in remote list!
installed package unbound-control cannot be found in remote list!
installed package wpad-openssl cannot be found in remote list!
installed package libunbound cannot be found in remote list!
installed package libopenssl cannot be found in remote list!
installed package openvpn-openssl cannot be found in remote list!
installed package libopenssl-conf cannot be found in remote list!
 zlib: 1.2.11-3 -> 1.2.11-4
installed package libevent2 cannot be found in remote list!

Thanks for all you do!

Likely related to the openssl build infra (engine.mk move from package to build include) by https://github.com/openwrt/openwrt/commit/1bf94b6797a1e04c0d3accd08b3efb666fbb280e

This will likely get fixed automatically, once the SDKs for targets are rebuilt with the .mk file in the new location, and then the phase2 packages buildbot builds openssl and dependent packages with the new udpated SDK. I think that the buildbot has already built the SDKs, but the packages rebuild may take 1-2 days until all targets have been built.

4 Likes

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.