View Single Post
Old 11-29-2015, 09:37 AM   #10
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
You will have to install my calibre-git package from the AUR for that.
Code:
yaourt -S calibre-git
There is a couple of outstanding five-year-old bugs in cherrypy that are fixed in calibre's bundled copy of cherrypy.
But most distros only see the "bundled code copy !!!!" part, freak out, and remove it in favor of a system copy of cherrypy.

For interest, here is the ArchLinux bug report for this issue: https://bugs.archlinux.org/task/43382
Debian does the same thing (though I have never bothered filing a bug report with them), which affects derivatives including raspbian and Ubuntu, so I can't really blame Arch specifically...

my calibre-git package in the AUR does the right (practical) thing and depends on calibre's own patched copy of cherrypy.


Since you are using an apache reverse proxy, it *shouldn't* matter, because you should be able to use apache's auth methods, and the upstream cherrypy bug only affects calibre-server's builtin password handling.
Maybe try to figure out what your apache problem is?
eschwartz is offline   Reply With Quote