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

Jellyseerr Failed Update #1070

New Issue
Closed
opened 2025-11-20 05:03:51 -05:00 by saavagebueno · 4 comments
saavagebueno commented 2025-11-20 05:03:51 -05:00
Owner
Copy Link

Originally created by @oOStroudyOo on GitHub (May 9, 2025).

✅ Have you read and understood the above guidelines?

Yes

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

Jellyseerr

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

Debian 12

📝 Provide a clear and concise description of the issue.

Jellyseerr fails to update, I have used the update script previously with no problem so unsure if it's a script problem, or a Jellyseerr problem.

Same error as https://github.com/community-scripts/ProxmoxVE/issues/4233 except I'm trying to update, rather than install, and using the correct script as seen instead my /bin/update file (bash -c "$(curl -qLO - https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyseerr.sh)")

I've also tried it with bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyseerr.sh)"

If I try and run npm install --frozen-lockfile manually, you get:
ERR_PNPM_NO_PKG_MANIFEST  No package.json found in /root

🔄 Steps to reproduce the issue.

Update Jellyseerr using update script.

❌ Paste the full error output (if available).

remote: Enumerating objects: 961, done.
remote: Counting objects: 100% (556/556), done.
remote: Compressing objects: 100% (20/20), done.
remote: Total 961 (delta 534), reused 547 (delta 530), pack-reused 405 (from 1)
Receiving objects: 100% (961/961), 352.78 KiB | 11.76 MiB/s, done.
Resolving deltas: 100% (673/673), completed with 178 local objects.
From https://github.com/Fallenbagel/jellyseerr
   5663ac1a..fac45387  main                -> origin/main
   e5ab8475..70a28dd1  develop             -> origin/develop
 + 21654614...a3feaba2 feat-dns-caching-manager -> origin/feat-dns-caching-manager  (forced update)
 * [new branch]        fix-pending-media   -> origin/fix-pending-media
 * [new branch]        fix-pgsql-timezone  -> origin/fix-pgsql-timezone
 * [new branch]        fix-typeorm-update  -> origin/fix-typeorm-update
 * [new tag]           preview-typeorm-fix -> preview-typeorm-fix
 * [new tag]           v2.5.2              -> v2.5.2
  ✖️   Updating pnpm from version 10.6.4 to ^9.0.0...

changed 1 package in 1s

1 package is looking for funding
  run `npm fund` for details
npm notice
npm notice New major version of npm available! 10.9.2 -> 11.3.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.3.0
npm notice To update run: npm install -g npm@11.3.0
npm notice
⠋ Updating Jellyseerr ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your pnpm version is incompatible with "/opt/jellyseerr".

Expected version: ^9.0.0
Got: 10.6.4

This is happening because the package's manifest has an engines.pnpm field specified.
To fix this issue, install the required pnpm version globally.

To install the latest version of pnpm, run "pnpm i -g pnpm".
To check your pnpm version, run "pnpm -v".
⠙ Updating Jellyseerr
[ERROR] in line 73: exit code 0: while executing command $STD pnpm install --frozen-lockfile

🖼️ Additional context (optional).

Image

Image

Originally created by @oOStroudyOo on GitHub (May 9, 2025). ### ✅ Have you read and understood the above guidelines? Yes ### 📜 What is the name of the script you are using? Jellyseerr ### 📂 What was the exact command used to execute the script? update ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Jellyseerr fails to update, I have used the update script previously with no problem so unsure if it's a script problem, or a Jellyseerr problem. Same error as https://github.com/community-scripts/ProxmoxVE/issues/4233 except I'm trying to update, rather than install, and using the correct script as seen instead my `/bin/update` file (`bash -c "$(curl -qLO - https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyseerr.sh)"`) I've also tried it with `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyseerr.sh)"` If I try and run `npm install --frozen-lockfile` manually, you get: `ERR_PNPM_NO_PKG_MANIFEST  No package.json found in /root` ### 🔄 Steps to reproduce the issue. Update Jellyseerr using update script. ### ❌ Paste the full error output (if available). ``` remote: Enumerating objects: 961, done. remote: Counting objects: 100% (556/556), done. remote: Compressing objects: 100% (20/20), done. remote: Total 961 (delta 534), reused 547 (delta 530), pack-reused 405 (from 1) Receiving objects: 100% (961/961), 352.78 KiB | 11.76 MiB/s, done. Resolving deltas: 100% (673/673), completed with 178 local objects. From https://github.com/Fallenbagel/jellyseerr 5663ac1a..fac45387 main -> origin/main e5ab8475..70a28dd1 develop -> origin/develop + 21654614...a3feaba2 feat-dns-caching-manager -> origin/feat-dns-caching-manager (forced update) * [new branch] fix-pending-media -> origin/fix-pending-media * [new branch] fix-pgsql-timezone -> origin/fix-pgsql-timezone * [new branch] fix-typeorm-update -> origin/fix-typeorm-update * [new tag] preview-typeorm-fix -> preview-typeorm-fix * [new tag] v2.5.2 -> v2.5.2 ✖️ Updating pnpm from version 10.6.4 to ^9.0.0... changed 1 package in 1s 1 package is looking for funding run `npm fund` for details npm notice npm notice New major version of npm available! 10.9.2 -> 11.3.0 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.3.0 npm notice To update run: npm install -g npm@11.3.0 npm notice ⠋ Updating Jellyseerr ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version) Your pnpm version is incompatible with "/opt/jellyseerr". Expected version: ^9.0.0 Got: 10.6.4 This is happening because the package's manifest has an engines.pnpm field specified. To fix this issue, install the required pnpm version globally. To install the latest version of pnpm, run "pnpm i -g pnpm". To check your pnpm version, run "pnpm -v". ⠙ Updating Jellyseerr [ERROR] in line 73: exit code 0: while executing command $STD pnpm install --frozen-lockfile ``` ### 🖼️ Additional context (optional). ![Image](https://github.com/user-attachments/assets/ac0e38ef-3953-42e7-9845-a9c60882b280) ![Image](https://github.com/user-attachments/assets/696565ca-c300-466c-9dea-74c31c0e7f38)
saavagebueno added the bug label 2025-11-20 05:03:51 -05:00
saavagebueno commented 2025-11-20 05:03:52 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 9, 2025):

