I uploaded golang-github-kelindar-simd to NEW using dgit push-built. Juan <[email protected]> writes:
>> - The *.go file seems auto-generated, shouldn't they be re-generated by >> the codegen/ tooling? > > Good catch. I had a deeper look. Those auto-generated .go and .s files > are committed upstream as canonical source. Author seems to be using > gocc (currently unpackaged). Since this can be considered a upstream > helper tool, not needed for packaging. > In addition, the author has gocc invocations commented out in > codegen/generate.sh. Let me know your thoughts. > > This has been documented in debian/README.source. Thanks. Still, I believe this is against Debian policy, but I also sympathize with solving upstream bugs like this is really tiresome. I won't stand in the way but let the DFSG Team decide here (which seems to have adopted a more flexible approach on these matters). Still, I would ask you to open a bug report about this on the package if it is approved, and to ask upstream about how the source-code is re-generated and make some attempt to reproduce that. If 'gocc' is needed, we should make an effort to package it, or at least open a RFP bug and let the bootstrap bug report block on it. This way, the problem is at least acknowledged through a bug report. Unless/until we have evidence that these source code files CANNOT be re-generated using DFSG-compliant tools, I think the pragmatic approach is to cast a blind eye on this. But I also wouldn't disagree with a decision to reject this package because of this problem. /Simon
signature.asc
Description: PGP signature
