LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Eric's latest Calibre for 14.0 (http://www.linuxquestions.org/questions/slackware-14/erics-latest-calibre-for-14-0-a-4175423666/)

SqdnGuns 08-23-2012 02:21 PM

Eric's latest Calibre for 14.0
 
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?

Thanks

Alien Bob 08-23-2012 02:45 PM

I do not write Calibre, I just package it. I have nothing to do with how the software is behaving.
You can rightfully complain to the developer.

Eric

SqdnGuns 08-23-2012 02:50 PM

Quote:

Originally Posted by Alien Bob (Post 4762443)
I do not write Calibre, I just package it. I have nothing to do with how the software is behaving.
You can rightfully complain to the developer.

Eric

Thanks Eric, was just curious as to why.

interndan 11-02-2012 11:56 AM

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.

Dan

Stephen Morgan 11-02-2012 01:19 PM

pydateutils, I think.

interndan 11-02-2012 01:36 PM

Where do I find them? I don't see them on SBO.

interndan 11-02-2012 02:04 PM

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


Alien Bob 11-02-2012 02:04 PM

Quote:

Originally Posted by interndan (Post 4820891)
Where do I find them? I don't see them on SBO.

Same place as where you find my calibre package... of course.

Eric

Alien Bob 11-02-2012 02:09 PM

Quote:

Originally Posted by interndan (Post 4820908)
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.

Eric

interndan 11-02-2012 02:50 PM

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.

wildwizard 11-02-2012 02:59 PM

Looking quickly over that thread the standout for me is this post by Eric :-

http://www.linuxquestions.org/questi...8/#post4469919

Which links to this file :-

http://slackware.com/~alien/slackbui...slack-required

interndan 11-02-2012 03:09 PM

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.

Dan

interndan 11-02-2012 04:35 PM

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.

Dan

Alien Bob 11-02-2012 06:39 PM

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.

Better would be to compare:
http://slackware.com/~alien/slackbui..._64-1alien.dep
and
http://slackware.com/~alien/slackbui..._64-1alien.dep
to see the difference in dependencies when using my calibre package on Slackware 14 or 13.37.

Eric


All times are GMT -5. The time now is 01:23 PM.