Comment 3 for bug 2052493

Hi Georgia,

Thank you for providing a fix for the bug.

I'd like to make a few recommendations for the next time. Hopefully these will help you better understand and navigate the sponsorship process :-).

1) Providing a PPA with the proposed package built goes a long way to help the sponsor verify the changes. If the package has DEP8 tests, providing a log of a DEP8 test run is also very welcome.

2) I noticed that you targeted jammy-security in the Jammy debdiff. I believe this may have been a typo/thinko, but just in case: if an upload needs to go to the -security pocket, then the process is a bit different. You need to contact the Security team, and they will perform their own checks. Also, uploads to the -security pocket don't go through the normal SRU process, and can't be sponsored by Ubuntu Sponsors.

3) When you have the time, I'd recommend learning about the git-ubuntu workflow. I personally don't mind sponsoring debdiffs, but I've noticed several people using git-ubuntu lately, and I think it can make the process a bit easier for the contributor.

Otherwise, the debdiffs are great. I just had to adjust the changelog message (the path for the file being changed is debian/usr.{s,}bin.tcpdump), and the target pocket for Jammy.

Uploaded.

Thanks!