F27 System Wide Change: RPM 4.14
= System Wide Change: RPM 4.14 =
https://fedoraproject.org/wiki/Changes/RPM-4.14
Change owner(s):
* Igor Gnatenko <ignatenkobrain(a)fedoraproject.org>
* Florian Festi <ffesti(a)redhat.com>
* Panu Matilainen <pmatilai(a)redhat.com>
Update RPM to the upcoming 4.14 release.
== Detailed Description ==
RPM 4.14 contains several improvements that needs to get released and
integrated in Fedora:
* Major macro engine bug fix + sanity work:
** Macro scope simplification + enforcing
** Macro arguments expanded
** Nested lua macro scoping fixes
** Improved error reporting
* Major header/package/signature rewrite:
** Unified code path for all header read/import
** Major hardening work on header parsing
** Unified code path for all header/package signature checking
** Signature checking before header imports
** Support for multiple signatures per package
** Support for configurable signature policies
* Major debuginfo rewrite (covered by two other changes and already
applied in F27)
* Signal handling rewrite:
** Custom signal handlers while rpmdb open
** Signals blocked throughout write transactions
* SSD conservation mode
* Improved support for reproducible builds
* RPMCALLBACK_ELEM_PROGRESS now carries index of header
* Support for OpenSSL as a one of crypto libraries used for
digests/signatures (already part of F27)
* Support for rich dependencies coming out from dependency generators
* %include can contain paths with whitespaces
* Dependency generator for pkg-config files doesn't check dependencies
in .pc recursively, but rather print top-level ones (if pkgconf is
used)
* Header digests use SHA256 by default
* Improvements in Python dependency generator
* Improvements and stabilization of "ndb"
* Support for "with" rich-operator:
** Specifying version range dependencies
** Specifying packages which provide special ability
== Scope ==
* Proposal owners:
Rebase RPM
* Other developers:
Test new release, report issues and bugs, fix bugs in packaging (if it
is not bug in RPM, should be detected during Mass Rebuild)
* Release engineering: [1] (a check of an impact with Release
Engineering is needed)
* List of deliverables:
Change affects whole distribution rather than deliverables
* Policies and guidelines:
FPC should look (and possibly approve) "with" rich dependency in
Packaging Guidelines
* Trademark approval: N/A (not needed for this Change)
[1] https://pagure.io/releng/issue/6875
Thanks,
Jaroslav