RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2056509 - opencv-3.4.6-7.el8 fails to rebuild from sources
Summary: opencv-3.4.6-7.el8 fails to rebuild from sources
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: opencv
Version: 8.6
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Jiri Kucera
QA Contact: CS System Management SST QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-21 12:12 UTC by Kamil Dudka
Modified: 2023-05-22 12:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-22 12:17:25 UTC
Type: Bug
Target Upstream Version:
Embargoed:
kdudka: needinfo-


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-112911 0 None None None 2022-02-21 12:15:29 UTC

Description Kamil Dudka 2022-02-21 12:12:20 UTC
Description of problem:
opencv-3.4.6-7.el8 fails to rebuild from source in up2date build root.  This is most likely caused by ceres-solver being built against an obsolete version of gflags but I am assigning it to opencv initially because RHEL-8 packages are supposed to be rebuildable.


Version-Release number of selected component (if applicable):
opencv-3.4.6-7.el8


How reproducible:
Easily.


Steps to Reproduce:
1. brew build --scratch rhel-8.6.0-candidate 'git://pkgs.devel.redhat.com/rpms/opencv#4585e7035197c8c5c5e2d49fb33074ea6ed13e45'


Actual results:
DEBUG util.py:634:  Error: 
DEBUG util.py:634:   Problem: package ceres-solver-devel-1.13.0-2.el8.s390x requires libceres.so.1()(64bit), but none of the providers can be installed
DEBUG util.py:634:    - package ceres-solver-devel-1.13.0-2.el8.s390x requires ceres-solver(s390-64) = 1.13.0-2.el8, but none of the providers can be installed
DEBUG util.py:634:    - conflicting requests
DEBUG util.py:634:    - nothing provides libgflags.so.2.1()(64bit) needed by ceres-solver-1.13.0-2.el8.s390x
DEBUG util.py:636:  (try to add '--skip-broken' to skip uninstallable packages)
DEBUG util.py:787:  Child return code was: 1


Expected results:
Successful build.


Additional info:
https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=43206246

Comment 2 Michel Lind 2022-02-24 19:48:00 UTC
ceres-solver seems to be an internal-only dependency? On my c8s install, the ceres-solver that shows is the EPEL one, which is also why finding gflags dependencies does not bring up ceres-solver (which is likely how it was missed).

I can confirm that it built fine in my local mock against the newer gflags, with no change (just bumping the release field and regenerating the SRPM). opencv also chain-builds fine with the same bump, once I downloaded and installed SFML{,-devel} and libdc1394{,-devel} from Koji

❯ ls ../repo/results/centos-stream-8-x86_64/*/*.rpm
../repo/results/centos-stream-8-x86_64/ceres-solver-1.13.0-3.fc35/ceres-solver-1.13.0-3.el8.src.rpm
../repo/results/centos-stream-8-x86_64/ceres-solver-1.13.0-3.fc35/ceres-solver-1.13.0-3.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/ceres-solver-1.13.0-3.fc35/ceres-solver-debuginfo-1.13.0-3.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/ceres-solver-1.13.0-3.fc35/ceres-solver-debugsource-1.13.0-3.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/ceres-solver-1.13.0-3.fc35/ceres-solver-devel-1.13.0-3.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/opencv-3.4.6-7.fc35/opencv-3.4.6-7.el8.src.rpm
../repo/results/centos-stream-8-x86_64/opencv-3.4.6-7.fc35/opencv-3.4.6-7.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/opencv-3.4.6-7.fc35/opencv-contrib-3.4.6-7.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/opencv-3.4.6-7.fc35/opencv-contrib-debuginfo-3.4.6-7.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/opencv-3.4.6-7.fc35/opencv-core-3.4.6-7.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/opencv-3.4.6-7.fc35/opencv-core-debuginfo-3.4.6-7.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/opencv-3.4.6-7.fc35/opencv-debuginfo-3.4.6-7.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/opencv-3.4.6-7.fc35/opencv-debugsource-3.4.6-7.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/opencv-3.4.6-7.fc35/opencv-devel-3.4.6-7.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/opencv-3.4.6-7.fc35/opencv-doc-3.4.6-7.el8.noarch.rpm
../repo/results/centos-stream-8-x86_64/opencv-3.4.6-7.fc35/python3-opencv-3.4.6-7.el8.x86_64.rpm
../repo/results/centos-stream-8-x86_64/opencv-3.4.6-7.fc35/python3-opencv-debuginfo-3.4.6-7.el8.x86_64.rpm


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