From: Kevin Coffman <kwc@citi.umich.edu>
To: Sam Hartman <hartmans@debian.org>,
Kevin Coffman <kwc@citi.umich.edu>,
Didier Raboud <odyx@debian.org>,
linux-nfs@vger.kernel.org, 629553@bugs.debian.org,
629692@bugs.debian.org
Subject: Re: libgssglue: incompatible with krb5 1.9
Date: Thu, 9 Jun 2011 01:18:43 -0400 [thread overview]
Message-ID: <BANLkTikKC5jdJG0KtrKxONmnSWSTm-9iyA@mail.gmail.com> (raw)
In-Reply-To: <20110609013756.GA5304@master.debian.org>
2011/6/8 Aníbal Monsalve Salazar <anibal@debian.org>:
> On Tue, Jun 07, 2011 at 12:55:02PM -0400, Sam Hartman wrote:
>>
>>package: libgssglue-dev
>>severity: serious
>>justification: package breaks nfs-utils build
>>version: 0.2-2
>>
>>Hi, Kevin and Debian maintainers:
>>
>>In an upcoming release, MIT has started adopting the new GSS-API type
>>names at the top of page 12 of RFC 5587.
>>
>>
>>For a variety of reasons, I pulled this change into Debian unstable.
>>Unfortunately, some applications such as nfs-utilsappear to pull in
>>gssapi.h from libgssglue, but pull in gssapi_ext.h from krb5.
>>
>>This does not work unless the gssapi.h from libgssglue includes the new
>>constant type names.
>>
>>--Sam
>
> Kevin,
>
> The original bug report #629553 is available at
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629553
>
> and bug report #629692 (which has build logs) is available at
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629692
>
> Sam,
>
> Could you please post the unified diff of gssapi.h from libgssglue that
> makes it work?
>
> Cheers,
>
> Aníbal
Sam's original message went to my spam folder. I will attempt to look
at this in the next couple of days, but I can't make any promises.
K.C.
next prev parent reply other threads:[~2011-06-09 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tsl1uz57fa1.fsf@mit.edu>
2011-06-09 1:37 ` libgssglue: incompatible with krb5 1.9 Aníbal Monsalve Salazar
2011-06-09 5:18 ` Kevin Coffman [this message]
2011-06-09 14:29 ` Sam Hartman
2011-06-13 15:45 ` Kevin Coffman
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=BANLkTikKC5jdJG0KtrKxONmnSWSTm-9iyA@mail.gmail.com \
--to=kwc@citi.umich.edu \
--cc=629553@bugs.debian.org \
--cc=629692@bugs.debian.org \
--cc=hartmans@debian.org \
--cc=linux-nfs@vger.kernel.org \
--cc=odyx@debian.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).