Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#27437 - [mongodb] not linked against the latest libboost

Attached to Project: Community Packages
Opened by Christian Sturm (Athaba) - Saturday, 03 December 2011, 21:13 GMT
Last edited by Thomas Dziedzic (tomd123) - Sunday, 04 December 2011, 03:40 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Thomas Dziedzic (tomd123)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

mongodb-2.0.1-3 isn't linked against the latest libboost. To be sure about having 2.0.1-3 I used pacman's -f parameter to enforce an overwrite, but it had no effect.

ldd /usr/bin/mongo | grep boost
libboost_system.so.1.47.0 => not found
libboost_thread.so.1.47.0 => not found
libboost_filesystem.so.1.47.0 => not found
libboost_program_options.so.1.47.0 => not found
This task depends upon

Closed by  Thomas Dziedzic (tomd123)
Sunday, 04 December 2011, 03:40 GMT
Reason for closing:  Fixed
Additional comments about closing:  2.0.1-4
Comment by Christian Sturm (Athaba) - Saturday, 03 December 2011, 21:25 GMT
I now directly checked the binary from a freshly downloaded package, to be sure it isn't a problem somewhere else. It isn't.
Comment by Thomas Dziedzic (tomd123) - Saturday, 03 December 2011, 21:31 GMT
on the 64bit mongodb package, ldd $(which mongo) shows it's linked against boost 1.48, I'm assuming you're experiencing this on i686.

The only explanation I can come up with is that the mirror wasn't fully synced when I did rebuild mongodb so when I started rebuilding the i686 version, the mirror still didn't have boost 1.48 and when that finished building, x86_64 started and by that time the mirror was fully synced...

just my luck, I am rebuilding this as I write this and will soon release 2.0.1-4 and close this bug report.

Thanks for reporting it.

Loading...