Dear Stanislav,
Am Sun, Sep 22, 2024 at 09:04:49AM +0100 schrieb Stanislav Maslovski:
> Dear Andreas,
>
> Thank you for your message. I will check what does the new version
> offer.
Thanks a lot for your quick response.
> In fact, the version that is currently packaged in Debian works
> just fine. I am using it myself on daily basis, and I had no problems
> with it. Also, as you can see, there have been no functional bugs
> reported for kbdd for many years.
I agree there are no functional bugs. However, the new version
incorporates some Debian patches - so it makes sense to rather use the
latest version. I'm actually unsure about the last remaining patch
which I deactivated for the moment. It seems upstream has found a
different solution. Its very good to know you are active and can verify
the functionality.
> I may need your help later when uploading the new version through
> debian-mentors if all goes well.
I'm perfectly fine to sponsor your package without doing the "detour"
via mentors. Just ping me if you are happy with the status of the
Git repository.
> Thanks,
You are perfectly welcome and thanks again for your quick response.
Kind regards
Andreas.
> On Sat, Sep 21, 2024 at 01:15:08PM +0200, Andreas Tille wrote:
> > Source: kbdd
> > Version: 0.6-4
> > Severity: normal
> > X-Debbugs-Cc: Stanislav Maslovski <stanislav.maslov...@gmail.com>,
> > 673...@bugs.debian.org, 836...@bugs.debian.org, 1079...@bugs.debian.org,
> > Package Salvaging Team <team+salv...@tracker.debian.org>
> >
> > Hi
> >
> > I'm interested in salvaging your package kbdd, 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:
> >
> > - Bugs filed against the package do not have answers from the
> > maintainer.
> > - Upstream has released several versions, but despite there being
> > a bug entry asking for it, it has not been packaged.
> > - 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/kbdd
> > [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
>
> --
> Stanislav Maslovski
>
--
https://fam-tille.de
