Hi Sage,

It's Ubuntu 12.04 LTS

Mongo wants to install libgoogle-perftools4, whereas ceph wants to install 
libgoogle-perftools0. 

This is leaving libgoogle-perftools0 in a broken state and, I'm assuming this 
is the cause, making ceph fault. Ceph works great before the installation of 
libgoogle-perftools4. 

This is with using mongo v2.4.6 and seemingly any version of ceph. I've tried 
bobtail, dumpling, and cuttlefish.

Dpkg status:
rc  libgoogle-perftools0
ii  libgoogle-perftools4

dpkg -p ceph:
Depends: binutils, ceph-common, cryptsetup-bin | cryptsetup, gdisk, parted, 
python, python-argparse, sdparm | hdparm, uuid-runtime, xfsprogs, libaio1 (>= 
0.3.93), libboost-thread1.46.1 (>= 1.46.1-1), libc6 (>= 2.14), libgcc1 (>= 
1:4.1.1), libgoogle-perftools0, libnspr4 (>= 1.8.0.10), libnss3 (>= 
3.12.0~1.9b1), libsnappy1, libstdc++6 (>= 4.6), libuuid1 (>= 2.16)

It makes sense that ceph would use the latest, but it's exploding for me :)


> -----Original Message-----
> From: Sage Weil [mailto:s...@inktank.com]
> Sent: Monday, December 09, 2013 6:07 PM
> To: Don Talton (dotalton)
> Cc: Ceph Development (ceph-devel@vger.kernel.org)
> Subject: Re: are there plans to move to a newer google perftools?
> 
> Hi Donald,
> 
> What exactly is the conflict?  And what distro?  I believe we should be using
> whatever version of the library is installed.
> 
> sage
> 
> On Tue, 10 Dec 2013, Don Talton (dotalton) wrote:
> 
> > I'm trying to package/install mongodb and ceph on the same server and
> there are conflict due to the version differences.
> >
> > Donald Talton
> > Systems Development Unit
> > dotal...@cisco.com
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe ceph-devel"
> > in the body of a message to majord...@vger.kernel.org More
> majordomo
> > info at  http://vger.kernel.org/majordomo-info.html
> >
> >
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to