Hi, As a result of this bug, dico will be out of testing. I've tried reaching to Ahmed but haven't had any reply.
As is mentioned in the bug, the build failure has to do with test suite. The packaging already carries a patch that fixed similar build failure in the past. I have zero knowledge about these guile testcases, so have reached out to upstream (email/logs attached) folks hoping they may have some input. Worst case, is it okay to prepare an (NMU) upload with the test suite disabled ? I'd not want to see this package out of testing. Ritesh On Sat, 2016-07-30 at 10:51 +0000, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > > > #I'm trying to reach out to upstream for help. Worst case, I'll upload a > > build with testcases disabled > > tags 819835 + confirmed > Bug #819835 [src:dico] dico: FTBFS in testing (test suite fails) > Added tag(s) confirmed. > > > > thanks > Stopping processing here. > > Please contact me if you need assistance. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
--- Begin Message ---Hello Sergey and others, Could you please help me with dico testcase failures which have begun recently? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819835 This bug has ended making dico unfit for release and I'd like to see this fixed. My fallback option is to disable tests, but I'd rather prefer if you could help with the test failure. Note: The same build used to build fine earlier. But I see a guilde-2.x patch to make it build earlier too. So my guess is something further broke in the testcases. Attached is the failing test log. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
testsuite.log.gz
Description: application/gzip
signature.asc
Description: This is a digitally signed message part
--- End Message ---
signature.asc
Description: This is a digitally signed message part