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 13 Packages Projects Releases 10 Wiki Activity

MySQL repo missing support for Debian 13 "Trixie" #1847

New Issue
Closed
opened 2026-02-05 02:27:12 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 02:27:12 +03:00
Owner
Copy Link

Originally created by @SirLokiRichards on GitHub (Oct 20, 2025).

✅ Have you read and understood the above guidelines?

yes

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

MySQL

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/mysql.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.0.11/3bf5476b8a4699e2 (running kernel: 6.14.11-4-pve)

📝 Provide a clear and concise description of the issue.

tried to create a MySQL LXC but there's no directory for trixie under dist there "http://repo.mysql.com/apt/debian/dists/".

Workaround is to make a copy of the script found here https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/mysql.sh
and place it on your Proxmox server somewhere.
I use 'nano ./.sh' and paste in the raw text

but update var_version="${var_version:-13}" to be var_version="${var_version:-12}" instead

Write out/save and exit.
use 'sudo chmod +x ./.sh'
and then run the script locally './.sh'

That should let you create your LXC with the bookworm release until MySQL is compatible for Trixie.

🔄 Steps to reproduce the issue.

step 1. open console on your proxmox node
step 2. run scripts as found on Community website for create My SQL:
example:
'bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/mysql.sh)"'
step 3. follow prompts as appropriate

error encountered after MySQL installation (regardless of 8.4 LTS or 8.0 choices):

❌ Paste the full error output (if available).

Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease
Ign:5 https://repo.mysql.com/apt/debian trixie InRelease
Err:6 https://repo.mysql.com/apt/debian trixie Release
404 Not Found [IP: 184.31.29.212 443]
Reading package lists... Done
W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details
E: The repository 'https://repo.mysql.com/apt/debian trixie Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

[ERROR] in line 1366: exit code 0: while executing command $STD apt-get update

[ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

🖼️ Additional context (optional).

relates to issue #7332

https://github.com/community-scripts/ProxmoxVE/issues/7332#issue-3371782899

Originally created by @SirLokiRichards on GitHub (Oct 20, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? MySQL ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/mysql.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.0.11/3bf5476b8a4699e2 (running kernel: 6.14.11-4-pve) ### 📝 Provide a clear and concise description of the issue. tried to create a MySQL LXC but there's no directory for trixie under dist there "http://repo.mysql.com/apt/debian/dists/". Workaround is to make a copy of the script found here https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/mysql.sh and place it on your Proxmox server somewhere. I use 'nano ./<yourscriptname>.sh' and paste in the raw text but update var_version="${var_version:-13}" to be var_version="${var_version:-12}" instead Write out/save and exit. use 'sudo chmod +x ./<yourscriptname>.sh' and then run the script locally './<yourscriptname>.sh' That should let you create your LXC with the bookworm release until MySQL is compatible for Trixie. ### 🔄 Steps to reproduce the issue. step 1. open console on your proxmox node step 2. run scripts as found on Community website for create My SQL: example: 'bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/mysql.sh)"' step 3. follow prompts as appropriate error encountered after MySQL installation (regardless of 8.4 LTS or 8.0 choices): ### ❌ Paste the full error output (if available). Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Ign:5 https://repo.mysql.com/apt/debian trixie InRelease Err:6 https://repo.mysql.com/apt/debian trixie Release 404 Not Found [IP: 184.31.29.212 443] Reading package lists... Done W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details E: The repository 'https://repo.mysql.com/apt/debian trixie Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. [ERROR] in line 1366: exit code 0: while executing command $STD apt-get update [ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)" ### 🖼️ Additional context (optional). relates to issue #7332 https://github.com/community-scripts/ProxmoxVE/issues/7332#issue-3371782899
OVERLORD added the bug label 2026-02-05 02:27:12 +03:00
OVERLORD commented 2026-02-05 02:27:18 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 20, 2025):

why you create an duplicate?

@MickLesk commented on GitHub (Oct 20, 2025): why you create an duplicate?
OVERLORD commented 2026-02-05 02:27:29 +03:00
Author
Owner
Copy Link

@SirLokiRichards commented on GitHub (Oct 29, 2025):

why you create an duplicate?

Although my glasses are thick, I still miss obvious things at times.

My bad, thanks for clean up.
I'm trying to get used to this by diving in blind.

Cheers

@SirLokiRichards commented on GitHub (Oct 29, 2025): > why you create an duplicate? Although my glasses are thick, I still miss obvious things at times. My bad, thanks for clean up. I'm trying to get used to this by diving in blind. Cheers
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 bug
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#1847
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?