Your message dated Mon, 2 Nov 2020 09:29:30 +0100
with message-id <[email protected]>
and subject line Cannot reproduce
has caused the Debian Bug report #973224,
regarding uwsgi-apparmor: FTBFS: make[1]: pyversions: No such file or directory
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.)
--
973224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973224
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: uwsgi-apparmor
Version: 0.0.0+git.2014.09.15.7d6d7bd7eb-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> make: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> dh build
> dh_update_autotools_config
> dh_autoreconf
> debian/rules override_dh_auto_build
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e && for pyvers in 3.9 3.8; do \
> PYTHON=python$pyvers uwsgi --build-plugin . ;\
> done
> make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/10/27/uwsgi-apparmor_0.0.0+git.2014.09.15.7d6d7bd7eb-3_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.
--- End Message ---
--- Begin Message ---
Hi,
Probably the issue was when Python 3.9 just came to Unstable. I cannot
reproduce here. So, I'm closing this bug.
Thomas
--- End Message ---
