not included in shibboleth RPM

David Hodnett david at
Tue May 6 20:11:18 EDT 2014

My apologies. I was very flippant and casual in my choice of words.

On Tue, May 6, 2014 at 11:53 AM, Cantor, Scott <cantor.2 at> wrote:

> On 5/6/14, 2:40 PM, "david at" <david at> wrote:
> >I'm using Amazon Linux (for Amazon AWS EC2 instances) and installed the
> >stock httpd24 and dependencies via yum. I assume this is considered a
> >custom
> >build in so far that it doesn't match any of the existing rules that
> >Shibboleth uses to determine when is appropriate.
> It's not a supported platform, so by definition it's a custom build in all
> cases.
Amazon Linux is binary compatible with CentOS 5. I have successfully
deployed the RPM from
it worked great with with Apache 2.2 as installed from Amazon's own

However, I misunderstood what I was trying to accomplish. I no longer think
Apache 2.4 is the problem. I think is what I was
originally looking for, and I'm very fortunate I didn't run into any halt
and catch fire instructions within the CentOS 5 build.

The only maintainer of any RPMs is me (Debian is packaged by other
> volunteers), and the only platforms I support with RPMs are those
> supported by the OpenSUSE build service. It is beyond the capacity of the
> project to consider anything more.
And I very much appreciate the effort. I took it for granted how easy it
was to set up and configure Shibboleth Service Providers thanks to this
RPM. I initially installed Shibboleth (via yum) on an Amazon free tier
"micro" instance, realized that I couldn't update it via RPM, tried to
build from source and encountered a fatal error compiling OpenSAML due to
the lack of memory available on that instance. It's been one obstacle after
another but I will keep an eye on that JIRA ticket and keep trying in the

david at
-------------- next part --------------
An HTML attachment was scrubbed...

More information about the users mailing list