Source: mitmproxy Version: 5.1.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201119 ftbfs-bullseye
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > [1m original = getattr(target, name, DEFAULT)[0m > [1m else:[0m > [1m local = True[0m > [1m [0m > [1m if name in _builtins and isinstance(target, ModuleType):[0m > [1m self.create = True[0m > [1m [0m > [1m if not self.create and original is DEFAULT:[0m > [1m> raise AttributeError([0m > [1m "%s does not have the attribute %r" % (target, name)[0m > [1m )[0m > [1m[31mE AttributeError: <module 'mitmproxy.ctx' from > '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_mitmproxy/build/mitmproxy/ctx.py'> > does not have the attribute 'log'[0m > > [1m[31m/usr/lib/python3.9/unittest/mock.py[0m:1378: AttributeError > [31m[1m====== 131 failed, 548 passed, 668 deselected, 94 error in 32.25 > seconds =======[0m > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2020/11/19/mitmproxy_5.1.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.