[
https://issues.apache.org/jira/browse/KAFKA-18342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-18342.
------------------------------------
Fix Version/s: 4.0.0
3.9.1
3.8.2
Resolution: Fixed
trunk:
https://github.com/apache/kafka/commit/a940d520703c133e964f13d2ec864a78972978b3
4.0:
https://github.com/apache/kafka/commit/60b646c70cd3500a237abc65a2bd971329acc2ea
3.9:
https://github.com/apache/kafka/commit/430892654bcf45d644e66b532d83aab0f569cb7d
3.8:
https://github.com/apache/kafka/commit/77712d521865a1c5b70c4909b98db8c58404709b
> Vagrantfile can't work with ruby 3.2
> ------------------------------------
>
> Key: KAFKA-18342
> URL: https://issues.apache.org/jira/browse/KAFKA-18342
> Project: Kafka
> Issue Type: Bug
> Reporter: Chia-Ping Tsai
> Assignee: Jhen-Yung Hsu
> Priority: Major
> Fix For: 4.0.0, 3.9.1, 3.8.2
>
>
> `File.exists` was removed from ruby 3.2 [0], and the newest vagrant could use
> ruby 3.2 and 3.3 [1]. Hence, we should ensure Vagrantfile[2] can work with
> ruby 3.2+
> [0]
> https://github.com/ruby/ruby/commit/bf97415c02b11a8949f715431aca9eeb6311add2
> [1] https://github.com/hashicorp/vagrant/blob/main/vagrant.gemspec#L15
> [2] https://github.com/apache/kafka/blob/trunk/Vagrantfile#L62
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
