Hi Simon and Juan,

On 11/05/2026 23:12, Simon Josefsson wrote:
There is a large difference between upstream 'siso/v1.5.12' git tag and
your upstream/latest and debian/latest source content.  Did you already
consider using upstream git as the source code?  Auditing that diff is
boring, and I'm not sure it is useful use of our time going forward.  Is
it possible to build from upstream git instead?  The debian/watch,
debian/README.source and the versioning doesn't seem entirely
consistent, are you using +ds source tarballs or not?  There is no
Files-Excluded in there either, and I wonder if debian/watch with
'uscan' really do the right thing?
I suggested this debian/watch file to Juan in [1] after reading his debian/scripts/repack-siso.sh script, but also suggested another way using Files-Excluded. I told Juan in private that the first option was probably easier for him as it did not change any of his previous work, but reading your concerns, the second one might be a better idea. It would allow to stay closer to upstream tags.

Also another thing that I noticed only afterwards Juan, is that you have to vendor in another directory that is in fact part of the same repository: go.chromium.org/build/kajiya. With the second option, you could add it to the Files-Included field.

The only issue is that dh-make-golang won't be as helpful as before, as it does not handle very well repositories with multiple modules inside.

This would also force to repack the tarball as before.

[1] https://lists.debian.org/debian-go/2026/05/msg00040.html
--
Nicolas Peugnet

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to