Hi everyone,
After some of the system upgrades (I'm using synth) SMB gfvs functionality in x11-fm/pcmanfm stopped working.
At the closer look I've noticed that devel/gvfs still depends on (and installs) net/samba-libsmbclient which the ports system now says is obsoleted:
So after a research I discovered that the latter kept being installed from the existing packages. However, during the building process gvfs builds net/samba44 as a dependency -- so one would expect it depends on libsmbclient.so from that port.
I then removed the existing samba36-libsmbclient package from /var/synth/live_packages/All directory to make things 100% clean and then reinstalled devel/gvfs using synth -- the surest way, one would think, to make things work for sure. And it did install without complains, but now SMB related parts of it complain:
So what am I supposed to do? Some people, commenting on an issue that seems related, report that just building net/samba44 and manually copying libsmbclient.so from the build directory fixes the problem. I haven't tried it myself, but obviously this is NOT they way it's supposed to work?
I'm going to run
After some of the system upgrades (I'm using synth) SMB gfvs functionality in x11-fm/pcmanfm stopped working.
At the closer look I've noticed that devel/gvfs still depends on (and installs) net/samba-libsmbclient which the ports system now says is obsoleted:
Code:
Port: net/samba-libsmbclient
Moved: net/samba43
Date: 2017-03-21
Reason: Obsolete
I then removed the existing samba36-libsmbclient package from /var/synth/live_packages/All directory to make things 100% clean and then reinstalled devel/gvfs using synth -- the surest way, one would think, to make things work for sure. And it did install without complains, but now SMB related parts of it complain:
Code:
Shared object "libsmbclient.so.0" not found, required by "gvfsd-smb-browse".
So what am I supposed to do? Some people, commenting on an issue that seems related, report that just building net/samba44 and manually copying libsmbclient.so from the build directory fixes the problem. I haven't tried it myself, but obviously this is NOT they way it's supposed to work?
I'm going to run
synth upgrade-system
anyway, but it will take a long time and I'm afraid will NOT fix the problem, just as isolated package run of synth
hasn't fixed it.