[Python-modules-team] Bug#355752: marked as done (python-logilab-common: upgrade from sarge, then purge, leaves file behind)

Debian Bug Tracking System owner at bugs.debian.org
Thu Feb 5 00:15:06 UTC 2009


Your message dated Thu, 5 Feb 2009 01:11:43 +0100
with message-id <8b2d7b4d0902041611v5f511ca1t620153546f7866c at mail.gmail.com>
and subject line Re: python-logilab-common: upgrade from sarge, then purge, leaves  file behind
has caused the Debian Bug report #355752,
regarding python-logilab-common: upgrade from sarge, then purge, leaves file behind
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.)


-- 
355752: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355752
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Lars Wirzenius <liw at iki.fi>
Subject: python-logilab-common: upgrade from sarge, then purge, leaves file
	behind
Date: Tue, 07 Mar 2006 19:11:55 +0200
Size: 2231
Url: http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20090205/7c17bd8c/attachment.eml 
-------------- next part --------------
An embedded message was scrubbed...
From: Sandro Tosi <morph at debian.org>
Subject: Re: python-logilab-common: upgrade from sarge, then purge, leaves 
	file behind
Date: Thu, 5 Feb 2009 01:11:43 +0100
Size: 2647
Url: http://lists.alioth.debian.org/pipermail/python-modules-team/attachments/20090205/7c17bd8c/attachment-0001.eml 


More information about the Python-modules-team mailing list