I'll take a look at it this weekend. I haven't looked at this for a while
so I will need to troubleshoot.
Thanks,
--Larry
On Tue, Jun 2, 2020 at 9:20 AM Chris Abela wrote:
> That brings out nothing:
>
> $ grep \/tmp /proc/mounts
>
> $ cat /proc/mounts
> proc /proc proc rw,relatime 0 0
> sysfs
That brings out nothing:
$ grep \/tmp /proc/mounts
$ cat /proc/mounts
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /run tmpfs rw,nosuid,nodev,noexec,relatime,size=32768k,mode=755 0 0
devtmpfs /dev devtmpfs rw,relatime,size=8192k,nr_inodes=1009193,mode=755 0 0
/dev/myvg/r
IMHO you could verify it with a
grep \/tmp /proc/mounts
Il mar 2 giu 2020, 17:35 Chris Abela ha scritto:
> No Matteo,
>
> $ ls -ld /tmp
> drwxrwxrwt 12 root root 102400 Jun 2 17:29 /tmp/
>
> I notice that I missed some dependencies as my queue files were outdated.
> My building machine is very
It still does not build. I suspect that either the recent qt5 update has
compromised calibre or I am missing a dependency. This is my queue file:
cssutils
dnspython
mechanize
podofo
setuptools-scm
six
python-dateutil
netifaces
psutil
cssselect
apsw
optipng
python3
ninja
meson
libxkbcommon
libwacom
No Matteo,
$ ls -ld /tmp
drwxrwxrwt 12 root root 102400 Jun 2 17:29 /tmp/
I notice that I missed some dependencies as my queue files were outdated.
My building machine is very slow, so please stand-by until I update you.
Chris
On Tue, Jun 2, 2020 at 5:16 PM Matteo Bernardini <
matteo.bernard..
Seeing that "permissione denied" makes me think that you are trying to
build it with a /tmp filesystem mounted with a "noexec" option...
Is that the case?
If It is, try to export a different TMP for building just calibro.
Il mar 2 giu 2020, 17:02 Chris Abela ha scritto:
> I have installed update
I have installed updated packages of all the dependencies but clibre will
still not build:
### Building extension podofo ###
### Building extension pictureflow ###
Traceback (most recent call last):
File "setup.py", line 121, in
sys.exit(main())
File "setup.py", line 106,
I just built this to see if it was a python2-sip problem, but it
failed on something completely different. The first time I ran it,
it complained of not finding QtCore. The next few times it was
socket related, so no idea what is going on there. DBus is running.
If it is sip related, try rebuil
Il giorno mer 12 dic 2018 alle ore 13:43 Alexander Verbovetsky
ha scritto:
>
> Hello,
>
> On Wed, 12 Dec 2018, at 13:11, Petar Petrov wrote:
> > just a quick question -- is calibre broken just for me or others
> > cannot start it, as well?
>
> I also cannot start it after a recent upgrade. I attac
Hello,
On Wed, 12 Dec 2018, at 13:11, Petar Petrov wrote:
> just a quick question -- is calibre broken just for me or others
> cannot start it, as well?
I also cannot start it after a recent upgrade. I attached the error
screenshot.
Best regards,
Alexander
___
Il giorno mer 12 dic 2018 alle ore 11:48 David Melik
ha scritto:
>
> On 12/12/18 2:11 AM, Petar Petrov wrote:
> > just a quick question -- is calibre broken just for me or others
> > cannot start it, as well?
> >
> > I ended up installing the binary from their website.
> >
> > -petar
>
> Most vers
On 12/12/18 2:11 AM, Petar Petrov wrote:
just a quick question -- is calibre broken just for me or others
cannot start it, as well?
I ended up installing the binary from their website.
-petar
Most versions have broken for me for years. Sometimes they work when
recompiled (not always.)
just a quick question -- is calibre broken just for me or others
cannot start it, as well?
I ended up installing the binary from their website.
-petar
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mai
On Tue, Dec 04, 2018 at 04:52:31PM +0200, Petar Petrov wrote:
> thanks, but recompiling these (to the latest version available, not
> that particular commit) did not make Calibre work. Any other ideas?
> What else should I recompile?
>
> -petar
This binary repackaging script will at least get you
On 12/2/18 1:41 PM, Petar Petrov wrote:
> hi all,
>
> calibre does not start. It shows this in the terminal:
>
> Failed to run pipe worker with command: from calibre.utils.ipc.pool
> import run_main, worker_main; run_main(worker_main)
> Traceback (most recent call last):
> File "/usr/bin/calibr
thanks, but recompiling these (to the latest version available, not
that particular commit) did not make Calibre work. Any other ideas?
What else should I recompile?
-petar
On Mon, 3 Dec 2018 at 08:02, flinchx via SlackBuilds-users
wrote:
>
> I recall seeing the same traceback right after the big
I recall seeing the same traceback right after the big qt5 update and privately
emailing the calibre maintainer about it. The problem was with python2-sip.
What fixed calibre for me was to rebuild python2-sip after a fix was pushed (I
believe it was this one
https://git.slackbuilds.org/slackbui
hi all,
calibre does not start. It shows this in the terminal:
Failed to run pipe worker with command: from calibre.utils.ipc.pool
import run_main, worker_main; run_main(worker_main)
Traceback (most recent call last):
File "/usr/bin/calibre-parallel", line 20, in
sys.exit(main())
File "/
Hello,
My attempt to build calibre (using slackrepo) failed with the following
error:
-
IOError: [Errno 13] Permission denied:
u'/tmp/SBo/calibre-3.9.0/build/pyqt/pictureflow/pictureflow.exp'
-
I think that this happens because "setup.py install" drops the root
privileges at some moment
On Mon, Aug 21, 2017 at 03:15 (+), Jeremy Hansen wrote:
> Looks like this might be a miss-type in the calibre.info file. It
> has html-parser in there, but it should be html5-parser. If your
> tool allows you to modify the .info before installing, try and
> change the html-parser on the REQUI
> Looks like this might be a miss-type in the calibre.info file. It has
> html-parser in there, but it should be html5-parser. If your tool allows
> you to modify the .info before installing, try and change the html-parser
> on the REQUIRES line to html5-parser.
Yes, it should be html5-parser
> I
On Sun, Aug 20, 2017, 9:48 PM Jim Diamond wrote:
> I did
> sbocheck
> and then
> sboupgrade calibre
> and was rewarded with
> Unable to locate html-parser in the SlackBuilds.org tree.
> I have html5-parser-0.4.4-x86_64-1_SBo installed, but I don't see any
> html-parser pac
I did
sbocheck
and then
sboupgrade calibre
and was rewarded with
Unable to locate html-parser in the SlackBuilds.org tree.
I have html5-parser-0.4.4-x86_64-1_SBo installed, but I don't see any
html-parser package, unless it is t
Hi Len,
On Mon, Aug 14, 2017 at 9:11 AM, Lenard Spencer
wrote:
> In working with calibre, I found that the new versions (3.5 and newer)
> have another dependency, httml5-parser (also written by Kavid Goyal), which
> doesn't have a SB script in the repo. I have created a script for it, and
> now
In working with calibre, I found that the new versions (3.5 and newer)
have another dependency, httml5-parser (also written by Kavid Goyal),
which doesn't have a SB script in the repo. I have created a script for
it, and now I can get calibre to buid and run on my system. Shoiuld I
go ahead a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/02/2015 01:15 PM, Willy Sudiarto Raharjo wrote:
> Since the maintainer wanted to keep maintainership and also willing
> to upgrade to newer version when next Slackware release has the
> required dependencies, let's just keep a single version of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I've been aware of calibre upgrading to Qt5 and I have my own
> system updated to work with it on Slackware 14.1. Right now
> Slackware 14.1 and current cannot use the newer calibre due to the
> sip package being too old. I was hoping Slackware cur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I built the new calibre a few month back on -current. It did require
me to update sip, but that wasnt the only thing that needs to be
updated. You also need to rebuild PyQt against the new sip, then QT5,
then PyQt5. Luckily the build scripts Pat used
On Thu, 2 Apr 2015, Larry Hajali wrote:
Hi,
I've been aware of calibre upgrading to Qt5 and I have my own system
updated to work with it on Slackware 14.1. Right now Slackware 14.1 and
current cannot use the newer calibre due to the sip package being too old.
I was hoping Slackware current wou
* Larry Hajali wrote:
> With that said, if the SBo community wants calibre to be updated
> with the binary repackaging then I'm willing to give up maintaining
> calibre.
I can only speak for myself but I think the way you maintain Calibre
is just fine.
Maybe the Calibre binary can be made avail
Hi,
I've been aware of calibre upgrading to Qt5 and I have my own system
updated to work with it on Slackware 14.1. Right now Slackware 14.1 and
current cannot use the newer calibre due to the sip package being too old.
I was hoping Slackware current would update the sip package so that I could
u
Hi,
Since Calibre made the move to Qt5 the available Slackware packages
(both from here and AlienBob) have been stuck to the 1.48 version.
Today I've realized that there's a binary package provided by
Calibre's developer that is quite simple to package and I've made a
SlackBuild that does just th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/02/2013 11:47 AM, Kees Theunissen wrote:
> On Sat, 30 Nov 2013, King Beowulf wrote:
>
...
>>
>> Some DE menus will then sort the name name "correctly." For
>> example, Xfce sorts capitals before lower case letters (If anyone
>> knows how to ch
On Sat, 30 Nov 2013, King Beowulf wrote:
>2. For "$PRGNAM-gui.desktop" (ie calibre-gui.desktop) I suggest we
>capitalize the menu file name:
>
>Name=calibre
>
>to
>
>Name=Calibre
>
>Some DE menus will then sort the name name "correctly." For example,
>Xfce sorts capitals before lower case letters
1) Done in next submission.
2) Done in next submission.
--Larry
On Sat, Nov 30, 2013 at 12:15 PM, King Beowulf wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I've tested calbire-1.13.0 with the current SBo slackbuild script and
> everything appears A-OK. Recommendations:
>
> 1. T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've tested calbire-1.13.0 with the current SBo slackbuild script and
everything appears A-OK. Recommendations:
1. This line does not seems to be needed as the version string appears
to be correct:
# Make sure version string is correct.
sed -i "/^num
On Dec 17, 2009, at 9:53 AM, Eric Hameleers wrote:
> On Thu, 17 Dec 2009, Eugen Wissner wrote:
>
> > Yes, it works with xvf.
> > thanks
> >
> > 2009/12/17 Heinz Wiesinger
> >
> >> On Thursday 17 December 2009 09:32:34 Eugen Wissner wrote:
> >>> Sorry, it doesn't help:
> >>> [..]
> >>> bash-3.1$
On Thu, 17 Dec 2009, Eric Hameleers wrote:
The problem is that the file calibre.tar.gz is not a .gzipped tar archive at
all, it is a plain tar archive. Run "file calibre.tar.gz" and it will show
you this.
I will fix the tarball on the server, but from work I am not able to fix the
.asc file.
On Thu, 17 Dec 2009, Eugen Wissner wrote:
Yes, it works with xvf.
thanks
2009/12/17 Heinz Wiesinger
On Thursday 17 December 2009 09:32:34 Eugen Wissner wrote:
Sorry, it doesn't help:
[..]
bash-3.1$ tar zxf calibre.tar.gz
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Bee
Yes, it works with xvf.
thanks
2009/12/17 Heinz Wiesinger
> On Thursday 17 December 2009 09:32:34 Eugen Wissner wrote:
> > Sorry, it doesn't help:
> > [..]
> > bash-3.1$ tar zxf calibre.tar.gz
> >
> > gzip: stdin: not in gzip format
> > tar: Child returned status 1
> > tar: Beende mit Fehlerstat
On Thursday 17 December 2009 09:32:34 Eugen Wissner wrote:
> Sorry, it doesn't help:
> [..]
> bash-3.1$ tar zxf calibre.tar.gz
>
> gzip: stdin: not in gzip format
> tar: Child returned status 1
> tar: Beende mit Fehlerstatus aufgrund vorheriger Fehler
I can verify this here. However, it works fin
Sorry, it doesn't help:
bash-3.1$ wget http://slackbuilds.org/slackbuilds/13.0/office/calibre.tar.gz
--2009-12-17 09:30:07--
http://slackbuilds.org/slackbuilds/13.0/office/calibre.tar.gz
Auflösen des Hostnamen »slackbuilds.org« 208.67.159.181
Verbindungsaufbau zu slackbuilds.org|208.67.159.181|
On Dec 17, 2009, at 5:08 AM, Eugen Wissner wrote:
> I can't extract calibre.tar.gz
> gzip: stdin: not in gzip format
> tar: Child returned status 1
> tar: Exiting with failure status due to previous errors
Something may have happened in transit. Please try:
wget http://slackbuilds.org/slackbuild
I can't extract calibre.tar.gz
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Exiting with failure status due to previous errors
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/l
44 matches
Mail list logo
