Hi team, This weekend I opened an ITP to package penelope, an advanced shell handler for penetration testing and CTFs [1].
I have already created a repo under pkg-security-team in advance [2] and intend to maintain it under the team's umbrella, unless you have any objections to it. Thus, I will wait for the team's word before uploading it. Penelope is already packaged for Kali [3], even though I didn't reuse it and packaged it from scratch. Do you think I should incorporate Kali's changelog in this case or just keep my packaging as is, considering it will end up in Kali again by the end? Before I wrap up, I also changed my debian/gbp.conf to use debian/latest and upstream/latest as debian-branch and upstream-branch, respectively, as that is the latest (no pun intended) recommendation from the candidate DEP-14. Should I keep it that way or revert back to the team's default gbp.conf as found on the Team's wiki [4]? Thanks in advance. PS: for the sake of full disclosure, an LLM (Gemini) was used to help generate both the description and the missing manpage for the tool. Please also let me know if that is a problem too. [1] https://bugs.debian.org/1140825 [2] https://salsa.debian.org/pkg-security-team/penelope [3] https://pkg.kali.org/pkg/penelope [4] https://wiki.debian.org/Teams/pkg-security#Git_packaging_tool_and_repository_layout Best regards, -- ⢀⣴⠾⠻⢶⣦⠀ David da Silva Polverari <[email protected]> ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ Debian: The universal operating system ⠈⠳⣄⠀⠀⠀⠀
signature.asc
Description: PGP signature
