[MacPorts] #69381: opencv4 @4.8.0_4+contrib build failure

MacPorts noreply at macports.org
Tue May 14 00:55:15 UTC 2024


#69381: opencv4 @4.8.0_4+contrib build failure
----------------------+----------------------------
  Reporter:  fmw42    |      Owner:  mascguy
      Type:  defect   |     Status:  assigned
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.9.1
Resolution:           |   Keywords:  Ventura, arm64
      Port:  opencv4  |
----------------------+----------------------------

Comment (by ryandesign):

 Replying to [comment:24 fmw42]:
 > >py39-opencv4 declares a dependency on openexr. Therefore when you try
 to install py39-opencv4 MacPorts will ensure openexr is up to date first.
 >
 > If it ensured openexr is up-to-date, then why did the install not work.

 As I have repeatedly said, I do not know. Presumably it means something
 other than openexr was the cause. If we knew what the problem was we would
 fix it. If you or anybody knows how to fix this or any problem in any
 port, please submit a pull request, as always.

 > Seems to me that perhaps it saw that openexr was installed and did not
 update it and that old version was not compatible

 That is not possible. That's not how MacPorts works. As I said, MacPorts
 will upgrade dependencies first.

 Ok, there are two ways that it is possible. One is if you upgrade to a new
 version of let's say openexr, and then deliberately downgrade to an older
 still-installed version using `sudo port activate`. Then, when you install
 a port that depends on openexr, MacPorts will not upgrade openexr to the
 new version first because it sees that it is already installed but
 deactivated so it assumes you did this deliberately and know what you're
 doing. The other way is if you install or upgrade a port using the `-n`
 flag to tell MacPorts not to upgrade dependencies first. But neither of
 those things happened here because your log says:
 {{{
 --     OpenEXR:                     OpenEXR::OpenEXR (ver 3.2.4)
 }}}
 and that is the latest version available in MacPorts, so your openexr was
 already up to date.

 There is [https://github.com/AcademySoftwareFoundation/openexr/issues/1566
 an openexr bug report about this] which was closed without any clear
 solution being discovered.

-- 
Ticket URL: <https://trac.macports.org/ticket/69381#comment:25>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list