Shibboleth Developers

["Scott Cantor" <>]

> After the upgrade to 2.1 (using "sudo port upgrade shibboleth") I now
> have problems starting the IdP on my Intel 10.5.5 system.

My guess is it also upgraded icu somewhere and that broke the Xerces
dependency. I don't think the port system "works" in the most general sense
of tracking dependencies for you and preventing issues. It certainly hasn't
for me.

It might help if the actual Xerces in the macport tree worked, but I can't
get them to fix it, since it only breaks when the package is used in the
presence of a fork/exec (Apache).

> but no entries in the log file or any other error message. But I assume
> the same above error would be output as well.

I assume so.

> As the error suggests, the problem maybe has to do with icu.

The problem is completely due to icu.

> Looking at which versions are installed, it seems there are the following:
> --->          icu @3.8.1_0
> --->          icu @4.0_0 (active)

Xerces was built against the former, whereas you or something you installed
pulled in the latter without regard for the fact that the old one was in
use. With RPM, that doesn't happen.
 
> Any ideas or hints what could be the problem? Anyone successfully could
> upgrade their SP on the Mac with Ports?

I think you need to perform microsurgery when you upgrade things with that
system. In this case, you'll need to manually identify what replaced icu,
get rid of it, get it back to 3.8.1, and then it will probably work.

I have a bunch of patches from Alan that apparently make RPM work on the
Mac, and I know RPM works better than this nonsense does, so that's probably
where we're headed, I just haven't had time to look at them. If you wanted
to try that somewhere, the patches are in jira.

-- Scott