https://ci.debian.net/packages/g/gsequencer/testing/armhf/76479971/

...
190s checking for poppler-glib >= 0.71.0... no
190s configure: error: Package requirements (poppler-glib >= 0.71.0) were not met:
190s
190s Package dependency requirement 'nss >= 3.130' could not be satisfied.
190s Package 'nss' has version '3.129', required version is '>= 3.130'
...


This is due to:
/usr/lib/x86_64-linux-gnu/pkgconfig/poppler.pc:Requires.private: freetype2 >= 2.13 zlib fontconfig >= 2.15 libjpeg libcurl >= 8.5 nss >= 3.130 gpgmepp >= 1.19 libopenjp2 lcms2 >= 2.14 libpng libtiff-4 >= 4.7.2


Putting the build version into Requires.private makes sense for
static linking, but if it is done the Depends of libpoppler-dev
have to be generated accordingly.

Control: forwarded -1
https://gitlab.freedesktop.org/poppler/poppler/-/work_items/1815

Thank you. I filed the bug upstream because this is caused by
upstream's build system.

If I used nss 3.130 in the Depends field, then poppler wouldn't be
able to transition to Testing until nss 1.30 does which is the same
situation we are in now. And I don't think it's very practical to
generate -dev Depends versions based on the version the package is
built with.

I agree that it feels like an RC bug for an unnecessary build system
design to delay security updates from reaching Testing.

To avoid this, I think we'd need to revert the 2025 change to how
poppler prepares its .pc files.

Thank you,
Jeremy Bícha

Control: found -1 26.07.0-2

The fundamental problem also affects the version in testing, let's not
block migration when the last autopkgtest will have finished on this bug.

cu
Adrian