Control: reassign -1 libssl1.1 1.1.0f-1 Control: affects -1 src:simple-tpm-pk11
Looking at the reproducible builds results, I noticed that simple-tpm-pk11 always FTBFS in unstable but never FTBFS in stretch. I confirmed that "make check" always succeeds with libssl1.1 1.1.0e-2 installed and always fails with 1.1.0f-1 installed. On Thu, Jun 01, 2017 at 09:55:02AM +0200, Michael Stapelberg wrote: > Thomas, here are the steps to reproduce using docker. They should be easily > transferrable to a VM: > > % docker run -t -i debian:sid /bin/bash > root# echo deb-src http://deb.debian.org/debian sid main >> > /etc/apt/sources.list > root# apt update > root# apt build-dep simple-tpm-pk11 > root# apt source simple-tpm-pk11 > root# cd simple-tpm-pk11-0.06/ > root# dpkg-buildpackage -b > > The backtrace of the coredump is: > > #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 > #1 0x00007f89a890c3fa in __GI_abort () at abort.c:89 > #2 0x000055cebe316ca5 in testing::internal::posix::Abort () > at /usr/include/gtest/internal/gtest-port.h:2410 > #3 testing::internal::GTestLog::~GTestLog (this=<optimized out>, > __in_chrg=<optimized out>) > at /usr/src/gtest/src/gtest-port.cc:923 > #4 0x000055cebe33d86d in testing::internal::GTestLog::~GTestLog > (this=<optimized out>, > __in_chrg=<optimized out>) at /usr/src/gtest/src/gtest-port.cc:921 > #5 > testing::internal::ThreadLocal<std::vector<testing::internal::TraceInfo, > std::allocator<testing::internal::TraceInfo> > >::~ThreadLocal > (this=<optimized out>, __in_chrg=<optimized out>) > at /usr/include/gtest/internal/gtest-port.h:2044 > #6 testing::internal::UnitTestImpl::~UnitTestImpl (this=0x55cebf698e10, > __in_chrg=<optimized out>) at /usr/src/gtest/src/gtest.cc:4359 > #7 0x000055cebe33d979 in testing::internal::UnitTestImpl::~UnitTestImpl > (this=0x55cebf698e10, > __in_chrg=<optimized out>) at /usr/src/gtest/src/gtest.cc:4367 > #8 0x000055cebe33d461 in testing::UnitTest::~UnitTest ( > this=0x55cebe56d7e0 <testing::UnitTest::GetInstance()::instance>, > __in_chrg=<optimized out>) > at /usr/src/gtest/src/gtest.cc:4307 > #9 0x00007f89a890d910 in __run_exit_handlers (status=0, > listp=0x7f89a8c715d8 <__exit_funcs>, > run_list_atexit=run_list_atexit@entry=true, > run_dtors=run_dtors@entry=true) > at exit.c:83 > #10 0x00007f89a890d96a in __GI_exit (status=<optimized out>) at exit.c:105 > #11 0x00007f89a88f82b8 in __libc_start_main (main=0x55cebe317520 <main(int, > char**)>, argc=1, > argv=0x7ffe994d5118, init=<optimized out>, fini=<optimized out>, > rtld_fini=<optimized out>, > stack_end=0x7ffe994d5108) at ../csu/libc-start.c:325 > #12 0x000055cebe3178ba in _start () > > Any ideas what could cause this? > > On Wed, May 31, 2017 at 4:09 PM, Chris Lamb <la...@debian.org> wrote: > > > Hi Michael, > > > > > Thanks for the report. Do you have a VM in which upstream (Thomas Habets) > > > could reproduce the failure? > > > > I'm inferring from this that you cannot reproduce it yourself? :) > > > > I'm not sure I can provide any more details apart from that it also fails > > on the Reproducible Builds testing framework (as well as my personal laptop > > from which I submitted my bug report): > > > > https://tests.reproducible-builds.org/debian/rb-pkg/ > > unstable/amd64/simple-tpm-pk11.html > > > > > > Regards, > > > > -- > > ,''`. > > : :' : Chris Lamb > > `. `'` la...@debian.org / chris-lamb.co.uk > > `- > > > > > > -- > Best regards, > Michael
