Even if the firmware selector was working, it wouldn't be able to build RC3. RC3 is not yet configured as an available branch on the sysupgrade server.
Interesting, I guess that was the cause of the "unsupported version" error we saw after the previous -rc releases.
Oh well, we'll just have to wait then.
It writes like this for many versions and has been doing so for a very long time.
You can no longer expect these versions to work.
To practice pressing buttons, they probably exist, or the site receives donations for clicks))), but of course there is a chance for a new one.
The sysupgrade server's configuration has to be manually updated each time there's a new RC or release. Otherwise, the firmware selector gets the "unsupported branch" error message.
The problem is there's currently only one person maintaining the sysupgrade server's configuration. He recently made a post asking for someone to help him with it. Call for help with sysupgrade.openwrt.org maintainance
You can check what's available to auc/asu here:
https://sysupgrade.openwrt.org/json/v1/latest.json
The error has changed to "unsupported version" now, so the problem with the firmware selector itself has been fixed.
Unsupported version: 23.05.0-rc3
I'm not much of a programmer, but I just noticed something that seems odd to me.
http://sysupgrade.openwrt.org/json/v1/overview.json
Near the very beginning of the file, at the start of the "branches" section:
"branches": {
"23.05": {
"enabled": true,
"extra_keys": [],
"extra_repos": {},
"git_branch": "openwrt-22.03",
Why does it say the git branch for 23.05 is openwrt-22.03? Could this possibly be a cause of the problem, maybe keeping a script from being able to automatically detect the latest tagged releases for the 23.05 branch, and then automatically add them as a supported versions in asu?
For both rc1 and rc2, I had to manually report the unsupported version error to @aparcar before it got fixed, and now it's happening again with rc3.
"The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application."
Model Xiaomi AX3600
Platform ipq807x/generic
Version 23.05.0-rc3 (r23389-5deed175a5)
Date 2023-08-20 23:31:59
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
https://sysupgrade.openwrt.org/stats/d/LM1HE4E7k/attended-sysupgrade-server?orgId=1&refresh=1m
No successfull generations seen for 23.0.5.0-rc3
Yep, it's gone back to the original error for me too, so the other error I got last night was just a one off.
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
Of course it's not possible that the server is overloaded as 23.05.0-rc3 wouldn't build anyway, so it's a bug. I wish I could do something about it but I'm not a programmer at all.
There is no 23.0.5.0-rc3 as the version is wrong
23.05.0-rc3 would be right...
It was a copy/paste - do not remember from where exactly
Today, I keep getting
The server encountered an internal error and was unable to complete your request. Either the server is overloaded or there is an error in the application.
also if I select version 22.03.5
or any other that used to work for me. Is there some server maintenance ongoing or something?
So, 23.05.0-rc3 has been added to the sysupgrade server and the "server is overloaded" error is also gone, but images still aren't building, the process remains stuck at "Received build request".
Edit: it has worked now, just downloaded a 23.05.0-rc3 image for my Belkin RT1800.
Likewise for Xiaomi AX3600 (qualcommax/ipq807x) - keeps processing build request.
Not completely directed towards you but the build it is cranking out the new release. After that's done, it can be used again.
So right now the server really is overloaded, though it's not complaining about it
I've managed to get an image out of it but I'll wait until tomorrow for my other devices images.
This is my first OpenWrt -rc cycle and it's been useful to learn how the firmware selector works after releases, thanks everyone for your input.
work perfectly build on my rt3200 thanks for all
Personnaliser les paquets installés et/ou le script de démarrage
SuccĂšs du Build
STDERR
STDOUT
Is it possible to add the making to collect 19.07.10 for old routers?
Extreme versions of such routers work very slowly, or do not support these devices at all.
This will greatly simplify and extend the life of such devices.
Thank you!.
19.07 is EOL and no longer supported, it must not be used, as it contains unfixed security issues. There is no alternative to upgrading to a supported version, yesterday (yes, at some point that may require a hardware upgrade).