Revision as of 16:01, 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.

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 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: N/A

Upgrade/compatibility impact

Everything should keep working.

How To Test

Install latest available packages from copr (https://copr.fedorainfracloud.org/coprs/jackorp/vagrant-devel/), and try them out with 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

N/A (not a system-wide change)

Contingency Plan

Contingency mechanism: 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), 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

@@ Line 1: / Line 1: @@
-<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
 = Vagrant 2.3 =
@@ Line 9: / Line 7: @@
 == Owner ==
-<!--
-For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
-This should link to your home wiki page so we know who you are.
--->
 * Name: [[ User:Jackorp1| Jarek Prokop ]], [[ User:Pvalena | Pavel Valena ]]
-<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
 * Email: jprokop@redhat.com , pvalena@redhat.com
 <!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
@@ Line 69: / Line 63: @@
 * 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?-->
 * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
-The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
-* Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Policies and guidelines: N/A (not needed for this Change)
-<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->
 * Trademark approval: N/A (not needed for this Change)
-<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
-* Alignment with Community Initiatives:
+* Alignment with Community Initiatives: N/A
-<!-- Does your proposal align with the current Fedora Community Initiatives: https://docs.fedoraproject.org/en-US/project/initiatives/ ? It's okay if it doesn't, but it's something to consider -->
 == Upgrade/compatibility impact ==
-<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
+Everything should keep working.
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 == How To Test ==
-<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
+Install latest available packages from copr (https://copr.fedorainfracloud.org/coprs/jackorp/vagrant-devel/),
+and try them out with new as well as existing Vagrantfiles and workflows.
-Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
-A good "how to test" should answer these four questions:
-. What special hardware / data / etc. is needed (if any)?
-. How do I prepare my system to test this change? What packages
-need to be installed, config files edited, etc.?
-. What specific actions do I perform to check that the change is
-working like it's supposed to?
-. What are the expected results of those actions?
--->
-<!-- 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.
 == User Experience ==
 Ideally no negative change, as this is mostly extension of capabilities of the Vagrant stack.
-<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
- This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
- Describe what Users will see or notice, for example:
-  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
-  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- - Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
--->
 == Dependencies ==
-<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
+N/A (not a system-wide change)
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 == Contingency Plan ==
+* Contingency mechanism: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
-* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
 * Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Blocks release? N/A (not a System Wide Change), No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 == Documentation ==
-<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 N/A (not a System Wide Change)
 == Release Notes ==
-<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are at https://docs.fedoraproject.org/en-US/fedora/latest/release-notes/ -->
-<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
-Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
--->
 See the upstream CHANGELOG.md file for full release notes:
 https://github.com/hashicorp/vagrant/blob/986a01734f008d62897bb66085381090e4fcabfc/CHANGELOG.md

Search

Changes/Vagrant 2.3: Difference between revisions