On 06/09/15 12:43, Kari Pahula wrote: > Here's quick steps to test that the library works correctly.
Thanks, this is very useful information. Could you automate this as an autopkgtest[1], please? (... although I will admit that I haven't been actively looking for autopkgtests or test information in README.source when NMUing or sponsoring for these transitions, only test-building rdeps against the new version, because it's a massive transition, and the small number of people who have been uploading most of the packages just don't scale very well. I've essentially been following vorlon's advice from <https://lists.debian.org/debian-devel/2015/08/msg00298.html>.) [1] https://anonscm.debian.org/gitweb/?p=autopkgtest/autopkgtest.git;a=blob_plain;f=doc/README.package-tests.rst;hb=HEAD > mkdir -p /tmp/gecode > cd /tmp/gecode > cp -r /usr/share/doc/libgecode-doc/examples . > cd examples > make > ./all-interval Works for me, in an up-to-date sid chroot with libgecode* and pkg-config... > I got a segfault with that. Running with gdb placed it in > libQtGui.so.4: > Program received signal SIGSEGV, Segmentation fault. > 0x00007ffff37c7144 in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 ... although my build of the examples used Qt 5 (not through anything I did deliberately, it's just what happens when I follow your instructions), which means a segfault in libQtGui.so.4 would have come as quite a surprise to me :-) I picked a few other random executables from the build you described, and they all seem to produce some sort of a result without crashing. S
