Your message dated Sat, 26 Jan 2019 13:33:50 +0100
with message-id
<CAMEZBDJS2de1eRXLZeLcD6n_LZ-vfT+boH=p+yy6yocqjov...@mail.gmail.com>
and subject line close 917694
has caused the Debian Bug report #917694,
regarding nuitka: FTBFS: build-dependency not installable: python-imaging
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 ow...@bugs.debian.org
immediately.)
--
917694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nuitka
Version: 0.6.0.6+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> +------------------------------------------------------------------------------+
> | Install package build dependencies
> |
> +------------------------------------------------------------------------------+
>
>
> Setup apt archive
> -----------------
>
> Merged Build-Depends: debhelper (>= 9), dh-python | base-files (<< 9.6),
> python (>= 2.6.6-2), python-all-dbg (>= 2.6.6-2), python-all-dev (>=
> 2.6.6-2), python-setuptools, rst2pdf (>= 0.14-2), python-imaging |
> python-pil, scons (>= 2.0.0), python3-all-dev (>= 3.2), python3-all-dbg (>=
> 3.2), python3-setuptools, python-appdirs | base-files (<< 7.2),
> python3-appdirs | base-files (<< 7.2), strace, chrpath, gdb
> Filtered Build-Depends: debhelper (>= 9), dh-python, python (>= 2.6.6-2),
> python-all-dbg (>= 2.6.6-2), python-all-dev (>= 2.6.6-2), python-setuptools,
> rst2pdf (>= 0.14-2), python-imaging, scons (>= 2.0.0), python3-all-dev (>=
> 3.2), python3-all-dbg (>= 3.2), python3-setuptools, python-appdirs,
> python3-appdirs, strace, chrpath, gdb
> dpkg-deb: building package 'sbuild-build-depends-nuitka-dummy' in
> '/<<BUILDDIR>>/resolver-kOsmDm/apt_archive/sbuild-build-depends-nuitka-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override
> file:
> dpkg-scanpackages: warning: sbuild-build-depends-core-dummy
> sbuild-build-depends-nuitka-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<<BUILDDIR>>/resolver-kOsmDm/apt_archive ./ InRelease
> Get:2 copy:/<<BUILDDIR>>/resolver-kOsmDm/apt_archive ./ Release [963 B]
> Ign:3 copy:/<<BUILDDIR>>/resolver-kOsmDm/apt_archive ./ Release.gpg
> Get:4 copy:/<<BUILDDIR>>/resolver-kOsmDm/apt_archive ./ Sources [620 B]
> Get:5 copy:/<<BUILDDIR>>/resolver-kOsmDm/apt_archive ./ Packages [678 B]
> Fetched 2261 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
>
> Install nuitka build dependencies (apt-based resolver)
> ------------------------------------------------------
>
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
> sbuild-build-depends-nuitka-dummy : Depends: python-imaging but it is not
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/nuitka_0.6.0.6+ds-1_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 ---
close 917694
The issue has been resolved in 0.6.1 (which was not uploaded) and
fixed with upload of 0.6.1.1 which contains the fix.
--- End Message ---
