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

Bookstack Update -> Failed at composer update #1630

New Issue
Closed
opened 2025-11-20 05:13:42 -05:00 by saavagebueno · 5 comments
saavagebueno commented 2025-11-20 05:13:42 -05:00
Owner
Copy Link

Originally created by @Kaputtnique on GitHub (Aug 4, 2025).

✅ Have you read and understood the above guidelines?

yes

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

bookstack

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

./bookstack.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.

i dont know whats the issue. i know it breaks by updating composer

🔄 Steps to reproduce the issue.

wanted to update to the latest

❌ Paste the full error output (if available).

`
Run the "diagnose" command to get more detailed diagnostics output.

⏳ Old Composer 2.8.10 found, updating to latest

[ERROR] in line 526: exit code 0: while executing command composer diagnose > /dev/null 2>&1
`

🖼️ Additional context (optional).

No response

Originally created by @Kaputtnique on GitHub (Aug 4, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? bookstack ### 📂 What was the exact command used to execute the script? ./bookstack.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. i dont know whats the issue. i know it breaks by updating composer ### 🔄 Steps to reproduce the issue. wanted to update to the latest ### ❌ Paste the full error output (if available). ` Run the "diagnose" command to get more detailed diagnostics output. ⏳ Old Composer 2.8.10 found, updating to latest [ERROR] in line 526: exit code 0: while executing command composer diagnose > /dev/null 2>&1 ` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:13:42 -05:00
saavagebueno commented 2025-11-20 05:13:42 -05:00
Author
Owner
Copy Link

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

i change the output of diagnose now, can you try again in 5min with verbose? Whats the output?

@MickLesk commented on GitHub (Aug 4, 2025): i change the output of diagnose now, can you try again in 5min with verbose? Whats the output?
saavagebueno commented 2025-11-20 05:13:43 -05:00
Author
Owner
Copy Link

@Kaputtnique commented on GitHub (Aug 4, 2025):

`Run the "diagnose" command to get more detailed diagnostics output.
⏳ Old Composer 2.8.10 found, updating to latest/dev/fd/63: line 526: composer: command not found

[ERROR] in line 526: exit code 0: while executing command $STD composer diagnose`

O_o

@Kaputtnique commented on GitHub (Aug 4, 2025): `Run the "diagnose" command to get more detailed diagnostics output. ⏳ Old Composer 2.8.10 found, updating to latest/dev/fd/63: line 526: composer: command not found [ERROR] in line 526: exit code 0: while executing command $STD composer diagnose` O_o
saavagebueno commented 2025-11-20 05:13:43 -05:00
Author
Owner
Copy Link

@Kaputtnique commented on GitHub (Aug 4, 2025):

using version BookStack v25.05.2 before upgrading

@Kaputtnique commented on GitHub (Aug 4, 2025): using version BookStack v25.05.2 before upgrading
saavagebueno commented 2025-11-20 05:13:43 -05:00
Author
Owner
Copy Link

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

can you try it again? i dont have any use case to test it with this issue

@MickLesk commented on GitHub (Aug 4, 2025): can you try it again? i dont have any use case to test it with this issue
saavagebueno commented 2025-11-20 05:13:43 -05:00
Author
Owner
Copy Link

@Kaputtnique commented on GitHub (Aug 4, 2025):

work perfectly <3

@Kaputtnique commented on GitHub (Aug 4, 2025): work perfectly <3
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#1630
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?