You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
APT repositories should have a release file with properties decribing them.
apt.corretto.aws
repository hasOrigin
andLabel
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 asLabel
.Having
. stable
doesn't allow proper disambiguation when adding the repository to something like unattended-upgrades.The text was updated successfully, but these errors were encountered: