Skip to content

Changelog google-perftools (2.9.1-0ubuntu3)

2022

google-perftools (2.9.1-0ubuntu3) jammy; urgency=medium

   * No-change rebuild for ppc64el baseline bump.

2021

google-perftools (2.9.1-0ubuntu2) impish; urgency=medium

   * No-change rebuild to build packages with zstd compression.

google-perftools (2.9.1-0ubuntu1) hirsute; urgency=medium

   * New upstream version. LP: #1922048.

google-perftools (2.8.1-1ubuntu1) hirsute; urgency=low

   * Merge from Debian unstable. Remaining changes:
     - debian/control: Use multiline syntax for Build-* fields.
     - Build using -fno-strict-aliasing.
     - Enable testing for all architectures by default.
     - Build-depend on libunwind-dev on architectures where available.
     - Disable libunwind on arm64 due to hangs.
     - Ignore test results on arm64 and armhf.
     - Fix wrong execute bit on .install file in packaging.
   * Dropped changes, included upstream:
     - debian/patches/riscv64-porting.patch: Enable building for riscv64.

2020

google-perftools (2.8.1-1) unstable; urgency=medium

   * New upstream release.

google-perftools (2.8-1ubuntu1) hirsute; urgency=low

   * Merge from Debian unstable.  Remaining changes:
     - debian/control: Use multiline syntax for Build-* fields.
     - Build using -fno-strict-aliasing.
     - Enable testing for all architectures by default.
     - Build-depend on libunwind-dev on architectures where available.
     - Disable libunwind on arm64 due to hangs.
     - Ignore test results on arm64 and armhf.
     - Fix wrong execute bit on .install file in packaging.
     - debian/patches/riscv64-porting.patch: Enable building for riscv64.
   * Dropped changes, included upstream:
     - d/p/0001-liberate-gperftools-tests-from-relying-on-fno-builti.patch:
       cherry-pick from upstream to fix build failures with current toolchain
       related to -fno-builtin-XXX.

