not included in shibboleth RPM

Cantor, Scott cantor.2 at
Tue May 6 14:53:48 EDT 2014

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
>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

> It instead tries to link against

Nothing links against that module, so I don't understand what that refers
to. If the appropriate flags are supplied to the rpmbuild command, then it
will build any modules you want it to, if the dependencies are in place.

>Is there a way that I can provide the "missing info" needed to the RPM
>maintainers short of building from source or via SRPM? And to whom? (A
>to the appropriate page on the Confluence Wiki is fine.)

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.

Building from SRPM is often easy and the flags required are documented,
but there are certainly cases where the dependency rules in the specfiles
just won't work for a totally unsupported OS. It's usually not too hard to
fix that, but it becomes not much better than just building from
source/scratch at that point. But I do accept patches to the specfiles
that correct issues with platforms I don't necessarily support.

>My yum is explicitly looking at the Shibboleth repo hosted by OpenSUSE. I
>have the feeling that if I were to complain to Amazon's package managers,
>they'd just redirect me back to this mailing list.

There is no repo for that OS, so you should not do that under any
circumstances. RPMs are NOT portable. The SRPMs are all identical across
repos, but yum doesn't have to be informed of where those come from, so
there is absolutely no reason you should be doing anything to yum here and
that will never work.

-- Scott

More information about the users mailing list