Your message dated Fri, 3 Feb 2017 13:29:29 +0100 with message-id <CAOkSjBirXY3i8=rypmycyc7dpcxzzvjibm_-csewryjo5ke...@mail.gmail.com> and subject line Re: Processed: Problem is also in the version in stretch has caused the Debian Bug report #853931, regarding FTBFS: dh_install: debian/suricata-hyperscan.install returned exit code 127 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 853931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: suricata Version: 3.2-2~bpo8+1 Severity: serious Justification: FTBFS Hi, 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 result. 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
--- End Message ---
--- Begin Message ---Control: notfound -1 3.2-2 On 3 February 2017 at 13:14, Adrian Bunk <b...@debian.org> wrote: >> >> Do you mean that the same source package FTBFS using debian stretch only? > > The "build dependencies are not strict enough" problem is also in 3.2-2. > > stretch might happen to have recent enough versions, but this doesn't > change the fact that the build dependencies are not strict enough. > I just tested the arm64 stretch build, with no issues. This bug doesn't affect stretch. I think we are not in position of doing a upload targeting stretch a this point. Closing this bug now. Please, feel free to reopen if you would like to further discuss this. best regards.
--- End Message ---
