Bug#1057621: valgrind should not drop valgrind-dbg

Hi - Please beware a possible naming confusion: "valgrind-gdb" vs "valgrind-dbg". The former is a relatively recently added subpackage for gdb interfacing support, and has nothing to do with valgrind's own debuginfo. - FChE

Bug#1055418: systemtap: autopkgtest regression: Pass 4: compilation failed. [man error::pass4]

Hi - > Version: 4.9-1 > https://ci.debian.net/data/autopkgtest/testing/amd64/s/systemtap/39374282/log.gz > > 223s /usr/share/systemtap/runtime/linux/print.c:367:46: error: ‘struct > module’ has no member named ‘core_text_size’; did you mean > ‘kprobes_text_size’? > 223s 367 |(un

Bug#892995: systemtap: failes to compile scripts, implicit declaration of some functions

Hi - > Package: systemtap > Version: 3.1-3 > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) > [...] Due to the absence of a fixed kernel API, newer systemtap versions are required to deal with newer kernels. The particular errors lis

Bug#856474: stap: include runtime_defines.h not found

Hi - On Thu, Mar 02, 2017 at 01:25:03PM -0800, Gerald Turner wrote: > FWIW, I attempted to kludge around the mangled include argument by > running stap with "-B 'EXTRA_CFLAGS += -I/usr/share/systemtap/runtime'". > This seems to work around the compilation failure of missing > runtime_defines.h in

Bug#750943: stunnel4: init script missing lsb-required status target

Peter, thanks for replying and for maintaining stunnel. > I do agree that not having a 'status' init script command is, to put it > mildly, a major nuisance, and I thank you for your work on it! Yeah, I just finally upgraded my last couple of hold-outs to wheezy and it took two tries to build a

Bug#750943: stunnel4: init script missing lsb-required status target

Package: stunnel4 Version: 3:4.53-1.1 Severity: serious Tags: upstream patch Justification: Policy 9.3 The stunnel4 init script is missing 'status' support. This makes it impossible to programatically tell whether stunnel4 is properly running. This makes stunnel4 unusable in high-availability en

Bug#678804: maelstrom: FTBFS on armhf: netlogic/liblogic.a: could not read symbols: Bad value

This looks like dpkg-buildflags injects some options that don't work on all platforms. Especially the '-fPIE' option looks like the culprit. Are these flags the same on all build machines? Do you have any ideas what is so special about 'armhf' in this case, as it is the only platform that has this

Bug#395484: systemtap: FTBFS: perfmon3/pfmlib.h: No such file or directory

Hi - On Fri, Oct 27, 2006 at 12:05:53PM +0200, Julien Danjou wrote: > There was a problem while autobuilding your package: > > > if i486-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I. -DBINDIR='"/usr/bin"' > > -DPKGDATADIR='"/usr/share/systemtap"' -DPKGLIBDIR='"/usr/lib/systemtap"' > > -DPERFMON