Source: ttf2ufm
Version: 3.4.4~r2+gbp-1.1
Severity: important
X-Debbugs-Cc: 772...@bugs.debian.org, Debian Fonts Task Force
<pkg-fonts-de...@lists.alioth.debian.org>, Ondřej Surý <ond...@debian.org>,
Package Salvaging Team <team+salv...@tracker.debian.org>
Hi
I'm interested in salvaging your package ttf2ufm, in accordance with the
Package Salvaging procedure outlined in the Developers Reference[1].
Your package meets the criteria for this process, and I would love to
assist in preserving and maintaining it. As the Salvage process
suggests, here is a list of the criteria that apply, in my opinion:
- NMU
- Bugs filed against the package do not have answers from the
maintainer.
- There are QA issues with the package.
I believe your package would be a great addition to the Debian Fonts
Task Force team, and I took the liberty to create the Salsa repository
here[2]. If you choose not to accept the ITS, I'd be more than happy to
help you move it to another location, such as debian/, or wherever you
prefer. My goal is to make it as easy as possible for you to join the
team. I'd also be delighted to assist in adding you as a team member if
you could share your Salsa login.
I've set up a repository within the salvage-team space[2] to assist you
with this initial setup. I tried to restore your old repository from
Alioth to keep the history of the packaging but for whatever reason I
was not able to find it inside the archive. Thus I've recreated a
repository using `gbp import-dscs`. (Please note: For whatever reason
the repository ended up being "Private" but I've pinged fonts-team
owners to fix this so this should be solved in a view days.)
If you decide not to accept the ITS, this repository can easily be moved
to another location, such as debian/, or any place of your choosing. I
hope this service helps make the transition to using a Git repository on
Salsa smoother and more convenient for you.
Your 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 familiarize newcomers 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/fonts-team/ttf2ufm
[3] https://salsa.debian.org/tille/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- 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
