-
Notifications
You must be signed in to change notification settings - Fork 27
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
apt: remove deprecated piuparts stuff #457
Conversation
checking piuparts failure... |
* xenial (16.04LTS) was already reached EOL. * do not skip piuparts for jammy (22.04) * use recent gnupg (old version is used for xenial, no need to do so) * remove unused bionic configuration * fix key verification failure of keyring path * remove unused --keyring option from piuparts Signed-off-by: Kentaro Hayashi <[email protected]>
There is no need to do so. Signed-off-by: Kentaro Hayashi <[email protected]>
Signed-off-by: Kentaro Hayashi <[email protected]>
No need to use gpg1 (Already dropped Xenial 16.04) Signed-off-by: Kentaro Hayashi <[email protected]>
path of keyring is passed to piuparts, so use it. Signed-off-by: Kentaro Hayashi <[email protected]>
Signed-off-by: Kentaro Hayashi <[email protected]>
rerun failed job. |
failure seems reproducible, check it... |
Checking with local bullseye container, piuparts succeeds. 🤔
|
It seems that as if no --priviledged is specified, but it is not true for bullseye.
|
It has nothing to do with piuparts error, it is reproducible on local environment. |
Observed different error with:
|
The above failure is caused by the fallback of missing access to bullseye/contrib. 🤔 |
Signed-off-by: Kentaro Hayashi <[email protected]>
--keyring is used to bootstrap chroot image. Signed-off-by: Kentaro Hayashi <[email protected]>
Signed-off-by: Kentaro Hayashi <[email protected]>
Signed-off-by: Kentaro Hayashi <[email protected]>
Thanks! |
need to do so)