starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-26 09:46:06 +03:00

[GH-ISSUE #11042] Whisparr v2 & v3 are different applications #2364

New issue

Closed

opened 2026-02-26 12:52:11 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 12:52:11 +03:00

Owner

Originally created by @derekgzn on GitHub (Jan 21, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11042

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

Whisparr

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/whisparr.sh)"

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.17.4-2-pve)

📝 Provide a clear and concise description of the issue.

Hi Community Scripts team,
This is not a bug or error, more of a request and a minor correction.

The whisparr app has 2 concurrent versions in active development, v2 & v3 are separate trains and use different sources for the media scenes lookup databases.

https://github.com/Whisparr/Whisparr

The standard Community Script installs version v2, and I have v3 running in docker, but nearly all of the apps I use run in Proxmox CT's, so it's a pain to maintain docker just for the few apps where the scripts are not yet available.

Would it be possible to create a script for v3? I believe it's just that the image is pulled from a different location (in docker), with the tag: v3.?

On to the correction, the Community script now shows that whisparr is version v3, but it still install v2.
Note: Just for clarification, v3 is NOT an update of v2, they are different trains and it will cause issues for many users if the v3 source is used to upgrade over v2.

🔄 Steps to reproduce the issue.

All detailed above

❌ Paste the full error output (if available).

N/A

🖼️ Additional context (optional).

No response

Originally created by @derekgzn on GitHub (Jan 21, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11042 ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? Whisparr ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/whisparr.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.1.4/5ac30304265fbd8e (running kernel: 6.17.4-2-pve) ### 📝 Provide a clear and concise description of the issue. Hi Community Scripts team, This is not a bug or error, more of a request and a minor correction. The whisparr app has 2 concurrent versions in active development, v2 & v3 are separate trains and use different sources for the media scenes lookup databases. https://github.com/Whisparr/Whisparr The standard Community Script installs version v2, and I have v3 running in docker, but nearly all of the apps I use run in Proxmox CT's, so it's a pain to maintain docker just for the few apps where the scripts are not yet available. Would it be possible to create a script for v3? I believe it's just that the image is pulled from a different location (in docker), with the tag: v3.? On to the correction, the Community script now shows that whisparr is version v3, but it still install v2. Note: Just for clarification, v3 is NOT an update of v2, they are different trains and it will cause issues for many users if the v3 source is used to upgrade over v2. ### 🔄 Steps to reproduce the issue. All detailed above ### ❌ Paste the full error output (if available). N/A ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:52:11 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:52:12 +03:00

Author

Owner

@tremor021 commented on GitHub (Jan 22, 2026):

Our webpage shows v3 as current installing version because thats what newreleases.io is reporting to us. BUT, we are actually installing the v2 via their official install instructions as v3 was a beta or something at the time we developed our install script.

Is v3 in stable state and SHOULD replace v2 or something?

@tremor021 commented on GitHub (Jan 22, 2026): Our webpage shows v3 as current installing version because thats what newreleases.io is reporting to us. BUT, we are actually installing the v2 via their official install instructions as v3 was a beta or something at the time we developed our install script. Is v3 in stable state and SHOULD replace v2 or something?

kerem commented

2026-02-26 12:52:12 +03:00

Author

Owner

@derekgzn commented on GitHub (Jan 22, 2026):

Thanks for you reply tremor021,

v2 and v3 are totally different applications, they use different reference media metadata source information, so v3 IS NOT an upgrade of v2.

Version 2.x (based on Sonarr)
Version 3.x (based on Radarr)

Many users (like me) are running v2.x & v3.x in separate containers.

The 2 trains run concurrently.

I hope that helps.

@derekgzn commented on GitHub (Jan 22, 2026): Thanks for you reply tremor021, v2 and v3 are totally different applications, they use different reference media metadata source information, so v3 IS NOT an upgrade of v2. Version 2.x (based on Sonarr) Version 3.x (based on Radarr) Many users (like me) are running v2.x & v3.x in separate containers. The 2 trains run concurrently. I hope that helps.

kerem commented

2026-02-26 12:52:12 +03:00

Author

Owner

@tremor021 commented on GitHub (Jan 22, 2026):

Ah, so it should be separate scripts then. Ok. I'm gonna close this one as we will most likely be doing some work on the version reporting for the website and probably be making a separate script for v3.

Thanks for clarifying

@tremor021 commented on GitHub (Jan 22, 2026): Ah, so it should be separate scripts then. Ok. I'm gonna close this one as we will most likely be doing some work on the version reporting for the website and probably be making a separate script for v3. Thanks for clarifying

kerem commented

2026-02-26 12:52:12 +03:00

Author

Owner

@MickLesk commented on GitHub (Jan 22, 2026):

ive removed the version check in newreleases

@MickLesk commented on GitHub (Jan 22, 2026): ive removed the version check in newreleases

kerem referenced this issue

2026-02-26 13:34:28 +03:00

[PR #2364] [MERGED] [core] update .app files #3726

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#2364

No description provided.

Rows
Columns