starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Jellyfin Update does not work -> solution in Additional context (optional). #1856

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

Originally created by @lxrkz on GitHub (Oct 21, 2025).

✅ Have you read and understood the above guidelines?

yes

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

update

📂 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?

Virtual Environment 9.0.11

📝 Provide a clear and concise description of the issue.

can not update

The missing dep, libicu70, is not considered installable on ubuntu noble (despite the install script supporting noble, as it defines SUPPORTED_UBUNTU_RELEASES as including noble), as per this issue.

🔄 Steps to reproduce the issue.

update
or
apt update && apt upgrade

❌ Paste the full error output (if available).

The following packages have unmet dependencies:
jellyfin-server : Depends: libicu70 but it is not installable
E: Unable to correct problems, you have held broken packages.

[ERROR] in line 49: exit code 0: while executing command $STD apt -y --with-new-pkgs upgrade jellyfin jellyfin-server

🖼️ Additional context (optional).

I fixed it by updating my jellyfin sources. I edited /etc/apt/sources.list.d/jellyfin.sources to look like this
solution for ubuntu
Types: deb
URIs: https://repo.jellyfin.org/ubuntu
Suites: noble
Components: main
Architectures: amd64
Signed-By: /etc/apt/keyrings/jellyfin.gpg

solution for debian
Types: deb
URIs: https://repo.jellyfin.org/debian
Suites: trixie
Components: main
Architectures: amd64
Signed-By: /etc/apt/keyrings/jellyfin.gpg

Originally created by @lxrkz on GitHub (Oct 21, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? update ### 📂 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? Virtual Environment 9.0.11 ### 📝 Provide a clear and concise description of the issue. can not update The missing dep, libicu70, is not considered installable on ubuntu noble (despite the install script supporting noble, as it defines SUPPORTED_UBUNTU_RELEASES as including noble), as per [this]([https://answers.launchpad.net/ubuntu/+so...ion/818827](https://answers.launchpad.net/ubuntu/+source/icu/+question/818827)) issue. ### 🔄 Steps to reproduce the issue. update or apt update && apt upgrade ### ❌ Paste the full error output (if available). The following packages have unmet dependencies: jellyfin-server : Depends: libicu70 but it is not installable E: Unable to correct problems, you have held broken packages. [ERROR] in line 49: exit code 0: while executing command $STD apt -y --with-new-pkgs upgrade jellyfin jellyfin-server ### 🖼️ Additional context (optional). I fixed it by updating my jellyfin sources. I edited /etc/apt/sources.list.d/jellyfin.sources to look like this solution for ubuntu Types: deb URIs: https://repo.jellyfin.org/ubuntu Suites: noble Components: main Architectures: amd64 Signed-By: /etc/apt/keyrings/jellyfin.gpg solution for debian Types: deb URIs: https://repo.jellyfin.org/debian Suites: trixie Components: main Architectures: amd64 Signed-By: /etc/apt/keyrings/jellyfin.gpg
OVERLORD added the bug label 2026-02-05 02:28:21 +03:00
OVERLORD commented 2026-02-05 02:28:26 +03:00
Author
Owner
Copy Link

@KlausHans commented on GitHub (Nov 2, 2025):

Just had the same issue. Why is it closed?

@KlausHans commented on GitHub (Nov 2, 2025): Just had the same issue. Why is it closed?
OVERLORD commented 2026-02-05 02:28:30 +03:00
Author
Owner
Copy Link

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

Converted into discussion

Its Not an Script issue, its an User Setting, because Sources Changed or OS Upgraded.

@MickLesk commented on GitHub (Nov 2, 2025): Converted into discussion Its Not an Script issue, its an User Setting, because Sources Changed or OS Upgraded.
OVERLORD commented 2026-02-05 02:28:34 +03:00
Author
Owner
Copy Link

@KlausHans commented on GitHub (Nov 2, 2025):

Thanks for the quick answer.
Hm, i think i never touched the container manually in this regard.

@KlausHans commented on GitHub (Nov 2, 2025): Thanks for the quick answer. Hm, i think i never touched the container manually in this regard.
OVERLORD commented 2026-02-05 02:28:39 +03:00
Author
Owner
Copy Link

@lxrkz commented on GitHub (Nov 2, 2025):

Thanks for the quick answer. Hm, i think i never touched the container manually in this regard.

Did you upgrade pve8 to pve9?

@lxrkz commented on GitHub (Nov 2, 2025): > Thanks for the quick answer. Hm, i think i never touched the container manually in this regard. Did you upgrade pve8 to pve9?
OVERLORD commented 2026-02-05 02:28:42 +03:00
Author
Owner
Copy Link

@KlausHans commented on GitHub (Nov 2, 2025):

No, i am still on 8.4.11. Is that the problem?

@KlausHans commented on GitHub (Nov 2, 2025): No, i am still on 8.4.11. Is that the problem?
OVERLORD commented 2026-02-05 02:28:47 +03:00
Author
Owner
Copy Link

@lxrkz commented on GitHub (Nov 2, 2025):

Is no problem. That could be the reason for the os upgrade.

@lxrkz commented on GitHub (Nov 2, 2025): Is no problem. That could be the reason for the os upgrade.
OVERLORD commented 2026-02-05 02:28:50 +03:00
Author
Owner
Copy Link

@KlausHans commented on GitHub (Nov 2, 2025):

Ok.
Anyway, thanks for the provided solution!

@KlausHans commented on GitHub (Nov 2, 2025): Ok. Anyway, thanks for the provided solution!
OVERLORD commented 2026-02-05 02:28:51 +03:00
Author
Owner
Copy Link

@JoaGamo commented on GitHub (Nov 9, 2025):

Thank you!

@JoaGamo commented on GitHub (Nov 9, 2025): Thank you!
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#1856
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?