We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
/etc/version
Describe the issue Kernelctl uses /etc/version when creating a backup of the current kernel. As this stops being a unique value in newer OS builds,
To Reproduce Steps to reproduce the behaviour:
kernelctl list
Expected behaviour It should be using RELEASE_VERSION from /usr/share/remarkable/update.conf for the OS version number instead.
RELEASE_VERSION
/usr/share/remarkable/update.conf
Upstream issue N/A
Screenshots
System information:
toltecctl status
Additional context toltecctl has the following code available that kernelctl could call:
toltecctl
toltec/package/toltec-bootstrap/toltecctl
Lines 108 to 110 in eed41f1
The text was updated successfully, but these errors were encountered:
@Etn40ff would you be willing to make this change?
Sorry, something went wrong.
Sure
No branches or pull requests
Describe the issue
Kernelctl uses
/etc/version
when creating a backup of the current kernel. As this stops being a unique value in newer OS builds,To Reproduce
Steps to reproduce the behaviour:
kernelctl list
to see list of kernelsExpected behaviour
It should be using
RELEASE_VERSION
from/usr/share/remarkable/update.conf
for the OS version number instead.Upstream issue
N/A
Screenshots
System information:
toltecctl status
output: N/AAdditional context
toltecctl
has the following code available that kernelctl could call:toltec/package/toltec-bootstrap/toltecctl
Lines 108 to 110 in eed41f1
The text was updated successfully, but these errors were encountered: