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

Task: Update base template to Debian 13.1 and verify compatibility #1872

New Issue
Closed
opened 2025-11-20 05:18:51 -05:00 by saavagebueno · 13 comments
saavagebueno commented 2025-11-20 05:18:51 -05:00
Owner
Copy Link

Originally created by @mschabhuettl on GitHub (Sep 8, 2025).

Originally assigned to: @MickLesk on GitHub.

📌 Task summary

Switch helper scripts from Debian 12 to the newly released Debian 13.1 template and test functionality.

📋 Task details

Switch base template to Debian 13.1 and test compatibility

Debian 13.1 LXC template has been officially released by Proxmox:
http://download.proxmox.com/images/system/ → debian-13-standard_13.1-1_amd64.tar.zst

There is already an older issue about Debian 13 (see #7332), but that was for 13.0, not 13.1.

To-Do

  • Update base template reference from Debian 12 to Debian 13.1
  • Run initial tests with the official 13.1 template
  • Verify which scripts/containers are working
  • Compare results with Debian 13.0 testing (see #7332)
  • Document remaining incompatibilities

References

Originally created by @mschabhuettl on GitHub (Sep 8, 2025). Originally assigned to: @MickLesk on GitHub. ### 📌 Task summary Switch helper scripts from Debian 12 to the newly released Debian 13.1 template and test functionality. ### 📋 Task details # Switch base template to Debian 13.1 and test compatibility Debian 13.1 LXC template has been officially released by Proxmox: [http://download.proxmox.com/images/system/](http://download.proxmox.com/images/system/) → `debian-13-standard_13.1-1_amd64.tar.zst` There is already an older issue about Debian 13 (see #7332), but that was for 13.0, not 13.1. ## To-Do - [ ] Update base template reference from Debian 12 to Debian 13.1 - [ ] Run initial tests with the official 13.1 template - [ ] Verify which scripts/containers are working - [ ] Compare results with Debian 13.0 testing (see #7332) - [ ] Document remaining incompatibilities ## References - Issue #7332: [Debian 13 Incompatibilities](https://github.com/community-scripts/ProxmoxVE/issues/7332) - Proxmox system images: [http://download.proxmox.com/images/system/](http://download.proxmox.com/images/system/)
saavagebueno added the enhancementinvestigationfeature labels 2025-11-20 05:18:51 -05:00
saavagebueno commented 2025-11-20 05:18:58 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 8, 2025):

Alright, its finally available. I can take a look for the next weeks, i push every ct as single with an special branch

Image
@MickLesk commented on GitHub (Sep 8, 2025): Alright, its finally available. I can take a look for the next weeks, i push every ct as single with an special branch <img width="605" height="305" alt="Image" src="https://github.com/user-attachments/assets/a7ae1deb-86fc-4bbe-ab1e-aeee976ff370" />
saavagebueno commented 2025-11-20 05:18:58 -05:00
Author
Owner
Copy Link

@mschabhuettl commented on GitHub (Sep 8, 2025):

Alright, its finally available. I can take a look for the next weeks, i push every ct as single with an special branch

Image

@MickLesk

Suggestion: Add Debian version picker

Instead of hard-coding the template, could we add the same selection dialog used elsewhere in the helpers, so users can choose the Debian version (e.g. 12 / 13.0 / 13.1)?

  • Default stays on the recommended/latest
  • Easier A/B testing between versions
  • Consistent UX with existing dialogs

That way we can quickly verify new minor releases without editing scripts each time.

@mschabhuettl commented on GitHub (Sep 8, 2025): > Alright, its finally available. I can take a look for the next weeks, i push every ct as single with an special branch > > <img alt="Image" width="605" height="305" src="https://private-user-images.githubusercontent.com/47820557/486683924-a7ae1deb-86fc-4bbe-ab1e-aeee976ff370.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTczMjE3MzgsIm5iZiI6MTc1NzMyMTQzOCwicGF0aCI6Ii80NzgyMDU1Ny80ODY2ODM5MjQtYTdhZTFkZWItODZmYy00YmJlLWFiMWUtYWVlZTk3NmZmMzcwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTA5MDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwOTA4VDA4NTAzOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE3Njk3NzEyMzBlOGM1N2YwNjAyN2QwMTc5MGFlYThkNWMxZjlmZDZkOGI4MmZmZDJjNTZiZDllZmRmMmYyMjgmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.tPMjs96DcKfNtsUcdvsx87KAK2MVU4Gdlrau0jw2t58"> @MickLesk **Suggestion:** Add Debian version picker Instead of hard-coding the template, could we add the **same selection dialog** used elsewhere in the helpers, so users can **choose the Debian version** (e.g. 12 / 13.0 / 13.1)? - Default stays on the recommended/latest - Easier A/B testing between versions - Consistent UX with existing dialogs That way we can quickly verify new minor releases without editing scripts each time.
saavagebueno commented 2025-11-20 05:18:58 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 8, 2025):

its already so since some months, you need to hit "var_version=13" before the bash call

@MickLesk commented on GitHub (Sep 8, 2025): its already so since some months, you need to hit "var_version=13" before the bash call
saavagebueno commented 2025-11-20 05:18:58 -05:00
Author
Owner
Copy Link

@mschabhuettl commented on GitHub (Sep 8, 2025):

its already so since some months, you need to hit "var_version=13" before the bash call

I mean an interactive selection dialog inside the script itself – so that all available Debian templates from pveam available are listed and the user can simply pick one.

This would make it easier to test different Debian versions (12 / 13.1) without setting variables manually, and keep the UX consistent with the other dialogs already used in the helpers.

