yes, it does require python3, not sure what the bug is here
hmm, where are you getting your rpm from? rpm2cpio /home/nhorman/rpmbuild/RPMS/noarch/redfish-finder-0.2-1.fc29.noarch.rpm | cpio -d -i 75 blocks [nhorman@hmswarspite test]$ head ./usr/bin/redfish-finder #!/usr/bin/python3 import sys import os import subprocess import ipaddress import argparse
Ok, I see, though thats less than self evident from a developer perspective. The rpm packaging macros apparently rewrite the script command line during the build, but makes it unclear what package to depend on. Given Ians response to your question on email, I think we're ok here though.
I am sorry, but, your package doesn't need to depend on 'python3' You use: #!/usr/libexec/platform-python rpm -qf /usr/libexec/platform-python platform-python-3.6.8-1.el8.x86_64 You package uses platform-python Answer from Ian McLeod is irrelevant to this bug.
Is there something actually broken here? do you have an actual error to report? You've got this opened against 8.0, and its way to late to get anything fixed in 8.0 unless its a critical bug, so unless there is something customer visible that is truly broken here, I'm really not especially worried about it.
Neil Hi. > Is there something actually broken here? >Do you have an actual error to report? Functionality is OK. This bug-report was opened for bug in RPM packaging. > You've got this opened against 8.0 I changed "Target Release" to 8.2
no, it can wait
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.