Basically all Calibre needs is an intelligently-designed conditional to catch all the growing number of OS's (Ubuntu 17.10 is only the 1st of many!) that require the new syntax for Calibre 3.x instead of 2.x !
In short, we need to insert this new conditional within roles/calibre/templates/calibre-serve.service.j2 Line 8-12 so these new OS's run:
ExecStart=/usr/bin/calibre-server --daemonize --log=/var/log/calibre.log --pidfile=/var/run/calibre.pid --port={{ calibre_port }} {{ calibre_dbpath }}
...instead of:
ExecStart=/usr/bin/calibre-server --daemonize --pidfile=/var/run/calibre.pid --port={{ calibre_port }} --with-library={{ calibre_dbpath }}
Thanks anybody who can help!
Background @ #502 (comment)
PS Let's discuss Thursday during our community/team call (http://minute.iiab.io) what ways are more futureproof / hassle-free to maintain this? And if we're not able to get this done for IIAB 6.5, it can slip to IIAB 6.6 !
PPS this builds off PR's #525 #526 #527
Basically all Calibre needs is an intelligently-designed conditional to catch all the growing number of OS's (Ubuntu 17.10 is only the 1st of many!) that require the new syntax for Calibre 3.x instead of 2.x !
In short, we need to insert this new conditional within roles/calibre/templates/calibre-serve.service.j2 Line 8-12 so these new OS's run:
...instead of:
Thanks anybody who can help!
Background @ #502 (comment)
PS Let's discuss Thursday during our community/team call (http://minute.iiab.io) what ways are more futureproof / hassle-free to maintain this? And if we're not able to get this done for IIAB 6.5, it can slip to IIAB 6.6 !
PPS this builds off PR's #525 #526 #527