Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1675668 - pki-core: FTBFS in Fedora rawhide/f30
Summary: pki-core: FTBFS in Fedora rawhide/f30
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: pki-core
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fraser Tweedale
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F30FTBFS
TreeView+ depends on / blocked
 
Reported: 2019-02-11 21:28 UTC by Fedora Release Engineering
Modified: 2019-06-01 00:52 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-01 00:52:00 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
build.log (1.00 KB, text/plain)
2019-02-11 21:28 UTC, Fedora Release Engineering
no flags Details
root.log (1.00 KB, text/plain)
2019-02-11 21:28 UTC, Fedora Release Engineering
no flags Details
state.log (629 bytes, text/plain)
2019-02-11 21:28 UTC, Fedora Release Engineering
no flags Details

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.


Note You need to log in before you can comment on or make changes to this bug.