Your message dated Tue, 08 Apr 2025 16:26:51 +0000
with message-id <[email protected]>
and subject line Bug#1102317: fixed in mumudvb 2.1.0-1
has caused the Debian Bug report #1102317,
regarding ITS: mumudvb
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.)


-- 
1102317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1102317
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mumudvb
Version: 1.7.1-1
Severity: important
X-Debbugs-Cc: [email protected]

Hi,

I'm interested in salvaging your package mumudvb, 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.

I believe your package would be a great addition to the Debian VDR
Team, and Andreas Tille took the liberty to create the Salsa
repository here[2] and then I made some improvements. 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
    Emmanuel.

[1] 
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://salsa.debian.org/vdr-team/mumudvb
[3] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks

--- End Message ---
--- Begin Message ---
Source: mumudvb
Source-Version: 2.1.0-1
Done: Emmanuel Arias <[email protected]>

We believe that the bug you reported is fixed in the latest version of
mumudvb, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Arias <[email protected]> (supplier of updated mumudvb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 05 Apr 2025 18:53:31 -0300
Source: mumudvb
Architecture: source
Version: 2.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team <[email protected]>
Changed-By: Emmanuel Arias <[email protected]>
Closes: 768319 1039273 1102317
Changes:
 mumudvb (2.1.0-1) unstable; urgency=medium
 .
   [ Andreas Tille ]
   * Team upload.
   * Maintain in Debian VDR Team
   * Fix Homepage
   * Fix watch file
   * Standards-Version: 4.7.2 (routine-update)
   * debhelper-compat 13 (routine-update)
   * cme fix dpkg-control
   * Pre-Depends: ${misc:Pre-Depends}
   * Propagate hardening options
 .
   [ Emmanuel Arias ]
   * New upstream version (Closes: #768319).
   * d/patches: Add patches to make it possible to build.
     - fix-compiling-with-kernels-upper-4.14.patch: fix compiling error due
     kernel 4.14+ removed CA_SET_PID.
     - fix-dont-compile-mumudvb_test.patch: Take patch from upstream that
     remove a mumudvb_test.c file. It is not necessary.
   * d/control: Add asciidoc as Build Depends.
   * d/rules: Build html documentation.
   * d/mumudvb.service: Add support for systemd (Closes: #1039273).
   * d/patches/avoid-privacy-breach-logo.patch: Add patch to avoid potential
     privacy breach.
   * d/control: Add myself as Uploaders (Closes: #1102317).
Checksums-Sha1:
 0791312d4666763dc7bcc5238128b7ff14f3fc40 1918 mumudvb_2.1.0-1.dsc
 b1567ae8dae5e930ee3826048e4cea8530125455 671935 mumudvb_2.1.0.orig.tar.gz
 34e8fa95505e771d4768b055a64f4673217e4d68 9628 mumudvb_2.1.0-1.debian.tar.xz
 6fab9f41b3eaff3faf5a10e2fe20b15ba8c4437a 7309 mumudvb_2.1.0-1_amd64.buildinfo
Checksums-Sha256:
 eee495520a1fdb8809bf23c28c41138a05c39f55914d47e3029535abb5f20f37 1918 
mumudvb_2.1.0-1.dsc
 beb61cb8d3c61ad4d8c7389374599bdf7d9ccff134728bf2833b710f64584e13 671935 
mumudvb_2.1.0.orig.tar.gz
 869d9a9e4ec9fb400d2a861dc7cb4f9babf09fc6a7a8713c5b5b5f3732a930ad 9628 
mumudvb_2.1.0-1.debian.tar.xz
 4b188a0344b66cae9262bcf44a8defe59bf34ac61e04110650400be1cfd6cfaa 7309 
mumudvb_2.1.0-1_amd64.buildinfo
Files:
 ababad7c8d07d38b63450f2f3e65eabf 1918 video optional mumudvb_2.1.0-1.dsc
 fd26e5c77bd33c3fbe9d9e6f07b7d98f 671935 video optional 
mumudvb_2.1.0.orig.tar.gz
 e94e6d92ee1c9e607f3291fd2048dae7 9628 video optional 
mumudvb_2.1.0-1.debian.tar.xz
 7441459665ef5c1f3f2bdcd5d74533e8 7309 video optional 
mumudvb_2.1.0-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJGBAEBCgAwFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmf1P0sSHGVhbWFudUBk
ZWJpYW4ub3JnAAoJEPqd7F3hHGPxg9cP/jbKobOvG0zdHMtjGjfYyPQaOIG+x5jd
2yT4zBpMxLs15onFXQ0WAHMdhTQdm83IiJAvzh5Z1Th5nUSTgKcDrgHEk/tfJLT8
czQHErzpY/Zuz+ilcCnndDLe1Wxza6u/pwySdaxQma1KyPUkKQJkrHmGRb9LsVqp
SZoWuU9rRVY+boNcqkDQHhNLY2MEpo75XMeaTmJ7pCNp4DIaLtJgro0v/heIjj5Q
FdOPpkrhrAcBqo6tU7WTUo+Kg/a2IdrT4Eb9cyvp7/ftfb1hpiCkq2tFliMv5hLV
S+XX/kmHQxBGko08zct+2tekmslmP8Zs6urLt2AZpMF9NbXhrnRJCEUt96/bX9u3
iWNwecihkVuqjFB5hfvB2LDlTYewg1PEI4BE8vGWYBMQNQ6B9vIT3fk534P5JAjB
I1HeZPVhtg+akBRQBRc/Jbg3Y/2UjlqzKIiKrAMpc/niFuq1llSEyfepGUeQEJgW
/JzPagRRPmlOTfC3ExJ4CRKAvhrprwFkQ9pMxmlMPmcSCzDcVQlSSVgIogJXuDcI
YQtQX0pO7E6R85lF69+JVcTdTyJr8JSpe2q0+5xuGY6K8HL8YtUcNtEdGLd1i88P
YHHF/1OAvPTyQTsiTjPelbPIJ8fcVx4pT4izKC3DEy0S8OypjNkODU27DBmhfjF5
GTKZtR2GqKa9
=X6z1
-----END PGP SIGNATURE-----

Attachment: pgpYOkZA0KlrN.pgp
Description: PGP signature


--- End Message ---

Reply via email to