-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[BUG] pwnagotchi image can't be built #1115
Comments
just tried to build using your fork and makefix branch, fork/exec /tmp/packer-plugin-3560001340.zip: permission denied Are you also stuck on that? |
I haven't quite worked out what causes that issue yet, but if you rerun the makefile with sudo (i.e. |
anyways i seemingly fixed everything.. building now, going without any issues, fixed re4son keys also, will push my work to github a bit later |
anyways i can confirm, i fully fixed builds and kernel keys, you can check my fork |
Tryed Building with your fork, i get a warning and it fails:
here is the failure:
|
Two things:
|
The issues are mainly that the versions of programs like Go, Packer and the like are so outdated that the newer programs that depend on them can't be built using them. You have to manually download newer versions from the websites via wget and install them in order to use them. On top of that, it seems that Packer was deliberately sabotaged as it includes scripts in the JSON that require sudo to run but won't work unless a separate bash script is used to run the commands. |
Describe the bug
It's currently impossible to build a pwnagotchi image due to a number of reasons:
apt-get update
to fail.To Reproduce
Steps to reproduce the behavior:
make image
Additional context
I recently started working on building a pwnagotchi but got a Waveshare v3 display. I saw that support for the display had been merged but that no pwnagotchi images have been released in over a year. I tried to build the image myself but kept running into issues.
I'm currently working on a fix for most of these. 👍
The text was updated successfully, but these errors were encountered: