-
Notifications
You must be signed in to change notification settings - Fork 968
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
chore: upgrade underlying debian version #11472
Conversation
Debian `stable` has moved from buster (10) to bullseye (11). Swapping out the underlying Debian version provides us with acces to newer package dependencies, specifically: gcc 8.3 => 10.2 Refs: https://www.debian.org/releases/bullseye/ Refs: https://www.debian.org/releases/bullseye/amd64/release-notes/ch-whats-new.en.html#newdistro Signed-off-by: Mike Fiedler <[email protected]>
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.
LGTM. Will wait for another warehouse dev who is actually involved in ops to merge though.
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.
Will let @ewdurbin merge this.
Interestingly this fails to build the image in cabotage (running on linux) but is fine locally for me (MacOS arm64). See imagemin/imagemin-gifsicle#37 (comment) Output from cabotage build:
|
Thanks for the fix - I guess this points out a weakness in the current CI steps, as they don't do the same thing as cabotage did, which is build the Docker image. Should the CI steps do that as well? |
Likely yes. When I can figure out what the difference is between the docker builds that causes this. It doesn't do much good to just run |
@ewdurbin I was trying this again, and can't seem to repro on a linux system, but I was running |
Debian `stable` has moved from buster (10) to bullseye (11). Swapping out the underlying Debian version provides us with acces to newer package dependencies, specifically: gcc 8.3 => 10.2 Refs: https://www.debian.org/releases/bullseye/ Refs: https://www.debian.org/releases/bullseye/amd64/release-notes/ch-whats-new.en.html#newdistro Signed-off-by: Mike Fiedler <[email protected]>
* Revert "Fix the production container build for new bullseye base images (pypi#11492)" This reverts commit 1671a69. * Revert "chore: upgrade underlying debian version (pypi#11472)" This reverts commit 8406057.
Circling back to this, I still haven't been able to reproduce the error observed. I'm inclined to try two actions here:
I'll open up a new PR and reference this one. |
As previously attempted in pypi#11472 and reverted in pypi#11493 After isolating the condition that was observed and removing the calls to compile `gifsicle` in pypi#12232, upgrade the `static` containers only with this changest. Signed-off-by: Mike Fiedler <[email protected]>
As previously attempted in #11472 and reverted in #11493 After isolating the condition that was observed and removing the calls to compile `gifsicle` in #12232, upgrade the `static` containers only with this changest. Signed-off-by: Mike Fiedler <[email protected]> Signed-off-by: Mike Fiedler <[email protected]>
Debian
stable
has moved from buster (10) to bullseye (11).Swapping out the underlying Debian version provides us with acces to
newer package dependencies, specifically: gcc 8.3 => 10.2
Refs: https://www.debian.org/releases/bullseye/
Refs: https://www.debian.org/releases/bullseye/amd64/release-notes/ch-whats-new.en.html#newdistro
Signed-off-by: Mike Fiedler [email protected]