google-perftools (2.8-1) unstable; urgency=medium

   * New major upstream release:
     - fixes FTBFS with GCC 10 (closes: #957297).
   * Add suggests of libgoogle-perftools-dev to google-perftools
     (closes: #739571).

google-perftools (2.7.90-1) experimental; urgency=medium

   * New major upstream release candidate version.
   * Update patches.
   * Update copyright file.
   * Update Standards-Version to 4.5.0 .

google-perftools (2.7-1ubuntu6) groovy; urgency=medium

   * Update debian/patches/riscv64-porting.patch for riscv64-specific syscall
     constants and marshalling, and ucontext handling.

google-perftools (2.7-1ubuntu5) groovy; urgency=medium

   * debian/patches/riscv64-porting.patch: Enable building for riscv64.

google-perftools (2.7-1ubuntu4) groovy; urgency=medium

   * d/p/0001-liberate-gperftools-tests-from-relying-on-fno-builti.patch:
     cherry-pick from upstream to fix build failures with current toolchain
     related to -fno-builtin-XXX.  Thanks to Aliaksey Kandratsenka
     <alkondratenko@gmail.com>.

google-perftools (2.7-1ubuntu3) groovy; urgency=medium

   * Omit libunwind on risvc64.

google-perftools (2.7-1ubuntu2) focal; urgency=medium

   * Fix wrong execute bit on .install file in packaging.

google-perftools (2.7-1ubuntu1) focal; urgency=low

   * Merge from Debian unstable.  Remaining changes:
     - debian/control: Use multiline syntax for Build-* fields.
     - Build using -fno-strict-aliasing.
     - Enable testing for all architectures by default.
     - Build-depend on libunwind-dev on architectures where available.
     - Disable libunwind on arm64 due to hangs.
     - Ignore test results on arm64 and armhf.
   * Dropped changes, included in Debian:
     - Build-depend on libunwind-dev instead of libunwind8-dev, which is
       now a transitional package.
     - Build for s390x.
     - Use 3.0 (quilt) format instead of cdbs' deprecated simple-patchsys.
     - Rewrite packaging using debhelper sequencer.
     - Build using recent autotools.
   * Dropped changes, superseded in Debian:
     - Don't try to install the profiler libraries on ppc64el.
   * Dropped changes, included upstream:
     - debian/patches/Use-initial-exec-tls-for-libunwind-s-recursion-flag.patch:
       Use initial-exec tls for libunwind's recursion flag.
     - Disable -fno-exceptions to fix test hangs on arm64.
     - Fix ftbfs with glibc-2.27 on ppc64el.

2018

google-perftools (2.7-1) unstable; urgency=medium

   * New upstream release.
   * Fix libprofiler build on ppc64el (closes: #894749).
   * Remove 0001-unbreak-printing-large-span-stats.patch as not needed.
   * Use short debhelper rules format.
   * Make package multiarch (closes: #893928).
   * Reference google-pprof in README (closes: #739572).
   * Update debhelper level to 11:
     - remove dh-autoreconf build dependency.
   * Update Standards-Version to 4.1.4 .
   * New maintainer (closes: #863782).

google-perftools (2.6.90-0.1) unstable; urgency=medium

   * Non-maintainer upload.
   * Upload to unstable.
   * Cherry-pick patches from upstream to fix tests on i386.

google-perftools (2.6.90-0.1~exp) experimental; urgency=medium

   * Non-maintainer upload.
   * Migrate to salsa.debian.org, and convert to git.
   * New upstream release, and use arch list to 'any' for test on experimental
     (Closes: #872511, #837343, #856203, #857275, #761685)
   * Migrate to 3.0 (quilt) format. (Closes: #872512)
   * Build-Dep on libunwind-dev instead of libunwind8-dev. (Closes: #872593)
   * Drop build-dep on binutils. (Closes: #873141)
   * Use standard version 4.1.3.
   * Use multiarch dir as libdir.
   * cdbs: dh-autoreconf.

google-perftools (2.5-2.2ubuntu3) bionic; urgency=medium

   * Don't try to install the profiler libraries on ppc64el.

google-perftools (2.5-2.2ubuntu2) bionic; urgency=medium

   * Fix ftbfs with glibc-2.27 on ppc64el.

2017

google-perftools (2.5-2.2ubuntu1) artful; urgency=medium

   * Merge from Debian. Remaining changes:
     - debian/control: Use multiline syntax for Build-* fields.
     - Use 3.0 (quilt) format instead of cdbs' deprecated simple-patchsys.
     - Rewrite packaging using debhelper sequencer.
     - Build using -fno-strict-aliasing.
     - Build using recent autotools.
     - Build for s390x.
     - debian/patches/Use-initial-exec-tls-for-libunwind-s-recursion-flag.patch:
       Use initial-exec tls for libunwind's recursion flag.
   * Enable testing for all architectures by default.
   * Build-depend on libunwind-dev instead of libunwind8-dev, which is
     now a transitional package.
   * Build-depend on libunwind-dev on architectures where available.
   * Disable libunwind on arm64 due to hangs. (LP: #1595242)
   * Disable -fno-exceptions to fix test hangs on arm64.
   * Ignore test results on arm64 and armhf.

google-perftools (2.5-2.2) unstable; urgency=medium

   * Non-maintainer upload
   * Tweak profiler_unittest.sh so test failures are just counted once
     (Closes: #849132)

google-perftools (2.5-2.1) unstable; urgency=medium

   * Non-maintainer upload
   * Update URL (Homepage, debian/copyright)
   * Ignore result for profiler unit test that fails "randomly" on i386
     (Closes: #849132)

2016

google-perftools (2.5-2) unstable; urgency=medium

   * Provide automatic debug packages rather than -dbg packages.
     (Closes: #838562)
   * Bump up Standards-Version to 3.9.8

google-perftools (2.5-1) unstable; urgency=medium

   * New upstream release. (Closes: #831240)
   * Update watch file
   * Remove patches that the upstream has applied
     - debian/patches/unbreak-heap-profiler-unittest-on-gcc-5.patch
     - debian/patches/unbreak-heap_checker_unittest-on-gcc-5.patch

google-perftools (2.5-0ubuntu4) zesty; urgency=medium

   * debian/patches/Use-initial-exec-tls-for-libunwind-s-recursion-flag.patch:
     Use initial-exec tls for libunwind's recursion flag. (LP: #1647864)

google-perftools (2.5-0ubuntu3) zesty; urgency=medium

   * Don't run the tests on arm64, hanging the buildds.
   * Ignore test results on armhf for a first build.

google-perftools (2.5-0ubuntu2) zesty; urgency=medium

   * New upstream version.
   * Build for s390x.
   * Build using recent autotools.
   * Build-depend on libunwind-dev everywhere.
   * Build using -fno-strict-aliasing.
   * Bump standards version.
   * Rewrite packaging using debhelper sequencer.

google-perftools (2.4-0ubuntu5) xenial; urgency=medium

   * Pass --add-missing to automake to fix build failure.

2015

google-perftools (2.4-0ubuntu4) wily; urgency=medium

   * Build using GCC 5.

google-perftools (2.4-0ubuntu2) wily; urgency=medium

   * Re-enable the build on Aarch64.
   * Disable the tests again on armhf and arm64.

google-perftools (2.4-0ubuntu1) wily; urgency=medium

   * New upstream version.
   * Enable futexes on ARM32 (taken from Fedora).
   * Enable tests everywhere for a first upload.

google-perftools (2.2.1-0.3) unstable; urgency=medium

   * Non-maintainer upload.
   * Apply upstream patches to fix test failures with gcc 5 (closes: #777887)
   * Pass --add-missing to automake to fix build failure.

2014

google-perftools (2.2.1-0.2) unstable; urgency=low

   * Non-maintainer upload.
   * Add actual arm64 support (Closes: #763837)

google-perftools (2.2.1-0.1) unstable; urgency=medium

   * Non-maintainer upload
   * New upstream release. (Closes: #757149)
   * Updated watch file
   * Added ppc64el, arm64 architectures (Closes: #737677)

2013

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

   * Now builds with automake 1.11. (Closes: #724381)
     Thanks to Eric Dorland for a patch.

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

   * New upstream release. (Closes: #701378)
   * debian/rules:
     - Enable tests on amd64 and i386. (Closes: #695293)
   * debian/control:
     - Add missing dependency on libunwind8-dev for amd64 architecture
       to libgoogle-perftools-dev. (Closes: #706860)
     - Add new architectures: armel armhf. (Closes: #695308)
     - Bumped up Standards-Version to 3.9.4.
   * Removed debian/patches/20120708_ppc_ftbfs.patch, which has been applied by
     the upstream.

2012

google-perftools (2.0-4) unstable; urgency=low

   * Added debian/patches/20121013-pprof.1.patch: Corrects a link.
     Thanks to Junichi Uekawa for reporting.  (Closes: #690313)

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

   * debian/patches/20120708_ppc_ftbfs.patch: Imported Ubuntu's patch, fixing
     a build failure on powerpc, derived from the upstream:
     http://code.google.com/p/gperftools/issues/detail?id=431
     Thanks to James Page <james.page@ubuntu.com>. (Closes: #680305)
   * debian/control: Bumped up to libunwind8-dev for Build-Depends.
     (Closes: #680724)

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

   * Some include files were left out of the package.
     Thanks to Laszlo Boszormenyi for a patch.  (Closes: #666099)

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

   * New upstream release.
     (Closes: #663652, #635038)
   * debian/watch: Followed the new upstream site.
   * debian/control:
     - Followed the new upstream site.
     - Bumped up Standards-Version to 3.9.3.
     - google-perftools depends on curl.  (Closes: #630829)
     - Updated the package names to match soname 4.
   * debian/copyright:
     - Followed the upstream' changes.
     - Applied copyright-format 1.0.
   * debian/compat:
     - Bumped up the compatibility level to 7.

2011

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

   * New upstream release
   * Updated debian/watch.
   * debian/control:
     - removed the meaningless google-perftools-dbg package.
     - google-perftools that only includes a perl script is now Architecture:
       all.
     (Closes: #595184)
     - Bumped up Standards-Version to 3.9.1.
   * debian/copyright: packaged by myself.

2010

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.

2009

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.

2008

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

   * New upstream release. (Closes: #425147)
   * Compiled with GCC 4.3. (Closes: #454841)
   * debian/watch: can now report upstream's version (Closes: #450294)
   * Because of a file conflict between tau and libgoogle-perftools the
     binary pprof is renamed as google-pprof. (Closes: #404001)
     Great thanks to Michael Mende.
   * debian/rules: autoconf files are now generated at the build time.
   * Bumped up Standards-Version to 3.7.3, no changes are required.
   * Split a new package, libtcmallc_minimal0. The upstream supports
     this module for wider platforms. So I leave its architecture to be
     `any'.
   * 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.
   * Removed an unnecessary patch, debian/patches/02_profiler.cc_alpha.diff.

2007

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

   * New upstream release
   * The hosting site of the upstream has been changed.

2006

google-perftools (0.8-5) unstable; urgency=low

   * Apply a patch from Yauheni Kaliuta to fix an error, 'sys_mmap' has not
     been declared, which may happen with Linux kernel 2.6.18.
     (Closes: #397908)

google-perftools (0.8-4) unstable; urgency=low

   * Fixed FTBFS (alpha) again. debian/patches/01_configure.ac_alpha.diff is no
     longer provided. Instead, configure.ac and configure are directly updated
     to be correctly built. (Closes: #387401)

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

   * Use DEB_AUTO_UPDATE_AUTOCONF to rebuild configure from patched
     configure.ac.
   * Fixed debian/watch file.

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

   * Make pathces for FTBFS (alpha). Thanks to Falk Hueffner. (Closes: #384236)
     (debian/patches/01_configure.ac_alpha.diff,
      debian/patches/02_profiler.cc_alpha.diff)

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

   * Remove the patches (thread_lister.c.diff and malloc_hook.cc.diff) that
     were included in the previous release because the upstream has fixed the
     issues.

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

   * Make a patch (debian/patches/thread_lister.c.diff) for FTBFS: error:
     conflicting types for 'ResumeAllProcessThreads' (Closes: #370449)
   * Make a patch (debian/patches/malloc_hook.cc.diff) for FTBFS:
     src/malloc_hook.cc:118: error: invalid conversion from 'long int' to
     'void*' (Closes: #370802)
   * Add a debian/watch file.

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

   * New upstream release.

2005

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

   * Initial release.