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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(debian): Pins Bullseye version for Debian #1657
Conversation
Your qeumu is probably out of date. That looks like a bug I filed and they fixed eventually |
Thank you Tim, I'm working with WSL2, and all my packages are up to date. 馃し |
I have the same error on Docker Desktop on macOS: it's related to the embeded |
Thank you Damien 馃 ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me so long as there is not too long a period until the merge of
Today the Debian versions are tracked by dependabot (as seen in #1651 and #1652). As far as I can tell, this will make it so that dependabot cannot track the Debian version.
I ran
BULLSEYE_TAG=20230522 JENKINS_VERSION=2.401.1 JENKINS_SHA=600b73eabf797852e39919541b84f7686ff601b97c77b44eb00843eb91c7dd6c make build-debian_slim_jdk11
and then checked that the older BULLSEYE_TAG value was used and that Jenkins 2.401.1 was placed in the container image.
The checks are ok for me: build + tests are ok. LGTM! |
Following #1655, I added a
BULLSEYE_TAG
ARG in the Dockerfiles and in the Docker bake file for Debian (regular/slim)*(11/17).Testing done
By the way, I had to comment out the platforms (except the
linux/amd64
) while testing because there is an issue when building forppc64le
on my machine. 馃しSubmitter checklist
Link to relevant issues in GitHub or JiraJust for your information, here is the faulty output for
ppc64le
when callingjlink
. I remember I had that also onaarch64
a while back.