Your message dated Tue, 11 Oct 2016 21:26:11 +0000 (UTC) with message-id <[email protected]> and subject line Re: Bug#840456: RFS: logdata-anomaly-miner/0.0.5-1 ITA has caused the Debian Bug report #840456, regarding RFS: logdata-anomaly-miner/0.0.5-1 ITA 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.) -- 840456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840456 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "logdata-anomaly-miner" * Package name : logdata-anomaly-miner Version : 0.0.5-1 Upstream Author : Roman Fiedler * URL : https://launchpad.net/logdata-anomaly-miner/ * License : GPLv3 Section : misc It builds those binary packages: logdata-anomaly-miner - This tool allows one to create log analysis pipelines To access further information about this package, please visit the following URL: https://mentors.debian.net/package/logdata-anomaly-miner Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/l/logdata-anomaly-miner/logdata-anomaly-miner_0.0.5-1.dsc More information about hello can be obtained from https://launchpad.net/logdata-anomaly-miner/ Changes since the last upload: logdata-anomaly-miner V0.0.5 is available upstream, see https://launchpad.net/logdata-anomaly-miner/+milestone/v0.0.5 Best Regards, Roman Fiedler
--- End Message ---
--- Begin Message ---Hi, >I am looking for a sponsor for my package "logdata-anomaly-miner" sponsored with two nitpicks: 1) this isn't an ITA, you are the maintainer and you can't adopt your own packages :) 2) there is no need to open a bug "new upstream release" and to close it by yourself :) both of them aren't packaging related, just something you can avoid for next updates! G.
--- End Message ---
