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? My memory is a bit vague on this package too... /Simon Reinhard Tartler <siretart@gmail.com> writes: > Hi Simon, > > Can you please do a sourceful upload to get the package into testing? > > seems otherwise clean: > > https://tracker.debian.org/pkg/golang-github-adamkorcz-go-fuzz-headers-1 > > Also, it appears this package is a fork of " > https://github.com/AdaLogics/go-fuzz-headers"; which I noticed at least some > container packages (such as later versions of docker) use in the testsuite. > > Can we make the packaging for the package cover both import paths so that > we don't have to duplicate sources in the archive? > > On Mon, Jan 15, 2024 at 7:51 AM Simon Josefsson <simon@josefsson.org> wrote: > >> Package: wnpp >> Severity: wishlist >> Owner: Simon Josefsson <simon@josefsson.org> >> >> * Package name : golang-github-adamkorcz-go-fuzz-headers-1 >> Version : 0.0~git20230919.8b5d3ce-1 >> Upstream Author : Adam Korcz <adam@adalogics.com> >> * URL : https://github.com/AdamKorcz/go-fuzz-headers-1 >> * License : Apache-2.0 >> Programming Lang: Go >> Description : helper functions for Go fuzzing (library) >> >> Various helper functions for go fuzzing. It is mostly used in combination >> with go-fuzz (https://github.com/dvyukov/go-fuzz), but compatibility with >> fuzzing in the standard library will also be supported. Any coverage >> guided >> fuzzing engine that provides an array or slice of bytes can be used with >> go-fuzz-headers. >> . >> go-fuzz-headers' approach to fuzzing structs is strongly inspired by >> gofuzz (https://github.com/google/gofuzz). >> >> I hope to maintain this package as part of Debian Go Packaging Team: >> >> >> https://salsa.debian.org/go-team/packages/golang-github-adamkorcz-go-fuzz-headers-1/ >> >> /Simon >>
Attachment:
signature.asc
Description: PGP signature