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

Incorrect properties for apt.corretto.aws repository #29

Open
orazioedoardo opened this issue Nov 22, 2023 · 3 comments
Open

Incorrect properties for apt.corretto.aws repository #29

orazioedoardo opened this issue Nov 22, 2023 · 3 comments

Comments

@orazioedoardo
Copy link

APT repositories should have a release file with properties decribing them.

apt.corretto.aws repository has Origin and Label properties as . stable which look like typos and/or placeholder values.

This can be seen by running apt-cache policy or by downloading the Release file.

Sensible values may be Amazon as Origin and Corretto as Label.

Having . stable doesn't allow proper disambiguation when adding the repository to something like unattended-upgrades.

Origin: . stable
Label: . stable
Suite: stable
Codename: stable
Date: Tue, 17 Oct 2023 17:02:31 UTC
Architectures: amd64 arm64 i386
Components: main
Description: Generated by aptly

[...]
@lutkerd
Copy link
Contributor

lutkerd commented Nov 27, 2023

Thanks for reporting this, we will look at changing those fields and ensuring we don't breaking any existing customers in the process.

@lutkerd
Copy link
Contributor

lutkerd commented Nov 27, 2023

We looked into this a bit and changing the Origin value would cause apt update to prompt for a y/n in an interactive shell or fail. This could break existing customers workflows and block critical security patches from getting installed.
You can find similar instances of this being reported and worked around:

@orazioedoardo
Copy link
Author

We looked into this a bit and changing the Origin value would cause apt update to prompt for a y/n in an interactive shell or fail. This could break existing customers workflows and block critical security patches from getting installed.

Well this would be terrible. By looking at the Debian repository format seems that one (ugly) way to get out of it would be to host a second Release file like https://apt.corretto.aws/dists/debian/Release, linking the debian folder to stable and adding the repo to the system as deb […] https://apt.corretto.aws debian main.

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