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

Scrypted #102

New Issue
Closed
opened 2026-02-04 16:37:26 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-04 16:37:26 +03:00
Owner
Copy Link

Originally created by @koush on GitHub (Nov 25, 2024).

Please verify that you have read and understood the guidelines.

Yes

A clear and concise description of the issue.

Hi, I’m the maintainer of Scrypted. I would appreciate it if Scrypted was removed from the helper scripts. It does not handle gpu/hardware pass-through correctly, and it has become a persistent support issue on my repository and discord. So much so, that I have added detection code to see if it’s from the helper script, and warn the user to install using the official script. There are official installation instructions and scripts for running Scrypted in proxmox already.

What settings are you currently utilizing?

  • Default Settings
  • Advanced Settings

Which Linux distribution are you employing?

Ubuntu 22.04

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

No response

Originally created by @koush on GitHub (Nov 25, 2024). ### Please verify that you have read and understood the guidelines. Yes ### A clear and concise description of the issue. Hi, I’m the maintainer of Scrypted. I would appreciate it if Scrypted was removed from the helper scripts. It does not handle gpu/hardware pass-through correctly, and it has become a persistent support issue on my repository and discord. So much so, that I have added detection code to see if it’s from the helper script, and warn the user to install using the official script. There are official installation instructions and scripts for running Scrypted in proxmox already. ### What settings are you currently utilizing? - [X] Default Settings - [ ] Advanced Settings ### Which Linux distribution are you employing? Ubuntu 22.04 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. _No response_
OVERLORD added the breaking changedelete script labels 2026-02-04 16:37:26 +03:00
OVERLORD commented 2026-02-04 16:37:39 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Nov 25, 2024):

Wouldn't it make more sense to simply fix the script or provide information on what is not working or what needs to be fixed?

We can also remove it, I don't care in the end.

@MickLesk commented on GitHub (Nov 25, 2024): Wouldn't it make more sense to simply fix the script or provide information on what is not working or what needs to be fixed? We can also remove it, I don't care in the end.
OVERLORD commented 2026-02-04 16:37:49 +03:00
Author
Owner
Copy Link

@remz1337 commented on GitHub (Nov 25, 2024):

Let me look into it. Not sure who built the script, but since your own repo provides an installation script, I should be able to easily integrate that

@remz1337 commented on GitHub (Nov 25, 2024): Let me look into it. Not sure who built the script, but since your own repo provides an installation script, I should be able to easily integrate that
OVERLORD commented 2026-02-04 16:38:06 +03:00
Author
Owner
Copy Link

@koush commented on GitHub (Nov 25, 2024):

Wouldn't it make more sense to simply fix the script or provide information on what is not working or what needs to be fixed?

We can also remove it, I don't care in the end.

I don't know exactly what's broken (something is failing in either one of the intel compute libraries or gpu/transcode drivers), and I don't want to maintain two scripts/repos. This project is welcome to figure that out. It would probably be easier for maintainers of both repos, and users running into issues before realizing they used the wrong script, to simply remove the script.

@koush commented on GitHub (Nov 25, 2024): > Wouldn't it make more sense to simply fix the script or provide information on what is not working or what needs to be fixed? > > We can also remove it, I don't care in the end. I don't know exactly what's broken (something is failing in either one of the intel compute libraries or gpu/transcode drivers), and I don't want to maintain two scripts/repos. This project is welcome to figure that out. It would probably be easier for maintainers of both repos, and users running into issues before realizing they used the wrong script, to simply remove the script.
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 breaking change delete script
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#102
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?