Your message dated Fri, 5 Jan 2024 04:09:15 +0100
with message-id <zzdy28b8r6lxn...@thunder.hadrons.org>
and subject line Re: Bug#1059837: opencolorio： Please help fix circle
dependence in Loongarch between openimageio and opencolorio
has caused the Debian Bug report #1060033,
regarding dpkg-dev: dpkg-checkbuilddeps not read BuildProfileSpec "Registered
profile names" pkg.$sourcepackage.$anything,in debian/control Build-Depends
section
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1060033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opencolorio
Version: 2.1.3+dfsg-1
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64
Dear Maintainer,
Currently when I built opencolorio in Loongarch env, I
found there is circle dependence between openimageio and opencolorio
The buildd link is following:
https://buildd.debian.org/status/package.php?p=opencolorio&suite=sid
https://buildd.debian.org/status/package.php?p=openimageio&suite=sid
But the initial version of opencolorio can build pass by using
DEB_BUILD_PROFILE="pkg.opencolorio.noopenimageio" when dpkg-buildpackage
running.
and then we can use this first binary output to compile
the openimageio to fix the circle dependence.
I have verified and passed in my local env.
Please help fix the issue for some other application waiting the
opencolorio and openimageio binary.
Any question, contact me!
--- End Message ---
--- Begin Message ---
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
--- End Message ---