Pnpm 9.0 what an sleeper Repo...

@MickLesk commented on GitHub (May 9, 2025): Pnpm 9.0 what an sleeper Repo...
saavagebueno commented 2025-11-20 05:03:53 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 9, 2025):

can you check again if #4365 merged?

@MickLesk commented on GitHub (May 9, 2025): can you check again if #4365 merged?
saavagebueno commented 2025-11-20 05:03:53 -05:00
Author
Owner
Copy Link

@oOStroudyOo commented on GitHub (May 10, 2025):

Hi @MickLesk

Same error occurs, just looks a little different this time:

remote: Enumerating objects: 959, done.
remote: Counting objects: 100% (552/552), done.
remote: Compressing objects: 100% (25/25), done.
remote: Total 959 (delta 527), reused 538 (delta 521), pack-reused 407 (from 1)
Receiving objects: 100% (959/959), 351.81 KiB | 12.56 MiB/s, done.
Resolving deltas: 100% (667/667), completed with 179 local objects.
From https://github.com/Fallenbagel/jellyseerr
   5663ac1a..fac45387  main                -> origin/main
   e5ab8475..8da1c929  develop             -> origin/develop
 + 21654614...a3feaba2 feat-dns-caching-manager -> origin/feat-dns-caching-manager  (forced update)
 * [new branch]        fix-pending-media   -> origin/fix-pending-media
 * [new branch]        fix-typeorm-update  -> origin/fix-typeorm-update
 * [new tag]           preview-typeorm-fix -> preview-typeorm-fix
 * [new tag]           v2.5.2              -> v2.5.2
  ✖️   Updating pnpm from version 10.6.4 to ^9.0.0...
  ✔️   Node.js 22 already installed

changed 1 package in 862ms

1 package is looking for funding
  run `npm fund` for details
  ✔️   All requested Node modules have been processed
⠸ Updating Jellyseerr ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your pnpm version is incompatible with "/opt/jellyseerr".

Expected version: ^9.0.0
Got: 10.6.4

This is happening because the package's manifest has an engines.pnpm field specified.
To fix this issue, install the required pnpm version globally.

To install the latest version of pnpm, run "pnpm i -g pnpm".
To check your pnpm version, run "pnpm -v".

   ╭──────────────────────────────────────────╮
   │                                          │
   │   Update available! 10.6.4 → 10.10.0.    │
   │   Changelog: https://pnpm.io/v/10.10.0   │
   │     To update, run: pnpm self-update     │
   │                                          │
   ╰──────────────────────────────────────────╯

⠼ Updating Jellyseerr
[ERROR] in line 73: exit code 0: while executing command $STD pnpm install --frozen-lockfile
@oOStroudyOo commented on GitHub (May 10, 2025): Hi @MickLesk Same error occurs, just looks a little different this time: ``` remote: Enumerating objects: 959, done. remote: Counting objects: 100% (552/552), done. remote: Compressing objects: 100% (25/25), done. remote: Total 959 (delta 527), reused 538 (delta 521), pack-reused 407 (from 1) Receiving objects: 100% (959/959), 351.81 KiB | 12.56 MiB/s, done. Resolving deltas: 100% (667/667), completed with 179 local objects. From https://github.com/Fallenbagel/jellyseerr 5663ac1a..fac45387 main -> origin/main e5ab8475..8da1c929 develop -> origin/develop + 21654614...a3feaba2 feat-dns-caching-manager -> origin/feat-dns-caching-manager (forced update) * [new branch] fix-pending-media -> origin/fix-pending-media * [new branch] fix-typeorm-update -> origin/fix-typeorm-update * [new tag] preview-typeorm-fix -> preview-typeorm-fix * [new tag] v2.5.2 -> v2.5.2 ✖️ Updating pnpm from version 10.6.4 to ^9.0.0... ✔️ Node.js 22 already installed changed 1 package in 862ms 1 package is looking for funding run `npm fund` for details ✔️ All requested Node modules have been processed ⠸ Updating Jellyseerr ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version) Your pnpm version is incompatible with "/opt/jellyseerr". Expected version: ^9.0.0 Got: 10.6.4 This is happening because the package's manifest has an engines.pnpm field specified. To fix this issue, install the required pnpm version globally. To install the latest version of pnpm, run "pnpm i -g pnpm". To check your pnpm version, run "pnpm -v". ╭──────────────────────────────────────────╮ │ │ │ Update available! 10.6.4 → 10.10.0. │ │ Changelog: https://pnpm.io/v/10.10.0 │ │ To update, run: pnpm self-update │ │ │ ╰──────────────────────────────────────────╯ ⠼ Updating Jellyseerr [ERROR] in line 73: exit code 0: while executing command $STD pnpm install --frozen-lockfile ```
saavagebueno commented 2025-11-20 05:03:53 -05:00
Author
Owner
Copy Link

@oOStroudyOo commented on GitHub (May 10, 2025):

Seems to work fine from a fresh install. Perhaps something wrong with my setup.
I'll close this and copy/paste my config over to the new one.

Thank you.

@oOStroudyOo commented on GitHub (May 10, 2025): Seems to work fine from a fresh install. Perhaps something wrong with my setup. I'll close this and copy/paste my config over to the new one. Thank you.
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#1070
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?