potiuk commented on PR #32004: URL: https://github.com/apache/airflow/pull/32004#issuecomment-1789856336
BTW. Yes. i think it's about enough time after bookworm was released (more than year) to get all the "other" software to catch up already (without us loosing time on it). As mentioneed before, we were not in a hurry because Bullseye will be supported from July 2024 to 2026 as part of Debian LTS, but we should definitely look closely to switching. And 2.8.0 might be the first time to support it. However I would very much like to do it like we did with `buster-> bullseye` switch - see release notes for 2.3 and 2.4 in our docker image changelog: https://airflow.apache.org/docs/docker-stack/changelog.html#airflow-2-4 We switched CI to bullseye by default in 2.3 (buster was deprecated) but we still continued to build buster (just build) in CI until 2.4 - and users could choose buster or bullsee by a flag in breeze or choosing buster or bullseye as base image (breeze flag was doing exactly this - switched the base image). Only in 2.4 we dropped buster. This means that once we figure out the right changes to get bookworm working, we should bring them to the code eventually as conditional code (they will slightly differ). This is for example why currently "Build CI image" job fails - because the code in "main" will pass buster image as the base image and it misses gcc11-dev dependency. Also it means that we have to add extra job to at least build bullseye in CI - or maybe at least a subset of tests to run on bullseye still. But we can do it as next step. For now let's make the `main` build succeed for @raphaelauv and then we figure out next steps. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
