From: "Richard W.M. Jones" <rjones@redhat.com>
To: Development discussions related to Fedora
<devel@lists.fedoraproject.org>
Cc: test@lists.fedoraproject.org, linux-btrfs@vger.kernel.org
Subject: Re: rawhide report: 20130505 changes
Date: Sun, 5 May 2013 20:41:51 +0100 [thread overview]
Message-ID: <20130505194151.GD25815@redhat.com> (raw)
In-Reply-To: <20130505112617.GA16141@releng03.phx2.fedoraproject.org>
On Sun, May 05, 2013 at 11:26:17AM +0000, Fedora Rawhide Report wrote:
> [libguestfs]
> 1:libguestfs-1.21.36-1.fc20.i686 requires libbtrfs.so.0
> 1:libguestfs-1.21.36-1.fc20.x86_64 requires libbtrfs.so.0()(64bit)
I've started a rebuild of libguestfs which should fix this.
Is there any significance to the soname change? Is libbtrfs.so an
internal implementation detail or a public API? (I don't have this
library on Fedora 18). And if it's a public API will any software
need source-level changes to accomodate this bump?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
parent reply other threads:[~2013-05-05 19:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20130505112617.GA16141@releng03.phx2.fedoraproject.org>]
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=20130505194151.GD25815@redhat.com \
--to=rjones@redhat.com \
--cc=devel@lists.fedoraproject.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=test@lists.fedoraproject.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