All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Trond Myklebust <trondmy@gmail.com>,
	Christoph Hellwig <hch@infradead.org>
Cc: Lever Charles Edward <chuck.lever@oracle.com>,
	Jim Rees <rees@umich.edu>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	An?bal Monsalve Salazar <anibal@debian.org>,
	"Steinar H. Gunderson" <sesse@debian.org>
Subject: Re: librpcsecgss: FTBFS on GNU/kFreeBSD
Date: Thu, 05 Dec 2013 11:37:46 -0500	[thread overview]
Message-ID: <52A0ABDA.8090903@RedHat.com> (raw)
In-Reply-To: <7AB02817-E6DE-486A-A4CB-8A67AF44972A@gmail.com>



On 05/12/13 08:45, Trond Myklebust wrote:
> 
> On Dec 5, 2013, at 8:43, Christoph Hellwig <hch@infradead.org> wrote:
> 
>> On Thu, Dec 05, 2013 at 08:41:27AM -0500, Trond Myklebust wrote:
>>>> libgssapi-krb5-2 seems to have dropped the libgssglue dependency in
>>>> unstable, but the others still seem to be be around.
>>>
>>> I thought that Debian installs the Heimdal kerberos libraries by default. Does it have the gssapi hooks?
>>
>> libgssapi-krb5-2 is described as "MIT Kerberos runtime libraries - krb5
>> GSS-API Mechanism" and depends on libkrb5-3 which is "MIT Kerberos
>> runtime libraries".  Nothing Heimdal related in this dependency chain.
> 
> Then it should be able to drop the CITI librpcsecgss and libgssglue.
I would think so.... 

librpcsecgss has already been remove from Fedora and I'll do the
same for libgssglue once f18 is no longer supported...

steved.

> 
> Cheers
>   Trond--
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2013-12-05 16:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090703133142.14887.33854.reportbug@localhost.localdomain>
2013-11-24  5:19 ` librpcsecgss: FTBFS on GNU/kFreeBSD Aníbal Monsalve Salazar
2013-11-24  9:09   ` Christoph Hellwig
2013-11-24 13:07     ` Jim Rees
2013-11-24 13:29       ` Christoph Hellwig
2013-12-04 13:13       ` Christoph Hellwig
2013-12-04 17:14         ` Chuck Lever
2013-12-04 17:53           ` Trond Myklebust
2013-12-04 18:14             ` Chuck Lever
2013-12-05 13:23               ` Christoph Hellwig
2013-12-05 13:41                 ` Trond Myklebust
2013-12-05 13:43                   ` Christoph Hellwig
2013-12-05 13:45                     ` Trond Myklebust
2013-12-05 16:37                       ` Steve Dickson [this message]
2013-12-10  6:27                   ` NeilBrown
2013-12-05 16:15                 ` Jim Rees
2013-12-04 18:24         ` J. Bruce Fields
2013-12-04 18:27           ` Chuck Lever

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52A0ABDA.8090903@RedHat.com \
    --to=steved@redhat.com \
    --cc=anibal@debian.org \
    --cc=chuck.lever@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rees@umich.edu \
    --cc=sesse@debian.org \
    --cc=trondmy@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.