Ran into a snag installing on Raspbian 8

Question

Ran into a snag installing on Raspbian 8

Closed this issue 5 years ago · 35 comments

I had the previous Weather.com version running for years. For some reason, the Weather.com API is no longer working, so I looked for an alternative.

Found this app developed by the developer of my previous app, so I gave it a try.

I followed instructions and the install died

I see quite a few notices that the app is intended to run on Raspbian 10. I have Raspbian 8. So maybe that is my problem.

Probably not a bug, but I can't seem to change the "bug" label

ronstar2820 commented 5 years ago

Will do!

Answer 1 · 2020-01-26T17:52:45.000Z

I’ll take a look today. I think the last line of output in your screenshot may be key.

_{Sent with GitHawk}

Answer 2 · 2020-01-26T20:05:31.000Z

I am going to check a couple of things on my side but I also have a question for you: do you have a need to stay on Raspbian 8 or are you game to upgrade? Personally, I have done the in-place upgrades and had good success.

Answer 3 · 2020-01-26T20:17:13.000Z

Thanks for the quick response! I just formatted my card and did a fresh install of Raspbian 10. I'll report back my findings.

Answer 4 · 2020-01-26T20:18:30.000Z

👍 Please do let me know how it goes because I do want to make sure that this works on current versions of Raspbian.

Answer 5 · 2020-01-26T20:54:46.000Z

Ok. Everything finished, but no service started on it's own. So I did "sudo systemctl status PiWeatherRock" and got the screenshot below. Also typed sudo python weather.py and got the other screenshot. Looks like weather.py can't find a module named "darksky"

Answer 6 · 2020-01-26T20:57:14.000Z

I think I know what is up... I should be able to post something back in about 10 or 15 minutes

Answer 7 · 2020-01-26T20:58:16.000Z

Thanks!

…

On Jan 26, 2020, at 2:57 PM, Gene Liverman ***@***.***> wrote: I think I know what is up... I should be able to post something back in about 10 or 15 minutes — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=AOL63UOGL2GYPC5U7MV5YUDQ7X2KVA5CNFSM4KLUXLM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ55WKA#issuecomment-578542376>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOL63UIHDJD3SVBF2IO4VWLQ7X2KVANCNFSM4KLUXLMQ>.

Answer 8 · 2020-01-26T21:18:36.000Z

I have the issue figured out, about to push an update.

Answer 9 · 2020-01-26T21:29:41.000Z

@ronstar2820 - would you mind running the following commands for me to validate the fix?

$ cd ~/PiWeatherRock
$ git checkout fix_pyhton
$ sudo puppet apply /home/pi/PiWeatherRock/setup.pp

The branch I am asking you to try has the following changes:

diff --git a/setup.pp b/setup.pp
index 5a1f0a4..f7181e4 100644
--- a/setup.pp
+++ b/setup.pp
@@ -83,10 +83,9 @@ vcsrepo { '/home/pi/PiWeatherRock':
 }

 python::requirements { '/home/pi/PiWeatherRock/requirements.txt':
-  virtualenv   => '/home/pi/PiWeatherRock',
   pip_provider => 'pip3',
-  owner        => 'pi',
-  group        => 'pi',
+  owner        => 'root',
+  group        => 'root',
   cwd          => '/home/pi/PiWeatherRock',
   require      => [
     Package[ $main_packages, $piweatherrock_packages, ],

Once you have run the commands, I suggest you go ahead and switch back to master by running git checkout master.

Answer 10 · 2020-01-26T21:36:08.000Z

BTW, for manual testing outside of systemd you will want to use python3 instead of python

Answer 11 · 2020-01-26T21:50:33.000Z

I'm a novice at this and don't understand what you mean by python3 vs python.

Don't I just enter these commands on terminal?

Is the second line supposed to be "python" or "pyhton"

In either case I get "error: pathspec 'fix_python' did not match any file(s) known to git"

Answer 12 · 2020-01-26T21:54:30.000Z

Oops, sorry about the assumptions!

So, you have two commands on your system: python runs Python version 2 whereas python3 runs Python version 3. I am only testing against the latter since Python 2 is now end of life.

In your terminal, you will first need to run git fetch and then the git checkout fix_python should work. Yes, the command above was a typo too.

Answer 13 · 2020-01-26T21:57:03.000Z

I get "Error: cannot open .git/FETCH HEAD: Permission denied" when I type git fetch on the terminal

Answer 14 · 2020-01-26T21:58:06.000Z

What does ls -la show?

_{Sent with GitHawk}

Answer 15 · 2020-01-26T22:01:17.000Z

and a few more files if I scroll more

Answer 16 · 2020-01-26T22:02:09.000Z

Does git pull work?

_{Sent with GitHawk}

Answer 17 · 2020-01-26T22:03:24.000Z

No - I get "error: cannot open .git?/FETCH HEAD: Permission Denied"

Answer 18 · 2020-01-26T22:05:09.000Z

It is acting like sudo got used somewhere... let me get back to you shortly.

_{Sent with GitHawk}

Answer 19 · 2020-01-26T22:31:31.000Z

I think I see the flaw in my approach to fixing the issue and why it’s causing problems. I should be able to resolve it tonight

_{Sent with GitHawk}

Answer 20 · 2020-01-26T22:33:43.000Z

Thanks! It’s no problem for me to start from scratch if need be. Whatever I can do to help make it easier for you.

…

On Jan 26, 2020, at 4:31 PM, Gene Liverman ***@***.***> wrote: I think I see the flaw in my approach to fixing the issue and why it’s causing problems. I should be able to resolve it tonight Sent with GitHawk <http://githawk.com/> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=AOL63ULMI6C5GGLH7E6BPF3Q7YFMHA5CNFSM4KLUXLM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ57THQ#issuecomment-578550174>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOL63UINRNDJQYSBTEL4YBDQ7YFMHANCNFSM4KLUXLMQ>.

Answer 21 · 2020-01-26T22:34:23.000Z

Much appreciated

_{Sent with GitHawk}

Answer 22 · 2020-01-27T00:08:37.000Z

FYI: I started a Gitter for this project to facilitate real time chats too. I’ll be in there a little later. https://gitter.im/PiWeatherRock/community

_{Sent with GitHawk}

Answer 23 · 2020-01-27T02:35:07.000Z

@ronstar2820 if #20 doesn't actually fix your issue feel free to reopen this.

Answer 24 · 2020-01-27T02:35:55.000Z

Thanks - I’m giving it a try now

…

On Jan 26, 2020, at 8:35 PM, Gene Liverman ***@***.***> wrote: @ronstar2820 <https://github.com/ronstar2820> if #20 <#20> doesn't actually fix your issue feel free to reopen this. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=AOL63UIQPSHBQUMSCQEY4WLQ7ZB53A5CNFSM4KLUXLM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ6FJJY#issuecomment-578573479>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOL63UK6XTHGMP56XOK7IY3Q7ZB53ANCNFSM4KLUXLMQ>.

Answer 25 · 2020-01-27T03:01:04.000Z

Still the same situation. Ran install. Service doesn't startup. Checked status and get same screenshot as above and same error running weather.py where it can't find module darksky

Answer 26 · 2020-01-27T03:26:34.000Z

Would you humor me and try the new update section of the readme?

_{Sent with GitHawk}

Answer 27 · 2020-01-27T03:31:07.000Z

Thanks - This is going to take a while. Since it didn’t work after your fix, I erased everything in PiWeatherRock. But I couldnt totally get rid of the directory, so I started again using PiWeatherRock2 Anyway, I’ll keep plugging

…

On Jan 26, 2020, at 9:26 PM, Gene Liverman ***@***.***> wrote: Would you humor me and try the new update section of the readme? Sent with GitHawk <http://githawk.com/> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=AOL63UNF6EBI5L3DRI5TQILQ7ZH6VA5CNFSM4KLUXLM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ6G2CQ#issuecomment-578579722>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOL63UOTI6F6NI7EZ5AU6DDQ7ZH6VANCNFSM4KLUXLMQ>.

Answer 28 · 2020-01-27T03:32:52.000Z

You can kill the entire directory by running sudo rm -rf /home/pi/PiWeatherRock

_{Sent with GitHawk}

Answer 29 · 2020-01-27T03:37:23.000Z

Thanks! I’ll start over with a fresh PiWeatherRock

…

On Jan 26, 2020, at 9:32 PM, Gene Liverman ***@***.***> wrote: You can kill the entire directory by running sudo rm -rf /home/pi/PiWeatherRock Sent with GitHawk <http://githawk.com/> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=AOL63UIZRFNRMKZZRSNDJUDQ7ZIWJA5CNFSM4KLUXLM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ6G7YY#issuecomment-578580451>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOL63ULLJM66GBHEJFQEVN3Q7ZIWJANCNFSM4KLUXLMQ>.

Answer 30 · 2020-01-27T04:20:07.000Z

Nope - still doesn't work. Same situation as before - same as above screenshots. Tried the update section of the readme. I get "no such file or directory" when I type "pi@rock:~/PiWeatherRock $ git pull"

Answer 31 · 2020-01-27T04:21:38.000Z

Did you type git pull while inside your PiWeatherRock folder?

_{Sent with GitHawk}

Answer 32 · 2020-01-27T04:22:36.000Z

yes and no. I’ve tried it both ways

…

On Jan 26, 2020, at 10:21 PM, Gene Liverman ***@***.***> wrote: Did you type git pull while inside your PiWeatherRock folder? Sent with GitHawk <http://githawk.com/> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#18?email_source=notifications&email_token=AOL63UNIVTNSFQZZEMDWKCLQ7ZONFA5CNFSM4KLUXLM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ6IPAI#issuecomment-578586497>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOL63UO6JPJMPYFUJBSPFOTQ7ZONFANCNFSM4KLUXLMQ>.

Answer 33 · 2020-01-27T04:23:48.000Z

Mind continuing this via Gitter?

_{Sent with GitHawk}

Answer 34 · 2020-01-27T04:51:46.000Z

We figured out via Gitter that he issue was the api key needed to have single quotes around it.

_{Sent with GitHawk}