Bug 1381114 - Inter-circular dependency in qt5-rpm-macros prevents cmake being rebuild on so-name bumps
Summary: Inter-circular dependency in qt5-rpm-macros prevents cmake being rebuild on s...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: qt5
Version: 26
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Helio Chissini de Castro
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-03 04:58 UTC by Björn 'besser82' Esser
Modified: 2018-02-03 15:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-03 15:17:47 UTC
Type: Bug

Attachments (Terms of Use)
root.log of failing cmake rebuild. (68.61 KB, text/plain)
2016-10-03 04:58 UTC, Björn 'besser82' Esser 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Björn 'besser82' Esser 2016-10-03 04:58:28 UTC 
Created attachment 1206740 [details]
root.log of failing cmake rebuild.

Description of problem:

  Inter-circular dependency in qt5-rpm-macros prevents cmake being rebuild
  on so-name bumps of its dependencies.

Version-Release number of selected component (if applicable):

  qt5-5.7.0-10.fc26


How reproducible:

  100%


Steps to Reproduce:

  see:  https://koji.fedoraproject.org/koji/taskinfo?taskID=15917326


Actual results:

  Re-building cmake fails, because qt5-rpm-macros is installed as
  a deep / implicit dependency.


Expected results:

  Rebuild should succeed, without further intervention.


Additional info:

  Currently one needs to bootstrap-rebuild without cmake-gui and
  then rebuild again with gui enabled.
Comment 1 Fedora End Of Life 2017-02-28 10:24:12 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.
Comment 2 Rex Dieter 2018-02-03 15:17:47 UTC 
koji build logs are no longer available, so it's not clear to be what the problem is.

Feel free to reopen if you can provide the neccesary details.
Note You need to log in before you can comment on or make changes to this bug.