Legacy CMake issue

[realratchet]

Hello,

We are currently using the legacy client version 3.2.7 in some of our legacy projects. Following the release of CMake 4.0.0 on March 28th, we encountered an issue where couchbase==3.2.7 is no longer buildable due to the weak CMake requirement and unfortunately python build tools ignore top level build tool requirements.

I understand this may be a bit of a long shot, but would it be possible to consider cherry-picking this fix from this commit and releasing a 3.2.8 version?

While we've managed to resolve this issue internally, we believe this fix could be helpful for others who may still be facing the same issue.

I attempted to create a pull request, but it seems that GitHub doesn't allow pull requests from forks into non-base branches.

Thank you for your time and consideration!

[puerile22]

Could you share how you resolved this issue? I'm facing the same issue currently and haven't found a solution yet.

[realratchet]

Mostly following the comment in OP:

1. Downloaded the .tar.gz file from PyPI.
2. Extracted the archive.
3. Modified the toml file based on the commit link.
4. Repackaged it into a .tar.gz file.
5. Uploaded it to a private GitLab repository.
6. Installed it from the private package repository instead.

Alternatively, you can install directly from the .tar.gz file if you prefer not to upload it to a package repository.

Edit: Formatted the text because I was previously replying from a phone.

[thejcfactor]

HI @puerile22 / @realratchet -- I will need to ask around, but I don't know if a change to an EOL version (see EOL policy) will be possible.

Could you try the following work-around:

• Prior to installing the Couchbase Python SDK, install a version of CMake < 4.0 from PyPI: python -m pip cmake==3.31.6
• When installing the Couchbase SDK do python -m pip install couchbase==3.2.7 --no-build-isolation (the no-build-isolation is needed in order to pick up the previously installed cmake version)

Out of curiosity, what are the reasons holding you back from upgrading to the 4.x version of the SDK?

[realratchet]

Poetry does not respect project level build settings when installing packages and pip is not applicable. New SDK is not compatible with this legacy project we're attempting to deprecate. As I've said we've solved it on our end but the way it's configured right now makes the wheel unbuildable for anyone else that still depends on it too.