Due to Python and Pylint version differences in different platforms, some changes need to be made in the PKI Python source code to prevent build failures. This includes:
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical - Issue set to the milestone: 10.4
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1456940
Metadata Update from @mharmsen: - Issue assigned to mharmsen
A revised patch was altered to change "args" ==> "argv" rather than "argv" ==> "args" since it was discovered that a number of the routines utilized "args" as a local variable that would have to be changed since if the "argv" input parameter were changed to "args". Consequently, the final submitted patch converts "args" ==> "argv".
commit f7b6305396581f5916498cc4ea8247596bf39aaf (HEAD -> master, origin/master, origin/HEAD) Author: Matthew Harmsen mharmsen@redhat.com Date: Fri Jun 2 02:10:02 2017 +0200
Fixed pylint issues - https://pagure.io/dogtagpki/issue/2713 - Build failure due to Pylint issues
Metadata Update from @mharmsen: - Issue assigned to cheimes (was: mharmsen) - Issue close_status updated to: fixed - Issue set to the milestone: 10.4.7 (was: 10.4) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.4.7-1.fc27
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2833
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.