[Debian-med-packaging] Bug#871377: pymia: FTBFS: build-dependency not installable: libmia-2.4-dev
Lucas Nussbaum
lucas at debian.org
Mon Aug 7 16:09:25 UTC 2017
Source: pymia
Version: 0.1.9-1
Severity: serious
Tags: buster sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64
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), pkg-config, python-all-dev, python3-all-dev, python-numpy, python3-numpy, python-setuptools, python3-setuptools, libmia-2.4-dev
> Filtered Build-Depends: debhelper (>= 9), pkg-config, python-all-dev, python3-all-dev, python-numpy, python3-numpy, python-setuptools, python3-setuptools, libmia-2.4-dev
> dpkg-deb: building package 'sbuild-build-depends-pymia-dummy' in '/<<BUILDDIR>>/resolver-mI6weo/apt_archive/sbuild-build-depends-pymia-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override file:
> dpkg-scanpackages: warning: sbuild-build-depends-core-dummy sbuild-build-depends-pymia-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<<BUILDDIR>>/resolver-mI6weo/apt_archive ./ InRelease
> Get:2 copy:/<<BUILDDIR>>/resolver-mI6weo/apt_archive ./ Release [963 B]
> Ign:3 copy:/<<BUILDDIR>>/resolver-mI6weo/apt_archive ./ Release.gpg
> Get:4 copy:/<<BUILDDIR>>/resolver-mI6weo/apt_archive ./ Sources [536 B]
> Get:5 copy:/<<BUILDDIR>>/resolver-mI6weo/apt_archive ./ Packages [620 B]
> Fetched 2119 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
>
> Install pymia 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-pymia-dummy : Depends: libmia-2.4-dev but it is not going to be installed
> 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/2017/08/07/pymia_0.1.9-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.
More information about the Debian-med-packaging
mailing list