Your message dated Thu, 20 Jul 2017 11:24:33 +0200
with message-id <[email protected]>
and subject line Re: Bug#866800: python2.7 FTBFS: RuntimeError: maximum
recursion depth exceeded while calling a Python object
has caused the Debian Bug report #866800,
regarding python2.7 FTBFS: RuntimeError: maximum recursion depth exceeded while
calling a Python object
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 [email protected]
immediately.)
--
866800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866800
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: python2.7
Version: 2.7.13-3
Severity: serious
python2.7 FTBFS on most architectures with variants of
RuntimeError: maximum recursion depth exceeded while calling a Python object
https://buildd.debian.org/status/package.php?p=python2.7
--- End Message ---
--- Begin Message ---
Version: 2.7.13-4
On 01.07.2017 21:30, Adrian Bunk wrote:
> Source: python2.7
> Version: 2.7.13-3
> Severity: serious
>
> python2.7 FTBFS on most architectures with variants of
> RuntimeError: maximum recursion depth exceeded while calling a Python object
>
> https://buildd.debian.org/status/package.php?p=python2.7
Fixed.
--- End Message ---
