Open Eeems opened 3 months ago
Describe the issue It appears that toltecctl isn't properly cleaning up opkg state when reenabling on an older OS version.
To Reproduce Steps to reproduce the behaviour:
toltecctl reenable
Expected behaviour A clear and concise description of what you expected to happen.
Screenshots
System information: toltecctl status output:
toltecctl status
reMarkable: ~/ toltecctl status Enabled: Yes Supported: Yes Branch: testing Model: rm2 OS: 2.15.1.1189
Additional context Upon inspecting /opt/lib/opkg/status there is only one entry for toltec-deletions, which has been changed to rm2os2, but it should be rmallos2. Changing this allows toltecctl reenable to work as expected.
/opt/lib/opkg/status
toltec-deletions
This also appears to happen on the rM1
Describe the issue It appears that toltecctl isn't properly cleaning up opkg state when reenabling on an older OS version.
To Reproduce Steps to reproduce the behaviour:
toltecctl reenable
Expected behaviour A clear and concise description of what you expected to happen.
Screenshots
![image](https://github.com/toltec-dev/toltec/assets/1176979/ccad5806-d299-4fad-a17f-52b70442bdc4)
System information:
toltecctl status
output:Additional context Upon inspecting
/opt/lib/opkg/status
there is only one entry fortoltec-deletions
, which has been changed to rm2os2, but it should be rmallos2. Changing this allowstoltecctl reenable
to work as expected.