#51963 closed defect (worksforme)
"Error: Failed to install gnome-vfs" when installing Wine
Reported by: | eclipzed@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Not set | Milestone: | |
Component: | ports | Version: | |
Keywords: | lion | Cc: | mojca (Mojca Miklavec), jyrkiwahlstedt |
Port: | gnome-vfs python35 |
Description
I'm trying to install Wine and I keep getting this error:
Error: org.macports.activate for port gnome-vfs returned: command execution failed Error: Failed to install gnome-vfs Please see the log file for port gnome-vfs for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_wine/wine/main.log Error: The following dependencies were not installed: gstreamer010-gst-plugins-base gnome-vfs iso-codes python35 libogg libtheora libvorbis orc coreutils xorg-libXv xorg-videoproto lcms2 libGLU To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port wine failed
Yes, I have tried doing a cleaning of the port, installing the port by itself afterwards, and then running "sudo port install wine" again. This didn't help. Doing a selfupdate/update outdated didn't make a difference either.
If I could have some help with this that would be great.
I've attached the main.log.
Attachments (2)
Change History (8)
Changed 8 years ago by eclipzed@…
comment:1 Changed 8 years ago by eclipzed@…
Cc: | eclipzed@… added |
---|
comment:2 Changed 8 years ago by mf2k (Frank Schima)
Cc: | eclipzed@… removed |
---|---|
Keywords: | wine error gnome-vfs removed |
comment:3 follow-up: 4 Changed 8 years ago by dbevans (David B. Evans)
From your logfile it appears that the gnome-vfs is failing during the post-activate phase when gconf is attempting to install (actually register the already installed gconf schema files) provided by gnome-vfs. The specific error is as follows
:info:clean Installed schema `/schemas/system/smb/workgroup' for locale `hr' :info:clean Installed schema `/schemas/system/smb/workgroup' for locale `te' :info:clean Installed schema `/schemas/system/smb/workgroup' for locale `dz' :info:clean Installed schema `/schemas/system/smb/workgroup' for locale `hu' :info:clean Installed schema `/schemas/system/smb/workgroup' for locale `pl' :info:clean Installed schema `/schemas/system/smb/workgroup' for locale `th' :info:clean Installed schema `/schemas/system/smb/workgroup' for locale `lt' :info:clean Command failed: export GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source` && gconftool-2 --makefile-install-rule /opt/local/etc/gconf/schemas/*.schemas :info:clean Exit code: 1 :error:clean org.macports.activate for port gnome-vfs returned: command execution failed :debug:clean Error code: NONE :debug:clean Backtrace: command execution failed while executing "proc-post-org.macports.activate-activate-0 org.macports.activate" ("eval" body line 1) invoked from within "eval $post $targetname" :error:clean Failed to install gnome-vfs :debug:clean could not read "/opt/local/share/locale/zu/LC_MESSAGES/gnome-vfs-2.0.mo": no such file or directory
This indicates that the gconftool command failed trying to register the schema for locale 'zu' during the post-activate phase due to the fact that the corresponding locale file
/opt/local/share/locale/zu/LC_MESSAGES/gnome-vfs-2.0.mo
which should have been installed during the previous gnome-vfs activate phase proper, seems to be missing. You might check to see if this is true.
However, at this point, gnome-vfs may be in a limbo state of sorts as port
may consider it to be installed and active since it completed the main installation and activation phases.
What does the following command report?
$ port installed gnome-vfs
If this indicates gnome-vfs is active, then I'd suggest you try the following command sequence to deactivate it and attempt a clean install
$ sudo port deactivate gnome-vfs $ sudo port clean gnome-vfs $ sudo port install gnome-vfs +universal
In the meantime, I'll attempt to recreate your results.
comment:4 Changed 8 years ago by eclipzed@…
Replying to devans@…:
From your logfile it appears that the gnome-vfs is failing during the post-activate phase when gconf is attempting to install (actually register the already installed gconf schema files) provided by gnome-vfs. The specific error is as follows
:info:clean Installed schema `/schemas/system/smb/workgroup' for locale `hr' :info:clean Installed schema `/schemas/system/smb/workgroup' for locale `te' :info:clean Installed schema `/schemas/system/smb/workgroup' for locale `dz' :info:clean Installed schema `/schemas/system/smb/workgroup' for locale `hu' :info:clean Installed schema `/schemas/system/smb/workgroup' for locale `pl' :info:clean Installed schema `/schemas/system/smb/workgroup' for locale `th' :info:clean Installed schema `/schemas/system/smb/workgroup' for locale `lt' :info:clean Command failed: export GCONF_CONFIG_SOURCE=`gconftool-2 --get-default-source` && gconftool-2 --makefile-install-rule /opt/local/etc/gconf/schemas/*.schemas :info:clean Exit code: 1 :error:clean org.macports.activate for port gnome-vfs returned: command execution failed :debug:clean Error code: NONE :debug:clean Backtrace: command execution failed while executing "proc-post-org.macports.activate-activate-0 org.macports.activate" ("eval" body line 1) invoked from within "eval $post $targetname" :error:clean Failed to install gnome-vfs :debug:clean could not read "/opt/local/share/locale/zu/LC_MESSAGES/gnome-vfs-2.0.mo": no such file or directoryThis indicates that the gconftool command failed trying to register the schema for locale 'zu' during the post-activate phase due to the fact that the corresponding locale file
/opt/local/share/locale/zu/LC_MESSAGES/gnome-vfs-2.0.mowhich should have been installed during the previous gnome-vfs activate phase proper, seems to be missing. You might check to see if this is true.
However, at this point, gnome-vfs may be in a limbo state of sorts as
port
may consider it to be installed and active since it completed the main installation and activation phases.What does the following command report?
$ port installed gnome-vfsIf this indicates gnome-vfs is active, then I'd suggest you try the following command sequence to deactivate it and attempt a clean install
$ sudo port deactivate gnome-vfs $ sudo port clean gnome-vfs $ sudo port install gnome-vfs +universalIn the meantime, I'll attempt to recreate your results.
Thank you for the quick reply.
I checked to see if gnome-vfs-2.0.mo was missing and it was, in fact, in its correct place.
I then checked to see if gnome-vfs was active, and it was, so I did what you suggested. When I got to the install command, it gave an error, but when I tried it again, strangely, it worked. I used the "sudo port install wine" command again and it began proceeding with the rest of the dependencies.
Now, however, it is having a problem with installing python35.
Error: org.macports.build for port python35 returned: command execution failed Error: Failed to install python35 Please see the log file for port python35 for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_python35/python35/main.log Error: The following dependencies were not installed: gstreamer010-gst-plugins-base iso-codes python35 libogg libtheora libvorbis orc coreutils xorg-libXv xorg-videoproto lcms2 libGLU To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port wine failed
I'll attach its main.log.
comment:5 follow-up: 6 Changed 8 years ago by dbevans (David B. Evans)
Cc: | mojca@… jwa@… added |
---|---|
Keywords: | lion added |
Port: | python35 added |
Resolution: | → worksforme |
Status: | new → closed |
Version: | 2.3.4 |
This is an entirely different compiler related issue for python35 on mac os 10.7 which has been previously reported in #49272 and upstream as well. If you look at the log file excerpt submitted in the upstream bug report, the error is exactly the same as you are seeing so you should pursue this new problem there.
This issue hasn't been fixed as yet but you might try using the work around suggested by mojca in comment:4 there to use a more modern compiler.
Closing this ticket as 'works for me' since the original problem has been resolved via a clean rebuild.
comment:6 Changed 8 years ago by eclipzed@…
Replying to devans@…:
This is an entirely different compiler related issue for python35 on mac os 10.7 which has been previously reported in #49272 and upstream as well. If you look at the log file excerpt submitted in the upstream bug report, the error is exactly the same as you are seeing so you should pursue this new problem there.
This issue hasn't been fixed as yet but you might try using the work around suggested by mojca in comment:4 there to use a more modern compiler.
Closing this ticket as 'works for me' since the original problem has been resolved via a clean rebuild.
Thank you for your help. I solved the Python problem with one of the work arounds you shared too.
I will come back should anymore problems arrive but for now things are good!
As reporter, you do not need to Cc yourself.