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.
I know that Eric does not like using spaces in file names and directory's so I was surprised to see a space in the directory in ~/Calibre Library when I installed it. I have set it up with as ~/Calibre_Library since I hate spaces as well.
Is there is specific reason why there is a space or is it an oversight?
Distribution: Slackware 15 64bit on Desktop Slackwarearm on Raspberry PI v1b
Posts: 381
Rep:
I upgraded my system to 14.0 and am trying to build calibre I get the following error
Code:
Traceback (most recent call last):
File "setup.py", line 99, in <module>
sys.exit(main())
File "setup.py", line 85, in main
command.run_all(opts)
File "/tmp/build/tmp-calibre/calibre/setup/__init__.py", line 163, in run_all
self.run_cmd(self, opts)
File "/tmp/build/tmp-calibre/calibre/setup/__init__.py", line 156, in run_cmd
self.run_cmd(scmd, opts)
File "/tmp/build/tmp-calibre/calibre/setup/__init__.py", line 159, in run_cmd
cmd.run(opts)
File "/tmp/build/tmp-calibre/calibre/setup/gui.py", line 37, in run
self.build_forms()
File "/tmp/build/tmp-calibre/calibre/setup/gui.py", line 60, in build_forms
from calibre.gui2 import build_forms
File "/tmp/build/tmp-calibre/calibre/src/calibre/gui2/__init__.py", line 21, in <module>
from calibre.utils.date import UNDEFINED_DATE
File "/tmp/build/tmp-calibre/calibre/src/calibre/utils/date.py", line 13, in <module>
from dateutil.tz import tzlocal, tzutc
ImportError: No module named dateutil.tz
mv: cannot stat '/tmp/build/package-calibre/usr/etc': No such file or directory
I know I'm missing something but can't figure what it is.
Distribution: Slackware 15 64bit on Desktop Slackwarearm on Raspberry PI v1b
Posts: 381
Rep:
I found the date utils on Eric's site, now I get this
Code:
Setting up completion failed with error:
__________________________________________________
Traceback (most recent call last):
File "/tmp/build/tmp-calibre/calibre/src/calibre/linux.py", line 221, in setup_completion
from calibre.ebooks.metadata.cli import option_parser as metaop, filetypes as meta_filetypes
File "/tmp/build/tmp-calibre/calibre/src/calibre/ebooks/metadata/cli.py", line 13, in <module>
from calibre.ebooks.metadata.meta import get_metadata, set_metadata
File "/tmp/build/tmp-calibre/calibre/src/calibre/ebooks/metadata/meta.py", line 9, in <module>
from calibre.ebooks.metadata.opf2 import OPF
File "/tmp/build/tmp-calibre/calibre/src/calibre/ebooks/metadata/opf2.py", line 14, in <module>
from lxml import etree
ImportError: No module named lxml
Setting up desktop integration...
Installing calibre environment module: /tmp/build/package-calibre/usr/lib64/python2.7/site-packages/init_calibre.py
calibre successfully installed. You can start it by running the command calibre
There were 1 warning(s):
* Setting up completion failed with error:
mv: cannot stat '/tmp/build/package-calibre/usr/etc': No such file or directory
I found the date utils on Eric's site, now I get this
Code:
Setting up completion failed with error:
__________________________________________________
Traceback (most recent call last):
File "/tmp/build/tmp-calibre/calibre/src/calibre/linux.py", line 221, in setup_completion
from calibre.ebooks.metadata.cli import option_parser as metaop, filetypes as meta_filetypes
File "/tmp/build/tmp-calibre/calibre/src/calibre/ebooks/metadata/cli.py", line 13, in <module>
from calibre.ebooks.metadata.meta import get_metadata, set_metadata
File "/tmp/build/tmp-calibre/calibre/src/calibre/ebooks/metadata/meta.py", line 9, in <module>
from calibre.ebooks.metadata.opf2 import OPF
File "/tmp/build/tmp-calibre/calibre/src/calibre/ebooks/metadata/opf2.py", line 14, in <module>
from lxml import etree
ImportError: No module named lxml
Code:
I think it is better if you install all dependencies first unless you want to post 8 more of these failures.
Quote:
Setting up desktop integration...
Installing calibre environment module: /tmp/build/package-calibre/usr/lib64/python2.7/site-packages/init_calibre.py
calibre successfully installed. You can start it by running the command calibre
There were 1 warning(s):
* Setting up completion failed with error:
mv: cannot stat '/tmp/build/package-calibre/usr/etc': No such file or directory
This is a circumstantial error which is going to be automatically fixed once you install all dependencies first.
Distribution: Slackware 15 64bit on Desktop Slackwarearm on Raspberry PI v1b
Posts: 381
Rep:
Ok. I thought your build script did that. I followed the instructions from here: http://www.linuxquestions.org/questi...8-18-a-902468/. I guess I need to find out which order to do this in step-by-step simplicity.
I had this working under 13.1 but forgot how I did it.
Distribution: Slackware 15 64bit on Desktop Slackwarearm on Raspberry PI v1b
Posts: 381
Rep:
Ok, I followed this:
Code:
Download all the files in ( http://taper.alienbase.nl/mirrors/pe...calibre/build/ ) , except calibre_pythondeps-13.37.0-i486.tar.bz2 AND calibre_pythondeps-13.37.0-i486.tar.bz2
Put then all into the same folder, enter a terminal, navigate to the folder, become root
Execute the script "./calibre.Slackbuild"
If any error happens and the build dont finish plx try to get some of the build log and copy in here
If everything turns to be good, as i think it will, use "upgradepkg /tmp/calibre*.txz" or "upgradepkg calibre*.txz"
The BUILD folder in alien repositorie is the formula that he uses to build the package he launchs every week. Its avaliable so everybody can see and learn how to build it thenselfs. If everything went fine and u did build the 0.8.18 version for your slackware-13.1_64bits, you can keep doing it by saving the folder you downloaded all the files from that BUILD and downloading and replacing just the calibre source code in it. Today ( its 2 AM of Friday here in Brazil ) the next version should be avaliable, the 0.9.19.
I will download and install each of the dependencies and try again.
Distribution: Slackware 15 64bit on Desktop Slackwarearm on Raspberry PI v1b
Posts: 381
Rep:
I downloaded and installed all the dependencies separately the downloaded the calbre package and installed it. Everything seems to be working now. Thanks for all the help. I guess in future I'll just use all of Eric's pre-built packages instead of trying the build scripts.
People, if you are desperate to use my SlackBuild scripts in order to rebuild the packages which I already supply for you, I expect that you also read the scripts. You would see that calibre for Slackware 14 is different from the version built for Slackware 13.37. In Slackware 14, python was upgraded to 2.7.x which matches the version that calibre requires. Therefore, my package for Slackware 14 does not have to build an internal python 2.7 interpreter plus several python modules anymore (which probably was what interndan was referring to when he said "Ok. I thought your build script did that").
Also, you should not be looking at my slack-required file in the build directory... because if you would have read the SlackBuild you'd have noticed that I edit that file before adding it to the package.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.