On Sun, Jun 02, 2019 at 08:04:25AM +0100, Sérgio Basto wrote:
On Sat, 2019-06-01 at 21:47 +0200, Georg Sauthoff wrote:
> This is caused by use of the %ghost directive in the %files
> section of the .spec file:
>
> %files -n dpm-copy-server-mysql
> %{_libdir}/dpm-mysql/dpmcopyd
> %ghost %{_sbindir}/dpmcopyd
> %doc %{_libdir}/dpm-mysql/dpmcopyd.8*
> %ghost %{_mandir}/man8/dpmcopyd.8*
>
> Apparently %ghost marks those files as belonging to the package but
> doesn't include them in the package. Thus, they aren't part of the
> cpio
> archive. Common use-case for this seems to be log-files - such that
> they
> are removed on package removal.
Sort of, after lines 1023 [1] we understand the reason this package
use
alternatives , the really location on file is /usr/lib64/dpm-
Good find.
mysql/dpmcopyd.8 so [2] should work
[2]
dnf provides /usr/lib64/dpm-mysql/dpmcopyd.8
I never questioned that `dnf provides /usr/lib64/dpm-mysql/dpmcopyd.8`
would work. It does. It's just a non-standard location and thus nothing
I would try when searching for the man page of dpmcopyd with `dnf
provides`.
Note that all the man-pages under Fedora a gzip-compressed, while this
file isn't.
But does this even work?
%{_sbindir}/update-alternatives --install %{_sbindir}/dpmcopyd dpmcopyd \
%{_libdir}/dpm-mysql/dpmcopyd 20 \
--slave %{_mandir}/man8/dpmcopyd.8.gz dpmcopyd.8.gz \
%{_libdir}/dpm-mysql/dpmcopyd.8.gz
I mean the archive just contains:
usr/lib64/dpm-mysql/dpmcopyd.8
where:
$ file o/usr/lib64/dpm-mysql/dpmcopyd.8
o/usr/lib64/dpm-mysql/dpmcopyd.8: ASCII text, with escape sequences
While the update-alternatives commands references:
%{_libdir}/dpm-mysql/dpmcopyd.8.gz
Best regards
Georg
--
'If you think this sentence is confusing, then change one pig.'
(Hofstadter, 2007)