for my device 23.05.1 is already available:
yet attended sysupgrade does not show it as an option, only showing 23.05.0 instead.
why? what needs to happen for it to show?
thanks.
for my device 23.05.1 is already available:
yet attended sysupgrade does not show it as an option, only showing 23.05.0 instead.
why? what needs to happen for it to show?
thanks.
It needs to be officially released/announced.
ok. but technically... the files are there, what else does auc
need?
Not all the files are there... in fact, many packages (including AUC, potentially) may not have been built yet.
thank you. i was about to mark this as solved with your answer, but i'm still surprised by something. i now know auc's behavior of not showing 23.05.1 yet is correct and by design. i also know that auc, luci auc, and the firmware selector are all clients to the same backend, so i'm surprised to find 23.05.1 in the selector but not in auc.
given what you said:
and that the users of the selector will inevitably just download latest, flash, and start reading later only if they find issues, could it be considered a bug that the selector is showing 23.05.1 right now?
About the thread I linked: I think that, at the time, the firmware selector was still in the works and wasn't the go-to method for finding firmware for your device. As such, people used one of two main entries into the downloads - a link from the main page at downloads.openwrt.org that leads directly into the into the specific version's subdirectory, or the 'releases' directory with all versions... this is where people would find the newest (and officially not yet released in these situations) version in the directory. So, my recommendation at the time was to always use the main page to navigate to the newest officially released version, rather than digging through the entire listing of releases.
Now, to be clear, the firmware selector is a huge improvement over the previous method of browsing those directories. I don't know exactly how the firmware selector builds its list, but I suspect it just searches the downloads directories and updates accordingly. I had actually put in a feature request at the beginning of the year that would allow new versions to be suppressed from display until someone flips a bit during the release announcement process. I don't know if this would be easy or hard to implement, but I agree that this could cause some confusion for some users. The good news is that it is a temporary situation -- usually just a matter of a few days and everything should be good. Hopefully that FR will find its way to implementation at some point, but coding is not my forte so I can't be the one to help bring it to life.
thanks. i read somewhere that selector and AUC both got their data from AUS, not digging dirs. thanks for explaining all!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.