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:
- Use codexctl to downgrade from 3.3.2 with toltec enabled to 2.15
- Run
toltecctl reenable
Expected behaviour
A clear and concise description of what you expected to happen.
Screenshots


System information:
toltecctl status output:
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.
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 reenableExpected behaviour
A clear and concise description of what you expected to happen.
Screenshots


System information:
toltecctl statusoutput:Additional context
Upon inspecting
/opt/lib/opkg/statusthere is only one entry fortoltec-deletions, which has been changed to rm2os2, but it should be rmallos2. Changing this allowstoltecctl reenableto work as expected.