Nathaniel van Diepen
Nathaniel van Diepen
Toltec doesn't support past 3.9, so we don't plan on making changes to make it easier to work on an unsupported version. We'd much rather work on the changes required...
Fresh install returns the following: ``` Run the following command(s) to use oxide as your launcher $ systemctl disable --now xochitl $ systemctl disable --now xochitl $ systemctl enable --now...
Upon further investigation, it's because the results of `get-conflicts tarnish` is the following: ``` xochitl.service xochitl.service sync.service ``` This will need to be cleaned up.
Tarnish is crashing when trying to run this. I'll have to dig into this before this can be merged. It might require a v2.8.2 release.
Opened https://github.com/Eeems-Org/oxide/issues/354 to resolve this.
It appears that libsysfs_preload is segfaulting on a rM2, which is keeping this from working as expected.
Upon further investigation, this might be due to rm2fb-client and sysfs_preload conflicting somehow. I'm not sure why.
- [x] Test upgrade path to make sure it adds the 2.x arch - [x] Test installing on 3.x to make sure it adds the 3.x arch - [x] Update...
Changes in this PR are now available on the `experimental` branch. You can switch to this by running the following: ```bash toltecctl switch-branch experimental opkg upgrade ``` You can do...
 ~~Not exactly what I was expecting, as the existing code handles creating `opkg.conf` using the same code.~~ This appears to be due to using `opkg` to compare version numbers.