Skip to content

Conversation

JVKeller
Copy link
Contributor

Changed location to one that exists.

✍️ Description

🔗 Related PR / Issue

Link: #

✅ Prerequisites (X in brackets)

  • [X ] Self-review completed – Code follows project standards.
  • [X ] Tested thoroughly – Changes work as expected.
  • [X ] No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • [ X] 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • [ X] 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

Changed location to one that exists.
@JVKeller JVKeller requested a review from a team as a code owner September 12, 2025 15:37
@github-actions github-actions bot added pve-tool update script A change that updates a script labels Sep 12, 2025
@MickLesk
Copy link
Member

/usr/local/bin exist always? Script Work since 4 years?

@JVKeller
Copy link
Contributor Author

JVKeller commented Sep 12, 2025

Right... I used this in the past without an issue, but this time:

-bash: /usr/local/bin/test.sh: No such file or directory

My proxmox server didn't even have /usr/local/bin, I can't be the only one?

@JVKeller
Copy link
Contributor Author

yeah, this was a bad idea. lol

@JVKeller JVKeller closed this Sep 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pve-tool update script A change that updates a script
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants