SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi folks, this problem has been nagging me for a while and I have been searching over the last week to find a solution with no luck. I'm hoping some of the great minds on the forum might be able to teach me what is wrong and how I might be able to figure out similar problems in the future on my own.
I recently attempted to install devedeng as well as virt-manager from slackbuilds.org and both are giving me problems. I have virtualbox installed so I'm really just focused on devedeng for now, but the problem seems to be related to python in both cases.
I am running Slackware 14.1 multilib fully updated as of this posting and all my packages from slackbuilds.org are also updated other than devedeng. Building py3cairo (dependency of devedeng) fails with this "error message" using sbopkg (doesn't really say much):
pycairo-1.10.0/wscript
patching file waf
Hunk #1 succeeded at 153 with fuzz 2.
/tmp/SBo/pycairo-1.10.0/.waf3-1.6.4-e3c1e08604b18a10567cfcd2d02eb6e6 /tmp/SBo/pycairo-1.10.0
patching file waflib/Tools/python.py
Reversed (or previously applied) patch detected! Assume -R? [n]
Apply anyway? [n]
Skipping patch.
1 out of 1 hunk ignored -- saving rejects to file waflib/Tools/python.py.rej
However when I build the package manually it compiles and I can install it. Even if I do that and then skip building the package with sbopkg I get this error when trying to launch devedeng:
Version: 4.2
Traceback (most recent call last):
File "/usr/bin/devede_ng.py", line 47, in <module>
mwindow = devedeng.project.devede_project()
File "/usr/lib64/python3.4/site-packages/devedeng/project.py", line 57, in __init__
builder.add_from_file(os.path.join(self.config.glade,"wmain.ui"))
gi._glib.GError: /usr/share/devede_ng/wmain.ui: required gtk+ version 3.10, current version is 3.8
Sorry, this is my fault. I failed test if devedeng ran in 14.1, only that it built fine since it was a chroot I was testing in. Seems 14.1 has an version of gtk+3 that is too old for devedeng... You could build a newer gtk+3 yourself with the current slackbuild/source, but that's not really a solution... I suggested that the old version of devede slackbuild remain on SBo since its a bit different with dependencies, but it was removed anyways. I did save the slackbuild though, maybe it will work better for you.
According to your error message devedeng seems to need at least gtk+3.10, 14.1 has gtk+3.8 and current has gtk+3.16 where it does work. Assuming you don't want to run current you could build a newer gtk+3 using Pat's current slackbuild (I'm not sure if that would mean if you need to rebuild anything else or not too?) or you could run the older version of devede which probably still works, but is no longer maintained since the developer jumped to python3.
"gi._glib.GError: /usr/share/devede_ng/wmain.ui: required gtk+ version 3.10, current version is 3.8"
Right, so I guess my real question is would you compile or try to compile gtk 3.10 from source and install say with src2pkg alongside or on top of the current version on my system? Or would that break things and me sad
Then I would make the make gtk+3.SlackBuild executable, run it just as any SBo slackbuild and install it with upgradepkg so it would replace your current gtk+3. Some packages may link against your old gtk+3 and break, but that can be fixed by just recompiling them just like you did with gtk+3. If that is the case you will have to find that out yourself and if you are not comfortable maintaining your own system I would not recommend it even if its not really all that difficult.
I did what you said and now the build fails with the same error and all text in xfce4 and in terminator are rectangular blocks.
Don't know what to do now.
Logged into another account that uses Enlightenment. No problems here.
This is too much for me I'm in over my head. Reverted back all the old packages with slackpkg upgrade-all. I didn't actually even need devedeng anymore I was just trying to get it to work for bragging rights I guess no luck maybe I'll wait for Slackware 14.2
Either way Slackware is still the best hands down most stable! I know I would have run into major problems trying this on any other distribution. Thank you to all the maintainers and developers for all your hard work as always and thanks to orbea for your quick explanation. I guess I'd better hit the books if I want to take it to the next level.
Any suggestions on how I could learn more about the building process? Maybe I should give LFS a try if I really want to learn any more, been contemplating it for some time now. Anyways marking as solved.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.