Bug#1107230: ITS: midish
Source: midish
Version: 1.0.4-1.2
Severity: important
X-Debbugs-Cc: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>, Alexandre Ratchov <alex@caoua.org>, 993811@bugs.debian.org, 1070255@bugs.debian.org, 1070255@bugs.debian.org, Package Salvaging Team <team+salvage@tracker.debian.org>
Hi Alexandre,
You are upstream developer and Debian Maintainer of this package in one
person. I realised you are very active to develop the upstream code
which is great. I would like to help you with the Debian packaging
which is hopefully in your interest. BTW, just some hint to you as
upstream developer: It would help if you would include the autoconf
sources (Makefile.am + configure.ac) that are used to create Makefile.in
and configure. Otherwise it might make sense to fetch the upstream
source directly from Git but it seems there is no annonymous access
enabled.
I'm interested in salvaging your package midish, 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 you
- You have 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 believe your package would be a great addition to the Debian
Multimedia, 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.
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.
PS: I do not plan to upload a salvaged package before the Trixie
release to not influenze the freeze process.
[1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://salsa.debian.org/multimedia-team/midish
[3] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- System Information:
Debian Release: 13.0
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
Reply to: