Open PieterGit opened 4 years ago
Somehow 0.7.0 still seems to depend on some parts of openaps
. When running, the settings/profile.json
didn't get updated (and stayed 0 bytes). I will look into it later. Any help to fix this is welcome.
Tracked cause down on the import recurrent
statement from https://github.com/openaps/openaps-contrib/blob/master/openapscontrib/timezones/__init__.py#L132-L139
When I remove the recurrent
references I managed to do a succesfull install.
@scottleibrand : can you give some guidance on how to proceed with this issue? I thought openaps
was deprecated for 0.7.0, but I don't think the rig works without it at this moment.
@PieterGit Solution found for now - replace version of python package from 2.6 to 2.5 pip install parsedatetime==2.5
After running this, run again the installation, it finishes successfuly
@ekazum Could you explain to me how to replace version of python package from 2.7 to 2.5? I believe I'm seeing the 2.7 in my script, but could be wrong.
@yduncan Just run: pip install parsedatetime==2.5
It will replace the relevant package (not entire python, just one package in my case)
@yduncan Just run:
pip install parsedatetime==2.5
It will replace the relevant package (not entire python, just one package in my case)
Before running the bootstrap script? Or change it in the bootstrap?
Or it may have been in the setup script. I'm not that technical sorry.
@yduncan Just run: pip install parsedatetime==2.5 It will replace the relevant package (not entire python, just one package in my case)
Before running the bootstrap script? Or change it in the bootstrap?
Or it may have been in the setup script. I'm not that technical sorry.
@yduncan I was able to get up and running by running pip install parsedatetime==2.5 right after the first setup failed as noted. I ran oref0-setup again after the pip command and setup completed successfully.
I'm not sure that this is a common problem, so I wouldn't know whether this should result in updates to the oref0-setup script or not.
Happened to me. And the fix has worked in other scenarios. Though running the bootstrap on a clean flash I get in a loop. It fails with this error, I run the fix successfully, then when I run the bootstrap again it reverts the change before running into the error again.
Installing collected packages: parsedatetime
Found existing installation: parsedatetime 2.5
Uninstalling parsedatetime-2.5:
Successfully uninstalled parsedatetime-2.5
Successfully installed parsedatetime-2.6
Traceback (most recent call last):
File "/usr/local/bin/activate-global-python-argcomplete", line 23, in <module>
argcomplete.autocomplete(parser)
AttributeError: 'module' object has no attribute 'autocomplete'
Couldn't run activate-global-python-argcomplete
I was able to back out of my corner with a Jubilinux reflash, repeatedly rerun bootstrap (fails several times), and then apply the fix pip install parsedatetime==2.5
before I came to finally run install.
Submitted a PR that fixes this in dev.
Thanks. Merged it.
Just as a note, Doing a clean install on latest Raspberry Pi OS following documentation nets this same error still, and the above pip command gets past the error.
After switching to the dev branch of oref0, does this still happen? The fix has only been applied to the dev branch, and I installed 2 rigs this morning without encountering this issue.
I'm not saying there's not an issue. I'm trying to narrow down where the issue is.
Initially I thought I was (was passing dev to oref0-setup) but my loops are reporting they are up to date with Master, so I'm not on dev.
Sorry about that.
On Sat, Oct 3, 2020, 10:48 PM Sarah King notifications@github.com wrote:
After switching to the dev branch of oref0, does this still happen? The fix has only been applied to the dev branch, and I installed 2 rigs this morning without encountering this issue.
I'm not saying there's not an issue. I'm trying to
narrow down where the issue is.
-------- Original Message -------- On Oct 3, 2020, 8:21 PM, Cameron Chunn wrote:
Just as a note, Doing a clean install on latest Raspberry Pi OS following documentation nets this same error still, and the above pip command gets past the error.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/openaps/oref0/issues/1377#issuecomment-703197544, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACAC7BLKSP2KKNAJBO6UTLSI7WCTANCNFSM4NQI4D4Q .
Just got stuck with this for about 6 hours this evening. Really can this be merged into master as a priority please?
Are you saying you had this issue with master, but using dev fixed it, and are proposing we do a release of current dev to master to avoid issues for those not otherwise using dev?
@scottleibrand that's how I read it. 7.0 is due a patch release yeah? If I recall there are quite a few bug fixes.
@scottleibrand. I agree with @old-square-eyes
As i understand it, this remains an issue for installing Master on an Edison. I've put a small PR in the updating Master docs https://github.com/openaps/docs/pull/1563, but not in the main instructions for first time installation.
i can see that the rPi installation instructions were updated at the start of summer which directs users to load Dev. https://github.com/openaps/docs/pull/1547
And installing Dev on Edison works fine following https://github.com/openaps/oref0/pull/1387
@ekazum I had the same issue and was solved with the same command you have posted: pip install parsedatetime==2.5
I have a RPI Zero w/ Explorer HAT board and started the install from the instance curl -s https://raw.githubusercontent.com/openaps/oref0/master/bin/openaps-install.sh > /tmp/openaps-install.sh && bash /tmp/openaps-install.sh dev
Many thanks
Same issue on a Raspberry Pi 0 w/ Explorer HAT, fresh install of master, fixed by installing parsedatetime 2.5.
Same issue on a Raspberry Pi 3 + Explorer HAT, fresh install of master, fixed by installing parsedatetime 2.5.
Same issue after reflashing an Edison with Explorer. Found the solution in the Looped Facebook group, but nowhere in the OpenAPS docs.
Confirming that I ran into this issue as well with a rasberry pi + explorer hat on a fresh install. Using "pip install parsedatetime==2.5" I was able to complete installation. This was following the most recent OpenAPS documentation and using the dev branch.
Describe the bug Fresh install fails
oref0-setup
withAttributeError: 'module' object has no attribute 'Locale'
while importingdevice.json
.To Reproduce Steps to reproduce the behavior:
Expected behavior A succesfull install
Errors The install fails with
Setup Information (please complete the following information): Pump WW, CGM Dexcom G6 / oref 0.7.0-dev / rig Explorer board
Additional context Fresh install. Temporary workaround. disable:
do_openaps_import
statements fromoref0-setup.sh
Please tell me what the suggested route is to fix, and I'll create a PR.