On Thursday, 7 September 2023 06:48:11 CEST Paul Wise wrote: > > Please note the extra steps when reintroducing packages, ie bug triage: > > https://www.debian.org/doc/manuals/developers-reference/ pkgs.en.html#reintroducing-packages
Thank you for the reference. I looked in the removal log: https://ftp-master.debian.org/removals-2020.txt Here are the bugs closed when the package was removed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757125 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938476 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956489 Only the first one was directly related to the package itself. The others were related to Python 2 removal. As part of repackaging this software, I have set up the packaging repository on Salsa: https://salsa.debian.org/pboddie/shedskin The CI functionality is being used to run the test suite as part of the autopkgtest job in each invoked pipeline: https://salsa.debian.org/pboddie/shedskin/-/pipelines This suite takes over an hour to complete and is therefore not part of the normal package build process. For example: https://salsa.debian.org/pboddie/shedskin/-/jobs/4671845 This should at least mitigate against the inadvertent breakage that occurred with bug #757125. Regards, Paul