-
Notifications
You must be signed in to change notification settings - Fork 30
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
gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation #19
Comments
and you tried with no modifications or additions at all? What was your make string? did you move any plugins around at all? |
I used sudo make REPO=Ubuntu for rpi3.I added gnupg to the packages list so that error is resolved. |
Ubuntu is not current supported, it's as the docs state "Ubuntu repository (Yakkety/Zesty only since no rpi support before that and currently rpi2 only)" |
I got the same error when in run the following command on windows 10 git-bash |
oh I have no idea using windows. I can't even try to support that, I have no windows machines around at all to even attempt to try to fix it. I'm open to PRs to fix it sadly otherwise I have to say it's unsupported. Unless you are also trying ubuntu which still isn't supported. |
As answered in https://stackoverflow.com/questions/50757647/e-gnupg-gnupg2-and-gnupg1-do-not-seem-to-be-installed-but-one-of-them-is-requ Try |
Hello
I'm trying to build image following all the instructions but I get this error,
gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
Setting up systemd-sysv (235-3) ...
Setting up init (1.51) ...
Processing triggers for libc-bin (2.25-3) ...
E: gnupg, gnupg2 and gnupg1 do not seem to be installed, but one of them is required for this operation
rootfs.mak:112: recipe for target '/root/rpi-img-builder/rootfs' failed
make[1]: *** [/root/rpi-img-builder/rootfs] Error 255
Makefile:21: recipe for target 'build-rootfs' failed
make: *** [build-rootfs] Error 2
Any help will be appreciated!
The text was updated successfully, but these errors were encountered: