-
Notifications
You must be signed in to change notification settings - Fork 131
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
no longer seems to install on raspberry pi 3 #95
Comments
I've confirmed that installing the application manually works on the Pi3. |
Great, thanks Dan, funny thing is I just retried it and got exactly the same result. pi@raspberrypi:~ $ dpkg-buildpackage -us -uc -i && sudo dpkg -i ../pi-blaster*.deb tail: cannot open 'debian/changelog' for reading: No such file or directory Am I missing something that's obvious to linux regulars here? do i need to be in a specific directory or something? |
I followed the manual installation steps (compiling from source, NOT creating a *.deb) on the latest Raspbian. To do this, clone the repository down (or download the zip and unzip it somewhere on your Pi), and follow the instructions under https://github.com/sarfata/pi-blaster#build-and-install-directly-from-source. |
ok Dan. I got it to work using that method. Still doesn't address that fact that the other technique is maybe out of date, but i'm good for now so moving on. |
Can we close this issue now? |
Well I would suggest an update to the documentation noting that the dpkg instructions may not work on a pi 3b and to try building from source if that's the case, just in case anyone comes after me with the same problem. other than that, I've got no problem with closing the issue. thanks for your help |
having trouble installing this on a raspberry pi 3.
I've been trying the dpkg instructions in the readme. The first command appears to work fine, but this one:
pi@raspberrypi:~/go/src $ dpkg-buildpackage -us -uc -i && sudo dpkg -i ../pi-blaster*.deb
produces this error message.
tail: cannot open 'debian/changelog' for reading: No such file or directory
googling this error suggests that the debian folder was changed to debianpkg some time late in 2017.
see: FRRouting/frr#1485
is the install script out of date due to this change?
The text was updated successfully, but these errors were encountered: