SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-28 08:42:37 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

MariaDB repository fail #1261

New Issue
Open
opened 2025-11-20 05:07:11 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:07:11 -05:00
Owner
Copy Link

Originally created by @mikafouenski on GitHub (Jun 12, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Shinobi

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

Hello 👋

While installing Shinobi, the script is failing at the MariaDB install stage.

🔄 Steps to reproduce the issue.

Just try to install any script using the MariaDB snippet.
https://github.com/community-scripts/ProxmoxVE/blob/main/misc/tools.func#L226

eg: Shinobi

❌ Paste the full error output (if available).

  ✔️  Latest GA MariaDB version is 12.0.1
Hit:1 http://archive.ubuntu.com/ubuntu jammy InReleasery 
Ign:2 http://mirror.mariadb.org/repo/12.0.1/debian jammy InRelease
Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease       
Hit:5 http://archive.ubuntu.com/ubuntu jammy-security InRelease     
Err:6 http://mirror.mariadb.org/repo/12.0.1/debian jammy Release
  404  Not Found [IP: 162.55.42.214 80]
Reading package lists... Done
E: The repository 'http://mirror.mariadb.org/repo/12.0.1/debian jammy 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 276: exit code 0: while executing command $STD apt-get update
/dev/fd/63: line 74: SPINNER_PID: unbound variable

🖼️ Additional context (optional).

jammy doesn't appear to be valid for the /debian subpath.
Image

Replacing the sourcelist with the bookworm distrib will fix the issue:

$ cat /etc/apt/sources.list.d/mariadb.list
deb [signed-by=/etc/apt/trusted.gpg.d/mariadb.gpg] http://mirror.mariadb.org/repo/12.0.1/debian bookworm main

OR
Use the /ubuntu subpath for the ubuntu distrib:
Image

(It's "probably" the same package either way)

Thank you for the scripts, they are really neat. 🙂

Originally created by @mikafouenski on GitHub (Jun 12, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Shinobi ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/shinobi.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Hello 👋 While installing Shinobi, the script is failing at the MariaDB install stage. ### 🔄 Steps to reproduce the issue. Just try to install any script using the MariaDB snippet. https://github.com/community-scripts/ProxmoxVE/blob/main/misc/tools.func#L226 eg: Shinobi ### ❌ Paste the full error output (if available). ``` ✔️ Latest GA MariaDB version is 12.0.1 Hit:1 http://archive.ubuntu.com/ubuntu jammy InReleasery Ign:2 http://mirror.mariadb.org/repo/12.0.1/debian jammy InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Hit:5 http://archive.ubuntu.com/ubuntu jammy-security InRelease Err:6 http://mirror.mariadb.org/repo/12.0.1/debian jammy Release 404 Not Found [IP: 162.55.42.214 80] Reading package lists... Done E: The repository 'http://mirror.mariadb.org/repo/12.0.1/debian jammy 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 276: exit code 0: while executing command $STD apt-get update /dev/fd/63: line 74: SPINNER_PID: unbound variable ``` ### 🖼️ Additional context (optional). `jammy` doesn't appear to be valid for the `/debian` subpath. ![Image](https://github.com/user-attachments/assets/8ed20c01-b57c-4786-9147-7cdbbf65eb82) Replacing the sourcelist with the `bookworm` distrib will fix the issue: ```shell $ cat /etc/apt/sources.list.d/mariadb.list deb [signed-by=/etc/apt/trusted.gpg.d/mariadb.gpg] http://mirror.mariadb.org/repo/12.0.1/debian bookworm main ``` OR Use the `/ubuntu` subpath for the ubuntu distrib: ![Image](https://github.com/user-attachments/assets/140c9553-8d38-435f-9425-93c3af337394) (It's "probably" the same package either way) Thank you for the scripts, they are really neat. 🙂
saavagebueno added the not a script issue label 2025-11-20 05:07:11 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#1261
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?