Bug#1065167: google-perftools: FTBFS on armhf/armel: static_assert(sizeof(int32_t) == sizeof(off_t), "")

/02adc8ceab39bbeac1f65e10bde577e1753094fa . On Fri, Mar 1, 2024 at 4:32 PM Aliaksey Kandratsenka < alkondrate...@gmail.com> wrote: > Hi. Upstream maintainer here. Please cherry-pick: > https://github.com/gperftools/gperftools/commit/198b3dd2d0b4d83c873b2ce480837edacc0f35ab > > > On

Bug#1065167: google-perftools: FTBFS on armhf/armel: static_assert(sizeof(int32_t) == sizeof(off_t), "")

Hi. Upstream maintainer here. Please cherry-pick: https://github.com/gperftools/gperftools/commit/198b3dd2d0b4d83c873b2ce480837edacc0f35ab On Fri, Mar 1, 2024 at 6:15 AM Emanuele Rocca wrote: > Source: google-perftools > Version: 2.15-1.1 > Severity: serious > Tags: ftbfs > User:

Bug#1062116: google-perftools: NMU diff for 64-bit time_t transition

Hi. Upstream maintainer here. Thanks for bringing this up. To my knowledge only cpu profiler bits expose time_t. So libtcmalloc-minimal4 is worth keeping as is. On Wed, Jan 31, 2024 at 7:21 AM Graham Inggs wrote: > Source: google-perftools > Version: 2.15-1 > Severity: serious > Tags: patch

Bug#1049383: google-perftools: please don't ship pprof from gperftools anymore

On Tue, Aug 15, 2023 at 2:22 PM László Böszörményi (GCS) wrote: > Hi Aliaksei, > Hi. > > Thanks for the heads-up. To help my work, please tag releases of the > Go pprof tool for: > - let me know how mature it is, > Google has used it internally for something on the order of 10 years. That

Bug#957297: should be fixed by 2.8 release

hi. I just tagged 2.8 that has a couple fixes for test failures in gcc 10. So should be fixed now.

Bug#831240: google-perftools: FTBFS: Running death test 0 hangs

On my machine this is passing reliably. Given that KVM virtual machine image was mentioned, maybe someone can share KVM image where this is failing? I am still eager to debug this. On Sun, Sep 18, 2016 at 4:07 AM, Santiago Vila wrote: > > On Fri, 16 Sep 2016, Lucas Nussbaum

Bug#831240: google-perftools: FTBFS: Running death test 0 hangs

On Thu, Jul 21, 2016 at 3:18 AM, Santiago Vila wrote: > severity 831240 important > reopen 831240 > > On Thu, 21 Jul 2016, Lucas Nussbaum wrote: > >> I recently discovered that the official Debian images on AWS EC2 include >> some sysctl tunings (see >>

Bug#831240: google-perftools: FTBFS: Running death test 0 hangs

On Tue, Jul 19, 2016 at 1:29 PM, Lucas Nussbaum <lu...@debian.org> wrote: > Hi Aliaksey, > > On 16/07/16 at 12:28 +0200, Santiago Vila wrote: >> On Fri, 15 Jul 2016, Aliaksey Kandratsenka wrote: >> >> > Thanks for reporting the issue. I just tried to reprodu

Bug#831240: google-perftools: FTBFS: Running death test 0 hangs

Thanks for reporting the issue. I just tried to reproduce the problem on my sid laptop in cleanly deboostrap-ed sid chroot and was unable to hit this issue. This maybe indicates that kernel matters or maybe there is something else in the host that is relevant. Can you please share more details on

Bug#777887: google-perftools: diff for NMU version 2.2.1-0.3

Hi all. I'm maintainer of upstream gperftools. Please keep in mind that latest release is gperftools 2.4 and we've moved to github.com/gpeftools/gperftools On Sat, Feb 20, 2016 at 8:49 AM, Julien Cristau wrote: > Control: tags 777887 + patch > Control: tags 777887 + pending

Bug#805536: google-perftools: --help refers to pprof but Debian command is google-pprof

On Thu, Nov 19, 2015 at 1:40 AM, Sandro Tosi wrote: > Source: google-perftools > Severity: minor > > Hello, > the --help output refers to pprof but in Debian the binary has been renamed to > google-pprof: Next gperftools release should have a fix:

Bug#777887: This is being fixed upstream

Hi. Upstream maintainer here. This is fixed upstream. Albeit not in any released version yet. But notable thing is that only tests are broken on gcc 5, not actual code.

Bug#743409: google-perftools: Reports strcmp() as __nss_hosts_lookup()

Hi. Upstream maintainer here. I've seen some similar issues myself which look like something with debug info (pprof is getting function names from addr2line tool). I'll investigate further. You can track my progress at matching upstream bug: https://github.com/gperftools/gperftools/issues/1

Bug#589442: libmemcached-tools is missing memcslap

Package: libmemcached-tools Version: 0.40-1 manpage for that command is present, but memcslap binary is missing.

Bug#574947: global: newer release (3.8.1) is available

Package: global Version: 5.7.1-1 Severity: wishlist -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32.9-alk64 (SMP w/2 CPU cores) Locale: LANG=be_BY.UTF-8,

Bug#564837: filehighlight.ini is not included into .deb, which leads to lack of filename highlighting

Package: mc Version: 3:4.7.0-1 Severity: minor -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32.3-alk (SMP w/2 CPU cores; PREEMPT) Locale: LANG=be_BY.UTF-8,

Bug#463677: undefined symbol: avahi_init_i18n (/usr/lib/libavahi-ui.so.0)

Hi. Updating libavahi-common3 solved issue for me. This looks like missing dependency. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]