On Thu, 02 Jan 2025 at 18:45:41 +0000, Simon McVittie wrote:
> Control: reassign -1 libwlroots-0.18-dev 0.18.2-1
> Control: retitle -1 libwlroots-0.18-dev: missing dependency on liblcms2-dev

Sorry, I forgot to cc the wlroots maintainers when reassigning. Quoting
full text below.

> On Thu, 02 Jan 2025 at 18:09:04 +0000, Santiago Vila wrote:
> > During a rebuild of all packages in unstable, [gamescope] failed to build:
> > 
> > Note: The following packages fail in a similar way:
> > cage gamescope phoc reform-firedecor sway wayfire wayfire-shadows wcm 
> > wf-shell wstroke
> ...
> > -----------
> > Called: `/usr/bin/pkg-config --cflags wlroots-0.18` -> 1
> > stderr:
> > Package lcms2 was not found in the pkg-config search path.
> > Perhaps you should add the directory containing `lcms2.pc'
> > to the PKG_CONFIG_PATH environment variable
> > Package 'lcms2', required by 'wlroots-0.18', not found
> 
> I think this is a wlroots packaging issue. It is also visible as
> an autopkgtest regression for at least reform-firedecor on wlroots'
> tracker.debian.org page.
> 
> * Steps to reproduce
> 
>     (In a minimal chroot or container, I used debian:sid-slim)
>     apt update
>     apt install --no-install-recommends libwlroots-0.18-dev
>     pkgconf --cflags --libs wlroots-0.18
> 
> * Expected result
> 
>     -I/usr/include/wlroots-0.18 -I/usr/include/libdrm -I/usr/include/pixman-1 
> -pthread -lwlroots-0.18
>     (or something similar)
> 
> * Actual result
> 
>     Package lcms2 was not found in the pkg-config search path.
>     Perhaps you should add the directory containing `lcms2.pc'
>     to the PKG_CONFIG_PATH environment variable
>     Package 'lcms2', required by 'wlroots-0.18', not found
> 
> * Suggested solution
> 
>     Add Depends: liblcms2-dev to libwlroots-0.18-dev
> 
> Adding a superficial autopkgtest similar to the one I contributed in
> https://bugs.debian.org/1088243, and running it in a minimal
> chroot/container/VM before each upload, can be a surprisingly effective
> way to avoid bugs in this category happening in future.
> 
>     smcv

Reply via email to