Description of problem:
Most probably a bogus, but worth checking.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. rpm -V PackageKit-1.1.5-2.el7_5
doRpmCommand: rpm -V PackageKit-1.1.5-2.el7_5.ppc64le
doRpmCommand-result (256): .M....... g /var/lib/PackageKit/transactions.db
result: verify test: FAIL:
PackageKit.ppc64le: /var/lib/PackageKit/transactions.db .M....... g [tps:B]
TPS verify test analysis tags:
tps:a -- verify errors on both arches
tps:b -- verify error on file not present in alternative arch
tps:c -- verify error on preferred binary/ELF file
tps:d -- significant type of verify error
no non-0 return code
Happen on all arches no only ppc64le
transactions.db is designed to store the transaction logs; do i need a %ghost or something?
(In reply to Richard Hughes from comment #1)
> transactions.db is designed to store the transaction logs; do i need a
> %ghost or something?
Well this is probably a question for experienced pkg maintainer. But I can give it a try if you create scratch build for me.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.