Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Create a branch dedicated to builds of ArcticDB against libevent 2.1.10 #64

Merged
merged 7 commits into from
Sep 26, 2023

Conversation

jjerphan
Copy link
Member

@jjerphan jjerphan commented Sep 25, 2023

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

Context

Builds of ArcticDB against libevent 2.1.10 are currently needed by some users of ArcticDB. On main,there is a build variant configuration to build ArcticDB against libevent 2.1.10 and libevent 2.1.12, but this causes several problems for conda-forge (see #60 for an overview of them).

This PR (which aims at starting the maintenance of another branch named libevent-2.1.10) would unlock conda-forge's migration bot as mentioned by @h-vetinari in #60 (comment). Once it is merged, libevent can be unpinned from the configuration.

The channel will remain the default and ArcticDB will continue to be installable as it is actually the case with, that is with:

mamba install -c conda-forge arcticdb

This solution is courtesy of @jamesmunro, and was mentioned to be effective by @h-vetinari in discussions we had.

Since those builds are going to be uploaded on a dedicated channel, I am not updating the build number (it could be reset to 0), but I prefer to keep it in sync with the one on main. We will then need to update main and this new libevent-2.1.10 branch synchronously.

@h-vetinari: can you explicitly approve this PR if this resolves the afore-referenced problem? Thank you.

Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
@conda-forge-webservices
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@jjerphan
Copy link
Member Author

@conda-forge-admin, please rerender

conda-forge-webservices[bot] and others added 2 commits September 25, 2023 07:07
See: conda-forge#61 (comment)

Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
@jjerphan
Copy link
Member Author

@conda-forge-admin, please rerender

Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
Co-authored-by: h-vetinari <h-vetinari@users.noreply.github.com>
@jjerphan
Copy link
Member Author

@conda-forge-admin, please rerender

@jjerphan jjerphan requested a review from h-vetinari September 26, 2023 13:19
@jjerphan jjerphan changed the title Create a dedicated conda-forge channel for builds against libevent 2.1.10 Create a branch dedicated to builds of ArcticDB against libevent 2.1.10 Sep 26, 2023
@JohanMabille JohanMabille merged commit cee139d into conda-forge:libevent-2.1.10 Sep 26, 2023
@jjerphan jjerphan deleted the libevent-2.1.10 branch September 26, 2023 13:50
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants