Bug 1675668

Summary: pki-core: FTBFS in Fedora rawhide/f30
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: pki-coreAssignee: Fraser Tweedale <ftweedal>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: alee, ascheel, awilliam, dmoluguw, edewata, ftweedal, kwright, mharmsen
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-01 00:52:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1674516    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2019-02-11 21:28:03 UTC 
pki-core failed to build from source in Fedora rawhide/f30

https://koji.fedoraproject.org/koji/taskinfo?taskID=32451024


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
Please fix pki-core at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
pki-core will be orphaned. Before branching of Fedora 31,
pki-core will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://fedoraproject.org/wiki/Fails_to_build_from_source
Comment 1 Fedora Release Engineering 2019-02-11 21:28:06 UTC 
Created attachment 1532028 [details]
build.log

file build.log too big, will only attach last 1024 bytes
Comment 2 Fedora Release Engineering 2019-02-11 21:28:07 UTC 
Created attachment 1532029 [details]
root.log

file root.log too big, will only attach last 1024 bytes
Comment 3 Fedora Release Engineering 2019-02-11 21:28:09 UTC 
Created attachment 1532030 [details]
state.log
Comment 4 Adam Williamson 2019-02-13 19:34:23 UTC 
Failure is due to a code lint check failing on a line being 1 character too long (100 chars, when the limit is 99).
Comment 5 Fraser Tweedale 2019-02-14 05:59:22 UTC 
There was already a commit on master to dispel these flake8 complaints
(0971afcf0afa8195bf60707a611476048b9f2f57).

I cherry-picked it to the DOGTAG_10_6_BRANCH.  COPR build succeeded
(https://copr.fedorainfracloud.org/coprs/ftweedal/pki-f30/build/858439/).
Pull request created (https://github.com/dogtagpki/pki/pull/167).  Waiting
on CI before merge.
Comment 6 Fraser Tweedale 2019-02-14 23:36:08 UTC 
Fix pushed to DOGTAG_10_6_BRANCH:

commit 842c7703f087f8e6be4752f8087510652172da84
Author: Stanislav Levin <slev>
Date:   Mon Jan 21 17:03:00 2019 +0300

    Fix flake8 3.6.0 errors

    Since 3.6.0 flake8 respects '# flake8: noqa' processor rule if           
    it is only on a line by itself.

    http://flake8.pycqa.org/en/latest/release-notes/3.6.0.html?highlight=noqa

    Additionally this fixes simple Python style errors found here.           

    Fixes: https://pagure.io/dogtagpki/issue/3090
    Signed-off-by: Stanislav Levin <slev>                       


Moving to POST.