Hi,

I'm the author of source-highlight; I seem to understand that that
failing test is actually wrong, isn't it?

Changes:
 source-highlight (3.1.6-1.3) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Use even more "wrong" regex in lib/tests_test_regexranges_main.cpp,
     since "{notclosed" is actually a valid perl regular expression
     (unmatched {}, is silently treated as literal string) (Closes:
     #724089)

so how should I fix that? Is there a patch I can apply upstream?

thanks in advance
        Lorenzo

On 22/09/2013 21:14, David Suárez wrote:
> Source: source-highlight
> Version: 3.1.6-1.2
> Severity: serious
> Tags: jessie sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20130922 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
>> ====================
>> 1 of 36 tests failed
>> ====================
>> make[4]: *** [check-TESTS] Error 1
>> make[3]: *** [check-am] Error 2
>> make[2]: *** [check-recursive] Error 1
>> make[1]: *** [check-recursive] Error 1
>> dh_auto_test: make -j1 check returned exit code 2
> 
> The full build log is available from:
>    
> http://aws-logs.debian.net/ftbfs-logs/2013/09/22/source-highlight_3.1.6-1.2_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
> 


-- 
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to