difference in sbopkg queue file and slackbuilds dependencies

the_zone · 04-09-2014, 03:08 PM

I have tried to install virt-manager via slackbuilds.
Downloading/installing every dependency and recursive dependencies.
I failed horribly.
virt-manager came up however I got some errors.
Installing avahi (complaint from virt-manager) was the death of normal vnc behaviour.

I did a fresh install of slackware (14.1 btw).
Now I took a different approach, being sbopkg.

However I see a difference in the dependencies of both methods.

Any one any idea why ?

grtz

Simon

brianL · 04-09-2014, 03:29 PM

Could be dependencies of dependencies listed in the queuefile, but not on the virt-manager page at SlackBuilds. Only guessing.

Didier Spaier · 04-09-2014, 04:25 PM

You could use sqg to rebuild the queue file.

moisespedro · 04-09-2014, 04:32 PM

imo the best way to deal with sbo dependencies is this one
http://slackblogs.blogspot.com.br/20...es-easily.html

mostlyharmless · 04-09-2014, 05:49 PM

Hmm, I have virt-manager working on 14.1, I used the Slackbuilds site and manually ran the builds in order. Can you list the packages and versions you built in order?

the_zone · 04-10-2014, 01:11 AM

Thanks for the replies.
This is my package list and they are ordered bottom up.

vte-0.35.2
libvirt-1.2.2
libvirt-python-1.2.2
vala-0.20.1
libvirt-glib-0.1.8
gtk-vnc-0.5.3
pyparsing-2.0.1
spice-protocol-0.12.6
celt-0.5.1.3
spice-0.12.4
libcacard-0.1.2
spice-gtk-0.23
pygobject-3.8.3
ipaddr-2.1.10
urlgrabber-3.10
tunctl-1.5
gnome-python-2.28.1
virt-manager-1.0.0

The end result op both install methods is the same.
See this post

To complete the system information, I using slackware64_14.1 on a HP Proliant ML350 (Xeon E5410 and 4GB of Memory) with the standard huge kernel.
No KDE, just XFCE.

Didier Spaier · 04-10-2014, 06:14 AM

This is the queue generated by sqg on a clean Slackware64-14.1 system, with command "sqg -p virt-manager":

vte3
vala
spice-protocol
pyparsing
celt051
spice
libcacard
spice-gtk
gtk-vnc
pygobject3
urlgrabber
ipaddr-py
tunctl
gnome-python2-gconf
yajl
libvirt
libvirt-python
libvirt-glib
virt-manager

Also, bear in mind that all SlackBuilds hosted @ http://slackbuilds.org assume that you have a full Slackware installation, in other words do not state dependencies already included in a full Slackware installation. So, if you don't have a full installation, you're on your own.

Oh and the build order should be the same for 32 and 64 bit, I think.

mostlyharmless · 04-12-2014, 09:52 AM

@the_zone The only difference I see in my setup (and Didier's output) vs those posted by you are (minor) version numbers. I originally built the 14.0 versions (the 14.1s weren't out) I built the following from SlackBuilds:

Code:

vde
qemu
urlgrabber
yajl
libvirt
ORBit2
vala
gtk-vnc
rarian
tunctl
pyorbit
gnome-mime-data
virtinst

but got stuck on libbonobo

Of course, the dependencies changed for 14.1, so when the new packages came out I built the 14.1 versions and updated as needed.

My build order was

Code:

/tmp/gnome-python2-gconf-2.28.1-x86_64-1_SBo.tgz
  /tmp/vte3-0.34.9-x86_64-1_SBo.tgz
  /tmp/tunctl-1.5-x86_64-2_SBo.tgz
  /tmp/urlgrabber-3.10-x86_64-1_SBo.tgz
  /tmp/ipaddr-py-2.1.10-x86_64-1_SBo.tgz
  /tmp/pygobject3-3.8.3-x86_64-1_SBo.tgz
  upgraded /tmp/vala-0.20.1-x86_64-1_SBo.tgz
  gtk-vnc, yajl unchanged
  upgraded /tmp/libvirt-1.2.0-x86_64-1_SBo.tgz
  /tmp/libvirt-glib-0.1.7-x86_64-1_SBo.tgz
  /tmp/libcacard-0.1.2-x86_64-1_SBo.tgz
  /tmp/celt051-0.5.1.3-x86_64-1_SBo.tgz
  /tmp/spice-protocol-0.12.6-noarch-1_SBo.tgz
  /tmp/pyparsing-2.0.1-x86_64-1_SBo.tgz
  /tmp/spice-0.12.4-x86_64-1_SBo.tgz
  /tmp/spice-gtk-0.21-x86_64-1_SBo.tgz
  /tmp/libvirt-python-1.2.0-x86_64-1_SBo.tgz
  /tmp/virt-manager-0.10.0-x86_64-1_SBo.tgz

I've subsequently upgraded libvirt, libvirt-glib, libvirt-python, usbredir, virt-manager to their current versions at SlackBuilds.org. Hope that helps.

the_zone · 04-14-2014, 03:26 PM

Thanks for the answers.
I did not have any time this weekend to look into it further.

grtz

Simon

XGizzmo · 04-14-2014, 07:13 PM

Quote:

However I see a difference in the dependencies of both methods.

Any one any idea why ?

The Slackbuild *.info file only list the dependencies REQUIRED to make
the package build/work. A queue file may contain optional dependencies
as well as the required ones.

the_zone · 04-22-2014, 03:28 PM

I made a slackware64 14.1 guest on slackware64 14.1 host

So i could try before, as happened numerous times already, my system would die on me.

I installed the packages in order and version number as described by mostlyharmless.
virt-manager now complains about the usb redirection which is not supported by the current version of QEMU.
Has this anything todo with the usbredir package which is available on slackbuilds ?

grtz

Simon

willysr · 04-22-2014, 04:03 PM

Have you update to the latest update for your SBo repository?
Please run sbopkg -r

mostlyharmless · 04-22-2014, 07:20 PM

Quote:

virt-manager now complains about the usb redirection which is not supported by the current version of QEMU.
Has this anything todo with the usbredir package which is available on slackbuilds ?

I run a qemu version from git that I massaged the SlackBuild to build for me; it is sort of 1.7.50... so I don't know whether whatever ships with 14.1 has a problem, sorry.

I vaguely remember some problem with usb redirection; but I don't think usbredir (a) has anything to do with it (b) helped when I did install it. Currently I passthrough one of my USB hubs instead.

the_zone · 04-23-2014, 05:51 AM

@mostlyharmless

This is a bit of topic.
I read your LQ blog on QEMU and slackware 14.1.
Since I started this thread because I need a windows7 machine on my server, I hope you are willing to share some experiences on how you set up a guest.

1. do you use qcow2 or raw images ?
2. have you installed a windows machine as guest ?
3. what are the qemu options you used an why ?

On topic again.

I'll try installing usbredir and see whether the issue remains.
Next is the qemu update then.

best regards

Simon

the_zone · 04-23-2014, 05:54 AM

Quote:

Originally Posted by willysr

Have you update to the latest update for your SBo repository?
Please run sbopkg -r

I'll try that too.

best regards

Simon