[Pkg-ime-devel] Bug#846688: libpyzy: FTBFS: build-dependency not installable: libopencc-dev

Lucas Nussbaum lucas at debian.org
Sat Dec 3 07:32:22 UTC 2016

Source: libpyzy
Version: 1.0.1-5
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64


During a rebuild of all packages in sid, your package failed to build on

Relevant part (hopefully):
> +------------------------------------------------------------------------------+
> | Install package build dependencies                                           |
> +------------------------------------------------------------------------------+
> Setup apt archive
> -----------------
> Merged Build-Depends: debhelper (>= 9.0.0), dh-autoreconf, libglib2.0-dev, uuid-dev, libsqlite3-dev, libopencc-dev, sqlite3, python
> Filtered Build-Depends: debhelper (>= 9.0.0), dh-autoreconf, libglib2.0-dev, uuid-dev, libsqlite3-dev, libopencc-dev, sqlite3, python
> dpkg-deb: building package 'sbuild-build-depends-libpyzy-dummy' in '/<<BUILDDIR>>/resolver-MMJ5CH/apt_archive/sbuild-build-depends-libpyzy-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy sbuild-build-depends-libpyzy-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<<BUILDDIR>>/resolver-MMJ5CH/apt_archive ./ InRelease
> Get:2 copy:/<<BUILDDIR>>/resolver-MMJ5CH/apt_archive ./ Release [963 B]
> Ign:3 copy:/<<BUILDDIR>>/resolver-MMJ5CH/apt_archive ./ Release.gpg
> Get:4 copy:/<<BUILDDIR>>/resolver-MMJ5CH/apt_archive ./ Sources [537 B]
> Get:5 copy:/<<BUILDDIR>>/resolver-MMJ5CH/apt_archive ./ Packages [620 B]
> Fetched 2120 B in 0s (181 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> Install libpyzy 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-libpyzy-dummy : Depends: libopencc-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:

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 Pkg-ime-devel mailing list