Hi! On Fri, 2024-01-05 at 09:27:29 +0800, xiao sheng wen wrote: > IMHO, it's not a bug of opencolorio, even is not a bug of Loongarch.
Well, the circular dependency is problematic for bootstrapping, ideally opencolorio and openimageio would not depend on each other, but that can be handled by the build profiles already present, which is something the porters need to do. This is not something for the maintainers to do. > In opencolorio debian/control, |Build-Depends|[1] already used: > > |libopenimageio-dev (>= 2.3.9.0) <!pkg.opencolorio.noopenimageio>,| > > > |<!pkg.opencolorio.noopenimageio> is a |BuildProfileSpec "Registered profile > names"pkg.$sourcepackage.$anything[2] > > After I installed other |Build-Depends packages of |opencolorio, then run: > > dpkg-checkbuilddeps > dpkg-checkbuilddeps: error: Unmet build dependencies: libopenimageio-dev (>= > 2.3.9.0) > > But after I export DEB_BUILD_PROFILES, dpkg-checkbuilddeps run success: > > export > DEB_BUILD_PROFILES="pkg.opencolorio.noopenimageio";dpkg-checkbuilddeps > atzlinux@nlx:~/opencolorio$ echo $? > 0 > > 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. 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
