-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
luci-mod-status: firmware version should include revision number #7343
Comments
To get to parity as before I assume we would need to change luci/modules/luci-mod-status/htdocs/luci-static/resources/view/status/include/10_system.js Line 41 in c85af3d
"description": "OpenWrt 24.10" (assuming that'll be the next stable version) that should work.
|
Yeah.👍 if we depend on the new file, this is likely a good update. Feeling up for a PR? |
Maybe the OpenWrt side change should be fixed, the commit sort of implies that the intention was to provide the same data and there's probably other downstream users affected by this as well. |
The information required for output via the ubus is currently read from the file '/etc/openwrt_release'. The same information can also be found under '/usr/lib/os-release'. This file contains further information and is also the most common used file in other Linux distributions. So let´s use this file. Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Unfortunately, I didn't know that information was missing here. I would fix this in the procd. And would replace PRETTY_NAME with the information from OPENWRT_RELESE ? I don't have access to any system at the moment as I'm travelling. So can someone send me the output of |
Now I was too hasty. I have just seen that these two values DISTRIB_DESCRIPTION in |
@feckert if you still need it.
|
I'm going to leave the issue open for visibility - at least until the patch is merged. |
Signed-off-by: Paul Donald <newtwen+github@gmail.com>
@feckert did you also send a PR to repo also? |
24.10 has now been branched without this fix being merged to procd and at least since 19.07 it hasn't had stable branches so backporting doesn't seem trivial in that repo. How do we go about solving this issue now? |
Stay the course. There are a few rc to go yet. |
@feckert any update on the patch? |
@feckert I will take care of that. Just one question the PRETTY_NAME was never used? It got dropped? |
@Ansuel Correct Before my change procd reads the variable DISTRIB_DESCRIPTION from This is not correct. Unfortunately, I overlooked that. The same information can be found in the variable OPENWRT_RELEASE in |
Fixed procd pushed. This will be magically fixed once updated packages gets built. |
@Ansuel Thank you for taking care of this. |
Thanks @Ansuel |
Steps to reproduce:
Firmware version
field does not include a revision number.Actual behavior:
Firmware version
doesn't include the revision number.Expected behavior:
Firmware version
should include the revision number.Additional Information:
The output of
ubus call system board
was changed in openwrt/procd@0f88a52 which introduced this problem. First discovered and discussed on the forum at https://forum.openwrt.org/t/strange-firmware-version-string/213745Here's the SNAPSHOT r27893 at point in time of writing this which doesn't work:
and here's a device I run r27687 on which does work
The text was updated successfully, but these errors were encountered: