Skip to content
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

build: do not support c-ares >= 1.33 #2473

Merged
merged 1 commit into from
Oct 7, 2024

Conversation

tchaikov
Copy link
Contributor

@tchaikov tchaikov commented Oct 5, 2024

we don't support c-ares 1.33 yet. so error out when c-ares >= 1.33 is detected.

Refs #2472

we don't support c-ares >= 1.33 yet. so error out when c-ares >= 1.33 is
detected.

Refs scylladb#2472

Signed-off-by: Kefu Chai <[email protected]>
@tchaikov tchaikov force-pushed the incompatible-with-c-ares-1.33 branch from 9d4efcc to a8850ac Compare October 5, 2024 05:51
@tchaikov
Copy link
Contributor Author

tchaikov commented Oct 5, 2024

@elcallio hi Calle, could you help review this change?

@elcallio
Copy link
Contributor

elcallio commented Oct 7, 2024

Looks ok to me, but I thought we still built c-ares as a submodule to seastar, based on our fork?

@tchaikov
Copy link
Contributor Author

tchaikov commented Oct 7, 2024

hi Calle, thank you for your review. the c-ares submodule was dropped in 8d99e3c .

@tchaikov
Copy link
Contributor Author

tchaikov commented Oct 7, 2024

@scylladb/seastar-maint hello maintainers, could you help merge this change?

@avikivity
Copy link
Member

What's wrong with c-ares 1.33?

@tchaikov
Copy link
Contributor Author

tchaikov commented Oct 7, 2024

@avikivity please see #2472

@avikivity avikivity merged commit 972258f into scylladb:master Oct 7, 2024
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants