Latest revision as of 16:51, 2 October 2024

RPM 4.20

Summary

Update RPM to the up coming 4.20 release.

Owner

Name: Florian Festi
Email: ffesti@redhat.com

Current status

Targeted release: Fedora Linux 41
Last updated: 2024-10-02
Announced
Discussion thread
FESCo issue: #3188
Tracker bug: #2276421
Release notes tracker: #107

Detailed Description

RPM 4.20 contains various improvements over previous versions.

Hands-free packaging
- Declarative build system
- Dynamic spec generation extended
- File trigger scriptlet arguments
- Support for spec local dependency generators
- Support for sysusers 'm' directive
- Guaranteed per-build directory
Public plugin API
Increased install scriptlet isolation (#2632, #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.

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

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: No Community Initiatives yet but several features (declarative build system support, dynamic spec generation and spec local dep generators) are relevant for Objective Review: We integrate programming language stack ecosystems

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

@@ Line 1: / Line 1: @@
 = RPM 4.20 =
-{{Change_Proposal_Banner}}
 == Summary ==
@@ Line 15: / Line 14: @@
 == Current status ==
-[[Category:ChangeReadyForWrangler]]
+[[Category:ChangeAcceptedF41]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 31: / Line 30: @@
 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]
-* Release notes tracker: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2276421 #2276421]
+* Release notes tracker: [https://gitlab.com/fedora/docs/fedora-linux-documentation/release-notes/-/issues/107 #107]
@@ Line 64: / Line 64: @@
 ** Release RPM 4.20 alpha
 ** Rebase RPM in rawhide
-** Assist with dealing with incompatibilities
+** 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 -->
 ** Test new release, report issues and bugs
@@ Line 77: / Line 77: @@
 * Trademark approval: N/A (not needed for this Change)
-* Alignment with Community Initiatives: None
+* 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 -->
@@ Line 84: / Line 84: @@
 <!-- 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 ==

Search

Changes/RPM-4.20: Difference between revisions