Your message dated Sat, 14 Apr 2012 00:14:56 +0100
with message-id
<CAPQ4b8=tZNyhKB4OTmdcU73B38ix=gkjbe5enfzcftsbdfy...@mail.gmail.com>
and subject line Closing obsolete/orphan bugs
has caused the Debian Bug report #379153,
regarding libdb4.4: DB->upgrade memory leak
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.)
--
379153: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=379153
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libnss-db
Version: 2.2.3pre1-2
Severity: normal
Easy to reproduce - run this program, and watch top.
#include <netdb.h>
int main()
{
struct servent *srv=NULL;
while (1) {
srv = getservbyname("ftp", "tcp");
}
return 0;
}
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages libnss-db depends on:
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libdb4.3 4.3.29-5 Berkeley v4.3 Database Libraries [
ii libselinux1 1.30-1 SELinux shared libraries
ii make 3.81-2 The GNU version of the "make" util
libnss-db recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello,
Thanks for the bug report. db4.4 has been removed a while ago (it's
not even present in lenny/oldstable and this bug report is orphan.
Sorry that the bug report was not dealt with when it was due, but I
don't think that it makes much sense to keep it open against this
version of the package. The cloned versions of the bug were closed
as well, in some of them the fix is applied, so I guess that newer
versions are correct.
So I'm closing this bug report now. Please reopen (perhaps against
the current libdb* versions) if you think that this is still an issue.
Regards.
--- End Message ---
