-
Notifications
You must be signed in to change notification settings - Fork 60
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
Automate re-enabling of Toltec after system upgrades #109
Comments
The current bootstrap script creates a script called |
I think @Eeems had the idea to add a specific feature to reMarkables update_engine. One would need to:
Maybe creating an issue there would be a better first step, to ask if they would even want to allow such a feature. |
Have we found a way to downgrade to a previous version to test the upgrade path? The only way I know of currently is flashing using uuuflash. |
Flashing a previous version to the other root partition while live and then switching partitions. |
Do you know if this is documented somewhere? |
Not that I'm aware of. |
Update: This is now easily doable thanks to ddvk’s remarkable-update project (works on rM1 and rM2). |
https://github.com/Jayy001/codexctl implements full on-device upgrade/downgrade handling, and would be extendable to run post-upgrade scripts for us. At some point soon, I'll add codexctl as a toltec package for us when I sort out automating the build for the device binary. |
Something I noticed recently, You can use the following to turn on logging to echo "POSTINST_LOGGING=1" > /etc/default/postinst
echo "LOGFILE=/tmp/postinst.log" >> /etc/default/postinst We should probably put a service in place that waits for |
@Jayy001 you should be aware of this issue |
when opkg/toltec is installed and there is a system upgrade, we need a way to re-enable opkg. the entware package comes with entware_reinstall which re-creates the opt mounting system service. i believe our bootstrap script (thanks linusCDE!) automatically re-enables the opkg as well. (is the bootstrap script saved locally for re-use after upgrade?)
currently, we do not have any hooks into the remarkable's upgrade process to automatically re-enable opkg.
options:
The text was updated successfully, but these errors were encountered: