Your message dated Tue, 16 Jun 2015 18:00:44 +0000
with message-id <e1z4vac-00037u...@franck.debian.org>
and subject line Bug#786914: fixed in ruby-get-process-mem 0.2.0-1
has caused the Debian Bug report #786914,
regarding ITP: ruby-get-process-mem -- Get memory usage of a process in Ruby
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.)


-- 
786914: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Balasankar C <balasank...@autistici.org>

* Package name    : ruby-get-process-mem
  Version         : 0.2.0
  Upstream Author : Richard Schneeman <richard.schneeman+...@gmail.com>
* URL             : https://github.com/schneems/get_process_mem
* License         : Expat
  Programming Lang: Ruby
  Description     : Get memory usage of a process in Ruby

--- End Message ---
--- Begin Message ---
Source: ruby-get-process-mem
Source-Version: 0.2.0-1

We believe that the bug you reported is fixed in the latest version of
ruby-get-process-mem, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 786...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Balasankar C <balasank...@autistici.org> (supplier of updated 
ruby-get-process-mem package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 26 May 2015 22:05:22 +0530
Source: ruby-get-process-mem
Binary: ruby-get-process-mem
Architecture: source all
Version: 0.2.0-1
Distribution: sid
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Balasankar C <balasank...@autistici.org>
Description:
 ruby-get-process-mem - get memory usage of a process in Ruby
Closes: 786914
Changes:
 ruby-get-process-mem (0.2.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #786914)
Checksums-Sha1:
 37404c9ebec508c89e0c43b21dbbb1d47636ef32 2133 ruby-get-process-mem_0.2.0-1.dsc
 8ed435eceed84529c37af4c1e69b5127502543ea 5970 
ruby-get-process-mem_0.2.0.orig.tar.gz
 7340040c2934cd872e5a40c332570018ea1d4b40 2764 
ruby-get-process-mem_0.2.0-1.debian.tar.xz
 d506fecbdd5d418577b3ff52396b06a15b97f818 4784 
ruby-get-process-mem_0.2.0-1_all.deb
Checksums-Sha256:
 145b3c11a5b15d627eade82b1ef1d81c4cad729f94f72966e710298ba88b3d48 2133 
ruby-get-process-mem_0.2.0-1.dsc
 8204e874050f84335ce26f9539ad81583bd8c439c31d755c3f178196322957d9 5970 
ruby-get-process-mem_0.2.0.orig.tar.gz
 dbe0597d98edc88d2aadb9641c87a3073b7ba337adda3a2deaece7141b2cb2bf 2764 
ruby-get-process-mem_0.2.0-1.debian.tar.xz
 8942a1543f93ae0dae7beaf63aea8914a9e692b292a590e834df1008cfe0e327 4784 
ruby-get-process-mem_0.2.0-1_all.deb
Files:
 da6a5c735c6b44ccbe7b6c5cd9fd0f25 2133 ruby optional 
ruby-get-process-mem_0.2.0-1.dsc
 c9ab3093398489b4bc9d108a805ec7ca 5970 ruby optional 
ruby-get-process-mem_0.2.0.orig.tar.gz
 01319f7f74c0f814cf9048edc4638896 2764 ruby optional 
ruby-get-process-mem_0.2.0-1.debian.tar.xz
 c071eb19963a4c6737a238134d9e99dc 4784 ruby optional 
ruby-get-process-mem_0.2.0-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVfVxvAAoJEFwT1tuTBS4DLxUP/AgcMOpl0pZdgXIeajQL0Cgp
j9Lyyrqej9jgEfOwtNRrTBxQgZHbvrPfSuysmIfiXuTabuoY1ZQurbqx2fzrOkHG
YWkVoo/vY7hrudXrzjNDB+PU7es+S258WnHwjiMuY2TMjnhlFmvLDKl+seb5DVf6
6aMRAZ5meIA3YKBfHgY4lEK36V/FK/reA9yjwJyvM9Lotz2SDM05HyjC8uM56qWw
mE6b/ySNKXpoa/kX/cerUruQUeJQJisp4wEvrxTolwq+rga3HXN3SzCPqadV1zdM
s/NrChjVokV/6okzo/W61rkX1pY56nAb8sy6EBJLvVKJ2vExQs6e3RhoZlrrPnTY
QX+Z3CZDMKlf/sFWYVRMVkz6CvPS0KSwTSSFrF6td/JyhWPMv2iOaJ+UBI2qv2ff
m38x+altKOoS5K/Sg5Y1k1L3PEWtV3mHvom9AMN2cjO01LSycnvc+32hNDCNE4xC
GqCdRVJCZVeFlic+M7Sv6fbYiY4vv731WwTg1aQPiLHKeKWxxLkuRLHVS1dHj3RT
L55xCIV3B39nwcMRrEEr+9BYXBNM1ddeOb1iDB+Sr/CsxqrKBBx4H6wmwQHVUjYM
NtsVJlxTwz1mFguyo8QBV0O8BrSqwupIS4FaL8z8UJuXHmzjV+hBqRuLTsBfASCQ
Tj5MZ/5I7hvhWePuFDpy
=tqZB
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to