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

homeassistant-core-install.sh needs to tackle issues with python3.12 on debian #24

New Issue
Closed
opened 2026-02-04 16:19:40 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 16:19:40 +03:00
Owner
Copy Link

Originally created by @real-amie42 on GitHub (Nov 9, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

When installing homeassistant into a debian LXC Container, the homeassistant-core-install.sh script will fail in this way:

`Reading package lists... Doneatience)
Building dependency tree... Done
Reading state information... Done
Note, selecting 'python3-pip' instead of 'pip'
|E: Unable to locate package python3.12-dev
E: Couldn't find any package by glob 'python3.12-dev'
E: Couldn't find any package by regex 'python3.12-dev'

[ERROR] in line 17: exit code 0: while executing command $STD apt-get install -y git curl sudo mc bluez libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libopenjp2-7 libturbojpeg0-dev ffmpeg liblapack3 liblapack-dev dbus-broker libpcap-dev libavdevice-dev libavformat-dev libavcodec-dev libavutil-dev libavfilter-dev libmariadb-dev-compat libatlas-base-dev pip python3.12-dev`

This is due to the fact that homeassistant ditched the support of python versions <3.12. However debian bookworm only provides python 3.11.
@pascallj provides a backport of python3.12 specifically to tackle this particular issue within homeassistant. ( #see

I would suggest to implement that within the homeassistant-core-install.sh script. Alternatively the process could provide a hook in the advanced settings to open a shell within the running container prior to the call of homeassistant-core-install.sh.

Cheers
Amie

What settings are you currently utilizing?

Advanced Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

No response

Originally created by @real-amie42 on GitHub (Nov 9, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. When installing homeassistant into a debian LXC Container, the homeassistant-core-install.sh script will fail in this way: `Reading package lists... Doneatience) Building dependency tree... Done Reading state information... Done Note, selecting 'python3-pip' instead of 'pip' |E: Unable to locate package python3.12-dev E: Couldn't find any package by glob 'python3.12-dev' E: Couldn't find any package by regex 'python3.12-dev' [ERROR] in line 17: exit code 0: while executing command $STD apt-get install -y git curl sudo mc bluez libffi-dev libssl-dev libjpeg-dev zlib1g-dev autoconf build-essential libopenjp2-7 libturbojpeg0-dev ffmpeg liblapack3 liblapack-dev dbus-broker libpcap-dev libavdevice-dev libavformat-dev libavcodec-dev libavutil-dev libavfilter-dev libmariadb-dev-compat libatlas-base-dev pip python3.12-dev` This is due to the fact that homeassistant ditched the support of python versions <3.12. However debian bookworm only provides python 3.11. @pascallj provides a backport of python3.12 specifically to tackle this particular issue within homeassistant. ( #[see](https://github.com/pascallj/python3.12-backport) I would suggest to implement that within the homeassistant-core-install.sh script. Alternatively the process could provide a hook in the advanced settings to open a shell within the running container prior to the call of homeassistant-core-install.sh. Cheers Amie ### What settings are you currently utilizing? Advanced Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. _No response_
OVERLORD commented 2026-02-04 16:19:45 +03:00
Author
Owner
Copy Link

@havardthom commented on GitHub (Nov 10, 2024):

Related issue: https://github.com/tteck/Proxmox/issues/3892

Adding custom python backports from unknown authors not something we want in our scripts (feel free to use it yourself manually though). You should use the default distribution which is clearly stated in documentation.
image
image

@havardthom commented on GitHub (Nov 10, 2024): Related issue: https://github.com/tteck/Proxmox/issues/3892 Adding custom python backports from unknown authors not something we want in our scripts (feel free to use it yourself manually though). You should use the default distribution which is clearly stated in documentation. ![image](https://github.com/user-attachments/assets/d99c5292-3b28-47d6-bbe3-d06d8c6feec5) ![image](https://github.com/user-attachments/assets/1816ef76-db26-4c3d-bbcc-def5f700aa4a)
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
question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label
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#24
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?