RPM Community Forums

Mailing List Message of <rpm-devel>

Does rpm really need to stop file check immediately when an issue is detected?

From: Denis Silakov <dsilakov@gmail.com>
Date: Fri 24 May 2013 - 10:45:49 CEST
Message-ID: <519F28BD.3090105@gmail.com>
Hi all,

During discussions with ROSA and OpenMandriva maintainers, we have found 
out that update of packages to newer versions sometimes takes much 
longer than it could due to rpmbuild specifics (I mean not 'rpm -iU', 
but the process of adopting spec file for a newer upstream version). The 
particular claiming is about rpmbuild exiting immidiately when a 
critical error concerning file lists is detected ("file not found", 
"installed but unpackaged file found", and some other issues like "file 
listed twice" which terminate the build in ROSA/MDV). However, the 
rpmbuild could continue the work to detect more issues with files, 
otherwise maintainers are able to detect and fix only one error per 
build iteration. And in case of large packages with large changes, this 
leads to a need to perform a lot of build iterations to eliminate all 
issues, though the build itself is proved to be successful and just 
takes the time.

The particular improvement suggestions are like the following:
1) If a package has several subpackages, then check file lists in every 
2) Perform all checks at once, do not return RPMRC_FAIL immediately if 
one of them failed

Here is a rough patch implementing this behavior which is currently used 
in OpenMandriva and available for ROSA, as well:

What do people think? Are others interested in such modifications?

Received on Fri May 24 11:16:45 2013
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.