Bug#752726: marked as done (stumpwm: FTBFS - SIGSEGV cannot be cured.)

Fri Sep 22 08:15:03 UTC 2017

Your message dated Fri, 22 Sep 2017 10:13:32 +0200
with message-id <1506068012.12056.20.camel at debian.org>
and subject line Re: Bug#752726: stumpwm: FTBFS - SIGSEGV cannot be cured.
has caused the Debian Bug report #752726,
regarding stumpwm: FTBFS - SIGSEGV cannot be cured.
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.)

-- 
752726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752726
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Michael Tautschnig <mt at debian.org>
Subject: stumpwm: FTBFS - SIGSEGV cannot be cured.
Date: Wed, 25 Jun 2014 23:29:07 +0100
Size: 18079
URL: <http://lists.alioth.debian.org/pipermail/pkg-common-lisp-devel/attachments/20170922/df4b56a5/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: =?ISO-8859-1?Q?S=E9bastien?= Villemot <sebastien at debian.org>
Subject: Re: Bug#752726: stumpwm: FTBFS - SIGSEGV cannot be cured.
Date: Fri, 22 Sep 2017 10:13:32 +0200
Size: 4856
URL: <http://lists.alioth.debian.org/pipermail/pkg-common-lisp-devel/attachments/20170922/df4b56a5/attachment-0001.mht>