[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#368006: marked as done (RFP: libtest-memory-cycle-perl -- Test::Memory::Cycle - Check for memory leaks and circular memory references)

Your message dated Sat, 24 May 2008 11:59:48 -0600
with message-id <E1Jzy20-00064g-9j@merkel.debian.org>
and subject line WNPP bug closing
has caused the Debian Bug report #368006,
regarding RFP: libtest-memory-cycle-perl -- Test::Memory::Cycle - Check for memory leaks and circular memory references
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.)


-- 
368006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368006
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist


* Package name    : libtest-memory-cycle-perl
  Version         : 1.02
  Upstream Author : Andy Lester <andy@petdance.com>
* URL             : http://search.cpan.org/dist/Test-Memory-Cycle/
* License         : As perl itself (GPL or artistic)
  Programming Lang: Perl
  Description     : Check for memory leaks and circular memory references in perl unit tests

Hello

I've noticed this package which is very usefull for any serious perl
development.

>From the manpage:

    Perl's garbage collection has one big problem: Circular references
    can't get cleaned up. A circular reference can be as simple as two
    objects that refer to each other.
    
    Test::Memory::Cycle is built on top of Devel::Cycle to give you an
    easy way to check for these circular references.
    
    You can also use memory_cycle_exists() to make sure that you have
    a cycle where you expect to have one.

Note that this module depends on Devel::Cycle
(http://search.cpan.org/dist/Devel-Cycle/) which is not packaged by
debian.

Cheers

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686-smp
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

--- End Message ---
--- Begin Message --- 
Hello,

This is an automatic mail sent to close the RFP you have reported or 
are involved with.

Your RFP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.

As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not 
intended by owners and submitters (like you) to be closed, for
example if the RFP is still of your interest, or there has been 
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).

To re-open it, you simply have to mail control@bugs.debian.org
with a body text like this:

 reopen 368006
 stop

Further comments on the work done in the bug sent to
368006@bugs.debian.org would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <damog@debian.org>.

A similar process is being applied to other kind of wnpp bugs.

Thanks for your cooperation,

 -- David Moreno Garza <damog@debian.org>.

--- End Message ---
Reply to: