[Piuparts-devel] Bug#826893: marked as done (piuparts aborts with "RuntimeError: maximum recursion depth exceeded")

Debian Bug Tracking System owner at bugs.debian.org
Sun Mar 19 16:24:03 UTC 2017


Your message dated Sun, 19 Mar 2017 16:20:23 +0000
with message-id <20170319162022.GA2139 at layer-acht.org>
and subject line input/output errors are most likely hardware issues or similar
has caused the Debian Bug report #826893,
regarding piuparts aborts with "RuntimeError: maximum recursion depth exceeded"
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.)


-- 
826893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826893
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Ryan Kavanagh <rak at debian.org>
Subject: piuparts aborts with "RuntimeError: maximum recursion depth exceeded"
Date: Thu, 9 Jun 2016 17:00:23 -0400
Size: 843040
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20170319/d706e21d/attachment-0002.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Holger Levsen <holger at layer-acht.org>
Subject: input/output errors are most likely hardware issues or similar
Date: Sun, 19 Mar 2017 16:20:23 +0000
Size: 3500
URL: <http://lists.alioth.debian.org/pipermail/piuparts-devel/attachments/20170319/d706e21d/attachment-0003.mht>


More information about the Piuparts-devel mailing list