-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
missing package dependency: systemd-resolved #360
Comments
Moved to the Supervisor installer repositiory, as the deb is maintained in this repository. FWIW, the dependency is listed in the installation instructions of the readme. I guess it (/all of them) could also be added to the deb, but maybe there are reasons this isn't being done? 🤔 @ikifar2012, you probably know better 😅 |
It already has quiet a bunch. |
Thanks for bringing this to my attention, I will definitely add I am trying to figure out what packages should be part of the pre-depends, it seems a lot of them should be except for |
Hm, I think only resolved got in my way because this was completely missing, and I downloaded the other ones beforehand. |
@ikifar2012 I've just re-installed the homeassistant-supervised package (on Ubuntu 22.04) and as part of the install it included this
However the next time I ran
So I assume there's an issue with how it's specified as a dependancy? Unsurprisingly without it the network storage using CIFS doesn't work. For now I've just run |
You can check which packages depend on it like this:
probably that dependency went missing? |
Yes, looks like the homeassistant-supervised didn't stick. I ran
|
Not sure why this happened... that being said Ubuntu is not officially supported |
Take a look at the latest release, I added BlueZ and moved some Dependency's to Pre-Depends |
I would rather keep BlueZ as optional / suggested package, as many people run the supervised on the servers - with no need to populate system by Bluez, Alsa, Pulse audio etc. - simple unnecessary packages on the server HW altogether. Please do not follow the old Nabu Casa story with supervised, where such changes were made on the user behalf for the greater good. ;-) I would still like to have my freedom to decide if I need Bluetooth support on the HW without Bluetooth. Thank you for reconsideration. |
If there is a mechanism that adds these packages once you select bluetooth to be used, I'd be on your side. |
To my knowledge that device is called docs and brain. Home Assistant doesn't require Bluetooth to start and/or run. The same for NetoworkManager. This is not real binary dependency, as so far I was happily running my installation without one or the other. Creating artificial dependency, just because users might need to run BlueZ and/or NetworkManager is against the way package dependencies work. Such packages shall be in the suggested packages, not in the required ones. Please refer to: https://www.debian.org/doc/debian-policy/ch-relationships.html You can clearly make the change in the documentation, where installation of the prerequisite packages is clearly mentioned. So just amending this documentation about cases using Bluez and NetworkManager would be required. I can prepare PR for this if you would agree. Thank you. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Describe the issue you are experiencing
the debian package invokes
systemctl enable systemd-resolved.service
however, it needs to pre-depend on it to warrant its available.It also seems, as bluetooth support only comes alive once
bluez
is installed on the host, could also be considered a dependency then.What type of installation are you running?
Home Assistant Supervised
Which operating system are you running on?
Debian
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
System Health information
xx
Supervisor diagnostics
xx
Additional information
please add the dependency.
The text was updated successfully, but these errors were encountered: