Hi, Thanks for your quick reply!
在 2024/1/5 11:09, Guillem Jover 写道:
So, my question is: Can dpkg-checkbuilddeps read ||BuildProfileSpec "Registered profile names"pkg.$sourcepackage.$anything in debian/control |Build-Depends section?| Perhaps, it's a bug of dpkg-checkbuilddeps.It can obviously parse the build profile, otherwise it would not have succeeded when you passed the build profile to it. So, I don't understand why this was cloned against dpkg-dev. So I'm closing this now.
If build profile already exist in env variable like DEB_BUILD_PROFILES, dpkg-checkbuilddeps can parse the build profile succeeded, that is right. But if there is nobuild profile env variable exist before, can dpkg-checkbuilddeps parse the debian/control Build-Depends section to getDEB_BUILD_PROFILES env variable? At present, Is dpkg-checkbuilddeps parse pkg.$sourcepackage.$anything in debian/control ? If dpkg-checkbuilddeps parse it, dpkg-checkbuilddeps will pass, then the buildd will begin build these packages.
The report against opencolorio should be closed too IMO, and the loong64 porters need to deal with the circular dependency as any other bootstrapping scenario. Regards, Guillem
Regards, -- 肖盛文 xiao sheng wen https://www.atzlinux.com 《铜豌豆 Linux》基于 Debian 的 Linux 中文 桌面 操作系统 Debian QA page:https://qa.debian.org/developer.php?login=atzlinux%40sina.com Debian salsa:https://salsa.debian.org/atzlinux-guest GnuPG Public Key: 0x00186602339240CB
OpenPGP_signature.asc
Description: OpenPGP digital signature
