Bug 1540650 - mongodb: Error: nothing provides libboost_system
Summary: mongodb: Error: nothing provides libboost_system
Keywords:
Status: CLOSED DUPLICATE of bug 1540311
Alias: None
Product: Fedora
Classification: Fedora
Component: mongodb
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Skalický
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-31 15:59 UTC by Jun Aruga
Modified: 2018-02-01 11:58 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-01 08:31:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jun Aruga 2018-01-31 15:59:18 UTC
Description of problem:

When building mongodb Ruby binding latest new version, I got an error in root.log

The logs are here.
https://koji.fedoraproject.org/koji/taskinfo?taskID=24598737
https://kojipkgs.fedoraproject.org//work/tasks/8737/24598737/root.log

The root log says 

```
DEBUG util.py:439:  Error: 
DEBUG util.py:439:   Problem: conflicting requests
DEBUG util.py:439:    - nothing provides libboost_system.so.1.64.0()(64bit) needed by mongodb-server-3.6.2-1.fc28.ppc64le
```

Perhaps, do I have to do "Requires:  boost-devel" in the Ruby binding spec file?


Version-Release number of selected component (if applicable):
mongodb-3.6.2-1.fc2

How reproducible:


Steps to Reproduce:
1. https://src.fedoraproject.org/fork/jaruga/rpms/rubygem-mongo
2. git clone ssh://jaruga.org/forks/jaruga/rpms/rubygem-mongo.git
3. cd rubygem-mongo
4. git checkout feature/update-to-v2.5.0
5. fedpkg --release master scratch-build --srpm

Actual results:
The build root.log has an error "nothing provides libboost_system.so.1.64.0()(64bit) needed by mongodb-server-3.6.2-1.fc28.ppc64le".


Expected results:
The build root.log finishes without error.

Additional info:

Comment 1 Vít Ondruch 2018-02-01 08:24:48 UTC
Mongo must be rebuild against updated Boost:

https://fedoraproject.org/wiki/Changes/F28Boost166
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/XHY6QJUCNPFGCXVN2PJOOOKSIPUTEDKA/

It probably failed the rebuild for some reason or looking into Koji, it even was not part of the rebuild:

https://koji.fedoraproject.org/koji/packageinfo?packageID=10883

Comment 2 Vít Ondruch 2018-02-01 08:31:19 UTC
This was already reported by boost maintainer.

*** This bug has been marked as a duplicate of bug 1540311 ***

Comment 3 Jonathan Wakely 2018-02-01 11:58:11 UTC
(In reply to Vít Ondruch from comment #1)
> It probably failed the rebuild for some reason or looking into Koji, it even
> was not part of the rebuild:
> 
> https://koji.fedoraproject.org/koji/packageinfo?packageID=10883

The boost rebuild process involves local builds on my own hardware and scratch builds in koji for a subset of arches, so for packages that FTBFS I don't waste koji resources (and hours and hours waiting for ARM builds to finish). So there won't always be a failed koji build even though a package is part of the rebuild.


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