Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#42874 closed defect (worksforme)

libgpod 0.8.0 + staging into destroot error

Reported by: rubend46@… Owned by: rmstonecipher@…
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: Cc: anlag@…, mspivak@…, ryandesign (Ryan Schmidt)
Port: libgpod

Description

Hello, trying to install digikam i'm way through but i can't be able to past libgpod installation.

I have OS X 10.9.2 and Xcode 5.1

XXXX-MacBook-Air:~ XXXXXX$ sudo port install digikam +debug
Password:
--->  Computing dependencies for digikam
--->  Dependencies to be installed: libgpod libkdcraw libraw libkexiv2 libkipi libksane sane-backends net-snmp liblqr marble gpsd libkdeedu opencv qt4-mac-sqlite3-plugin
--->  Staging libgpod into destroot
Error: org.macports.destroot for port libgpod returned: error renaming "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_libgpod/libgpod/work/destroot/opt/local/lib/python2.7": no such file or directory
Error: Failed to install libgpod
Please see the log file for port libgpod for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_multimedia_libgpod/libgpod/main.log
Error: The following dependencies were not installed: libgpod libkdcraw libraw libkexiv2 libkipi libksane sane-backends net-snmp liblqr marble gpsd libkdeedu opencv qt4-mac-sqlite3-plugin
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port digikam failed

Attachments (1)

main.log (247.2 KB) - added by rubend46@… 6 years ago.

Download all attachments as: .zip

Change History (16)

comment:1 Changed 6 years ago by persramd@…

Cc: persramd@… added

Cc Me!

comment:2 Changed 6 years ago by persramd@…

Cc: persramd@… removed

Cc Me!

comment:3 Changed 6 years ago by mf2k (Frank Schima)

Keywords: libgpod removed
Owner: changed from macports-tickets@… to rmstonecipher@…
Port: libgpod added

In the future, please fill in the Port field and Cc the port maintainers (port info --maintainers libgpod).

This is not a clean build log. Please clean the port and try again. Then attach the new main.log file.

Changed 6 years ago by rubend46@…

Attachment: main.log added

comment:4 Changed 6 years ago by rubend46@…

I cleaned the port and attached the new log. Thanks in advance.

comment:5 Changed 6 years ago by anlag@…

Cc: anlag@… added

Cc Me!

comment:6 Changed 6 years ago by rubend46@…

Cc: rubend46@… added

Cc Me!

comment:7 Changed 6 years ago by rubend46@…

Cc: rubend46@… removed

Cc Me!

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

Cc: mspivak@… added

Has duplicate #42939.

comment:9 in reply to:  8 ; Changed 6 years ago by rubend46@…

Replying to ryandesign@…:

Has duplicate #42939.

Yes is the same problem but none is solved.

comment:10 in reply to:  9 Changed 6 years ago by mspivak@…

Replying to rubend46@…:

Replying to ryandesign@…:

Has duplicate #42939.

Yes is the same problem but none is solved.

Any ideas on what my next step is to be? Thanks again

comment:11 Changed 6 years ago by mspivak@…

I tried a other things but nothing seems to work. Any ideas? Thanks for helping

comment:12 in reply to:  11 Changed 6 years ago by contacto@…

Replying to mspivak@…:

I tried a other things but nothing seems to work. Any ideas? Thanks for helping

I just did a port selfupdate and then installed it again (doing a clean before) and worked right.

comment:13 Changed 6 years ago by anlag@…

I can confirm that cleaning up and selfupdating now solves the problem. Specifically, I used:

  • sudo port clean digikam
  • sudo port clean libgpod
  • sudo port selfupdate
  • sudo port install digikam

This lead to digikam being successfully installed.

comment:14 Changed 6 years ago by mf2k (Frank Schima)

Resolution: worksforme
Status: newclosed

Calling this issue closed then.

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

Cc: ryandesign@… added

See #49384 for the real solution: it needed swig-python.

Note: See TracTickets for help on using tickets.