@mschabhuettl commented on GitHub (Sep 8, 2025): > its already so since some months, you need to hit "var_version=13" before the bash call I mean an **interactive selection dialog inside the script** itself – so that all available Debian templates from `pveam available` are listed and the user can simply pick one. This would make it easier to test different Debian versions (12 / 13.1) without setting variables manually, and keep the UX consistent with the other dialogs already used in the helpers.
saavagebueno commented 2025-11-20 05:18:59 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 8, 2025):

No, we removed the whiptails some time ago because many people simply choose the wrong things and mark it as an issue. That leads to even more problems. Either we switch completely to 13, or we stay at 12 (where it is not yet possible). For testing, it's very easy to do via the branch or a variable.

https://github.com/community-scripts/ProxmoxVE/discussions/3300

@MickLesk commented on GitHub (Sep 8, 2025): No, we removed the whiptails some time ago because many people simply choose the wrong things and mark it as an issue. That leads to even more problems. Either we switch completely to 13, or we stay at 12 (where it is not yet possible). For testing, it's very easy to do via the branch or a variable. https://github.com/community-scripts/ProxmoxVE/discussions/3300
saavagebueno commented 2025-11-20 05:18:59 -05:00
Author
Owner
Copy Link

@mschabhuettl commented on GitHub (Sep 8, 2025):

No, we removed the whiptails some time ago because many people simply choose the wrong things and mark it as an issue. That leads to even more problems. Either we switch completely to 13, or we stay at 12 (where it is not yet possible). For testing, it's very easy to do via the branch or a variable.

https://github.com/community-scripts/ProxmoxVE/discussions/3300

Ok, understood — then I’ll stick with using the variables for now. 👍 Thanks for clarifying!

@mschabhuettl commented on GitHub (Sep 8, 2025): > No, we removed the whiptails some time ago because many people simply choose the wrong things and mark it as an issue. That leads to even more problems. Either we switch completely to 13, or we stay at 12 (where it is not yet possible). For testing, it's very easy to do via the branch or a variable. > > https://github.com/community-scripts/ProxmoxVE/discussions/3300 Ok, understood — then I’ll stick with using the variables for now. 👍 Thanks for clarifying!
saavagebueno commented 2025-11-20 05:18:59 -05:00
Author
Owner
Copy Link

@mschabhuettl commented on GitHub (Sep 8, 2025):

@MickLesk would it make sense to create (or do we already have) a community-maintained list that documents which LXC helpers are compatible with Debian 13.1?

@mschabhuettl commented on GitHub (Sep 8, 2025): @MickLesk would it make sense to create (or do we already have) a **community-maintained list** that documents which LXC helpers are compatible with Debian 13.1?
saavagebueno commented 2025-11-20 05:18:59 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 8, 2025):

that will be included in the open PR; I just haven't had time to format the list as output/table yet.

@MickLesk commented on GitHub (Sep 8, 2025): that will be included in the open PR; I just haven't had time to format the list as output/table yet.
saavagebueno commented 2025-11-20 05:18:59 -05:00
Author
Owner
Copy Link

@mschabhuettl commented on GitHub (Sep 8, 2025):

that will be included in the open PR; I just haven't had time to format the list as output/table yet.

I think you mean that compatibility will be listed in the PR once it’s finalized.

What I mean is a simple doc/table where I (and others) can already give feedback when creating/testing 13.1 LXCs before the official release here - so we can report if it works or not and take some workload off you.

@mschabhuettl commented on GitHub (Sep 8, 2025): > that will be included in the open PR; I just haven't had time to format the list as output/table yet. I think you mean that compatibility will be listed in the PR once it’s finalized. What I mean is a simple doc/table where I (and others) can already give feedback when creating/testing 13.1 LXCs *before* the official release here - so we can report if it works or not and take some workload off you.
saavagebueno commented 2025-11-20 05:18:59 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 8, 2025):

Thats an mess of over 300 scripts. Maybe we can push an Site in Discussions or on Frontend. Idk. I Talk later to other contributor

@MickLesk commented on GitHub (Sep 8, 2025): Thats an mess of over 300 scripts. Maybe we can push an Site in Discussions or on Frontend. Idk. I Talk later to other contributor
saavagebueno commented 2025-11-20 05:18:59 -05:00
Author
Owner
Copy Link

@mschabhuettl commented on GitHub (Sep 8, 2025):

Thats an mess of over 300 scripts. Maybe we can push an Site in Discussions or on Frontend. Idk. I Talk later to other contributor

Thanks! I’m happy to help out in general, not only with a compatibility list but also wherever it makes sense for the project. 🙌

@mschabhuettl commented on GitHub (Sep 8, 2025): > Thats an mess of over 300 scripts. Maybe we can push an Site in Discussions or on Frontend. Idk. I Talk later to other contributor Thanks! I’m happy to help out in general, not only with a compatibility list but also wherever it makes sense for the project. 🙌
saavagebueno commented 2025-11-20 05:19:00 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 8, 2025):

https://github.com/community-scripts/ProxmoxVE/discussions/7485

@MickLesk commented on GitHub (Sep 8, 2025): https://github.com/community-scripts/ProxmoxVE/discussions/7485
saavagebueno commented 2025-11-20 05:19:00 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 23, 2025):

Closing due #7485, some scripts will be updated in next week. stack for stack

@MickLesk commented on GitHub (Sep 23, 2025): Closing due #7485, some scripts will be updated in next week. stack for stack
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 enhancement feature investigation
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#1872
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?