Bug#856198: marked as done (RFS: entropybroker/2.9-0.1 [RC] [NMU])
Your message dated Mon, 27 Feb 2017 15:48:09 +0000 (UTC)
with message-id <1375234112.3275221.1488210489851@mail.yahoo.com>
and subject line Re: Bug#856198: RFS: entropybroker/2.9-0.1 [RC] [NMU]
has caused the Debian Bug report #856198,
regarding RFS: entropybroker/2.9-0.1 [RC] [NMU]
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.)
--
856198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856198
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "entropybroker"
* Package name : entropybroker
Version : 2.9-0.1
Upstream Author : Folkert van Heusden
* URL : https://www.vanheusden.com/entropybroker/
* License : AGPL V3
Section : utils
It builds those binary packages:
entropybroker - infrastructure for distributing random numbers (entropy data)
To access further information about this package, please visit the following URL:
https://mentors.debian.net/package/entropybroker
Alternatively, one can download the package with dget using this command:
dget -x https://mentors.debian.net/debian/pool/main/e/entropybroker/entropybroker_2.9-0.1.dsc
Changes since the last upload:
* Non-maintainer upload.
* new upstream version : 2.9
* 100% cpu use fixes (Closes: #856187)
* remove patches merged upstream
Regards,
Fabrice Dagorn
--- End Message ---
--- Begin Message ---
Hi,
>This is rather strange.
it happens from time to time :)
>On the contrary I say: Thanks for the work, but no thanks.
thanks for caring, I'm closing this one!
G.
--- End Message ---
Reply to: