-
Notifications
You must be signed in to change notification settings - Fork 394
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
0.7.0 upgrade notes and known issues #1303
Comments
I just ran into this a few times with 2 different rigs, after reflashing: |
That’s a basic Linux command installed with Debian by default. If it’s missing you probably have a corrupted flash. I’d try reflashing to start. |
yikes. on two chips ... Thank you! |
What image are you using to flash? Maybe re-download that too? |
I had just re-downloaded Jubilinux before reflashing these two chips. I am having a hard time getting a clean install, been trying for a few days, actually. I'll redownload. |
Seems I got a strange TZ issue after upgrading. Looplog... https://omniaps.slack.com/files/UP2SZTXNC/FQ87YUQ0H/Loop_log.js Edit: On investigation, unrelated to TZ, rather token based auth breaking and stopping ALL downloads/uploads from NS. The error for stale data time since fresh data increased linearly from the last successful download. |
Just committed 9d4c739 to dev to fix the install_requires issue. |
Will leave this issue open until we release 0.7.1 to track the install_requires fix. |
Running bash /tmp/openaps-install.sh dev (without a reflash) causes the rig to lose connectivity after updating dnsmasq and hostapd (used for the offline-only hotspot), and requiring me to log back in and re-run the setup a second time. I don’t know of any fix for that short of removing those packages and the offline-only hotspot support, but the workaround (running openaps-install again) shouldn’t be too big a deal. (It doesn’t happen on every upgrade, but when upgrading a rig that hasn’t been updated since before the last time those packages were updated upstream.)
Another install error that others have reported:
Fix is to update pip's setuptools via
pip install setuptools -U
and re-run the last install/setup command. If this happens to everyone, we can probably add that command to run automatically before it installs / updates the openaps toolkit.The text was updated successfully, but these errors were encountered: