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
Executing "step_script" stage of the job scriptUsing docker image sha256:662c05203bab4c59568d24689fa5c3955439360a35c483178598d226b9a5ad10 for debian:stretch with digest debian@sha256:c5c5200ff1e9c73ffbf188b4a67eb1c91531b644856b4aefe86a58d2f0cb05be ...
$ apt-get update -qqW: The repository 'http://deb.debian.org/debian stretch Release' does not have a Release file.W: The repository 'http://deb.debian.org/debian stretch-updates Release' does not have a Release file.W: The repository 'http://security.debian.org/debian-security stretch/updates Release' does not have a Release file.E: Failed to fetch http://deb.debian.org/debian/dists/stretch/main/binary-amd64/Packages 404 Not Found [IP: 146.75.38.132 80]E: Failed to fetch http://deb.debian.org/debian/dists/stretch-updates/main/binary-amd64/Packages 404 Not Found [IP: 146.75.38.132 80]E: Failed to fetch http://security.debian.org/debian-security/dists/stretch/updates/main/binary-amd64/Packages 404 Not Found [IP: 151.101.130.132 80]E: Some index files failed to download. They have been ignored, or old ones used instead.
Updating the image from debian:stretch (Debian 9) to debian:buster (Debian
10) works, though it could be useful to keep the same older image to check that
firejail can still be built with the same older toolchains.
The text was updated successfully, but these errors were encountered:
Log from
build_debian_package
:https://gitlab.com/Firejail/firejail_ci/-/jobs/4195782936:
Updating the image from
debian:stretch
(Debian 9) todebian:buster
(Debian10) works, though it could be useful to keep the same older image to check that
firejail can still be built with the same older toolchains.
The text was updated successfully, but these errors were encountered: