-
Notifications
You must be signed in to change notification settings - Fork 341
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
Add support for specifying a custom key to be added to the trusted keys #41
base: master
Are you sure you want to change the base?
Conversation
b8be18d
to
7b924a7
Compare
I'm not sure if the tests will pass without resolving #16. |
Thanks for fixing this. Do we plan to merge it soon into master? I am using amiels repo for now |
any news on a merge into master? |
This has been open for over a year, are there plans to merge it? I'm using amiel's repo for now as well. |
This has been open for over two years now; I'm using amiel's repo as well eg. |
I resolved the conflicts in my fork: https://github.com/4ormat/heroku-buildpack-apt/tree/keys buildpack: |
I'd also like to see this. I've re-resolved the conflicts with the latest master in this fork: elkrange@6cb6822 (the only conflict was around the context with the |
@edmorley do you think there's a chance this would be accepted if conflicts were resolved? |
@dentarg Hi! I'm not against the idea of adding support for this (it seems useful), however:
|
Add a key with the following format: 🔑name:url For example: 🔑nginx:https://nginx.org/keys/nginx_signing.key 🔑confluent:http://packages.confluent.io/deb/4.1/archive.key Co-Authored-By: Grant Hollingworth <grant@antiflux.org> Thank you to @4ormat for helping resolve conflicts
7b924a7
to
bea88ab
Compare
Ok, I've pushed an updated branch, so this should be mergeable. Thanks to @granth for dealing with the conflicts, although I have not tested the conflict-resolved version. Is someone actively using this that could test it? |
This should resolve #33
Add a key with the following format:
For example:
I tested this with the following
Aptfile
(this is @catkhuu's example and the package I got stuck on without having a key):