Source: aspell-ro
Version: 3.3.9-1.2
Severity: important
X-Debbugs-Cc: 1061...@bugs.debian.org, Package Salvaging Team 
<team+salv...@tracker.debian.org>, Lior Kaplan <kap...@debian.org>, Eddy 
Petrișor <eddy.petri...@gmail.com>

Hi

I'm interested in salvaging your package aspell-ro, 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:

  - Upstream has released a version
  - There are QA issues with the package.

I've set up a repository within the Debian team space[2] where I found
lots of other aspell-LANG packages to assist you with this initial
setup. If you decide not to accept the ITS, this repository can easily
be moved to another location to 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/debian/aspell-ro
[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

Reply via email to