Bug#952013: cogl: FTBFS: configure: error: Package requirements ( cairo >= 1.10 gobject-2.0 gmodule-no-export-2.0 gdk-pixbuf-2.0 >= 2.0 wayland-egl >= 1.0.0 wayland-client >= 1.0.0 gbm libdrm wayland-server >= 1.1.90 egl x11 xext xfixes >= 3 xdamage xcomposite >= 0.4 xrandr >= 1.2) were not met

Lucas Nussbaum lucas at debian.org
Sun Feb 23 06:49:58 GMT 2020


Source: cogl
Version: 1.22.4-3
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> checking for GNU gettext in libc... yes
> checking whether to use NLS... yes
> checking where the gettext function comes from... libc
> checking for linguas... an ar as ast be bg bs ca ca at valencia cs da de el en_CA en_GB eo es eu fa fr fur gl he hi hr hu id it ja km kn ko lt lv ml nb ne nl oc or pa pl pt pt_BR ro ru sk sl sr sr at latin sv ta te th tr ug uk vi zh_CN zh_HK zh_TW 
> checking for COGL_DEP... no
> configure: error: Package requirements ( cairo >= 1.10 gobject-2.0 gmodule-no-export-2.0 gdk-pixbuf-2.0 >= 2.0 wayland-egl >= 1.0.0 wayland-client >= 1.0.0 gbm libdrm wayland-server >= 1.1.90 egl x11 xext xfixes >= 3 xdamage xcomposite >= 0.4 xrandr >= 1.2) were not met
> 
> No package 'libdrm' found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables COGL_DEP_CFLAGS
> and COGL_DEP_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> 	tail -v -n \+0 config.log

The full build log is available from:
   http://qa-logs.debian.net/2020/02/22/cogl_1.22.4-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.



More information about the pkg-gnome-maintainers mailing list