From Fedora Project Wiki
< Changes
(Initial proposal. (WIP)) |
(Fill out more things, add side-tag) |
||
| Line 46: | Line 46: | ||
Update the main Vagrant package to version 2.3.4 to bring the latest bug fixes and new features as well as update mentioned rubygem-net-* packages required for Vagrant runtime. | Update the main Vagrant package to version 2.3.4 to bring the latest bug fixes and new features as well as update mentioned rubygem-net-* packages required for Vagrant runtime. | ||
Due to the new rubygem-net-ssh, the updates for mentioned packages will be built and delivered as one unit via the side tag "f39-build-side-67362". | |||
== Feedback == | == Feedback == | ||
| Line 60: | Line 60: | ||
== Scope == | == Scope == | ||
* Proposal owners: | * Proposal owners: | ||
* Review and merge pull requests for components: | |||
* rubygem-net-ssh: https://src.fedoraproject.org/rpms/rubygem-net-ssh/pull-request/14 | |||
* rubygem-net-scp: https://src.fedoraproject.org/rpms/rubygem-net-scp/pull-request/4 | |||
* rubygem-net-sftp: https://src.fedoraproject.org/rpms/rubygem-net-sftp/pull-request/3 | |||
* vagrant: https://src.fedoraproject.org/rpms/vagrant/pull-request/33 and https://src.fedoraproject.org/rpms/vagrant/pull-request/35 | |||
* Preview of the previous PR contents available in copr: https://copr.fedorainfracloud.org/coprs/jackorp/vagrant-devel/ | |||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Other developers: | * Other developers: N/A (not a System Wide Change) | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
| Line 100: | Line 106: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Install latest available packages from copr (https://copr.fedorainfracloud.org/coprs/jackorp/vagrant-devel/), and try out with their new as well as existing Vagrantfiles and workflows. | |||
Revision as of 15:29, 5 May 2023
Vagrant 2.3
This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.
Summary
Update the Vagrant package to the latest version 2.3.4 and the dependencies rubygem-net-ssh, rubygem-net-scp and rubygem-net-sftp to their latest versions.
Owner
- Name: Jarek Prokop , Pavel Valena
- Email: jprokop@redhat.com , pvalena@redhat.com
Current status
- Targeted release: Fedora Linux 39
- Last updated: 2023-05-05
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
Update the main Vagrant package to version 2.3.4 to bring the latest bug fixes and new features as well as update mentioned rubygem-net-* packages required for Vagrant runtime.
Due to the new rubygem-net-ssh, the updates for mentioned packages will be built and delivered as one unit via the side tag "f39-build-side-67362".
Feedback
Benefit to Fedora
Fedora will have the latest bug fixes and improvements for Vagrant and the rubygem-net-ssh, further enhancing the support for OpenSSL 3.0.
Notable enhancements include:
- rsa-sha2 in kex algorithm set to enable in key exchange
- Support for VirtualBox 7.0
Scope
- Proposal owners:
* Review and merge pull requests for components: * rubygem-net-ssh: https://src.fedoraproject.org/rpms/rubygem-net-ssh/pull-request/14 * rubygem-net-scp: https://src.fedoraproject.org/rpms/rubygem-net-scp/pull-request/4 * rubygem-net-sftp: https://src.fedoraproject.org/rpms/rubygem-net-sftp/pull-request/3 * vagrant: https://src.fedoraproject.org/rpms/vagrant/pull-request/33 and https://src.fedoraproject.org/rpms/vagrant/pull-request/35 * Preview of the previous PR contents available in copr: https://copr.fedorainfracloud.org/coprs/jackorp/vagrant-devel/
- Other developers: N/A (not a System Wide Change)
- Release engineering: #Releng issue number
- Policies and guidelines: N/A (not needed for this Change)
- Trademark approval: N/A (not needed for this Change)
- Alignment with Community Initiatives:
Upgrade/compatibility impact
How To Test
Install latest available packages from copr (https://copr.fedorainfracloud.org/coprs/jackorp/vagrant-devel/), and try out with their new as well as existing Vagrantfiles and workflows.
User Experience
Ideally no negative change, as this is mostly extension of capabilities of the Vagrant stack.
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)
Release Notes
See the upstream CHANGELOG.md file for full release notes: https://github.com/hashicorp/vagrant/blob/986a01734f008d62897bb66085381090e4fcabfc/CHANGELOG.md