[MacPorts] #45521: osxfuse 2.7.0 fails to load (Yosemite)
MacPorts
noreply at macports.org
Thu Oct 23 15:33:27 PDT 2014
#45521: osxfuse 2.7.0 fails to load (Yosemite)
---------------------------------+----------------------
Reporter: nicolas.stransky@… | Owner: dports@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.2
Resolution: | Keywords: yosemite
Port: osxfuse |
---------------------------------+----------------------
Comment (by macports.org@…):
I do have an Apple developer certificate, but I ran into problems where my
signature was valid, but not accepted by the system security assessment
policy. The problem seems to be that not every developer certificate can
be used to sign kernel extensions. This may prove to be a real problem for
many (most) MacPorts users.
Meanwhile, I have used the following workaround:
1. Install the upstream (i.e. "official") ''osxfuse'' binary from
https://osxfuse.github.io/ that corresponds to what MacPorts is using. At
the time of this writing, it is 2.7.0.
2. In the shell, replace the MacPorts ''osxfuse'' with the signed binary:
{{{
$ cd /opt/local/Library/Filesystems
$ sudo mv osxfusefs.fs osxfusefs.fs.macports
$ sudo ln -s /Library/Filesystems/osxfusefs.fs osxfusefs.fs
}}}
Any port that has a dependency on
/opt/local/Library/Filesystems/osxfusefs.fs/... should now work.
I have tested successfully with ''encfs'' and ''TrueCrypt'' (the latter
with a local portfile, see https://trac.macports.org/ticket/41421 for
details).
Maybe the cleanest solution is to modify the ''osxfuse'' port to download
and install the upstream binaries?
--
Ticket URL: <https://trac.macports.org/ticket/45521#comment:5>
MacPorts <https://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list