9:27 a.m.
libreoffice on F16 requires yajl 1.0, but virt-preview built libvirt
against yajl 2.0. This means that it is not possible to use
virt-preview on an F16 machine with libreoffice installed:
--> Finished Dependency Resolution
Error: Package: raptor2-2.0.4-2.fc16.x86_64 (@anaconda-0)
Requires: libyajl.so.1()(64bit)
Removing: yajl-1.0.12-1.fc16.x86_64 (@anaconda-0)
libyajl.so.1()(64bit)
Updated By: yajl-2.0.1-1.fc16.x86_64 (fedora-virt-preview)
Not found
It looks like we need to back out the yajl changes from virt-preview,
and rebuild libvirt to not require the newer yajl libraries.
--
Eric Blake eblake(a)redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
10:17 a.m.
On Mon, 2011-11-14 at 08:27 -0700, Eric Blake wrote:
libreoffice on F16 requires yajl 1.0, but virt-preview built libvirt
against yajl 2.0. This means that it is not possible to use
virt-preview on an F16 machine with libreoffice installed:
--> Finished Dependency Resolution
Error: Package: raptor2-2.0.4-2.fc16.x86_64 (@anaconda-0)
Requires: libyajl.so.1()(64bit)
Removing: yajl-1.0.12-1.fc16.x86_64 (@anaconda-0)
libyajl.so.1()(64bit)
Updated By: yajl-2.0.1-1.fc16.x86_64 (fedora-virt-preview)
Not found
It looks like we need to back out the yajl changes from virt-preview,
and rebuild libvirt to not require the newer yajl libraries.
Thanks, I did some checking to see if anything on my system required
yajl before I built it, but I don't have libre installed on that
machine. I am kind of questioning what to do here, if we revert the
yajl requirement in libvirt, what are we missing, it certainly isn't a
full virt-preview. On the other hand, if we tell people they can only
test on systems without Libre installed, we are going to have fewer
testers. I suppose the other option is to add libreoffice from F17 to
virt-preview (ouch). What do people think?
Justin
10:21 a.m.
On 11/14/2011 09:17 AM, Justin M. Forbes wrote:
On Mon, 2011-11-14 at 08:27 -0700, Eric Blake wrote:
> libreoffice on F16 requires yajl 1.0, but virt-preview built libvirt
> against yajl 2.0. This means that it is not possible to use
> virt-preview on an F16 machine with libreoffice installed:
>
> --> Finished Dependency Resolution
> Error: Package: raptor2-2.0.4-2.fc16.x86_64 (@anaconda-0)
> Requires: libyajl.so.1()(64bit)
> Removing: yajl-1.0.12-1.fc16.x86_64 (@anaconda-0)
> libyajl.so.1()(64bit)
> Updated By: yajl-2.0.1-1.fc16.x86_64 (fedora-virt-preview)
> Not found
>
> It looks like we need to back out the yajl changes from virt-preview,
> and rebuild libvirt to not require the newer yajl libraries.
Thanks, I did some checking to see if anything on my system required
yajl before I built it, but I don't have libre installed on that
machine. I am kind of questioning what to do here, if we revert the
yajl requirement in libvirt, what are we missing, it certainly isn't a
full virt-preview. On the other hand, if we tell people they can only
test on systems without Libre installed, we are going to have fewer
testers. I suppose the other option is to add libreoffice from F17 to
virt-preview (ouch). What do people think?
Libvirt should compile just fine with either yajl 1.0 or yajl 2.0 - that
is, libvirt does not rely on any new features added in yajl 2.0, and the
new yajl soname in rawhide is not a necessity for virt-preview (contrast
that to other packages, such as where using an older sanlock-devel is
problematic, and libvirt really does need sanlock-devel >= 1.8).
I think it's better to drop yajl from virt-preview, then rebuild libvirt
against the yajl 1.0 library already present in F16, than it is to
recompile libreoffice and anything else that is still stuck on the older
yajl soname in F16.
--
Eric Blake eblake(a)redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
11:06 a.m.
On Mon, 2011-11-14 at 09:21 -0700, Eric Blake wrote:
On 11/14/2011 09:17 AM, Justin M. Forbes wrote:
> On Mon, 2011-11-14 at 08:27 -0700, Eric Blake wrote:
>> libreoffice on F16 requires yajl 1.0, but virt-preview built libvirt
>> against yajl 2.0. This means that it is not possible to use
>> virt-preview on an F16 machine with libreoffice installed:
>>
>> --> Finished Dependency Resolution
>> Error: Package: raptor2-2.0.4-2.fc16.x86_64 (@anaconda-0)
>> Requires: libyajl.so.1()(64bit)
>> Removing: yajl-1.0.12-1.fc16.x86_64 (@anaconda-0)
>> libyajl.so.1()(64bit)
>> Updated By: yajl-2.0.1-1.fc16.x86_64 (fedora-virt-preview)
>> Not found
>>
>> It looks like we need to back out the yajl changes from virt-preview,
>> and rebuild libvirt to not require the newer yajl libraries.
>
> Thanks, I did some checking to see if anything on my system required
> yajl before I built it, but I don't have libre installed on that
> machine. I am kind of questioning what to do here, if we revert the
> yajl requirement in libvirt, what are we missing, it certainly isn't a
> full virt-preview. On the other hand, if we tell people they can only
> test on systems without Libre installed, we are going to have fewer
> testers. I suppose the other option is to add libreoffice from F17 to
> virt-preview (ouch). What do people think?
Libvirt should compile just fine with either yajl 1.0 or yajl 2.0 - that
is, libvirt does not rely on any new features added in yajl 2.0, and the
new yajl soname in rawhide is not a necessity for virt-preview (contrast
that to other packages, such as where using an older sanlock-devel is
problematic, and libvirt really does need sanlock-devel >= 1.8).
I think it's better to drop yajl from virt-preview, then rebuild libvirt
against the yajl 1.0 library already present in F16, than it is to
recompile libreoffice and anything else that is still stuck on the older
yajl soname in F16.
Probably a silly question, but if it does not require features from yajl
2.0, then why does the spec have:
BuildRequires: yajl-devel >= 2.0.1
Can we drop the versioning there if there is no real version
requirement?
Justin
11:10 a.m.
On 11/14/2011 10:06 AM, Justin M. Forbes wrote:
> I think it's better to drop yajl from virt-preview, then
rebuild libvirt
> against the yajl 1.0 library already present in F16, than it is to
> recompile libreoffice and anything else that is still stuck on the older
> yajl soname in F16.
>
Probably a silly question, but if it does not require features from yajl
2.0, then why does the spec have:
BuildRequires: yajl-devel >= 2.0.1
Hmm. Upstream libvirt does not have that, so it must be something added
locally in the Fedora build. Dan?
--
Eric Blake eblake(a)redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
11:17 a.m.
On Mon, Nov 14, 2011 at 10:10:33AM -0700, Eric Blake wrote:
On 11/14/2011 10:06 AM, Justin M. Forbes wrote:
>> I think it's better to drop yajl from virt-preview, then rebuild libvirt
>> against the yajl 1.0 library already present in F16, than it is to
>> recompile libreoffice and anything else that is still stuck on the older
>> yajl soname in F16.
>>
> Probably a silly question, but if it does not require features from yajl
> 2.0, then why does the spec have:
>
> BuildRequires: yajl-devel >= 2.0.1
Hmm. Upstream libvirt does not have that, so it must be something added
locally in the Fedora build. Dan?
It can be reverted - I just did that in rawhide to ensure we were
building against the newer yajl
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
8:14 a.m.
On Mon, 2011-11-14 at 17:17 +0000, Daniel P. Berrange wrote:
On Mon, Nov 14, 2011 at 10:10:33AM -0700, Eric Blake wrote:
> On 11/14/2011 10:06 AM, Justin M. Forbes wrote:
> >> I think it's better to drop yajl from virt-preview, then rebuild
libvirt
> >> against the yajl 1.0 library already present in F16, than it is to
> >> recompile libreoffice and anything else that is still stuck on the older
> >> yajl soname in F16.
> >>
> > Probably a silly question, but if it does not require features from yajl
> > 2.0, then why does the spec have:
> >
> > BuildRequires: yajl-devel >= 2.0.1
>
> Hmm. Upstream libvirt does not have that, so it must be something added
> locally in the Fedora build. Dan?
It can be reverted - I just did that in rawhide to ensure we were
building against the newer yajl
This has been reverted and fixed in virt-preview as well now.
Justin
4543
days inactive
4546
days old
6 comments
3 participants
participants (3)
-
Daniel P. Berrange -
Eric Blake -
Justin Forbes