Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#31991 closed defect (fixed)

digikam, objectmarker, frei0r-plugins, auto-multiple-choice need revbump following opencv 2.3.x update

Reported by: johannes@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: jgosmann (Jan Gosmann), ddennedy (Dan Dennedy), phw@…, clot@…, trog24 (Frank J. R. Hanstick)
Port: digikam, objectmarker, frei0r-plugins, auto-multiple-choice

Description

Hi, when upgrading all the outdated ports, the upgrade of opencv fails because

Error: opencv 2.3.1a cannot be built while opencv 2.2.0 is installed and active.
Error: Please deactivate opencv 2.2.0 first.

I attach the log for info.

When I manually deactivate opencv and then install the latest version digikam won't start anymore. So there seems to be some inconsistency.

Attachments (4)

main.log (3.8 KB) - added by johannes@… 13 years ago.
log of opencv upgrade attempt
digikam_error.txt (36 bytes) - added by johannes@… 13 years ago.
digikam_2011-11-09-153716_poseidon.crash (37.7 KB) - added by johannes@… 13 years ago.
digikam CrashReport
main.2.log (828.2 KB) - added by trog24 (Frank J. R. Hanstick) 13 years ago.
build failure log file

Download all attachments as: .zip

Change History (16)

Changed 13 years ago by johannes@…

Attachment: main.log added

log of opencv upgrade attempt

comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

The opencv error messages are accurate. You must deactivate old versions of opencv before you can build the new one.

If you then have problems running digikam, please tell us about those. What happens when you start digikam?

Changed 13 years ago by johannes@…

Attachment: digikam_error.txt added

comment:2 Changed 13 years ago by johannes@…

Hi, thank you for looking into this. I have found a solution: First uninstall digikam, then upgrade opencv, then install digikam. Then digikam works again. (The version of digikam stays the same: 2.1.1_0)

It is a bit strange that this is not done automatically by "port upgrade outdated" though; that is when the original error message of opencv occurred. Just deactivating digikam, then upgrading opencv, then activating digikam does not work either; that's when the digikam icon in the dock hops about but instead of the digikam window I get an error message with the newly attached digikam_error details. Digikam appears to need to recompilation.

Anyway, everything seems to be fine for me, now. Thanks again.

comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: jan@… added
Owner: changed from macports-tickets@… to ryandesign@…
Port: digikam added; opencv removed
Summary: opencv @2.3.1a cannot be builtdigikam needs to be recompiled following opencv update

But what happened when you opened digikam before recompiling it? Did it show an error message? Did it crash? (If so, can you attach the crash log, from ~/Library/Logs/CrashReporter)

Changed 13 years ago by johannes@…

digikam CrashReport

comment:4 Changed 13 years ago by johannes@…

I clicked the digikam icon, then the icon in the dock hopped up and down, after while a window opened that asked me whether I wanted to submit a crash report to Apple. The digikam window never appeared. The details of that suggested report to Apple are in the second attachment of this ticket. I am also attaching one of the reports from ~/Library/Logs/CrashReporter. Hope this helps.

comment:5 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Ok, the crash log contains what I suspected:

Dyld Error Message:
  Library not loaded: /opt/local/lib/libopencv_core.2.2.dylib
  Referenced from: /opt/local/lib/libkface.1.dylib
  Reason: image not found

So really we should revbump every port that depends on opencv.

comment:6 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: dan@… phw@… clot@… added
Port: objectmarker frei0r-plugins auto-multiple-choice added
Status: newassigned
Summary: digikam needs to be recompiled following opencv updatedigikam, objectmarker, frei0r-plugins, auto-multiple-choice need revbump following opencv 2.3.x update

comment:7 Changed 13 years ago by ddennedy (Dan Dennedy)

FYI, frei0r-plugins is not critically affected since only 2 of its numerous plugins are affected, and each plugin is a separate lib.

comment:8 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: assignedclosed

comment:9 Changed 13 years ago by trog24 (Frank J. R. Hanstick)

Resolution: fixed
Status: closedreopened

I started out with the same cannot be built error:

Error: opencv 2.3.1a cannot be built while opencv 2.2.0 is installed and active.
Error: Please deactivate opencv 2.2.0 first.
Error: Target org.macports.build returned: incompatible opencv version active
Log for opencv is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_opencv/opencv/main.log
Error: Unable to upgrade port: 1
To report a bug, see <http://guide.macports.org/#project.tickets>

I then deactivated opencv and continued the upgrade of outdated. Opencv did not update.

I then tried sudo port install opencv and got the following error:

Error: Target org.macports.build returned: shell command failed (see log for details)
Log for opencv is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_opencv/opencv/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

I thought that it remnants remained from the previous attempt and did the following: sudo port clean opencv

Before reattempting the install, I thought that it may be better if I uninstalled opencv.

I then made another attempt at installing and got the following error:

--->  Computing dependencies for opencv
--->  Fetching archive for opencv
--->  Attempting to fetch opencv-2.3.1a_1.darwin_9.ppc.tgz from http://packages.macports.org/opencv
--->  Fetching opencv
--->  Verifying checksum(s) for opencv
--->  Extracting opencv
--->  Applying patches to opencv
--->  Configuring opencv
--->  Building opencv
Error: Target org.macports.build returned: shell command failed (see log for details)
Log for opencv is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_graphics_opencv/opencv/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

Attached is the log file from the failure. Please note that this is the PowerPC version.

Changed 13 years ago by trog24 (Frank J. R. Hanstick)

Attachment: main.2.log added

build failure log file

comment:10 Changed 13 years ago by trog24 (Frank J. R. Hanstick)

Cc: trog24@… added

Cc Me!

comment:11 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: reopenedclosed

This ticket is about digikam, objectmarker, frei0r-plugins, and auto-multiple-choice needing their revisions increased in order to force a rebuild against the latest opencv. This was accomplished in r87084 and this ticket is therefore closed. You are experiencing a build failure of opencv, which is an unrelated matter. Please open a new ticket for that.

comment:12 Changed 13 years ago by trog24 (Frank J. R. Hanstick)

It changed from opencv to digikam for the opening complaint is the same as mine.

Note: See TracTickets for help on using tickets.