[Bug 2136829] Re: pyqt6 FTBFS with dpkg from resolute-proposed due to --package-metadata
Launchpad Bug Tracker
2136829 at bugs.launchpad.net
Sat Jan 10 18:52:15 UTC 2026
This bug was fixed in the package dpkg - 1.22.21ubuntu9
---------------
dpkg (1.22.21ubuntu9) resolute; urgency=medium
* Escape { and } for --package-metadata as well (LP: #2136829)
dpkg (1.22.21ubuntu8) resolute; urgency=medium
* Fix typo in the last patch.
dpkg (1.22.21ubuntu7) resolute; urgency=medium
* Revert the dpkg-buildflags change from last upload. This would
introduce regressions for packages not correctly picking up flags
from the command line. If such a change should be made, it should
be made after an LTS release, together with the commitment to check
the build artifact in the archive. Still, don't export the env vars
DEB_BUILD_OS_RELEASE_ID, DEB_HOST_ARCH, DEB_SOURCE, DEB_VERSION.
See LP: #2071468.
Also include the architecture variant in the env var. See LP: #2131806.
dpkg (1.22.21ubuntu6) resolute; urgency=medium
* Drop unused elf-package-metadata specs files
* dpkg-buildflags: set --package-metadata directly in LDFLAGS instead of
exporting ELF_PACKAGE_METADATA (Closes: #1117999, LP: #2071468)
* Include architecture variant in ELF package metadata (LP: #2131806)
-- Benjamin Drung <bdrung at ubuntu.com> Thu, 18 Dec 2025 20:18:21 +0100
** Changed in: dpkg (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dpkg in Ubuntu.
https://bugs.launchpad.net/bugs/2136829
Title:
pyqt6 FTBFS with dpkg from resolute-proposed due to --package-metadata
Status in dpkg package in Ubuntu:
Fix Released
Status in pyqt6 package in Ubuntu:
Fix Released
Bug description:
pyqt6 FTBFS in resolute-proposed with the following error:
https://launchpadlibrarian.net/837876594/buildlog_ubuntu-resolute-
amd64v3.pyqt6_6.10.1-1_BUILDING.txt.gz
E: pybuild pybuild:389: configure: plugin custom failed with:
'%22type%22'
It happens because PYBUILD_CONFIGURE_ARGS has the following value:
{interpreter} /usr/bin/sip-build --verbose --no-make --confirm-
license --pep484-pyi --target-dir /usr/lib/python3/dist-packages
--build-dir {build_dir} --qmake /usr/lib/qt6/bin/qmake --qmake-setting
CONFIG += nostrip --qmake-setting QMAKE_CXXFLAGS += "-g -O2 -fno-omit-
frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-
map=/pyqt6-6.10.1=. -flto=auto -ffat-lto-objects -fstack-protector-
strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-
protection -fdebug-prefix-map=/pyqt6-6.10.1=/usr/src/pyqt6-6.10.1-1
-Wdate-time -D_FORTIFY_SOURCE=3" --qmake-setting QMAKE_LFLAGS +=
"-Wl,-Bsymbolic-functions -Wl,--package-
metadata={%22type%22:%22deb%22%2C%22os%22:%22ubuntu%22%2C%22name%22:%22pyqt6%22%2C%22version%22:%226.10.1-1%22%2C%22architecture%22:%22amd64%22}
-flto=auto -ffat-lto-objects -Wl,-z,relro"
But pybuild treats everything between { and } as substitution markers.
If it’s possible to escape { and } as %7B and %7D, that should fix the
error.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/2136829/+subscriptions
More information about the foundations-bugs
mailing list