Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "riemann-c-client":

 * Package name     : riemann-c-client
   Version          : 1.10.4-3
   Upstream contact : Gergely Nagy <alger...@madhouse-project.org>
 * URL              : https://git.madhouse-project.org/algernon/riemann-c-client
 * License          : LGPL-3+
 * Vcs              : 
https://git.madhouse-project.org/algernon/riemann-c-client/src/branch/debian/master
   Section          : libs

The source builds the following binary packages:

  libriemann-client0 - C language client library for the Riemann event stream 
processor
  libriemann-client-dev - Development files for the Riemann C client library
  riemann-c-client - Client utility for the Riemann event stream processor

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/riemann-c-client/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/r/riemann-c-client/riemann-c-client_1.10.4-3.dsc

Changes since the last upload:

 riemann-c-client (1.10.4-3) unstable; urgency=medium
 .
   * Fix GnuTLS send/recv.


This change is intended to fix bugs in the library that make the TLS
transport unreliable. I created patches to rebuild the Debian package we
use in production, they solved our issues so I upstreamed them and I
would like them to be introduced in Debian to avoid the need to maintain
patched packages and so that other users can have a better experience
with the package on Debian.

It is my very first submission of a package, so do not intend to request
maintainership for this package ATM.

The mentors.debian.net page list some points that are probably legit,
but I am not sure that they should be addressed in a bugfix release of
the package, so for now I refrained to fix them until instructed to do
so.  Likewise, when filling-in patches "metadata" I was unsure about if
they where intended to be filled by me or not, so left them untouched
(this is not reported on the website).

So I am looking forward for reading mentors feedback to help me leverage
this package fix according to the Debian standards and guide me through
the process of making Debian even better!

Thank you!

Regards,

-- 
Romain Tartière <rom...@blogreen.org>        http://romain.blogreen.org/
pgp: 8234 9A78 E7C0 B807 0B59  80FF BA4D 1D95 5112 336F (ID: 0x5112336F)
(plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)

Attachment: signature.asc
Description: PGP signature

Reply via email to