Source: chrootuid
Version: 1.3-6.2
Severity: important
X-Debbugs-Cc: [email protected], Javier Fernandez-Sanguino Pen~a
<[email protected]>, Package Salvaging Team <[email protected]>
Hi,
I would be interested in helping with chrootuid, following the Package
Salvaging procedure outlined in the Developers Reference[1]. From what I
see, the package seems to meet the criteria for this process, and I'd
like to support keeping it maintained in Debian. As the Salvage process
suggests, here is a list of the criteria that I believe apply:
- NMUs (more than one NMU in a row).
- Last maintainer upload 14 years ago
- There are QA issues with the package.
There is a quite new bug filed against this package thus I do not expect
a prompt answer here.
I admit the package would be a great addition to some security related
team but I'm not a member of some team that fits. Thus *for the moment*
I've set up a repository within the salvage-team space[2] to assist you
with this initial setup. In case there will be no volunteer inside the
Salvage team to serve as human uploader I even might consider orphaning
the package and rather move it to Debian team. But my real hope is you
would rather take over what was prepared in Git since I trust your
insight into this package perfectly. So please regard the preparation
in Git rather as some service to save you some time that might help you
to keep on with the maintenance.
This package was highlighted in the Bug of the Day[3] 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://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://salsa.debian.org/salvage-team/chrootuid
[3] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5,
'experimental'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.38+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
