[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#853931: FTBFS: dh_install: debian/suricata-hyperscan.install returned exit code 127

Source: suricata
Version: 3.2-2~bpo8+1
Severity: serious
Justification: FTBFS


the suricata package fails to build from source in jessie-backports [0] in
several architectures, in which hyperscan is not available.

The pattern is always the same:

	cp -a ./debian/tmp/dh-exec.3aIscV32/usr/bin/suricata.generic debian/suricata//usr/bin//
	cp -a ./debian/build-tmp/suricata-no-hs/usr/bin/suricatasc debian/suricata/usr/bin/
	install -d debian/suricata/usr/lib
	cp -a ./debian/build-tmp/suricata-no-hs/usr/lib/python2.7 debian/suricata/usr/lib/
Failed to copy 'debian/build-tmp/suricata-hs/usr/bin/suricata': No such file or directory at /usr/share/dh-exec/dh-exec-install-rename line 32, <> line 1.
dh_install: problem reading debian/suricata-hyperscan.install: 
debian/rules:76: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 127

Files d/control, d/rules and d/*.install all seem fine: they specify in which
architectures the hyperscan-enabled package should be built.

I was able to reproduce the issue in an arm64 porterbox.

Sascha pointed to bug #698054 [1] in debhelper, but I tried debhelper
10.2.2~bpo8+1 from jessie-backports again in an arm64 porterbox with the same

So, we keep investigating.

[0] https://buildd.debian.org/status/package.php?p=suricata&suite=jessie-backports
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698054

Reply to: