Your message dated Sun, 05 Sep 2021 20:22:21 +0200
with message-id <[email protected]>
and subject line Re: Bug#987378: yara breaks golang-github-hillu-go-yara
autopkgtest + ftbfs
has caused the Debian Bug report #987378,
regarding yara causes ftbfs of + autopktest regression in
golang-github-hillu-go-yara
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 [email protected]
immediately.)
--
987378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987378
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: yara, golang-github-hillu-go-yara
Control: found -1 yara/4.1.0~rc2-1
Control: found -1 golang-github-hillu-go-yara/4.0.4-1
Severity: serious
Tags: sid bullseye ftbfs bullseye-ignore
X-Debbugs-CC: [email protected]
User: [email protected]
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of yara the autopkgtest of
golang-github-hillu-go-yara fails in testing when that autopkgtest is
run with the binary packages of yara from unstable. It passes when run
with only packages from testing. In tabular form:
pass fail
yara from testing 4.1.0~rc2-1
golang-github-hillu-go-yara from testing 4.0.4-1
all others from testing from testing
I copied some of the output at the bottom of this report. The same error
can be seen to cause golang-github-hillu-go-yara to FTBFS on
reproducible-builds [0].
Currently this regression is blocking the migration of yara to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?
More information about this bug and the reason for filing it can be found
on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
With my Release Team member hat on, I have set this bug as
bullseye-ignore, as without yara migrating, the packages in testing
don't have a problem. So I really don't mind if this bug is fixed only
after the bullseye release.
Paul
[0]
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-hillu-go-yara.html
[1] https://qa.debian.org/excuses.php?package=yara
https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-hillu-go-yara/11828537/log.gz
=== RUN TestIterator
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x0]
runtime stack:
runtime.throw(0x598548, 0x2a)
/usr/lib/go-1.15/src/runtime/panic.go:1116 +0x72
runtime.sigpanic()
/usr/lib/go-1.15/src/runtime/signal_unix.go:726 +0x4ac
goroutine 11 [syscall]:
runtime.cgocall(0x544ba0, 0xc0000b8dd0, 0x1)
/usr/lib/go-1.15/src/runtime/cgocall.go:133 +0x5b fp=0xc0000b8da0
sp=0xc0000b8d68 pc=0x407ffb
github.com/hillu/go-yara._Cfunc_yr_rules_scan_mem_blocks(0x170c630,
0xc0000e03f0, 0x8, 0x5440f0, 0x16db838, 0xc000000000, 0xc000000000)
_cgo_gotypes.go:1567 +0x4d fp=0xc0000b8dd0 sp=0xc0000b8da0 pc=0x53536d
github.com/hillu/go-yara.(*Rules).ScanMemBlocks.func1(0xc000010098,
0xc0000e03f0, 0x0, 0x5c1fe0, 0xc00000e200, 0x16db838, 0x0, 0x7f9408f51108)
/tmp/autopkgtest-lxc.7gx74fvj/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src/github.com/hillu/go-yara/rules.go:182
+0x145 fp=0xc0000b8e30 sp=0xc0000b8dd0 pc=0x540365
github.com/hillu/go-yara.(*Rules).ScanMemBlocks(0xc000010098, 0x5c3620,
0xc00000e220, 0x0, 0x0, 0x5c1fe0, 0xc00000e200, 0x0, 0x0)
/tmp/autopkgtest-lxc.7gx74fvj/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src/github.com/hillu/go-yara/rules.go:182
+0x277 fp=0xc0000b8ef0 sp=0xc0000b8e30 pc=0x53a377
github.com/hillu/go-yara.TestIterator(0xc000190600)
/tmp/autopkgtest-lxc.7gx74fvj/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src/github.com/hillu/go-yara/mem_blocks_test.go:54
+0xda fp=0xc0000b8f80 sp=0xc0000b8ef0 pc=0x52a4da
testing.tRunner(0xc000190600, 0x59c290)
/usr/lib/go-1.15/src/testing/testing.go:1123 +0xef fp=0xc0000b8fd0
sp=0xc0000b8f80 pc=0x4e206f
runtime.goexit()
/usr/lib/go-1.15/src/runtime/asm_amd64.s:1374 +0x1 fp=0xc0000b8fd8
sp=0xc0000b8fd0 pc=0x471541
created by testing.(*T).Run
/usr/lib/go-1.15/src/testing/testing.go:1168 +0x2b3
goroutine 1 [chan receive]:
testing.(*T).Run(0xc000190600, 0x58fc79, 0xc, 0x59c290, 0x489901)
/usr/lib/go-1.15/src/testing/testing.go:1169 +0x2da
testing.runTests.func1(0xc000001b00)
/usr/lib/go-1.15/src/testing/testing.go:1439 +0x78
testing.tRunner(0xc000001b00, 0xc0000b7cf0)
/usr/lib/go-1.15/src/testing/testing.go:1123 +0xef
testing.runTests(0xc00000e0a0, 0x685300, 0x27, 0x27, 0xc0183cc551984456,
0x8bb3451eea, 0x69a980, 0xc0000b7db8)
/usr/lib/go-1.15/src/testing/testing.go:1437 +0x2fe
testing.(*M).Run(0xc000180000, 0x0)
/usr/lib/go-1.15/src/testing/testing.go:1345 +0x1eb
github.com/hillu/go-yara.TestMain(0xc000180000)
/tmp/autopkgtest-lxc.7gx74fvj/downtmp/autopkgtest_tmp/obj-x86_64-linux-gnu/src/github.com/hillu/go-yara/main_test.go:35
+0x1a5
main.main()
_testmain.go:125 +0x165
FAIL github.com/hillu/go-yara 0.033s
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
* Paul Gevers:
>>> If there are incompatible API changes, the soname needs to be bumped.
>>
>> The soname was bumped, from 4 to 8.
>
> Sorry, I somehow missed that. So if I understand it, you just forgot to
> close the bug?
Sorry for the confusion, I am closing it now.
Cheers,
-Hilko
--- End Message ---
