SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm trying to modify the slackbuild script from sbo to use the latest version of calibre. I get the following errors:
patching file src/calibre/linux.py
Hunk #1 FAILED at 288.
Hunk #2 FAILED at 304.
2 out of 2 hunks FAILED -- saving rejects to file src/calibre/linux.py.rej
patching file src/calibre/utils/help2man.py
Hunk #1 FAILED at 4.
Hunk #2 FAILED at 58.
2 out of 2 hunks FAILED -- saving rejects to file src/calibre/utils/help2man.py.rej
any ideas how to fix this?
Click here to see the post LQ members have rated as the most helpful post in this thread.
It sounds like the patch file you're using wasn't created using the file which you're trying to patch - it can't find the bits of code it needs to change. Where did you get the source and the patch from?
The SlackBuild script at SBo is useless for any recent version of Calibre. Slackware ships python 2.6 and Calibre requires python 2.7.
My own SlackBuild script adds an internal python 2.7 compiler plus several python modules to circumvent this problem. That is why the package is so big.
Well, I tried your package and it doesn't run. Something else must have changed on my system. Perhaps when I installed LXDE. I also tried recompiling the version I was running, and it also fails. I've got to search through the dependencies list and see what else has changed.
I apologize for the delay (my granddaughter's softball games interfered with computer work). I installed the other two packages, and calibre still does not run. This is the error when trying to start from terminal:
Traceback (most recent call last):
File "/usr/bin/calibre", line 18, in <module>
from calibre.gui2.main import main
File "/usr/lib64/calibre/calibre/gui2/__init__.py", line 7, in <module>
from PyQt4.Qt import (QVariant, QFileInfo, QObject, SIGNAL, QBuffer, Qt,
ImportError: cannot import name QVariant
What release of Slacwkare are you running? I can see that it is a 64bit version.
The error is related to the PyQt package, a full installation of Slackware 13.37 should fullfill all requirements.
You are not installing my Slackware 13.37 calibre package on an older Slackware release are you?
I did the same that Dan tried some months ago, work around the slackbuilds script trying to make a package for the new Calibre, and because of the python requirement it obviously didnt work. Im just curious, Bob, why ICU4C and PODOFO werent build inside ur package, as all the others requirements like Beautifulsoup, lxml, setuptools and those others i cant really remenber?
I was studying how to build packages and those things, and since Slackware dont check for dependencies, i was wondering how can i decide if i include dependencies compiled inside the package. Im not talking just about the size of the package , im thinking about stability and how, for example, Calibre, in this example, behaves if Beautifulsoup was in the system when i installed it(calibre) and remove it(beautifulsoup) later from the system. I never had this kinda of problem in Slackware, that i know of.
Funny that while i was thinking about another example i realized its exactly the thing KDE-Developers did with 4.7. They splited the packages in more packages.
I dont want to drag this post too much, but im building Gnome 2.32.1, Enlightement , PCSX2-devel, PCSX2-release, and others, all to slackware, and was havind these toughts about package building. I will create another topic about these builds.
Dan, there is a package in the build folder (calibre_pythondeps-13.1.0-x86_64.tar.bz2) that should handle everything if u try to build the Calibre 0.8.18 yourself, but u shouldnt upgrade ur 64b with a 32b.
If that was not the question , and u just asking if u can run the newest Calibre in Slackware-13.1, after another Calibre-0.8 worked, im pretty sure u can.