Hello,
I noticed a case where the `dnf provides` output is inconsistent. That
means the actual rpm package doesn't provide the requested file:
# cat /etc/fedora-release
Fedora release 29 (Twenty Nine)
# dnf provides /usr/share/man/man8/dpmcopyd.8.gz
dpm-copy-server-mysql-1.12.0-2.fc29.x86_64 : DPM copy server with MySQL database
: back-end
Repo : updates
Matched from:
Filename : /usr/share/man/man8/dpmcopyd.8.gz
But:
$ dnf download dpm-copy-server-mysql
Last metadata expiration check: 1:46:49 ago on Sat 01 Jun 2019 05:31:01 PM CEST.
dpm-copy-server-mysql-1.12.0-2.fc29.x86_64.rpm
$ mkdir -p o ; rpm2cpio dpm-copy-server-mysql-1.12.0-2.fc29.x86_64.rpm | cpio -di -D o -v
./etc/dpm-mysql/dpmcopyd.logrotate
./usr/lib/.build-id
./usr/lib/.build-id/70/bf043a9b1a0954bb464faa59261f8edb0564d3
./usr/lib64/dpm-mysql/dpmcopyd
./usr/lib64/dpm-mysql/dpmcopyd.8
./usr/share/dpm-mysql
./usr/share/dpm-mysql/dpmcopyd.service
1589 blocks
$ ls -l o/usr/share/man/man8/dpmcopyd.8.gz
ls: cannot access 'o/usr/share/man/man8/dpmcopyd.8.gz': No such file or directory
That means there is no /usr/share/man/man8/dpmcopyd.8.gz - just:
./usr/lib64/dpm-mysql/dpmcopyd.8
Ok, I guess I could open a bug against dpm-copy-server-mysql - regarding
fixing the location of the manpage.
But what about the `dnf provides` output?
It looks like something is going wrong in the process that generates the
file-index. Should I open a bug for this, as well? And where?
Best regards
Georg
--
'The complexity for minimum component costs has increased at a
rate of roughly a factor of two per year ... Certainly over the
short term this rate can be expected to continue, if not to
increase.' (Moore's law, 1965)
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
