1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
Unpackaged files message in RPM-4.1 and following
-------------------------------------------------
RPM version 4.1 and following demonstrate a new behaviour in the rpmbuild process. Previously,
a build process might place any number of files, say in the %install stanza, when running the
make install part of a Makefile, in the customary /var/tmp/%{name}-root/ BuildRoot (the
RPM_BUILD_ROOT). Once through that part of the Makefile, it can then completely ignore these
files in the %files binary packaging stanza.
This often happens when an upstream maintainer adds, or deletes items from new directory spurs
in the make install , and the change might be missed during an unattended or automated rebuild.
This option permits careful packagers to cross check the quality of their packaging.
So as a cross check, /usr/lib/rpm/check-files is now enabled during the %files stanza, to help
a packager identify possibly omitted files. This obviously will disclose breakage in existing
.SPEC files, but this should be a reasonably plainless transition as the specfile packager amends
them to properly account for all expected files.
Obviously some maintaining packagers will take some time to complete the process for their
packages; in the interim, for the causal package builder, Jeff Johnson offered this advice.
2) Reconfigure to warn, not stop, the build. The relevant macro(s) are (from /usr/lib/rpm/macros):
#
# Script gets packaged file list on input and buildroot as first parameter.
# Returns list of unpackaged files, i.e. files in $RPM_BUILD_ROOT not packaged.
#
# Note: Disable (by commenting out) for legacy compatibility. %__check_files /usr/lib/rpm/check-files %{buildroot}
#
# Should unpackaged files in a build root terminate a build?
#
# Note: The default value should be 0 for legacy compatibility. %_unpackaged_files_terminate_build 1
#
# Should missing %doc files in the build directory terminate a build?
#
# Note: The default value should be 0 for legacy compatibility. %_missing_doc_files_terminate_build 1
|