[RomM] Update Script Fails During UV Sync
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
Research direction
The failing step is uv sync --all-extras at line 87 of the update flow in ct/romm.sh, which the reporter ran through the curl command in the issue. The error says RomM requires uv >=0.12.15,<0.13, but the script upgrades uv to 0.13.0 just before that step, so start by comparing those two version steps. Done means the update completes on Debian 13 with uv 0.13.0 or with uv pinned to a compatible version, and you can confirm this by re-running the update in verbose mode.
Written by the indexing model from the issue text.
Description
Script: RomM
Reported by: @ThiccChimichanga
Guidelines
- Read and understood guidelines: yes
- Verbose mode used: yes
Issue occurs during: Script Update
Environment
- Command run from: Proxmox web UI → LXC → Console
- Linux distribution: Debian
- Distribution version: 13
- Host is arm64: No
- Host platform: Proxmox VE
- Proxmox version: 9.2.21
- Default settings: Yes
- Advanced settings: No
- Exact command:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/romm.sh)"
Description
Running update script to update to new version 5.4.0 fails during uv sync.
Steps to reproduce
Step 1: Open LXC console
Step 2: type "update"
Step 3: Select verbose mode
Step 4: Observe failed update with error message
Error output
/ __ ____ ____ ___ / |/ /
/ // / __ / __ `__ / /|/ /
/ , / // / / / / / / / / /
// ||_// // /// /_/
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://security.debian.org trixie-security InRelease
Hit:3 http://deb.debian.org/debian trixie-updates InRelease
Hit:4 https://deb.nodesource.com/node_24.x nodistro InRelease
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
nodejs is already the newest version (24.21.0-1nodesource1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
changed 10 packages in 1s
✔️ Update Node.js 24 (npm 12.2.0)
✔️ Update available: romm 5.3.1 -> 5.4.0
✔️ Stopped Services
✔️ Backed up data to /opt/romm.backup
✔️ Backed up data to /opt/romm-players.backup
✔️ Deployed: romm (5.4.0)
⏳ Installing Python 3.13 via uvPython 3.13 is already installed
✔️ Python 3.13 installed
✔️ Setup uv 0.13.0
✔️ Restored data
⏳ Updating ROMMerror: Required uv version >=0.12.15, <0.13 does not match the running version 0.13.0
✖️ in line 87: exit code 2 (Misuse of shell builtins (e.g. syntax error)): while executing command uv sync --all-extras
--- Last 20 lines of log ---
[2026-10-10 19:36:54] [INFO] Update Node.js 24
[2026-10-10 19:36:56] [OK] Update Node.js 24 (npm 12.2.0)
[2026-10-10 19:36:56] [INFO] Checking for update: romm
[2026-10-10 19:36:56] [OK] Update available: romm 5.3.1 -> 5.4.0
[2026-10-10 19:36:56] [INFO] Stopping Services
[2026-10-10 19:36:58] [OK] Stopped Services
[2026-10-10 19:36:58] [INFO] Backing up data
[2026-10-10 19:36:58] [OK] Backed up data to /opt/romm.backup
[2026-10-10 19:36:58] [INFO] Backing up data
[2026-10-10 19:36:58] [OK] Backed up data to /opt/romm-players.backup
[2026-10-10 19:36:59] [INFO] Fetching github release: romm (5.4.0)
[2026-10-10 19:37:15] [OK] Deployed: romm (5.4.0)
[2026-10-10 19:37:16] [INFO] Upgrade uv from 0.12.13 to 0.13.0
[2026-10-10 19:37:16] [INFO] Installing Python 3.13 via uv
[2026-10-10 19:37:16] [OK] Python 3.13 installed
[2026-10-10 19:37:16] [OK] Setup uv 0.13.0
[2026-10-10 19:37:16] [INFO] Restoring data
[2026-10-10 19:37:16] [OK] Restored data
[2026-10-10 19:37:16] [INFO] Updating ROMM
[2026-10-10 19:37:16] [ERROR] in line 87: exit code 2 (Misuse of shell builtins (e.g. syntax error)): while executing command uv sync --all-extras
Attachments

- Dominant language
- Shell
- Stars
- 29.8k
- Forks
- 2.9k
- Avg merge
- 5h 12m
- Merged PRs (30d)
- 430
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from community-scripts/ProxmoxVE
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
community-scripts/ProxmoxVE#17824 ·
Maintainers usually reply within 1 day
-
website
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
community-scripts/ProxmoxVE#17821 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 Half a day Newbie friendliness 42/100
community-scripts/ProxmoxVE#17843 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
community-scripts/ProxmoxVE#17833 · 5 comments ·
Maintainers usually reply within 1 day
-
Update caddy errorOpenbug external
Difficulty 3/5 Half a day Newbie friendliness 50/100
community-scripts/ProxmoxVE#17830 · 1 comment ·
Maintainers usually reply within 1 day
All issues in community-scripts/ProxmoxVE
Similar issues
-
docs(evals): note CLAUDE_CODE_PRINT_BG_WAIT_CEILING_MS for headless eval runs that use workflowsOpengood first issue needs-triage priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
melodic-software/claude-code-plugins#7022 · 1 comment ·
Maintainers usually reply within 1 day
-
ready
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
kubeflow/pipelines#14784 · 1 comment ·
Maintainers usually reply within 2 days
-
implement-spec: step 9 cleanup collides with branch -D guards and with rewritten integration historyOpenneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mattpocock/skills#1251 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NuSkooler/enigma-bbs#907 ·
Maintainers usually reply within 1 day
-
initramfs: -type f (#18686) skips the libcurl.so.4 symlink, libcurl no longer copied into initramfsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days