Source: cdrkit Version: 9:1.1.11-3.5 Severity: important X-Debbugs-Cc: Joerg Jaspert <jo...@debian.org>, Eduard Bloch <bl...@debian.org>, Steve McIntyre <93...@debian.org>, 902...@bugs.debian.org, Package Salvaging Team <team+salv...@tracker.debian.org>, Andrey Rakhmatullin <w...@debian.org>, Ying-Chun Liu (PaulLiu) <paul...@debian.org>, Sebastian Ramacher <sramac...@debian.org>, Laurent Bigonville <bi...@debian.org>
Hi, your package cdrkit 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 familiarize newcomers with a consistent Git-based workflow. Usually we file Intend To Salvage bugs[2] if we create a repository on Salsa if the package is not maintained in Vcs yet. However, given its importance I can't imagine that this package is not in some Git repository yet. I realised that a search on Salsa is not reliable if some package is in private user repository. In any case the Vcs fields are not declared in d/control. Thus I would like to ask first before I might inject the result of gbp import-dscs --debsnap --create-missing-branches --pristine-tar into https://salsa.debian.org/debian/cdrkit which is somehow the default procedure for Bug of the Day targets. I'm just filing this ITS-like bug report to formalise and document the procedure. The ITS criteria - NMUs, especially if there has been more than one NMU in a row. - Bugs filed against the package do not have answers from the maintainer. - There are QA issues with the package. are fulfilled formally but well, the Package Salvage team is not up to maintain this package. However, I could imagine that there are several contributors motivated to work on this package if there is some easy way to contribute via direct commits or MRs. (That's why I also added authors of previous NMUs to this bug report receivers.) In short: 1. Is there any Git repository somewhere on Salsa and we just need to advertise these in Vcs fields (which I would do in some NMU / team upload)? 2. If not are you OK to move the package to the debian/ team and let me fix some low hanging fruits withh patch (like #902402 in CC) before doing the upload. Thank you for all your work on this package which had a great history which I vividly remember and would love to do some tiny contribution right now. Kind regards Andreas. [1] https://salsa.debian.org/tille/tiny_qa_tools/-/wikis/Tiny-QA-tasks [2] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
