Package Details: homeassistant-supervised 2.0.0-1

Git Clone URL: https://aur.archlinux.org/homeassistant-supervised.git (read-only, click to copy)
Package Base: homeassistant-supervised
Description: Home Assistant Supervised
Upstream URL: https://www.home-assistant.io/
Keywords: haos hass homeassistant supervised
Licenses: Apache
Conflicts: docker-desktop
Submitter: rokam
Maintainer: rokam (frostwork)
Last Packager: rokam
Votes: 4
Popularity: 0.000000
First Submitted: 2022-08-05 22:00 (UTC)
Last Updated: 2025-01-02 20:28 (UTC)

Pinned Comments

gaelic commented on 2024-06-19 18:07 (UTC) (edited on 2024-06-19 18:48 (UTC) by gaelic)

cgroup v1 is deprecated as of now and my pc is not booting anymore with the required parameter. I am downgrading systemd for the moment, but we need a solution for this problem rather soon. From the systemd changelog (version 256):

Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now considered obsolete and systemd by default will refuse to boot under it. To forcibly reenable cgroup v1 support, SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must be set on kernel command line. The meson option 'default-hierarchy=' is also deprecated, i.e. only cgroup v2 ('unified' hierarchy) can be selected as build-time default.

rokam commented on 2022-08-05 22:03 (UTC) (edited on 2022-08-05 22:04 (UTC) by rokam)

You need to add systemd.unified_cgroup_hierarchy=false in your kernel parameters.

Read more at: https://wiki.archlinux.org/title/Kernel_parameters

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

Maxwell175 commented on 2022-11-06 05:53 (UTC)

When trying to build, i get the following error:

==> Starting build()... go: module cache not found: neither GOMODCACHE nor GOPATH is set ==> ERROR: A failure occurred in build(). Aborting...

Running latest version of Manjaro.

rokam commented on 2022-09-28 16:19 (UTC)

Feel free to use it, although I'm not able to test it. That way, I can't fix any issues related to ARM. I just provided it the same way the installer exists for debian, you can set the MACHINE envvar to whatever you want and the pkg will accept it.

Adrian.Chmiel commented on 2022-09-28 15:52 (UTC)

In fact, Arch only officially supports x86.
But in documentation point 3.2:
https://wiki.archlinux.org/title/PKGBUILD
It is allowed to support other architectures in the AUR. Do you prefer to stay only with x86_64?

rokam commented on 2022-09-28 04:01 (UTC)

https://terms.archlinux.org/docs/code-of-conduct/#arch-linux-distribution-support-only

Adrian.Chmiel commented on 2022-09-27 20:10 (UTC)

ARM arch. is also supported (for exam. I using ARCH on ARM CPU)
https://archlinuxarm.org/

rokam commented on 2022-09-27 16:56 (UTC) (edited on 2022-09-27 16:56 (UTC) by rokam)

@adrian.chmiel, archlinux only support x86_64. When running on a x86_64 arch, the correct machine is selected. The machine is something different than uname -m.

Adrian.Chmiel commented on 2022-09-27 16:33 (UTC)

Thanks @rokam, regarding MACHINE, "uname -m" always will return architecture of system.
If we use env. variable then maybe better to use something like that?
echo $MACHINE

rokam commented on 2022-09-26 13:56 (UTC) (edited on 2022-09-26 14:04 (UTC) by rokam)

@adrian.chmiel fixed the systemd-journal-gatewayd.socket, it was my mistake to create hassio-journal-gatewayd.socket. Now the script edits the systemd-journal-gatewayd.socket to add the listenstream file used by docker. There was no need to install a package because systemd-journal-gatewayd is part of systemd.

About the machine, in your case you need to set the MACHINE env var before installing.

eg.: 

$ export MACHINE=raspberrypi3-64

I moved the check arch and machine to pre_install step. (The original deb installer does it in the post_install fase)

Adrian.Chmiel commented on 2022-09-26 12:24 (UTC) (edited on 2022-09-26 12:58 (UTC) by Adrian.Chmiel)

@rokam, if I'm not mistake, this version requires worked systemd-journal-remote (probably for remore control).
hassio-journal-gatewayd.socket requires systemd-journal-gatewayd which one require and libmicrohttpd package(it is not included now in the installation reuire list)
But we cannot start hassio-journal-gatewayd.socket bcause:
hassio-journal-gatewayd.socket: Socket service hassio-journal-gatewayd.service not loaded, refusing.

Moreover, if I have different machine that on the list, files is copped but the installation procedure stopped, even though RP3 is listed.

In my opinion, if they shoundn't install the package on a platform other than one on the list, it should check it first and return the error of platform not supported and stop the procedure.
Now they copies the files and leaves them unconfigured.

In line 140 should be "*)"?

Regarding MACHINE, if we have RP3, they "uname -m" return aarm64, then the script will not put information about MACHINE and check_machine() function will done with "exit 1".
Currently in my opinion the install script only supports x86 architecture, any other ends with "exit 1".

rokam commented on 2022-09-24 14:45 (UTC) (edited on 2022-09-24 14:45 (UTC) by rokam)

@adrian.chmiel, thanks for the suggestions. The first one will be fixed, although both will work the same way. The second is incorect. MACHINE should be one of the following:

  • generic-x86-64
  • odroid-c2
  • odroid-n2
  • odroid-xu
  • qemuarm
  • qemuarm-64
  • qemux86
  • qemux86-64
  • raspberrypi
  • raspberrypi2
  • raspberrypi3
  • raspberrypi4
  • raspberrypi3-64
  • raspberrypi4-64
  • tinker
  • khadas-vim3

That's why we have a check_machine function in the install script.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »