starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-16 05:34:07 +03:00
Code Issues 23 Packages Projects Releases 44 Wiki Activity

Issue updating Linkwarden #1990

New Issue
Closed
opened 2026-02-05 03:13:29 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-05 03:13:29 +03:00
Owner
Copy Link

Originally created by @Thrilleratplay on GitHub (Nov 12, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Linkwarden

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

update

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.04

📈 Which Proxmox version are you on?

pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-3-pve)

📝 Provide a clear and concise description of the issue.

When running rustc, the following error is returned:

error: rustup could not choose a version of rustc to run, because one wasn't specified explicitly, and no default is configured.
help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain.

I ran rustup default stable and reran update which completed successfully.

Could rustup default be set by the installation script?

🔄 Steps to reproduce the issue.

Step 1: Install old version of Linkwarden via proxmox-helper script
Step 2: try to update lxc.

❌ Paste the full error output (if available).

    __    _       __                           __         
   / /   (_)___  / /___      ______ __________/ /__  ____ 
  / /   / / __ \/ //_/ | /| / / __ `/ ___/ __  / _ \/ __ \
 / /___/ / / / / ,<  | |/ |/ / /_/ / /  / /_/ /  __/ / / /
/_____/_/_/ /_/_/|_| |__/|__/\__,_/_/   \__,_/\___/_/ /_/ 
                                                          

  ✔️   Update available: linkwarden 2.13.0 → 2.13.1
Get:1 https://pkgs.tailscale.com/stable/ubuntu noble InRelease
Hit:2 https://apt.postgresql.org/pub/repos/apt noble-pgdg InRelease                       
Hit:3 http://archive.ubuntu.com/ubuntu noble InRelease                                    
Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease
Hit:5 http://archive.ubuntu.com/ubuntu noble-updates InRelease
Hit:6 http://archive.ubuntu.com/ubuntu noble-security InRelease
Fetched 6,581 B in 1s (9,012 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
20 packages can be upgraded. Run 'apt list --upgradable' to see them.

changed 13 packages in 2s

28 packages are looking for funding
  run `npm fund` for details
  ✔️   Update Node.js 22
  ⏳   Updating yarn to latest version
changed 1 package in 728ms
  ✔️   Installed Node.js modules: yarn@latest
  ✔️   Stopped Service

[ERROR] in line 4332: exit code 0: while executing command CURRENT_VERSION=$(rustc --version 2> /dev/null | awk '{print $2}')

🖼️ Additional context (optional).

No response

Originally created by @Thrilleratplay on GitHub (Nov 12, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Linkwarden ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 24.04 ### 📈 Which Proxmox version are you on? pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-3-pve) ### 📝 Provide a clear and concise description of the issue. When running `rustc`, the following error is returned: ``` error: rustup could not choose a version of rustc to run, because one wasn't specified explicitly, and no default is configured. help: run 'rustup default stable' to download the latest stable release of Rust and set it as your default toolchain. ``` I ran `rustup default stable` and reran `update` which completed successfully. Could `rustup default` be set by the installation script? ### 🔄 Steps to reproduce the issue. Step 1: Install old version of Linkwarden via proxmox-helper script Step 2: try to update lxc. ### ❌ Paste the full error output (if available). ``` __ _ __ __ / / (_)___ / /___ ______ __________/ /__ ____ / / / / __ \/ //_/ | /| / / __ `/ ___/ __ / _ \/ __ \ / /___/ / / / / ,< | |/ |/ / /_/ / / / /_/ / __/ / / / /_____/_/_/ /_/_/|_| |__/|__/\__,_/_/ \__,_/\___/_/ /_/ ✔️ Update available: linkwarden 2.13.0 → 2.13.1 Get:1 https://pkgs.tailscale.com/stable/ubuntu noble InRelease Hit:2 https://apt.postgresql.org/pub/repos/apt noble-pgdg InRelease Hit:3 http://archive.ubuntu.com/ubuntu noble InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Hit:5 http://archive.ubuntu.com/ubuntu noble-updates InRelease Hit:6 http://archive.ubuntu.com/ubuntu noble-security InRelease Fetched 6,581 B in 1s (9,012 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done 20 packages can be upgraded. Run 'apt list --upgradable' to see them. changed 13 packages in 2s 28 packages are looking for funding run `npm fund` for details ✔️ Update Node.js 22 ⏳ Updating yarn to latest version changed 1 package in 728ms ✔️ Installed Node.js modules: yarn@latest ✔️ Stopped Service [ERROR] in line 4332: exit code 0: while executing command CURRENT_VERSION=$(rustc --version 2> /dev/null | awk '{print $2}') ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 03:13:29 +03:00
OVERLORD commented 2026-02-05 03:13:38 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 12, 2025):

How old is the Install? (Which Version before?)

@MickLesk commented on GitHub (Nov 12, 2025): How old is the Install? (Which Version before?)
OVERLORD commented 2026-02-05 03:13:42 +03:00
Author
Owner
Copy Link

@Thrilleratplay commented on GitHub (Nov 12, 2025):

linkwarden 2.13.0 → 2.13.1

@Thrilleratplay commented on GitHub (Nov 12, 2025): linkwarden 2.13.0 → 2.13.1
OVERLORD commented 2026-02-05 03:13:48 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 12, 2025):

