Russ == Russ Allbery r...@debian.org writes:
Russ This is what I did for now. I created a libshibsp-plugins
Russ package and a shibboleth-sp2-utils package and made the
Russ dependencies from libapache2-mod-shib2 and from -utils to
Russ -plugins strict (to require exactly the
Sam Hartman hartm...@debian.org writes:
Russ == Russ Allbery r...@debian.org writes:
Russ This is what I did for now. I created a libshibsp-plugins
Russ package and a shibboleth-sp2-utils package and made the
Russ dependencies from libapache2-mod-shib2 and from -utils to
Makes sense to me.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Cantor, Scott canto...@osu.edu writes:
Yeah, I get it, and yes, they are linked directly to specific ABIs. If
the ABI changes, that's when the SONAME changes on libshibsp or the
others.
The intent is that they're part of Shibboleth proper, rather than part
of the library package, in the
Cantor, Scott canto...@osu.edu writes:
On 3/3/14, 4:56 PM, Russ Allbery r...@debian.org wrote:
I am a little worried about downgrading the shibd dependency in
libapache2-mod-shib2 to recommends; maybe it should stay as depends for
now even though it's possible to run shibd on a different
Russ Allbery r...@debian.org writes:
shibboleth-sp2-common (new package)
/etc/shibboleth
Oh, and also, I could move the contents of shibboleth-sp2-schemas into
this package as well, but it would require a transitional package to
handle the upgrades. I'm not sure it's worth it, but if the
On 3/16/14, 5:48 PM, Russ Allbery r...@debian.org wrote:
libshibsp6 would depend on shibboleth-sp2-common. libapache2-mod-shib2
would depend on shibboleth-sp2-utils. Every other package would retain
its current contents and dependency structure. (I know the authorizer and
responder need to be
On 3/16/14, 6:01 PM, Russ Allbery r...@debian.org wrote:
Russ Allbery r...@debian.org writes:
shibboleth-sp2-common (new package)
/etc/shibboleth
Oh, and also, I could move the contents of shibboleth-sp2-schemas into
this package as well, but it would require a transitional package to
Cantor, Scott canto...@osu.edu writes:
On 3/16/14, 5:48 PM, Russ Allbery r...@debian.org wrote:
libshibsp6 would depend on shibboleth-sp2-common. libapache2-mod-shib2
would depend on shibboleth-sp2-utils. Every other package would retain
its current contents and dependency structure. (I
On 3/16/14, 10:31 PM, Russ Allbery r...@debian.org wrote:
Hm, okay, in that case I'm inclined to change the -common package to
-runtime (which is a more typical convention for arch-dependent supporting
files for libraries), put both the configuration and the plugins in that,
and have the library
Cantor, Scott canto...@osu.edu writes:
On 3/16/14, 10:31 PM, Russ Allbery r...@debian.org wrote:
Hm, okay, in that case I'm inclined to change the -common package to
-runtime (which is a more typical convention for arch-dependent
supporting files for libraries), put both the configuration and
Cantor, Scott canto...@osu.edu writes:
They're not linked to, they're plugin extension libraries that are
specific to the ABI of the surrounding libraries they're built against.
Oh, wait, I missed a subtlety in this, and then failed to make clear what
I had meant by a comment I made earlier.
On 3/16/14, 11:03 PM, Russ Allbery r...@debian.org wrote:
Oh, are they linked to the libraries? Oh, sure enough. Okay, those have
to go into a separate package then. Are they needed by shibd? I know
they're needed by the Apache module, so it should depend on the plugin
package.
None of them
On 3/16/14, 11:50 PM, Russ Allbery r...@debian.org wrote:
If the plugins that come with Shibboleth 2.4 (libshibsp5, IIRC) are not
guaranteed to work with Shibboleth 2.5 (libshibsp6), then the way they're
packaged right now only works because they're with the only client that
can currently use
Package: libapache2-mod-shib2
Version: 2.4.3+dfsg-5+b1
The libapache2-mod-shib2 package contains the files for /etc/shibboleth. When
you do not use libapache2-mod-shib (as we do in the Moonshot project), the
contents for that directory does not get installed. The file listing for the
package
Russ,
I'm happy to implement whatever solution is decided for this.
However it would be good to get discussion on how to approach separating
the aspects from /etc/shibboleth that are apache-specific from those
that are not.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
On 3/3/14, 10:01 AM, Sam Hartman hartm...@debian.org wrote:
Russ,
I'm happy to implement whatever solution is decided for this.
However it would be good to get discussion on how to approach separating
the aspects from /etc/shibboleth that are apache-specific from those
that are not.
None of it
stefan.pae...@diamond.ac.uk writes:
The libapache2-mod-shib2 package contains the files for
/etc/shibboleth. When you do not use libapache2-mod-shib (as we do in
the Moonshot project), the contents for that directory does not get
installed. The file listing for the package confirms this:
On 3/3/14, 4:27 PM, Russ Allbery r...@debian.org wrote:
Could you explain a bit more about what the use case is? I think I
understand, but I'm not sure. You're using libshibsp5, and you want the
standard configuration files, but you aren't using Apache so you don't
want libapache2-mod-shib2?
Cantor, Scott canto...@osu.edu writes:
On 3/3/14, 4:27 PM, Russ Allbery r...@debian.org wrote:
Could you explain a bit more about what the use case is? I think I
understand, but I'm not sure. You're using libshibsp5, and you want
the standard configuration files, but you aren't using Apache
On 3/3/14, 4:56 PM, Russ Allbery r...@debian.org wrote:
Am I correct in my understanding of the original bug report that the
shibsp library actually requires /etc/shibboleth to work? In other words,
from a package perspective, should libshibsp depend on the configuration
files (however
21 matches
Mail list logo
