Source: sslh
Version: 1.13b-3
Severity: serious
Tags: wheezy sid
User: [email protected]
Usertags: qa-ftbfs-20120814 qa-ftbfs
Justification: FTBFS in wheezy on amd64

Hi,

During a rebuild of all packages in *wheezy*, your package failed to
build on amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> ./t
> Can't exec "lcov": No such file or directory at ./t line 37.
> Testing sslh-select
> spawned 10495
> ./sslh-select -v -f -u user --listen localhost:9002 --ssh ip6-localhost:9000 
> --ssl ip6-localhost:9001 -P /tmp/sslh_test.pid
> ssh addr: localhost:9000. libwrap service: sshd family 2 2
> ssl addr: localhost:9001. libwrap service: (null) family 2 2
> listening on:
>       localhost:9002
>       localhost:9002
> timeout to ssh: 2
> listening to 2 addresses
> localhost:9002:bind: Address already in use
> ***Test: SSL connection
> Connection refused
> ***Test: Shy SSH connection
> Connection refused
> ***Test: Bold SSH connection
> Connection refused
> ***Test: One SSL half-started then one SSH
> Connection refused
> ***Test: One SSH half-started then one SSL
> Connection refused
> ***Test: big message
> Connection refused
> ***Test: Stalled connection
> Connection refused
> Connection refused
> cat: /tmp/sslh_test.pid: No such file or directory
> killing 
> Can't kill a non-numeric process ID at ./t line 194.
> # Looks like your test exited with 1 before it could output anything.
> make[1]: *** [test] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/08/14/sslh_1.13b-3_wheezy.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.


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to