Maintaining cl-launch in Debian Common Lisp Team? (Was: Updating the cl-launch Uploaders list)
Hi Francois-Rene,
I stumbled upon this bug report and would like to clarify the situation
of cl-launch. Since you maintain cl-asdf inside Debian Common Lisp Team
I conclude you are a member of this team and you might be able to
maintain cl-launch inside this team as well. Is there any reason to
have it outside the team?
The package is featuring a long list of Uploaders. Are all these
Uploaders active and is Julien Danjou the only inactive maintainer (as
per this bug report)? Christoph and Milan signed uploads until 10 years
ago. While there is a new upstream version there was no maintainer
upload since then.
If the Debian Common Lisp Team agrees I would recommend to migrate the
packaging to this team and also updating the Uploaders list. Please
also package the latest upstream version.
BTW, there was an NMU 4.1.4-1.1
No source change upload to rebuild on buildd with .buildinfo files
which is not imported into the packaging Git. I would recommend to do
this to make sure the debian/changelog will list all uploads in future.
This package was highlighted in the Bug of the Day[1] initiative, which
aims to introduce newcomers to manageable tasks and guide them through
the workflow to solve them. The focus of this initiative is on migrating
packages to Salsa, as it's a great way to help newcomers become familiar
with a consistent Git-based workflow.
Kind regards
Andreas.
[1] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks
--
https://fam-tille.de
Reply to: