Martin Samuelsson @ 2005-12-30 (Friday), 09:23 (+0100) > I just started rebuilding octave again with DEB_BUILD_OPTIONS set to > "nostrip noopt". Hopefully that will give some clues.
The compilation has finished, but it seems like the build process did not honour DEB_BUILD_OPTIONS. (Debian Policy 10.1 [1]) 12:43|lusa% file /usr/bin/octave-2.1.72 /usr/bin/octave-2.1.72: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.0, dynamically linked (uses shared libs), stripped Unless someone tells me how to easily produce a debugable debian package, I'm not spending more time on this bug. Does anyone know if there is a tool available to simply find out which of the packages that octave2.1 depends on that have been updated in Debian between 2.1.72-5 and 2.1.72-6? -- /Martin 1. http://www.debian.org/doc/debian-policy/ch-files.html#s10.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
