Bug#915141: marked as done (RFS: rtags/2.21-1)
Your message dated Sat, 01 Dec 2018 16:25:43 +0000
with message-id <E1gT85P-0007yj-Ug@quantz.debian.org>
and subject line closing RFS: rtags/2.21-1
has caused the Debian Bug report #915141,
regarding RFS: rtags/2.21-1
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 owner@bugs.debian.org
immediately.)
--
915141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915141
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "rtags"
* Package name : rtags
Version : 2.21-1
Upstream Author : Anders Bakken
* URL : https://github.com/Andersbakken/rtags
* License : GPL-3+
Section : devel
It builds those binary packages:
elpa-ac-rtags - auto-complete back-end for RTags
elpa-company-rtags - company back-end for RTags
elpa-flycheck-rtags - flycheck integration for RTags
elpa-helm-rtags - helm interface for RTags
elpa-ivy-rtags - ivy back-end for RTags
elpa-rtags - emacs front-end for RTags
rtags - C/C++ client/server indexer with integration for Emacs
To access further information about this package, please visit the following URL:
https://mentors.debian.net/package/rtags
Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/r/rtags/rtags_2.21-1.dsc
Changes since the last upload:
* New upstream version 2.21
* rebase patches
* rename rc and rdm binaries (Closes: #914805)
Regards,
Denis Danilov
--- End Message ---
--- Begin Message ---
Package rtags version 2.21-1 is in unstable now.
https://packages.qa.debian.org/rtags
--- End Message ---
Reply to: