Bug 2084312

Summary:	F37FailsToInstall: hpx-devel, hpx-mpich, hpx-mpich-devel, hpx-openmpi, hpx-openmpi-devel, hpx
Product:	[Fedora] Fedora	Reporter:	Miro Hrončok <mhroncok>
Component:	hpx	Assignee:	Patrick Diehl <patrickdiehl1>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	junghans, jwakely, patrickdiehl1
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:	2022-06-16 01:20:39 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:	2045109, 2062915

Description Miro Hrončok 2022-05-11 21:00:52 UTC

Hello,

Please note that this comment was generated automatically. If you feel that this output has mistakes, please contact me via email (mhroncok).

Your package (hpx) Fails To Install in Fedora 37:

can't install hpx-devel:
  - nothing provides libboost_filesystem.so.1.76.0()(64bit) needed by hpx-devel-1.7.1-2.fc36.x86_64
  
can't install hpx-mpich:
  - nothing provides libboost_filesystem.so.1.76.0()(64bit) needed by hpx-mpich-1.7.1-2.fc36.x86_64
  
can't install hpx-mpich-devel:
  - nothing provides libboost_filesystem.so.1.76.0()(64bit) needed by hpx-mpich-devel-1.7.1-2.fc36.x86_64
  
can't install hpx-openmpi:
  - nothing provides libboost_filesystem.so.1.76.0()(64bit) needed by hpx-openmpi-1.7.1-2.fc36.x86_64
  
can't install hpx-openmpi-devel:
  - nothing provides libboost_filesystem.so.1.76.0()(64bit) needed by hpx-openmpi-devel-1.7.1-2.fc36.x86_64
  
can't install hpx:
  - nothing provides libboost_filesystem.so.1.76.0()(64bit) needed by hpx-1.7.1-2.fc36.x86_64
  
If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.


If you don't react accordingly to the policy for FTBFS/FTI bugs (https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/), your package may be orphaned in 8+ weeks.


P.S. The data was generated solely from koji buildroot, so it might be newer than the latest compose or the content on mirrors. To reproduce, use the koji/local repo only, e.g. in mock:

    $ mock -r fedora-37-x86_64 --disablerepo='*' --enablerepo=local install hpx-devel hpx-mpich hpx-mpich-devel hpx-openmpi hpx-openmpi-devel hpx


P.P.S. If this bug has been reported in the middle of upgrading multiple dependent packages, please consider using side tags: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#updating-inter-dependent-packages

Thanks!

Comment 1 Miro Hrončok 2022-05-19 10:22:38 UTC

Hello,

This is the first reminder (step 3 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs).

If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.

Comment 2 Miro Hrončok 2022-06-09 18:52:28 UTC

Hello,

This is the second reminder (step 4 from https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs).

If you know about this problem and are planning on fixing it, please acknowledge so by setting the bug status to ASSIGNED. If you don't have time to maintain this package, consider orphaning it, so maintainers of dependent packages realize the problem.

Comment 3 Patrick Diehl 2022-06-16 01:20:39 UTC

Hi, 

I can not do much since one boost lib is missing. I can contact the boost maintainers and ask for guidance.

Best,

Patrick

Comment 4 Jonathan Wakely 2022-07-20 18:33:27 UTC

No, this is a bug in your package. You need to fix its build failure so it can be rebuilt to use the new version of boost. No boost libraries are missing.