Bug#626888: marked as done (nmu: valgrind_1:3.6.1-5)
Your message dated Mon, 16 May 2011 08:07:16 +0100
with message-id <61771c0697c8decc44acab199cae131f.squirrel@adsl.funky-badger.org>
and subject line Re: Bug#626888: nmu: valgrind_1:3.6.1-5
has caused the Debian Bug report #626888,
regarding nmu: valgrind_1:3.6.1-5
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.)
--
626888: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626888
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: binnmu
nmu valgrind_1:3.6.1-5 . amd64 . -m "rebuild for to strip references to /home/madcoder/bin/gdb (Closes: #626886)"
The bug is due to valgrind being built in an unclean environment.
--- End Message ---
--- Begin Message ---
On Mon, May 16, 2011 07:37, Pierre Habouzit wrote:
> nmu valgrind_1:3.6.1-5 . amd64 . -m "rebuild for to strip references to
> /home/madcoder/bin/gdb (Closes: #626886)"
>
> The bug is due to valgrind being built in an unclean environment.
Scheduled.
Note that binNMUs don't support bug closure afair (dak only does that for
sourceful uploads), so #626886 will need closing by hand.
Regards,
Adam
--- End Message ---
Reply to: