OS conflict when trying to install on Debian Bullseye #1
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Automated install script fails when installing on Debian Bullseye (11), this is because Bibliotecha requires a Debian Buster (10) environment. Can this be upgraded to work on Debian Bullseye as well?
Threw in
9e59b405d1
untested and this is now live on https://install.bibliotecha.info.Hopefully this can be tested and it works 🙏
Tested with Debian Bullseye 5.10.92-v71+, automated install succeeded, but unable to set the calibre database path as /opt/calibre-database, returns with:
On further inspection, the directory /opt/calibre-database is empty, so it seems that this command did not work:
Furthermore, there is no directory called /usr/bin/calibredb, which should have been created when calibre was installed.
Maybe we need a thingy that wraps us the entire installation logs into a file or sends it to a paste bin online so that it can be shared? This would mean I could just go back through the logs easily from any install from anyone. Otherwise, v hard to debug issues. Thanks for the report in any case!
Isn't this meant to be run on Raspbian?
Correction - I installed an OS from an image flashed with the Raspberry Pi Imager app, which says it's a port of Debian, but doesn't explictly say it's Raspbian. The OS I installed was a port of Debian Bullseye named Raspberry OS Lite (Legacy) - see screenshot of imager app
Raspbian is indeed the Pi-flavoured debian. The (Legacy) images are based on Buster, not Bullseye, perhaps that is your issue?
Oops, sorry - getting confused and I meant to say I was testing with Raspbian Bullseye, flashed with the Raspberry Pi Imager. The output from checking the version was "Debian Bullseye 5.10.92-v71+". Managed to install Bibliotecha with no complaints, but couldn't set the path of the calibre database (as described above)