Booklore Install Error

[vigoren]

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

BookLore

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/booklore.sh)"

⚙️ What settings are you using?

• Default Settings
• Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Attempting to set up a new instance of booklore results in an error during installation and the tool failing to build.

🔄 Steps to reproduce the issue.

• Paste the comman bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/booklore.sh)" into the shell of your PVE environment.
• Select Default Settings (verbose)
• The script will fail during the Customized LXC Container portion of the build.

❌ Paste the full error output (if available).

    ____              __   __                  
   / __ )____  ____  / /__/ /   ____  ________ 
  / __  / __ \/ __ \/ //_/ /   / __ \/ ___/ _ \
 / /_/ / /_/ / /_/ / ,< / /___/ /_/ / /  /  __/
/_____/\____/\____/_/|_/_____/\____/_/   \___/ 
                                               
  ⚙️  Using Default Settings on node pve (🔍  Verbose)
  🆔  Container ID: 105
  🖥️  Operating System: debian (12)
  📦  Container Type: Unprivileged
  💾  Disk Size: 7 GB
  🧠  CPU Cores: 3
  🛠️  RAM Size: 2048 MiB
  🔍  Verbose Mode: Enabled
  🚀  Creating a BookLore LXC using the above default settings
  
  ✔️   Validated Storage (rootdir / vztmpl).
  ✔️   LXC Template List Updated
  ✔️   Started LXC Container
  ✔️   Customized LXC Container
/dev/stdin: line 109: syntax error near unexpected token `('
/dev/stdin: line 109: `      GIT_STATUS+="$HOST:($DNSFAIL)"'

[ERROR] in line 1249: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/"$var_install".sh)" $?

🖼️ Additional context (optional).

The booklore team did just release a new version, 0.31.0, that could be the reason for this failing.