Sync google-perftools 1.5-1 (universe) from Debian unstable (main)

Bug #519996 reported by Roman Shtylman
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
google-perftools (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Please sync google-perftools 1.5-1 (universe) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
New upstream versions. Ubuntu version is outdated.

Changelog entries since current lucid version 0.98-1ubuntu1:

google-perftools (1.5-1) unstable; urgency=low

  * New upstream release (Closes: #521935)
  * Now this package will be built on i386, amd64 and powerpc
    (Closes: #387401, #506679, #556908)
  * debian/control: Bumped up Standards-Version to 3.8.4.

 -- Daigo Moriwaki <email address hidden> Sun, 07 Feb 2010 09:57:09 +0900

google-perftools (1.4-3) unstable; urgency=low

  * debian/control: Bumpled up Standards-Version to 3.8.3.
  * debian/control: google-perftools package now recommends graphviz and gv.
    (Closes: #507823)
  * debian/{control|rules}: autoconf and automake will be executed in a build
    time. (Closes: #558508)

 -- Daigo Moriwaki <email address hidden> Mon, 30 Nov 2009 21:53:39 +0900

google-perftools (1.4-2) unstable; urgency=low

  * debian/control, debian/rules: Added a new package, google-perftools, which
    contains command line utilities. (Closes: #547956)

 -- Daigo Moriwaki <email address hidden> Mon, 26 Oct 2009 20:19:18 +0900

google-perftools (1.4-1) unstable; urgency=low

  * New upstream release. (Closes: #537269)
  * debian/control:
    - Bumped up Standards-Version to 3.8.2.
    - Build-depends on libunwind. (Closes: #487374)
    - Provides debugging symbol packages: libtcmalloc-minimal0-dbg and
      libgoogle-perftools0-dbg.
  * Merged contents of
    - debian/libgoogle-perftools0.docs
    - debian/libgoogle-perftools0.manpages
    - debian/docs
    - debian/libtcmalloc-minimal0.dirs
    - debian/libgoogle-perftools-dev.dirs
    - debian/libtcmalloc-minimal0.install
    - debian/libgoogle-perftools0.dirs
    - debian/libgoogle-perftools-dev.install
    - debian/libgoogle-perftools0.install
    into debian/rules.

 -- Daigo Moriwaki <email address hidden> Sat, 19 Sep 2009 00:10:06 +0900

Revision history for this message
Stephan Rügamer (sruegamer) wrote :

Hi,

libunwind7-dev is missing from our archives,
but it's being needed for amd64

Transscript of buildlog:

Automatic build of google-perftools_1.5-1 on buildserver01 by sbuild/amd64 0.57.7
Build started at 20100210-1834
******************************************************************************
/usr/bin/apt-get -q update
Hit http://172.24.14.27 lucid Release.gpg
Hit http://172.24.14.27 lucid Release
Hit http://172.24.14.27 lucid/main Packages
Hit http://172.24.14.27 lucid/restricted Packages
Hit http://172.24.14.27 lucid/universe Packages
Hit http://172.24.14.27 lucid/multiverse Packages
Reading package lists...
google-perftools_1.5-1.dsc exists in .; copying to chroot
** Using build dependencies supplied by package:
Build-Depends: cdbs, autoconf, automake1.9, libtool, patchutils, debhelper (>= 7.0.0), binutils, libunwind7-dev [!i386]
Build-Conflicts: autoconf2.13, automake1.4
Checking for already installed source dependencies...
W: Unable to locate package libunwind7-dev
cdbs: missing
autoconf: missing
automake1.9: missing
libtool: missing
patchutils: missing
debhelper: missing
Using default version 7.4.11ubuntu1
binutils: already installed (2.20-5ubuntu1)
libunwind7-dev: missing
autoconf2.13: already deinstalled
automake1.4: already deinstalled
Checking for source dependency conflicts...
Reading package lists...
Building dependency tree...
Reading state information...
E: Couldn't find package libunwind7-dev
apt-get failed.
Package installation failed
Trying to reinstall removed packages:
Trying to uninstall newly installed packages:
Source-dependencies not satisfied; skipping google-perftools
Not removing build depends: cloned chroot in use

Regarding the changelog google-perftools is building now on amd64 and i386...but doesn't :)

Please check,
\sh

Revision history for this message
Roman Shtylman (shtylman) wrote :

According to: https://launchpad.net/ubuntu/+source/libunwind the package does exist in our archive? Am I miss-understanding something?

Revision history for this message
Michael Bienia (geser) wrote :

In Debian libunwind7 exists now on amd64 too (formerly only on ia64). Both Debian and Ubuntu has libunwind in P-a-S restricting it to build only on ia64. The Debian amd64 debs got directly uploaded with the source (so circumvented P-a-S).
To get a libunwind build for amd64 on Ubuntu amd64 has to be added to the libunwind entry in P-a-S.

Revision history for this message
Benjamin Drung (bdrung) wrote :

Looking at https://savannah.nongnu.org/news/?group=libunwind, the package should build on x86, x86_64, ARM, MIPS, and PowerPC. So why not change the Architecture to any?

Revision history for this message
Stephan Rügamer (sruegamer) wrote :

Moins,

the libunwind source is only build on ia64, not on amd64 neither on i386
https://edge.launchpad.net/ubuntu/+source/libunwind/0.99-0.2

You are right, when you say, it should be build on all other archs.

As Michael stated, please ask someone from the buildd admins team to unbreak libunwind to be accepted and build also for the other archs != ia64

Regards,

\sh

PS: I'm taking this bug pls update this report when we are able to have libunwind built on all other archs,
Thx :)

Revision history for this message
Stephan Rügamer (sruegamer) wrote :

not removing sponsors, but assigning it to me.

Changed in google-perftools (Ubuntu):
assignee: nobody → Stephan Hermann (shermann)
status: New → Confirmed
Revision history for this message
StefanPotyra (sistpoty) wrote :

libunwind currently FTBFS on i386/amd64, so it needs fixing first.

Revision history for this message
Stephan Rügamer (sruegamer) wrote :

@Stefan:

baeh...so
a) fixing libunwind
b) removing libunwind from P-a-S
c) rebuild google-perftools

baeh...

@Roman/Reporter: would you like to do that?

\sh

Revision history for this message
StefanPotyra (sistpoty) wrote :

@Stephan: libunwind build error is strange, might be a problem elsewhere, as the same package builds fine in unstable/amd64

Revision history for this message
Stephan Rügamer (sruegamer) wrote :

Found the fix in fedoras rpm cvs.
It's a sideissue with newer GLIBC

See https://bugs.edge.launchpad.net/ubuntu/+source/libunwind/+bug/522106 for the real bug ;)

Uploaded a fixed libunwind already, and now we need to un-P-a-S libunwind for i386 and amd64

Revision history for this message
Benjamin Drung (bdrung) wrote :

You need a Feature Freeze exception [1] for the sync. Either delay your request to lucid+1 or provide the required information for the freeze exception.

[1] https://wiki.ubuntu.com/FreezeExceptionProcess

Revision history for this message
Ilya Barygin (randomaction) wrote :

Unsubscribing ubuntu-universe-sponsors for now, please resubscribe if/when the exception has been granted.

Revision history for this message
Fabrice Coutadeur (fabricesp) wrote :
Changed in google-perftools (Ubuntu):
assignee: Stephan Hermann (shermann) → nobody
importance: Undecided → Wishlist
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package google-perftools - 1.5-1

---------------
google-perftools (1.5-1) unstable; urgency=low

  * New upstream release (Closes: #521935)
  * Now this package will be built on i386, amd64 and powerpc
    (Closes: #387401, #506679, #556908)
  * debian/control: Bumped up Standards-Version to 3.8.4.

google-perftools (1.4-3) unstable; urgency=low

  * debian/control: Bumpled up Standards-Version to 3.8.3.
  * debian/control: google-perftools package now recommends graphviz and gv.
    (Closes: #507823)
  * debian/{control|rules}: autoconf and automake will be executed in a build
    time. (Closes: #558508)

google-perftools (1.4-2) unstable; urgency=low

  * debian/control, debian/rules: Added a new package, google-perftools, which
    contains command line utilities. (Closes: #547956)

google-perftools (1.4-1) unstable; urgency=low

  * New upstream release. (Closes: #537269)
  * debian/control:
    - Bumped up Standards-Version to 3.8.2.
    - Build-depends on libunwind. (Closes: #487374)
    - Provides debugging symbol packages: libtcmalloc-minimal0-dbg and
      libgoogle-perftools0-dbg.
  * Merged contents of
    - debian/libgoogle-perftools0.docs
    - debian/libgoogle-perftools0.manpages
    - debian/docs
    - debian/libtcmalloc-minimal0.dirs
    - debian/libgoogle-perftools-dev.dirs
    - debian/libtcmalloc-minimal0.install
    - debian/libgoogle-perftools0.dirs
    - debian/libgoogle-perftools-dev.install
    - debian/libgoogle-perftools0.install
    into debian/rules.
 -- Roman Shtylman <email address hidden> Sun, 07 Feb 2010 09:57:09 +0900

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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