On Wed, Jan 22, 2025 at 10:18:18PM -0800, Otto Kekäläinen wrote: > I see you have now version number '1.0.5+ds2-1'. Since it has never > been uploaded, we should probably use '1.0.5+ds1-1', right?
Sorry, I hadn't cleaned house on the repository yet. I've deleted the invalid tags/branches and pushed my rebased debian/latest branch up to my repo. I had already squashed some of the unneccessary history, but never pushed it up. Overall, this package was a big experiment as my first complete, from scratch Go application for Debian so there was a lot of experimentation in the beginning. It also took a while to understand how to use the //go:generate directives, but the current version of the branch should be a lot cleaner. This package uses golang-github-cilium-ebpf-dev, which is a wrapper around clang to compile eBPF code for the kernel, which is used for the instrumentation that it collects. clang is called when the generate directives are run while compiling this package. I have started some work on a man page, but it's not ready for release yet. I am also aware about newer releases of pwru, but all of them require additional dependencies that I haven't had a chance to get around to packaging yet. I started this package over a year ago when I first joined the Go Team. The ds2 version has been dropped and it's only ds1. The +ds1 suffix to the upstream package is being I am repacking the upstream tarball to drop the embedded libpcap library it has and the vendor folder of Go modules. It relies on external packages already in Debian for those dependencies. The new history under penguin359/pwru should be much easier to follow. The go-team copy of the repo will need to be resynced once this is finalized. Nothing has been published beyond this git repo. > > I think this looks overall pretty good, you could rebase git history > and remove your temporary experiment commits etc what you want and put > this debian/latest branch on the team repo. > > All the important parts such as copyright, rules, control seem correct. > > There are a could minor details I am still pondering about. Can you > clarify a bit > https://salsa.debian.org/penguin359/pwru/-/commit/e616c50f5d3187d631fea7649ac053d7bb1102c4 > why you need clang as a build dependency? -- Loren M. Lang lor...@north-winds.org http://www.north-winds.org/ IRC: penguin359 Public Key: http://www.north-winds.org/lorenl_pubkey.asc Fingerprint: 7896 E099 9FC7 9F6C E0ED E103 222D F356 A57A 98FA
signature.asc
Description: PGP signature
