Re: afflib fails to build on some architectures
* Simson Garfinkel sims...@acm.org [20091213 01:15]: I have had a persistent problem getting the tests to work because the binary and test files are in different locations when I am do a make check vs. a make distcheck. The directory where the binaries are is set to be read-only in some cases but not in other cases. There is a file that is distributed which ends up I-dont-know-where. If you can show me a list of all of the environment variables at my disposal for the test scripts and how they are supposed to be used, I can put out a bug fix within the next 24 hours. Sadly I can't reproduce it via *manually* building it on an affected plattform as it works within the following environment: agricola% env LC_MESSAGES=en_US.UTF-8 LANG=C USER=mika LOGNAME=mika HOME=/home/mika PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games MAIL=/var/mail/mika SHELL=/bin/zsh SSH_CLIENT=[...] SSH_CONNECTION=[...] SSH_TTY=/dev/pts/2 TERM=screen SHLVL=2 PWD=/home/mika/afflib-3.5.2+dfsg OLDPWD=/home/mika _=/usr/bin/env % debuild -us -uc [...] dpkg-deb: building package `libafflib0' in `../libafflib0_3.5.2+dfsg-1_armel.deb'. dpkg-deb: building package `libafflib-dev' in `../libafflib-dev_3.5.2+dfsg-1_armel.deb'. dpkg-deb: building package `afflib-dbg' in `../afflib-dbg_3.5.2+dfsg-1_armel.deb'. dpkg-deb: building package `afflib-tools' in `../afflib-tools_3.5.2+dfsg-1_armel.deb'. Could the empty TERM variable (as mentioned in https://buildd.debian.org/status/package.php?suite=unstablep=afflib#fail-afflib-armel) be related to the issue? Any race conditions depending on the power of the build machine? regards, -mika- signature.asc Description: Digital signature ___ forensics-devel mailing list forensics-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/forensics-devel
afflib fails to build on some architectures
[Please CC me on replies as I'm not subscribed to the aff-discuss list, thanks.] Hi, I'm member of the Debian forensics team and wanted to inform you that we noticed a problem with building afflib on some architectures: https://buildd.debian.org/status/package.php?suite=unstablep=afflib As you can see the tests fail at/with: af_open(blank.aff): No such file or directory ENCRYPTED SEGMENTS IN BLANKE.AFF --- STOP FAIL: test_passphrase.sh The bugs are reported in Debian's BTS at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552049 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549832 As this is a showstopper for afflib being shipped with the upcoming stable release of Debian I'd appreciate any help so we can resolve this issue. Do you have any ideas how we could fix this issue (without having to disable the tests of course :))? BTW: We already have a patch which addresses a bashism issue in the tools/test_*.sh scripts. You're welcome to apply it in your upstream tree: http://patch-tracker.debian.org/patch/series/dl/afflib/3.5.2+dfsg-1/03-bashism.patch PS: The mailaddress referenced in the source tree where bugreports should be sent to is broken (mails to b...@afflib.org just bounce), Cc-ing Simson directly therefore. Thanks. regards, -mika- signature.asc Description: Digital signature ___ forensics-devel mailing list forensics-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/forensics-devel
afflib fails to build on some architectures
Hi, I'm member of the Debian forensics team and wanted to inform you that we noticed a problem with building afflib on some architectures: https://buildd.debian.org/status/package.php?suite=unstablep=afflib As you can see the tests fail at/with: af_open(blank.aff): No such file or directory ENCRYPTED SEGMENTS IN BLANKE.AFF --- STOP FAIL: test_passphrase.sh The bugs are reported at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552049 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549832 As this is a major showstopper for afflib being shipped with the upcoming stable release of Debian I'd appreciate any help so we can resolve this issue. Do you have any ideas how we could fix this issue? PS: We already have a patch which addresses a bashism issue in the tools/test_*.sh scripts. You're welcome to apply it in your upstream tree: http://patch-tracker.debian.org/patch/series/dl/afflib/3.5.2+dfsg-1/03-bashism.patch Thanks for any assistance. regards, -mika- signature.asc Description: Digital signature ___ forensics-devel mailing list forensics-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/forensics-devel