From Fedora Project Wiki
(Initial version without content)
 
(adding tracker bug)
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
= RPM 4.20 =
= RPM 4.20 =


{{Change_Proposal_Banner}}


== Summary ==
== Summary ==
Update RPM to the [https://rpm.org/wiki/Releases/4.20.0 4.20] release.
Update RPM to the up coming  [https://rpm.org/wiki/Releases/4.20.0 4.20] release.


== Owner ==
== Owner ==
Line 15: Line 14:


== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF41]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
Line 31: Line 30:
ON_QA -> change is fully code complete
ON_QA -> change is fully code complete
-->
-->
* [<will be assigned by the Wrangler> devel thread]
* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/TNZVMTVWDEJVA7ZONT3D6Y56HM6RHTMC/ Announced]
* FESCo issue: <will be assigned by the Wrangler>
* [https://discussion.fedoraproject.org/t/f41-change-proposal-rpm-4-20-system-wide/109573 Discussion thread]
* Tracker bug: <will be assigned by the Wrangler>
* FESCo issue: [https://pagure.io/fesco/issue/3188 #3188]
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2276421 #2276421]
* Release notes tracker: <will be assigned by the Wrangler>
* Release notes tracker: <will be assigned by the Wrangler>


Line 40: Line 40:


RPM 4.20 contains various improvements over previous versions.
RPM 4.20 contains various improvements over previous versions.
* Hands-free packaging
** [https://github.com/rpm-software-management/rpm/issues/1087 Declarative build system]
** Dynamic spec generation extended
** [https://github.com/orgs/rpm-software-management/projects/16/views/1 File trigger scriptlet arguments]
** [https://github.com/rpm-software-management/rpm/issues/782 Support for spec local dependency generators]
** [https://github.com/rpm-software-management/rpm/issues/2816 Support for sysusers 'm' directive]
** [https://github.com/rpm-software-management/rpm/issues/2078 Guaranteed per-build directory]
* [https://github.com/rpm-software-management/rpm/issues/1536 Public plugin API]
* Increased install scriptlet isolation ([https://github.com/rpm-software-management/rpm/issues/2632 #2632], [https://github.com/rpm-software-management/rpm/issues/2665 #2665])


The 4.20 alpha release is expected in late March/early April and the final release is expected in time for the Fedora 41 release cycle as usual.
The 4.20 alpha release is expected in late March/early April and the final release is expected in time for the Fedora 41 release cycle as usual.
Line 52: Line 62:
== Scope ==
== Scope ==
* Proposal owners:
* Proposal owners:
 
** Release RPM 4.20 alpha
** Rebase RPM in rawhide
** Assist with dealing with incompatibilities by working with a provenpackager to get the affected packages fixed before pushing the alpha release into rawhide.
* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** Test new release, report issues and bugs
** Test new release, report issues and bugs
Line 65: Line 77:
* Trademark approval: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)


* Alignment with Community Initiatives:  
* Alignment with Community Initiatives: No Community Initiatives yet but several features (declarative build system support, dynamic spec generation and spec local dep generators) are relevant for [https://discussion.fedoraproject.org/t/objective-review-we-integrate-programming-language-stack-ecosystems/79289 Objective Review: We integrate programming language stack ecosystems]
<!-- 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 -->
<!-- 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 -->


Line 72: Line 84:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
=== %patchN ===
The %patchN macro syntax (where N is a patch number) is now obsolete and will produce a build error (instead of an warning in 4.19). Use %patch N (or %patch -P N) instead.


This affects currently > 1000 spec files. They need to get fixed before pushing the alpha into rawhide. This compatibility issue probably needs to go into the release notes


== How To Test ==
== How To Test ==

Latest revision as of 14:31, 22 April 2024

RPM 4.20

Summary

Update RPM to the up coming 4.20 release.

Owner


Current status


Detailed Description

RPM 4.20 contains various improvements over previous versions.

The 4.20 alpha release is expected in late March/early April and the final release is expected in time for the Fedora 41 release cycle as usual.

Feedback

Benefit to Fedora

This release comes with many improvements. It opens the possibility for Fedora to adopt the new major features mentioned above.

Scope

  • Proposal owners:
    • Release RPM 4.20 alpha
    • Rebase RPM in rawhide
    • Assist with dealing with incompatibilities by working with a provenpackager to get the affected packages fixed before pushing the alpha release into rawhide.
  • Other developers:
    • Test new release, report issues and bugs
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

%patchN

The %patchN macro syntax (where N is a patch number) is now obsolete and will produce a build error (instead of an warning in 4.19). Use %patch N (or %patch -P N) instead.

This affects currently > 1000 spec files. They need to get fixed before pushing the alpha into rawhide. This compatibility issue probably needs to go into the release notes

How To Test

Rpm receives a thorough and constant testing via every single package build, system installs and updates. New features can be tested specifically as per their documentation.

User Experience

There are no major differences in the normal user experience.

Dependencies

Contingency Plan

  • Contingency mechanism: Revert back to RPM 4.19
  • Contingency deadline: Beta freeze
  • Blocks release? No

Documentation

Release notes at https://rpm.org/wiki/Releases/4.20.0 (still tbd) and reference manual at https://rpm-software-management.github.io/rpm/manual/


Release Notes