Bug 1723810
| Summary: | mongo-cxx-driver 3.4.0 is available | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Till Hofmann <thofmann> |
| Component: | mongo-cxx-driver | Assignee: | Honza Horak <hhorak> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 31 | CC: | hhorak, mhroncok, mskalick, tdawson |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | mongo-cxx-driver-3.4.0-1.fc32 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-09-09 08:44:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Till Hofmann
2019-06-25 12:59:48 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'. This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31. Honza, I see you are now the official Fedora maintainer of this package according to https://src.fedoraproject.org/rpms/mongo-cxx-driver Could you please have a look at this (or delegate)? There is a thread on the devel mailing list for some time: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/CNNUFKVBEPFJQANEBUFROKVTUXB3GSQS/ Thanks. I'm on it now, sorry for the delay. Changes in git now: https://src.fedoraproject.org/rpms/mongo-cxx-driver/c/e197b2098fc01e5643c45c69b299e7b5c44748ab?branch=master Build done: https://koji.fedoraproject.org/koji/buildinfo?buildID=1374548 I'm not planning to update F31 unless there is a reason I'm not aware of, because the library rebase is always a risk. Let me know if there is a reason to do so, and we can re-consider. Thank You! |