Re: [mod-security-packagers] ModSecurity 3.x (almost) enters Debian
Brought to you by:
victorhora,
zimmerletw
From: Ervin H. <ai...@gm...> - 2018-10-19 20:47:53
|
Hi folks, On Fri, Oct 19, 2018 at 07:34:48PM +0200, Alberto Gonzalez Iniesta wrote: > Neither can I, that's why I asked for help :-) > Those errors are from build daemons. Logs: > > > > > https://buildd.debian.org/status/package.php?p=modsecurity&suite=sid just a quick notice: on this list, I just found logfile for i386: https://buildd.debian.org/status/fetch.php?pkg=modsecurity&arch=i386&ver=3.0.2-1&stamp=1539703808&raw=0 but there isn't logfile for amd64. May be there is an architectural difference, which triggers this error - I still can't reproduce on amd64, but the other 3 FAIL test occures with other method. I think that if I can found the reason for these bugs, we can fix it on i386 too. The 3 failed tests occure only in chroot, but all of them comes always. When I leave the chroot, but it's still mounted, I change dir to, and run test again, then I got also error, but for other test case: Test failed. From: test-cases/regression/operator-detectxss.json. Test name: Testing Operator :: @detectXSS. Reason: Debug log was not matching the expected results. Expecting: Added DetectXSS match TX.0: f\(f\(f Debug log: If I build the package out of chroot, all test has passed. I'll continue at weekend. Regards, a. |