Have you an snapshot? I can test tomorrow something, but i need your execution after this

@MickLesk commented on GitHub (Nov 12, 2025): Have you an snapshot? I can test tomorrow something, but i need your execution after this
OVERLORD commented 2026-02-05 03:13:56 +03:00
Author
Owner
Copy Link

@Thrilleratplay commented on GitHub (Nov 12, 2025):

I don't, sorry.

@Thrilleratplay commented on GitHub (Nov 12, 2025): I don't, sorry.
OVERLORD commented 2026-02-05 03:14:03 +03:00
Author
Owner
Copy Link

@arjen-w commented on GitHub (Nov 16, 2025):

When I try to update linkwarden today, I get the following error:
✖️ Cannot update package lists - APT is critically broken
/dev/fd/63: line 1460: jq: command not found
✔️ Update available: linkwarden 2.10.0 →

[ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1

Seems like there is still something wrong in the script.
I tried the rustup default stable command, but that did not change the outcome.

@arjen-w commented on GitHub (Nov 16, 2025): When I try to update linkwarden today, I get the following error: ✖️ Cannot update package lists - APT is critically broken /dev/fd/63: line 1460: jq: command not found ✔️ Update available: linkwarden 2.10.0 → [ERROR] in line 159: exit code 0: while executing command "$@" > /dev/null 2>&1 Seems like there is still something wrong in the script. I tried the rustup default stable command, but that did not change the outcome.
OVERLORD commented 2026-02-05 03:14:08 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 16, 2025):

No, you have an old Install, jq is missing Like the Text say, Just Install it

@MickLesk commented on GitHub (Nov 16, 2025): No, you have an old Install, jq is missing Like the Text say, Just Install it
OVERLORD commented 2026-02-05 03:14:14 +03:00
Author
Owner
Copy Link

@arjen-w commented on GitHub (Nov 16, 2025):

No, you have an old Install, jq is missing Like the Text say, Just Install it

Hmm. That only solved part of the error, still getting this message:

✔️ Update available: linkwarden 2.10.0 → 2.13.1
✖️ Cannot update package lists - APT is critically broken

[ERROR] in line 30: exit code 0: while executing command return 1

@arjen-w commented on GitHub (Nov 16, 2025): > No, you have an old Install, jq is missing Like the Text say, Just Install it Hmm. That only solved part of the error, still getting this message: ✔️ Update available: linkwarden 2.10.0 → 2.13.1 ✖️ Cannot update package lists - APT is critically broken [ERROR] in line 30: exit code 0: while executing command return 1
OVERLORD commented 2026-02-05 03:14:21 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 16, 2025):

Then Like the other Text say, Check your apt packages.

@MickLesk commented on GitHub (Nov 16, 2025): Then Like the other Text say, Check your apt packages.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1990
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?