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

Support for signed repos #9

Open
Frzk opened this issue Apr 26, 2024 · 3 comments
Open

Support for signed repos #9

Frzk opened this issue Apr 26, 2024 · 3 comments

Comments

@Frzk
Copy link

Frzk commented Apr 26, 2024

The buildpack currently allows to add a repo, but there's no easy way to add a signed repo.
Since these are more and more widespread, it would be nice to support them too.

@EtienneM
Copy link
Member

EtienneM commented Oct 8, 2024

There is currently a workaround for this. One can add trusted=yes when adding a repository in order to automatically trust he repository. For example:

:repo:deb [trusted=yes] https://cli.github.com/packages stable main

This still leads to a warning in the deployment logs:

W: GPG error: https://cli.github.com/packages stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 23F3D4EA75716059

But the repository is still usable.

@EtienneM
Copy link
Member

EtienneM commented Oct 8, 2024

In case we actually want to support the public key, here is a comment from someone who implemented it in a fork: heroku#98 (comment)

@Frzk
Copy link
Author

Frzk commented Oct 8, 2024

🤯 🤯 🤯
I've never heard about such an option.
We should really document it (at least).

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

2 participants