LinuxQuestions.org - [SOLVED] virt-manager current problem

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - virt-manager current problem (https://www.linuxquestions.org/questions/slackware-14/virt-manager-current-problem-4175578145/)

virt-manager current problem

All dependencies are installed in the correct order.

I had to build

gstreamer1 and gst1-plugins with 14.1 slackbuilds but they complied OK they are not on current. Oh I think orc was also the same.

Anyway it worked better on my current test machine here is some strace that seemed relevant

Code:

access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)

open("/usr/lib64/locale/locale-archive", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

open("/usr/lib64/gconv/gconv-modules.cache", O_RDONLY) = -1 ENOENT (No such file or directory)

stat("/usr/bin/Modules/Setup", 0x7fffc6ac6590) = -1 ENOENT (No such file or directory)

stat("/usr/bin/lib64/python2.7/os.py", 0x7fffc6ac6590) = -1 ENOENT (No such file or directory)

stat("/usr/bin/lib64/python2.7/os.pyc", 0x7fffc6ac6590) = -1 ENOENT (No such file or directory)



write(2, "  File \"/usr/share/virt-manager/"..., 83) = 83

open("/usr/share/virt-manager/virtinst/distroinstaller.py", O_RDONLY) = 3

fstat(3, {st_mode=S_IFREG|0644, st_size=16397, ...}) = 0

read(3, "#\n# Copyright 2006-2009, 2013, 2"..., 4096) = 4096

write(2, "    ", 4)                    = 4

write(2, "from . import urlfetcher\n", 25) = 25

close(3)                                = 0

write(2, "  File \"/usr/share/virt-manager/"..., 78) = 78

open("/usr/share/virt-manager/virtinst/urlfetcher.py", O_RDONLY) = 3

fstat(3, {st_mode=S_IFREG|0644, st_size=40565, ...}) = 0

read(3, "#\n# Represents OS distribution s"..., 4096) = 4096

write(2, "    ", 4)                    = 4

write(2, "import requests\n", 16)      = 16

close(3)                                = 0

write(2, "ImportError", 11)            = 11

write(2, ": ", 2)                      = 2

write(2, "No module named requests", 24) = 24

write(2, "\n", 1)                      = 1

rt_sigaction(SIGINT, {SIG_DFL, [], SA_RESTORER, 0x7f4f7e5c73b0}, {0x7f4f7e920b10, [], SA_RESTORER, 0x7f4f7e5c73b0}, 8) = 0

close(6)                                = 0

exit_group(1)                          = ?

+++ exited with 1 +++

I realize that using the old stuff could be the problem if so my bad anyone get this to build on current ?

If so how did you do it ?

The stuff from python 2.7 where does it come from ? as that has me puzzled some of it seems pretty standard.

That was not the whole strace in case anyone actually thought it was.

Patiently wait for the release of Slackware 14.2 then the updates of the SlackBuilds @ slackbuilds.org for 14.2, then upgrade sbopkg, configure it, sync the repository, use sqg to write a queue file for virt-manager then use it to build and install virt-manager.

Until then and as far as I am in concern, you are on your own.

Quote:

gstreamer1 and gst1-plugins with 14.1 slackbuilds but they complied OK they are not on current. Oh I think orc was also the same

gstreamer1 (called now gstreamer), gst1-plugins-base (called now gst-plugins-base) and orc are already included in current

- use a SlackBuild repository dedicated to current;

- like Didier writes above build a queue with semiautomatic tools like sqg and then integrate it reading the README of every build script you run

Code:

vala

vte3

spice-protocol

six

pyparsing

celt051

spice

usbredir

spice-gtk

gtk-vnc

qemu

python-requests

python-urllib3

ipaddr-py

tunctl

gnome-python2-gconf

urlgrabber

yajl

libvirt

libvirt-python

libvirt-glib

libosinfo

virt-manager

- read carefully the error you got

Quote:

write(2, "ImportError", 11) = 11
write(2, ": ", 2) = 2
write(2, "No module named requests", 24) = 24

and you will see that you're missing (at least) python-requests.

Thanks Ponce I was missing python-requests as you observed. I was using the correct repository. For some reason the python-requests never showed up as a prereq for anything else. I usually work backwards from what I want to build on SlackBuilds but for some reason python-requests never was listed as a requirement (or I missed it). Should have checked my build list from before to see if it was there.

It's seems to work now.

I thought I was missing something, just not sure what.

It's part of the REQUIRES

Code:

REQUIRES="libosinfo libvirt-glib libvirt-python gnome-python2-gconf tunctl ipaddr-py python-urllib3 python-requests gtk-vnc spice-gtk vte3"

perhaps you are using the old queue file?
better to run sqg -a everytime there's a public update or changes are merged back to master

Thanks willysr I don't use sqg but I guess it's probably time to start. Must have missed python-requests. I will try to pay better attention in the future.

I had to go to

https://github.com/Ponce/slackbuilds...t-manager.info

to find that requires. It does not show up in the readme with sbopkg looks like it may be cutoff oh well I got worked out and learned several things thanks for the help.

if you haven't done it already you can download a local copy cloning the git repository (I linked above in my previous post another one where I explain how to do it) so it could be easier parsing it.

the *.info files show mandatory dependencies for the relative SlackBuild (the REQUIRES variable), while in the READMEs are listed the optional ones.

OK that sounds good. Just to make sure though this only involves the requirements and not necessarily the optional things that might be required for whatever it is you want to do.

I need OpenShot but that has lots of optional things that I want to use so in that case I need to do some manual builds to get what I want ?

Use sqg to generate the queue file for it and run sbopkg to install it using those queue

Maybe I am asking the wrong question.

If I put options in for a package in sbopkg will it grab the required packages and install them first ?

Sorry for the delay. But it really depends on how the package maintainer and the program itself are set up. Most ./configures will autodetect software, so if you have it installed, it will add support for it. Some, like ffmpeg, require you to manually enable options within the configure line.

If the program is set to autodetect optional dependencies, the package maintainer doesn't have to do much other than notify you what the optional dependencies are. You can then ensure they're installed before you install the main program and then all the support will be there. If it is something that requires you to manually specify the options, the package maintainers will usually put checks within the SlackBuild for a certain variable, so with ffmpeg, you could end up with a long line of variables like

Code:

X264=yes BLURAY=yes OPENCV=yes ./ffmpeg.SlackBuild

The latter setups are more difficult to use with tools like sbopkg, so, for me, I'll usually edit the SlackBuild and remove the if/then checks for the variables I desire. I suppose you could also add the variables at the top of the SlackBuild.

For the simpler autodetect configures, as long as you have the optional software installed beforehand, that's all you need to do. If I want to fully automate the building, I'll usually edit the requires line on the .info to change it to contain what I want built. A good example of this for me is kodi. It used to be that libmicrohttpd was an optional dependency. I wanted it to be built automatically with kodi. I also didn't want it to build jdk because 1. it wouldn't work unless I already downloaded the source, and 2. I used Eric's precompiled openjdk. So on the kodi.info REQUIRES line, I removed jdk and added libmicrohttpd and regenerated the queue file with sqg. Then I removed the if/then check in the SlackBuild to see if I specified that WEBSERVER=yes and had it set the needed variable to enable it during the compilation.

This is falls under a bit of the advanced usage of sbopkg. For others, it might be easier to just download those crazy builds manually and run them manually from the CLI.

I kind of figured that was going to be the case.