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

gpg: no valid OpenPGP data found. #207

Closed
cedws opened this issue Apr 27, 2018 · 5 comments
Closed

gpg: no valid OpenPGP data found. #207

cedws opened this issue Apr 27, 2018 · 5 comments

Comments

@cedws
Copy link

cedws commented Apr 27, 2018

Reporter info

NAME="Ubuntu"
VERSION="17.10 (Artful Aardvark)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 17.10"
VERSION_ID="17.10"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=artful
UBUNTU_CODENAME=artful

Issue/Bug Description
On the distinst branch, I have executed deps.sh and then make to begin the build. The process will run, but fails after a while with:

gpg: no valid OpenPGP data found.
mk/chroot.mk:23: recipe for target 'build/pop-os/18.04/chroot' failed
make: *** [build/pop-os/18.04/chroot] Error 2

Expected behavior
The ISO should finish building and be available in the build directory.

Other Notes
Contents of build/pop-os/18.04/ is chroot.partial and debootstrap. After the initial (failing) build, running buildchain.sh gives me the same error message mentioned above. This leads me to believe that the very last part of the process is failing. I also getting the error on the master branch.

Thanks!

@mmstick
Copy link
Member

mmstick commented Apr 28, 2018

Make sure you've done this:

mmstick:/mnt/data/Sources/iso# gpg --recv-keys 204DD8AEC33A7AFF
gpg: key 204DD8AEC33A7AFF: public key "Pop OS (ISO Signing Key) <[email protected]>" imported
gpg: Total number processed: 1
gpg:               imported: 1

You will also need to have have uploaded your own GPG key to a keyserver (ie: keyserver.ubuntu.com).

gpg --full-generate-key
gpg --send-keys --keyserver keyserver.ubuntu.com ${YOUR_KEY_ID_HERE}

Then I've been running:

env GPG_NAME=${YOUR_KEY_ID_HERE} make

@cedws
Copy link
Author

cedws commented Apr 28, 2018

@mmstick Worked, thanks. Getting another issue now which I will open shortly.
As for this issue, could we add this information to the README? I had a look around to see if this was documented anywhere but couldn't find anything. I'd be happy to submit a PR.

@mmstick
Copy link
Member

mmstick commented Apr 28, 2018

The instructions exist within the readme for the distinst branch

@cedws
Copy link
Author

cedws commented Apr 29, 2018

@mmstick Ah, did not see that. They don't seem to be mentioned in the README on master though. Is it worth adding it in there, or is the distinst branch going to be merged sometime soon?

@jackpot51
Copy link
Member

Yes, the distinst branch is used to build 18.04, so it will be merged soon

@cedws cedws closed this as completed Apr 29, 2018
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