Your message dated Tue, 17 May 2022 17:08:55 +0200
with message-id <2724b8de-7312-5643-0d71-0c17fd2c3...@debian.org>
and subject line Re: RFS: nemo-audio-tab/5.0.0-1 [ITP] -- View audio tag
information from Nemo's properties tab
has caused the Debian Bug report #992214,
regarding RFS: nemo-audio-tab/5.2.0-1 [ITP] -- View audio tag information from
Nemo's properties tab
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 ow...@bugs.debian.org
immediately.)
--
992214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "nemo-audio-tab":
* Package name : nemo-audio-tab
Version : 5.0.0-1
Upstream Author : Clement Lefebvre <r...@linuxmint.com>
* URL : https://community.linuxmint.com/software/view/nemo-audio-
tab
* License : GPL-3+
* Vcs : https://salsa.debian.org/cinnamon-team/nemo-audio-tab
Section : utils
It builds those binary packages:
nemo-audio-tab - View audio tag information from Nemo's properties tab
To access further information about this package, please visit the following
URL:
https://mentors.debian.net/package/nemo-audio-tab/
Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/n/nemo-audio-tab/nemo-
audio-tab_5.0.0-1.dsc
Or, to view the code as a whole, visit:
https://salsa.debian.org/cinnamon-team/nemo-audio-tab
Changes for the initial release:
nemo-audio-tab (5.0.0-1) unstable; urgency=medium
.
* Initial release. (Closes: #971971)
Regards,
--
Joshua Peisach
--- End Message ---
--- Begin Message ---
When the upstream contains all the extensions in one repo, you should really think of having one
source package with all the extensions as binary packages.
Please work on this or have a sane way to repack the orig tarball that upstream
provides.
I am closing this RFS.
--- End Message ---
