On Tue, Jul 2, 2024 at 12:21 PM Simon Josefsson <[email protected]> wrote:
> Hi > > Thanks for noticing this -- the reason I hesitates was exactly because I > felt uncertain which namespace and which implementation to promote here. > There is only a little difference between these two packages, but maybe > some package somewhere breaks if we use one of them instead of the > other? Which code path to pick? I do agree it would be nice for one > package to export both namespaces, if indeed that really works. Maybe > it is sufficient that it works for at least ONE package that use the > AdamKorcz namespace AND at least ONE package that use the AdaLogics > namespace? Then we know there is reusability of the shared code without > causing breakage. If some package eventually breaks as a result, we > have to figure out what to do about the situation later on. > > Thoughts? > May I ask why you have packaged this? I don't see any other package build-depending on this package (in build-rdeps golang-github-adamkorcz-go-fuzz-headers-1-dev). Looking at the difference between the two branches, it seems that the fork contains 9 additional commits that appears to only be adding functionality: https://github.com/AdaLogics/go-fuzz-headers/compare/main...AdamKorcz:go-fuzz-headers-1:main With this, I think we can just install a symlink as suggested at https://go-team.pages.debian.net/packaging.html#_upstream_package_moves Best, -rt
