On Mittwoch, 19. Januar 2022, 10:17:30 CET Kai Liu wrote:
On 2022/01/19 Wed 09:41, Andreas Schwab wrote:
On Jan 19 2022, Kai Liu wrote: ...
But most of the BuildRequires only point to a package name, without specifying any EVR. In such case if my paths provide different versions/releases of that package I should have seen "have choice" for versions. But I don't remember seen such case, all "have choices" I have seen are only about different packages can provide the same capability.
Binary package are only looked up by name. Thus if you have multiple repositories in the path that contain binary packages with the same name, only the package from the first such repository will be used, disregarding the version. That can result in an unresolved dependency if the BuildRequires has a versioned dependency, even if a later repository would provide a matching version.
From here: https://openbuildservice.org/help/manuals/obs-user-guide/cha.obs.prjconfig.h...
I noticed there is an "ExpandFlags: unorderedimagerepos" option that set the preference for image build to highest version instead of first found. Is there a similar thing for package build?
no (on purpose)
--
Adrian Schroeter