Skip to content

action fails since bookworm release #606

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.

Sign up for GitHub

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

Jump to bottom
Closed
SvenStaehs opened this issue Jun 15, 2023 · 4 comments · Fixed by #605
Closed

action fails since bookworm release #606

SvenStaehs opened this issue Jun 15, 2023 · 4 comments · Fixed by #605
Labels
bug Something isn't working properly

Comments

@SvenStaehs
Copy link
Contributor

The problem

using the action, github first builds the Dockerfile, which references python:3.10 without any mention which version of debian to use. Debian 12 bookworm has been released recently, and a python:3.10-bookworm published, which is now used.
But the Dockerfile then tries to install git from bullseye-backports, which would downgrade the git package, resulting in the following errors, probably for every single user out there (unless there's some caching going on):

E: Packages were downgraded and -y was used without --allow-downgrades.
ERROR: failed to solve: process "/bin/sh -c echo "deb http://deb.debian.org/debian bullseye-backports main" >> /etc/apt/sources.list; apt-get update; apt-get install -y git/bullseye-backports" did not complete successfully: exit code: 100

Expected behavior

action should work

Additional context

proposed fix for now is to specify the version of debian to use by pinning to python:3.10-bullseye as base image.
Long-term you'll want to adopt python:3.11-bookworm, but that's a completely different matter.
@SvenStaehs SvenStaehs added the bug Something isn't working properly label Jun 15, 2023
@SvenStaehs SvenStaehs mentioned this issue Jun 15, 2023
Merged
@bernardcooke53
Copy link
Contributor

Thank you for spotting this @SvenStaehs , I will make a PR later today when at my computer unless someone can get to it first 👍

@SvenStaehs
Copy link
Contributor Author

Thank you for spotting this @SvenStaehs , I will make a PR later today when at my computer unless someone can get to it first 👍

Thanks, I already made one, just have to merge it 😉 #605

@bernardcooke53
Copy link
Contributor

Didn't see whoops 😂 commitlint failed with the same issue... it's gonna be a good day at the office

@SvenStaehs
Copy link
Contributor Author

Thanks for the quick solution! I think commitlint was complaining about the error message I included in the body being too wide... I had worried about that, but no idea how to include something like that differently. Probably just not the place for lengthy error messages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working properly
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: docker build fails installing git
2 participants
@bernardcooke53 @SvenStaehs