Your message dated Wed, 20 Nov 2024 11:39:29 +0100
with message-id <[email protected]>
and subject line Re: Bug#1087694: ITS: gkrellm-reminder
has caused the Debian Bug report #1087694,
regarding ITS: gkrellm-reminder
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1087694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087694
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gkrellm-reminder
Version: 2.0.0-3.2
Severity: important
X-Debbugs-Cc: [email protected], [email protected], Joerg Jaspert 
<[email protected]>, Ricardo Mones <[email protected]>, Package Salvaging Team 
<[email protected]>

Hi

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

  - NMUs (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.

I've set up a repository within the salvage-team space[2] to assist you
with this initial setup. 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/salvage-team/gkrellm-reminder
[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)
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

--- End Message ---
--- Begin Message ---
Hi Ricardo,

Am Tue, Nov 19, 2024 at 08:30:36PM +0100 schrieb Ricardo Mones:
> Yes, please, this has been neglected for too many moons…

Uploaded.  Thanks a lot for your quick confirmation to do so
    Andreas.

-- 
https://fam-tille.de

--- End Message ---

Reply via email to