Feature wish: compatibility with Debian bookworm

[petermkr]

Hello everyone,

I have just seen that many of the version thresholds in requirements/env_climada.yml were resolved for good.
Thanks for your great work!

For the team working on a containerized version of CLIMADA, this is great news as we will be able to get rid of manual compilation of libraries (e.g. proj) and reduce our build times considerably.

The official Python docker image (https://hub.docker.com/_/python/) is based on the currently stable Debian release. A new release 'bookworm' was released just some weeks ago, remaining in place for two years. It ships with the following library versions:

• gdal 3.6.2+dfsg-1+b
• proj 9.1.1-1+b1
• eccodes 2.28.0-1

Meanwhile, the current version thresholds in CLIMADA develop are:

• gdal>=3.6
• proj>=9.1
• eccodes>=2.27,<2.28

So this means that there could be full alignment if #678 were resolved which would be awesome!

My question is the following:
Do you think that it could be feasible to keep the alignment for these dependencies in place for as long as possible, ideally 1.5 years until the next Debian base image version is already appearing on the horizon and an upgrade of these dependencies can be planned and coordinated together?

It's completely clear that there could be very good reasons to upgrade these dependencies before that, I just wanted to drag the focus to the current situation which is very beneficial for the container team so that it could last for as long as reasonable.

Thanks in advance! Peter

[peanutfun]

Thank you for your input, @petermkr! As this is not urgent and a rather convoluted topic, I'll take the liberty to move this to the Discussions