Mattéo Delabre

These are interesting ideas, but moving the `xochitl` binary could prove to be a bit fragile and we will need to think about all corner cases and interactions. I’m not...

Agreed. I think we should also seek compatibility with the structure of Entware packages (if they do have a consistent structure).

Some GitHub API findings: * To find the latest successful workflow run of PR 300, one can run: ```sh wget "https://api.github.com/repos/toltec-dev/toltec/actions/workflows/pr.yml/runs" --output-document - --quiet | jq '[.workflow_runs[] | select(.pull_requests[] |...

Any logs on the server side when this loop occurs?

The current bootstrap script [creates a script called `entware-reenable`](https://github.com/toltec-dev/toltec/blob/36bdcfdc7162054ff0f3553576c7fe3733b30ccb/scripts/bootstrap/bootstrap#L324) in the home folder, and shows “Use '/home/root/entware-reenable' to re-enable Toltec after a system update” to the user after install. Automatically...

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.

Do you know if this is documented somewhere?

Update: This is now easily doable thanks to ddvk’s [remarkable-update](https://github.com/ddvk/remarkable-update) project (works on rM1 and rM2).

We may also want to rebuild Entware packages from source, for example to make sure that they match our toolchain. To avoid having to rewrite their recipes to our format,...

Related: #255