Bug 1349191 - [RFE] Need a version of libmongodb that gets along with Windows Server MongoDB 3.2.
Summary: [RFE] Need a version of libmongodb that gets along with Windows Server MongoD...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Software Collections
Classification: Red Hat
Component: mongodb
Version: rh-mongodb32
Hardware: All
OS: Linux
medium
medium
Target Milestone: alpha
: 2.3
Assignee: Marek Skalický
QA Contact: Vaclav Danek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-22 22:12 UTC by Greg Scott
Modified: 2020-01-17 15:48 UTC (History)
6 users (show)

Fixed In Version: rh-mongodb32-mongo-cxx-driver-1.1.2-3.el7, rh-mongodb32-mongo-cxx-driver-1.1.2-3.el6
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-15 10:11:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:2735 0 normal SHIPPED_LIVE rh-mongodb32 bug fix and enhancement update 2016-11-15 14:47:57 UTC

Description Greg Scott 2016-06-22 22:12:52 UTC
This is a request for enhancement for SCL to package a version of libmongodb on RHEL 6 and 7 that functions properly with Windows Server MongoDB 3.2.  The goal here is to use the newest possible versions of all components.

A note from the customer with more information:

MongoDB C++ Driver on MongoDB site:
The most recent Legacy driver release is: https://github.com/mongodb/mongo-cxx-driver/releases/tag/legacy-1.1.1,
 
Please note that there are changes required to migrate from 26compat to legacy. In particular, there are changes to the build system, and to the APIs. I recommend reading the following two pages:
       https://github.com/mongodb/mongo-cxx-driver/wiki/Download-and-Compile-The-Legacy-Driverhttps://github.com/mongodb/mongo-cxx-driver/wiki/Configuring%20the%20Legacy%20Driverhttps://github.com/mongodb/mongo-cxx-driver/wiki/Breaking-changes-between-26compat-and-legacy

Comment 1 Honza Horak 2016-07-11 18:12:53 UTC
Just a comment about implementation details. If we added libmongodb into SCL, the library wouldn't be available on standard library path, so what the user would have to do is enabling the collection properly via `scl enable rh-mongodb32` in those two cases:

1) every-time some application that uses this library is built

2) every-time such an application is run

(unless user will use some trick with rpath)

Would that be acceptable for the customer?

Comment 2 Arno Karner 2016-07-14 21:56:54 UTC
The application currently sets up an environment before it runs, so using the rpath option would be the most likely solution, we would just add setting up the rpath variable to find the rh-mongodb-32 libraries.

We had previously compiled libmongo to use ssl, and were able to use ssl, and tls without issue. But we're having troubles getting it to work with Kerberos when we tried compiling with 
scons --full --use-system-boost --ssl --sharedclient --use-sasl-client

Comment 7 errata-xmlrpc 2016-11-15 10:11:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-2735.html


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