https://bugzilla.redhat.com/show_bug.cgi?id=1723013
Troy Curtis troy@troycurtisjr.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(k4hw8m62b@converg | |enceservice.com) CC| |troy@troycurtisjr.com
--- Comment #23 from Troy Curtis troy@troycurtisjr.com --- A few points:
* All dependencies need to be available in the Fedora/EPEL release you are targeting. If a new enough version of a library/tool isn't available, then a separate package request with that tool will need to be submitted and added to the distribution. * The consequence of the above point is that all that should be built as part of the source RPM is the software being packaged itself.
On the question of the Python tools, the only Python I see is the mnetracer.py script. Since this is a helper tool intended to be used as a cli application, it probably doesn't need it's own sub-package. Unless there is another piece that I'm missing?
Lastly, do you have a FAS account already? If so what is your FAS username. If you do not, the first step will be going through the process described here https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package....
Until the FAS account is given, and an updated spec & source RPM is provided addressing the existing comments, we should leave the NEEDSINFO state in place to alert other potential reviewers that you are working on updates.