From: Peter Rosin <peda@lysator.liu.se>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/2] bump libtirpc to 1.0.1
Date: Fri, 06 Nov 2015 09:06:19 +0100 [thread overview]
Message-ID: <563C5F7B.9060104@lysator.liu.se> (raw)
In-Reply-To: <563B32F8.8050607@lysator.liu.se>
On 2015-11-05 11:44, Peter Rosin wrote:
> On 2015-11-05 10:05, Thomas Petazzoni wrote:
>> Dear Peter Rosin,
>>
>> On Thu, 5 Nov 2015 09:30:08 +0100, Peter Rosin wrote:
>>
>>> I'd like to bump libtirpc to 1.0.1. However there is an api incompatibility
>>> introduced in 0.3.2 which requires a patch to rpcbind, which I took from
> oops, introduced in -> introduced since
>>> upstream. The rpcbind patch make rpcbind work with either tirpc 0.3.2 or
>>> 1.0.1, so I added that patch first in the series even if it might seem
>>> backwards.
>> Thanks for those patches. Is rpcbind the only user of libtirpc that is
>> affected by the API change ?
>>
>> Thomas
> Good question...
So, I grepped for "xp_auth" in the sources of all other packages that sport a dependency on
libtirpc (argus, busybox, conntrack-tools, lmbench, ltp-testsuite, nfs-utils, quota and xinetd)
and came up empty.
Good enough?
Cheers,
Peter
prev parent reply other threads:[~2015-11-06 8:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 8:30 [Buildroot] [PATCH 0/2] bump libtirpc to 1.0.1 Peter Rosin
2015-11-05 8:30 ` [Buildroot] [PATCH 1/2] rpcbind: backport adjustment to changes in libtirpc 1.0.1 Peter Rosin
2015-11-06 8:27 ` Peter Rosin
2015-11-05 8:30 ` [Buildroot] [PATCH 2/2] libtirpc: bump to version 1.0.1 Peter Rosin
2015-11-08 13:30 ` Brendan Heading
2015-11-08 13:37 ` Thomas Petazzoni
2015-11-15 7:43 ` Peter Rosin
2015-11-16 22:08 ` Thomas Petazzoni
2015-11-24 18:43 ` Thomas Petazzoni
2015-11-24 21:52 ` Peter Rosin
2015-11-24 22:08 ` Thomas Petazzoni
2015-11-24 22:12 ` Peter Rosin
2015-11-25 8:05 ` Thomas Petazzoni
2015-11-05 9:05 ` [Buildroot] [PATCH 0/2] bump libtirpc to 1.0.1 Thomas Petazzoni
2015-11-05 10:44 ` Peter Rosin
2015-11-06 8:06 ` Peter Rosin [this message]
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=563C5F7B.9060104@lysator.liu.se \
--to=peda@lysator.liu.se \
--cc=buildroot@busybox.net \
/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.