Google Perftools lib and dev package are out of sync

[Monty Taylor]

Binary package hint: libgoogle-perftools-dev

In Jaunty, I am unable to install libgoogle-perftools-dev because the matching libgoogle-perftools0 package is missing (or, more to the point, old)

The following packages have unmet dependencies:
  libgoogle-perftools-dev: Depends: libgoogle-perftools0 (= 0.98-1ubuntu1) but 0.8-5.1 is to be installed

I'm trying to install this to get what should be libtcmalloc-dev. There is also a new-to-jaunty libtcmalloc-minimal0, but it only installs libtcmalloc-minimal0, and I'd like the actual lib.

[TheHobbit (the-hobbit)]

I'm unable to reproduce it. Could it be a problem in your soures.list? or a synch problem in one of the servers used there? Please, post your /etc/apt/sources.list

[Monty Taylor (mordred)]

I also had this problem in a PPA, after uploading a package that build-depended on libgoogle-protobuf-dev to a Jaunty PPA. (which is how I noticed the problem in the first place) I have since modified the build-dep of that package, but I'd be happy to try uploading another package to a PPA with that in the build-deps line for you... Here's my sources.list.

deb http://us.archive.ubuntu.com/ubuntu/ jaunty main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates main restricted
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## universe WILL NOT receive any review or updates from the Ubuntu security
## team.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty universe
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty universe
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates universe
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty multiverse
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-backports main restricted universe multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ jaunty-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'commercial' repository. This software is not part of Ubuntu, but is
## offered by Canonical and the respective vendors as a service to Ubuntu
## users.
deb http://archive.canonical.com/ubuntu jaunty partner
deb-src http://archive.canonical.com/ubuntu jaunty partner

deb http://ppa.launchpad.net/bzr/ppa/ubuntu jaunty main
deb-src http://ppa.launchpad.net/bzr/ppa/ubuntu jaunty main

deb http://ppa.launchpad.net/drizzle-developers/ppa/ubuntu jaunty main
deb-src http://ppa.launchpad.net/drizzle-developers/ppa/ubuntu jaunty main

[John Ferlito (johnf-inodes)]

I think the problem is that the amd64 version is out of date. Check http://packages.ubuntu.com/jaunty/libgoogle-perftools0 and you'll see that it's still 0.8-5.1 for some reason. Maybe the build is failing?

[spark (dc04)]

I today moved from 32bit to 64bit ubuntu and got this dependency bug, It's quite annoying. Should be easy to fix though.

[Monty Taylor (mordred)]

spark wrote:
> I today moved from 32bit to 64bit ubuntu and got this dependency bug,
> It's quite annoying. Should be easy to fix though.
>

There is an out of date package upstream. We're working on a new version
of the package upstream.

In the mean time, I've got some packages in the drizzle-developers PPA at:

http://launchpad.net/~drizzle-developers/+archive/ppa

deb http://ppa.launchpad.net/drizzle-developers/ppa/ubuntu jaunty main

That should get you through the hard times.

As soon as I've got something I'm happy with upstream, I'll submit to
MOTU as well.

Monty

[spark (dc04)]

changelog mentions:

  * libgoogle-perftools0's architecture is now i386. The upstream supports this module for x86 and x86_64. However, x86_64 requires libunwind's development head, which Debian does not have yet.

see also:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530885

[spark (dc04)]

Ah thanks Monty, i hadn't updated in time to see your post before adding another comment :)

[Monty Taylor (mordred)]

spark wrote:
> changelog mentions:
>
> * libgoogle-perftools0's architecture is now i386. The upstream
> supports this module for x86 and x86_64. However, x86_64 requires
> libunwind's development head, which Debian does not have yet.

There is also a set of libunwind packages in the ~drizzle-developers PPA.

[Monty Taylor (mordred)]

Working on this with debian upstream packager. I'll get it uploaded here as soon as we have it.

[Scott MacVicar (scottmac)]

This has been fixed upstream in February, any plans to include this in lucid?

As far as I can see nothing depends on libtcmalloc-minimal0 or libgoogle-perftools0. There has also been a version bump to 1.5 so the packages can have the 0 changes to a 1 to avoid breaking anything.

[Fabrice Coutadeur (fabricesp)]

Fixed in 1.5-1 (builds fine in amd64)

[Matt Ingenthron (ingenthr)]

I didn't see how to reopen this, so I opened bug 69480. Pardon my launchpad n00bness.

The issue in bug 69480 is exactly the same, it just needs to be applied to Karmic.

[Matt Ingenthron (ingenthr)]

Make that bug 689480.