Hello!
> I have tested this back and forward. It does _not_ affect Buster, > only Sid. Indeed, it's due to an incremental change in bison and as > such this is expected, _not_ a bug in it. > I might fix it in a day or two, until then I may disagree with the > severity - sure, it would affect binNMUs but otherwise not a problem > now. I think the severity is correct since the bug is about sid distribution (and the reason for me discovering this is that I'm trying to move the json-c transition forward, so this is why I'm testing rebuilds). I'm pretty sure, since the problematic bison won't go in testing, that Release Team will be happy to ignore this bug for Buster :) I confirm i386 is fine, I can't really easily test s390x (maybe in a porterbox, but I presume the bug is the same). http://debomatic-i386.debian.net/distribution#buster/syslog-ng/3.19.1-5/buildlog thanks for caring, G.
