SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Booklore update to 0.38.2 #1795

New Issue
Closed
opened 2025-11-20 05:17:34 -05:00 by saavagebueno · 6 comments
saavagebueno commented 2025-11-20 05:17:34 -05:00
Owner
Copy Link

Originally created by @jrporter on GitHub (Aug 26, 2025).

✅ 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.

This script throws an error when trying to update the container, but is able to create a new container without issue.

🔄 Steps to reproduce the issue.

Step 1: enter the shell of a container where this script has been used to install a prior version of Booklore successfully
Step 2: run "update" command or the full script call – both produce the same error result

❌ Paste the full error output (if available).

    ____              __   __                  
   / __ )____  ____  / /__/ /   ____  ________ 
  / __  / __ \/ __ \/ //_/ /   / __ \/ ___/ _ \
 / /_/ / /_/ / /_/ / ,< / /___/ /_/ / /  /  __/
/_____/\____/\____/_/|_/_____/\____/_/   \___/ 
                                               

  ✔️   Stopped BookLore
  ✔️   booklore is already up-to-date (v0.38.2)
  ⏳   Building Frontendnpm warn using --force Recommended protections disabled.

up to date, audited 1238 packages in 709ms

216 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
npm warn Unknown cli config "--configuration". This will stop working in the next major version of npm.

> booklore@0.0.0 build
> ng build

Initial chunk files   | Names         |  Raw size | Estimated transfer size
main-NJ7FNQVI.js      | main          |   3.21 MB |               572.75 kB
chunk-OYRZ3TK6.js     | -             | 178.87 kB |                52.14 kB
styles-DBE7MW2H.css   | styles        |  72.35 kB |                11.75 kB
polyfills-B6TNHZQ6.js | polyfills     |  34.58 kB |                11.32 kB
chunk-WWX6BADO.js     | -             |   1.60 kB |               680 bytes

                      | Initial total |   3.50 MB |               648.64 kB

Lazy chunk files      | Names         |  Raw size | Estimated transfer size
chunk-LEIPEF52.js     | quill         | 204.93 kB |                51.77 kB
chunk-MEOMQIVO.js     | browser       |  64.07 kB |                17.14 kB

Application bundle generation complete. [8.521 seconds]

▲ [WARNING] bundle initial exceeded maximum budget. Budget 500.00 kB was not met by 3.00 MB with a total of 3.50 MB.


▲ [WARNING] src/app/book/components/book-reviews/book-reviews.component.scss exceeded maximum budget. Budget 4.00 kB was not met by 159 bytes with a total of 4.16 kB.


▲ [WARNING] src/app/book/components/cbx-reader/cbx-reader.component.scss exceeded maximum budget. Budget 4.00 kB was not met by 896 bytes with a total of 4.90 kB.


Output location: /opt/booklore/booklore-ui/dist/booklore

  ✔️   Built Frontend
  ⏳   Building Backendusage: yq [-h] [--yaml-output] [--yaml-roundtrip] [--yaml-output-grammar-version {1.1,1.2}] [--width WIDTH]
          [--indentless-lists] [--in-place] [--version]
          [jq_filter] [files ...]
yq: error: argument files: can't open '.app.version = ""v0.38.2""': [Errno 2] No such file or directory: '.app.version = ""v0.38.2""'

[ERROR] in line 49: exit code 0: while executing command yq eval ".app.version = \"${APP_VERSION}\"" -i src/main/resources/application.yaml

🖼️ Additional context (optional).

No response

Originally created by @jrporter on GitHub (Aug 26, 2025). ### ✅ 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? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. This script throws an error when trying to update the container, but is able to create a new container without issue. ### 🔄 Steps to reproduce the issue. Step 1: enter the shell of a container where this script has been used to install a prior version of Booklore successfully Step 2: run "update" command or the full script call – both produce the same error result ### ❌ Paste the full error output (if available). ``` ____ __ __ / __ )____ ____ / /__/ / ____ ________ / __ / __ \/ __ \/ //_/ / / __ \/ ___/ _ \ / /_/ / /_/ / /_/ / ,< / /___/ /_/ / / / __/ /_____/\____/\____/_/|_/_____/\____/_/ \___/ ✔️ Stopped BookLore ✔️ booklore is already up-to-date (v0.38.2) ⏳ Building Frontendnpm warn using --force Recommended protections disabled. up to date, audited 1238 packages in 709ms 216 packages are looking for funding run `npm fund` for details found 0 vulnerabilities npm warn Unknown cli config "--configuration". This will stop working in the next major version of npm. > booklore@0.0.0 build > ng build Initial chunk files | Names | Raw size | Estimated transfer size main-NJ7FNQVI.js | main | 3.21 MB | 572.75 kB chunk-OYRZ3TK6.js | - | 178.87 kB | 52.14 kB styles-DBE7MW2H.css | styles | 72.35 kB | 11.75 kB polyfills-B6TNHZQ6.js | polyfills | 34.58 kB | 11.32 kB chunk-WWX6BADO.js | - | 1.60 kB | 680 bytes | Initial total | 3.50 MB | 648.64 kB Lazy chunk files | Names | Raw size | Estimated transfer size chunk-LEIPEF52.js | quill | 204.93 kB | 51.77 kB chunk-MEOMQIVO.js | browser | 64.07 kB | 17.14 kB Application bundle generation complete. [8.521 seconds] ▲ [WARNING] bundle initial exceeded maximum budget. Budget 500.00 kB was not met by 3.00 MB with a total of 3.50 MB. ▲ [WARNING] src/app/book/components/book-reviews/book-reviews.component.scss exceeded maximum budget. Budget 4.00 kB was not met by 159 bytes with a total of 4.16 kB. ▲ [WARNING] src/app/book/components/cbx-reader/cbx-reader.component.scss exceeded maximum budget. Budget 4.00 kB was not met by 896 bytes with a total of 4.90 kB. Output location: /opt/booklore/booklore-ui/dist/booklore ✔️ Built Frontend ⏳ Building Backendusage: yq [-h] [--yaml-output] [--yaml-roundtrip] [--yaml-output-grammar-version {1.1,1.2}] [--width WIDTH] [--indentless-lists] [--in-place] [--version] [jq_filter] [files ...] yq: error: argument files: can't open '.app.version = ""v0.38.2""': [Errno 2] No such file or directory: '.app.version = ""v0.38.2""' [ERROR] in line 49: exit code 0: while executing command yq eval ".app.version = \"${APP_VERSION}\"" -i src/main/resources/application.yaml ``` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:17:34 -05:00
saavagebueno commented 2025-11-20 05:17:35 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 27, 2025):

Duplicate

@MickLesk commented on GitHub (Aug 27, 2025): Duplicate
saavagebueno commented 2025-11-20 05:17:35 -05:00
Author
Owner
Copy Link

@jrporter commented on GitHub (Aug 27, 2025):

Duplicate

Why was this marked as a duplicate? Other than both pertaining to Booklore, these appear to be completely different problems based on a quick comparison of the error output in both issues.

@jrporter commented on GitHub (Aug 27, 2025): > Duplicate Why was this marked as a duplicate? Other than both pertaining to Booklore, these appear to be completely different problems based on a quick comparison of the error output in both issues.
saavagebueno commented 2025-11-20 05:17:35 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 27, 2025):

No its the Same, every time the requirements are broken in this tool

@MickLesk commented on GitHub (Aug 27, 2025): No its the Same, every time the requirements are broken in this tool
saavagebueno commented 2025-11-20 05:17:35 -05:00
Author
Owner
Copy Link

@rostbond commented on GitHub (Sep 2, 2025):

@jrporter I found the solution. The problem is that the apt/pip installs wrong yq (you can check that the wrong version was installed by executing the yq --version command, the output will always be yq 0.0.0).

So, you need to remove that version by executing the pip uninstall yq (if yq was installed via pip) / apt remove yq (if yq was installed via apt) command, then get correct version by executing the wget https://github.com/mikefarah/yq/releases/latest/download/yq_linux_amd64 -O /bin/yq command and make it executable: chmod +x /bin/yq. Check that the correct version is installed: yq --version (the output should be something like yq (https://github.com/mikefarah/yq/) version 4.43.1) and run the update command again.

@rostbond commented on GitHub (Sep 2, 2025): @jrporter I found the solution. The problem is that the `apt`/`pip` installs wrong `yq` (you can check that the wrong version was installed by executing the `yq --version` command, the output will always be `yq 0.0.0`). So, you need to remove that version by executing the `pip uninstall yq` (if `yq` was installed via `pip`) / `apt remove yq` (if `yq` was installed via `apt`) command, then get correct version by executing the `wget https://github.com/mikefarah/yq/releases/latest/download/yq_linux_amd64 -O /bin/yq` command and make it executable: `chmod +x /bin/yq`. Check that the correct version is installed: `yq --version` (the output should be something like `yq (https://github.com/mikefarah/yq/) version 4.43.1`) and run the `update` command again.
saavagebueno commented 2025-11-20 05:17:35 -05:00
Author
Owner
Copy Link

@jrporter commented on GitHub (Sep 6, 2025):

@rostbond THANK YOU! So awesome to finally be able to update.

@jrporter commented on GitHub (Sep 6, 2025): @rostbond THANK YOU! So awesome to finally be able to update.
saavagebueno commented 2025-11-20 05:17:35 -05:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Sep 7, 2025):

@jrporter I found the solution. The problem is that the apt/pip installs wrong yq (you can check that the wrong version was installed by executing the yq --version command, the output will always be yq 0.0.0).

So, you need to remove that version by executing the pip uninstall yq (if yq was installed via pip) / apt remove yq (if yq was installed via apt) command, then get correct version by executing the wget https://github.com/mikefarah/yq/releases/latest/download/yq_linux_amd64 -O /bin/yq command and make it executable: chmod +x /bin/yq. Check that the correct version is installed: yq --version (the output should be something like yq (https://github.com/mikefarah/yq/) version 4.43.1) and run the update command again.

I mean, how the hell can they do this wrong.... We can't fix this on the script side, because that would be messing with the dependencies of the application and potentially lead into more breakage.

You should post this to their github so they can fix it on the application side.

@tremor021 commented on GitHub (Sep 7, 2025): > [@jrporter](https://github.com/jrporter) I found the solution. The problem is that the `apt`/`pip` installs wrong `yq` (you can check that the wrong version was installed by executing the `yq --version` command, the output will always be `yq 0.0.0`). > > So, you need to remove that version by executing the `pip uninstall yq` (if `yq` was installed via `pip`) / `apt remove yq` (if `yq` was installed via `apt`) command, then get correct version by executing the `wget https://github.com/mikefarah/yq/releases/latest/download/yq_linux_amd64 -O /bin/yq` command and make it executable: `chmod +x /bin/yq`. Check that the correct version is installed: `yq --version` (the output should be something like `yq (https://github.com/mikefarah/yq/) version 4.43.1`) and run the `update` command again. I mean, how the hell can they do this wrong.... We can't fix this on the script side, because that would be messing with the dependencies of the application and potentially lead into more breakage. You should post this to their github so they can fix it on the application side.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1795
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?