-
Notifications
You must be signed in to change notification settings - Fork 340
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
Does this support adding a ppa using gpg? #98
Comments
Finally got a chance to research my problems here. From what I've learned in the code, I see now how it grabs ascii armored keys and stores them. It seems, though, in my case, the key is only available as the unarmored binary. |
@rschwiebert do you mind elaborating? |
Once I figured out that souffle had a (not easily discovered) direct link I could use in the Aptfile, I found that I could use this. Otherwise I would not have known how to accomplish what is done in the grey box at the top. |
For any future reader here's what I did to install libraries using a gpg keyring. I didn't make it generic since I changed my approach and no longer needed this. In your fork's compile script before the repos are parsed, pull the keyring down for the package you need. This one is for tailscale. I put it in topic "Add tailscale keyring"
# Add Tailscale's GPG key
mkdir -p --mode=0755 /app/share/keyrings
curl -fsSL https://pkgs.tailscale.com/stable/ubuntu/jammy.noarmor.gpg | tee /app/share/keyrings/tailscale-archive-keyring.gpg >/dev/null
Since we're putting the response into a specific file, we can't use the listed package. https://pkgs.tailscale.com/stable/ubuntu/jammy.tailscale-keyring.list Click this link and you'll find
The This means that our Aptfile needs to include the following line:
Where /app/share/keyrings/tailscale-archive-keyring.gpg matches the earlier filepath in the |
What I'd like to do is install
souffle
on my node. Following thesouffle
docs, one would do this:I haven't been able to find any examples of Aptfiles that seem to reflect this situation. Advice? Thanks in advance...
The text was updated successfully, but these errors were encountered: