package dependencies broken or missing

Bug #689480 reported by Matt Ingenthron
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
google-perftools (Ubuntu)
Fix Released
Undecided
Unassigned
Lucid
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: google-perftools

This seems to be related to bug #359736, but I could not reopen it and even though it's marked as fixed, I see the issue in Karmic.

# apt-get install libgoogle-perftools-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  libgoogle-perftools-dev: Depends: libgoogle-perftools0 (= 0.98-1ubuntu1) but it is not going to be installed
E: Broken packages

And, in fact it appears to have the same downrev package as identified in bug 359736.
See http://packages.ubuntu.com/karmic/libgoogle-perftools0

Revision history for this message
Matt Ingenthron (ingenthr) wrote :

By the way, it works as expected on 32bit, based on what I see above.

Revision history for this message
Matt Ingenthron (ingenthr) wrote :

Incidentally, I grabbed the sources of the existing package, changed the architecture to "any" and was able to build the package with the appropriate flags on 64-bit. No code changes are needed, I merely changed Architecture to "any" on the control file for the libgoogle-perftools0 package.

Revision history for this message
Phil M (unmobile+ubuntu) wrote :

I'm seeing this exact issue on Lucid amd64. This is an LTS release, and a rather useful library. Any chance we'll see this corrected?

Revision history for this message
Stuart Campbell (stuartcampbell) wrote :

Any chance that Lucid can go to 1.5 ? Since that seems to work for amd64 ok.

Otherwise, it is a bit bad that this sort of problem is present in an LTS release.

Changed in google-perftools (Ubuntu):
status: New → Confirmed
Revision history for this message
Kendall Gifford (zettabyte) wrote :

Also having this problem in lucid and would love a fix. I second Stuart's comments: something like this existing (still) in an LTS release (about 15 months old) where the fix (apparently) doesn't require any actual code changes... well, I'll just say I'd love a fix. I'd do the work too but I'm not familiar with contribution requirements for debia^H^H^H^H^Hubuntu.

Revision history for this message
Patrick Allaert (patrick-allaert) wrote :

*Bump*

Still having this problem on Lucid.

Open for more than one year now, it would be good if this can be fixed once and for all...

Thanks!

James Page (james-page)
Changed in google-perftools (Ubuntu):
status: Confirmed → Fix Released
Changed in google-perftools (Ubuntu Lucid):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in google-perftools (Ubuntu Lucid):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.