[pkg-go] Bug#987378: yara breaks golang-github-hillu-go-yara autopkgtest + ftbfs

[Hilko Bengen]

control: tag -1 confirmed
control: notfound -1 golang-github-hillu-go-yara/4.0.4-1

* Paul Gevers:

> 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: debian-ci at lists.debian.org
> User: debian-ci at lists.debian.org
> Usertags: breaks needs-update
>
> 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. 

As the maintainer of the yara package and (upstream) author of go-yara,
I am aware of the problem. The culprit is the yara package, not
golang-github-hillu-go-yara.

I don't know yet how yara/4.1.0 will address the API/ABI incompatibility
issue that is the root cause of this bug. For the time being I think
I'll leave the yara package in unstable in its current broken state. (My
upload to unstable was an error.)

> 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?

Done, see above. (I hope I have whispered the right things at the BTS.)

> 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.

That was pretty much my plan. Thanks.

Cheers,
-Hilko