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 2246611 - F40FailsToInstall: luxcorerender-core
Summary: F40FailsToInstall: luxcorerender-core
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: luxcorerender
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Luya Tshimbalanga
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2246603
Blocks: F40FailsToInstall 2246605 2246616
TreeView+ depends on / blocked
 
Reported: 2023-10-27 16:33 UTC by Fedora Fails To Install
Modified: 2023-10-30 15:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-10-30 11:13:13 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Fedora Fails To Install 2023-10-27 16:33:40 UTC 
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

Your package (luxcorerender) Fails To Install in Fedora 40:

can't install luxcorerender-core:
  - nothing provides libopenvdb.so.10.0()(64bit) needed by luxcorerender-core-2.7-0.5.beta1.fc39.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-40-x86_64 --config-opts mirrored=False install luxcorerender-core


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 Ben Beasley 2023-10-27 19:09:09 UTC 
This is due to an unannounced SONAME version bump in openvdb: https://bugzilla.redhat.com/show_bug.cgi?id=2243424#c1.

I opened side tag f40-build-side-76558, and OpenImageIO was already rebuilt there. Please rebuild luxcorerender into f40-build-side-76558 as well; then I can rebuild usd and blender and merge the side tag.
Comment 2 Ben Beasley 2023-10-28 01:27:43 UTC 
I went ahead and merged the side tag with Blender, OpenImageIO, and USD. The update https://bodhi.fedoraproject.org/updates/FEDORA-2023-cbe8ef4af1 should be in the rawhide buildroot very shortly, at which point you can just rebuild luxcorerender into rawhide directly.
Comment 3 Fedora Fails To Install 2023-10-30 11:13:13 UTC 
Hello,

Please note that this comment was generated automatically by https://pagure.io/releng/blob/main/f/scripts/ftbfs-fti/follow-policy.py
If you feel that this output has mistakes, please open an issue at https://pagure.io/releng/

All subpackages of a package against which this bug was filled are now installable or removed from Fedora 40.

Thanks for taking care of it!
Comment 4 Luya Tshimbalanga 2023-10-30 15:40:20 UTC 
(In reply to Ben Beasley from comment #2)
> I went ahead and merged the side tag with Blender, OpenImageIO, and USD. The
> update https://bodhi.fedoraproject.org/updates/FEDORA-2023-cbe8ef4af1 should
> be in the rawhide buildroot very shortly, at which point you can just
> rebuild luxcorerender into rawhide directly.

Thanks. It turned out switching to C++17 standard resolved the issue.
Note You need to log in before you can comment on or make changes to this bug.