[Python-modules-team] Bug#437830: marked as done (pynjb: not handling nostrip build option (policy 10.1))

[Debian Bug Tracking System]

Your message dated Wed, 2 Jul 2008 20:08:16 +0200
with message-id <8b2d7b4d0807021108i3a606bdt74b094743a3a2efd at mail.gmail.com>
and subject line Re: bug 437830 - pynjb - still valid?
has caused the Debian Bug report #437830,
regarding pynjb: not handling nostrip build option (policy 10.1)
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 at bugs.debian.org
immediately.)


-- 
437830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437830
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Julien Danjou <acid at debian.org>
Subject: pynjb: not handling nostrip build option (policy 10.1)
Date: Tue, 14 Aug 2007 14:42:39 +0200
Size: 17014
Url: http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20080702/3da4aa17/attachment-0002.eml 
-------------- next part --------------
An embedded message was scrubbed...
From: "Sandro Tosi" <matrixhasu at gmail.com>
Subject: Re: bug 437830 - pynjb - still valid?
Date: Wed, 2 Jul 2008 20:08:16 +0200
Size: 2761
Url: http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20080702/3da4aa17/attachment-0003.eml