[PR #6701] [MERGED] Fix: Bazarr requirements.txt file not parse-able by UV #6338

Closed
opened 2026-02-26 15:31:35 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/6701
Author: @Xerovoxx98
Created: 8/9/2025
Status: Merged
Merged: 8/9/2025
Merged by: @michelroegl-brunner

Base: mainHead: bazarr-uv


📝 Commits (4)

  • 82ea366 fix: delete unparseable flag from requirements file
  • a2ea582 fix: remove unparseable flag from requirements.txt
  • 63c9cf0 Update bazarr.sh
  • bef68a9 fix: update sed line and remove --only-binary section from uv

📊 Changes

2 files changed (+2 additions, -0 deletions)

View changed files

📝 ct/bazarr.sh (+1 -0)
📝 install/bazarr-install.sh (+1 -0)

📄 Description

✍️ Description

The requirements.txt file that ships with Bazarr includes a flag that is not parse-able by UV, this PR simply strips that flag out of the file and adds it manually to the UV install line.

Please reject this PR if this is not an elegant enough solution.

Link: #6700

Prerequisites (X in brackets)

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

🛠️ Type of Change (X in brackets)

  • 🐞 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.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/6701 **Author:** [@Xerovoxx98](https://github.com/Xerovoxx98) **Created:** 8/9/2025 **Status:** ✅ Merged **Merged:** 8/9/2025 **Merged by:** [@michelroegl-brunner](https://github.com/michelroegl-brunner) **Base:** `main` ← **Head:** `bazarr-uv` --- ### 📝 Commits (4) - [`82ea366`](https://github.com/community-scripts/ProxmoxVE/commit/82ea36651e18843c71eee0e5d5e369810db14d8b) fix: delete unparseable flag from requirements file - [`a2ea582`](https://github.com/community-scripts/ProxmoxVE/commit/a2ea58267571fe1a1b093810b23e0f9879ca0eec) fix: remove unparseable flag from requirements.txt - [`63c9cf0`](https://github.com/community-scripts/ProxmoxVE/commit/63c9cf02f3f5724afdad5ba7470997ad8fee2d35) Update bazarr.sh - [`bef68a9`](https://github.com/community-scripts/ProxmoxVE/commit/bef68a9af2d934cf489bffffbb28e07470b72054) fix: update sed line and remove --only-binary section from uv ### 📊 Changes **2 files changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `ct/bazarr.sh` (+1 -0) 📝 `install/bazarr-install.sh` (+1 -0) </details> ### 📄 Description <!--🛑 New scripts must be submitted to [ProxmoxVED](https://github.com/community-scripts/ProxmoxVED) for testing. PRs without prior testing will be closed. --> ## ✍️ Description The requirements.txt file that ships with Bazarr includes a flag that is not parse-able by UV, this PR simply strips that flag out of the file and adds it manually to the UV install line. Please reject this PR if this is not an elegant enough solution. ## 🔗 Related PR / Issue Link: #6700 ## ✅ 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. - [ ] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 15:31:35 +03:00
Sign in to join this conversation.
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#6338
No description provided.