[Bug 1249716] rt-4.2.11-1.fc24 FTBFS: Installed (but unpackaged) file(s) found with rpm-4.13

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1249716

Florian Festi <ffesti at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ffesti at redhat.com
          Component|rpm                         |rt
           Assignee|packaging-team-maint at redhat |rc040203 at freenet.de
                   |.com                        |



--- Comment #4 from Florian Festi <ffesti at redhat.com> ---
You are right that using rt's "make install" in combination with %doc is a
legitimate (and recommended) way of handling this situation and you are right
in your expectation that both can be used together.

But if you do install files with "make install" (or any other command than
%doc) you must add the files to a (sub) package by adding it to a %files
section - either directly or as part of a glob or directory. The error you see
is caused by not adding those files.

So one way to solve this for the rt package is to add %pkgdocdir/* to the
%files section.


Unfortunately this packaging error has been hidden by a bug until now that adds
all files in %{_pkgdocdir} to the (sub) package if %doc is used in the %files
section. This is clearly wrong for a number of reasons:

1) It creates an error about unrelated files if you remove the %doc directives
2) It adds files to a package it may not belong into if the files should
actually go into a different sub package.
3) It hides the error message for files erroneously copied into the
%{_pkgdocdir}


For the case that there are too many other packages with this problem this need
obviously handled in a proper way. We already have some code to keep the
packages building and just issue a warning. But I am not sure if this is really
the way to go. If there is just a small number packages affected fixing those
and getting rid of the whole issue seems like a better and easier way.

-- 
You are receiving this mail because:
You are on the CC list for the bug.