Skip to content
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

RPI2 testing [closed] #3

Closed
technicalpyro opened this issue Feb 12, 2017 · 13 comments
Closed

RPI2 testing [closed] #3

technicalpyro opened this issue Feb 12, 2017 · 13 comments

Comments

@technicalpyro
Copy link
Contributor

was going to attempt my first PR but i either dont have it setup right or my account is not able either way here is the info i was attempting to add

| Raspberry Pi 2 | Raspbian Jessie | armv7l | arm-linux-gnueabihf | @Technicalpyro |

@dschaper
Copy link
Member

If you were trying to PR to make changes to an existing file, the easiest way is to fork the repo, make the changes on a local branch of your local repo and then submit a PR against the master branch. (Unless that is what you already tried to do, but creating a PR from a fork of the repo shouldn't require any permissions on the repo itself.)

@technicalpyro
Copy link
Contributor Author

ok will attempt that the tutorial that taught me how tried to get me to branch and not fork and thats probably the problem

@dschaper
Copy link
Member

Yes, non Pi-hole members do not have write access to the FTL repo branches, so you would need to fork to make any changes. I see now that you are adding to the README.md file, so that should be able to have a PR submitted against it.

@technicalpyro
Copy link
Contributor Author

ok kinda exhilarating for me a total non coder(i can troubleshoot just suck at writing it from scratch) even to be able to do something this small ... i know how sad i am lol

@dschaper
Copy link
Member

:) We all had to start at the beginning at one time or another.

@technicalpyro
Copy link
Contributor Author

so now another idiot question how would i change binaries ? im willing to do it just unsure how

@dschaper
Copy link
Member

Just download the other binary files and run them. Try passing on the debug flag along with the binary to see if there is any information passed along. ./pihole-FTL-arm-linux-gnueabi debug (after you chmod +x the file of course.)

@technicalpyro
Copy link
Contributor Author

may give it a shot tomorrow but right now its doing my head in ... im sure with fresh eyes i will be able to manage it

@technicalpyro
Copy link
Contributor Author

thinking testing the arm-linux-gnuabi might be a pipe dream for me i have not been successfully able to get any of the packages it requires nor have i been able to find any files within the project containing the files every time i attempt to install the packages i get an unable to install

@DL6ER
Copy link
Member

DL6ER commented Feb 12, 2017

I don't know what you mean, you can get the binaries here:

https://github.com/pi-hole/FTL/releases/tag/v0.2

Download (one of) them and make the file executable. There should be no need to install any system packages.

@technicalpyro
Copy link
Contributor Author

there we go i knew it was here somewhere think i was trying to get the tools used from apt-get not the actual binaries

@technicalpyro
Copy link
Contributor Author

SUCCESS you guys put up with me way too much but go it working and no error flags thrown modifying my local copy of the fork readme now

@technicalpyro technicalpyro changed the title RPI2 testing RPI2 testing [closed] Feb 12, 2017
@technicalpyro
Copy link
Contributor Author

closing because i learned what needed i love you guys

@Felisse Felisse mentioned this issue Jun 21, 2017
3 tasks
@TC1977 TC1977 mentioned this issue Sep 28, 2019
3 tasks
DL6ER pushed a commit that referenced this issue Oct 14, 2019
Add more parameters to `/stats/history`
@jens1205 jens1205 mentioned this issue Dec 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants