| 28 Jun 2021 |
 @hexa:lossy.network | 71% | 12:58:22 |
| @hexa:lossy.network |
712 / 994 components supported, i.e. 71.63%
| 12:58:59 |
 dotlambda | Mic92: Why are you asking? | 14:05:17 |
 Mic92 (Old) | Just curiosity. I saw you guys opening so many PRs.. | 14:05:57 |
| dotlambda | It's up from <65% less than two weeks ago I think. | 14:07:21 |
| @hexa:lossy.network | yep | 15:05:14 |
| dotlambda | Though that number is somewhat deceiving: Only 64% of all components' requirements are satisfied. | 15:16:25 |
| dotlambda | cause there are some components that don't have any requirements | 15:18:13 |
| dotlambda | In reply to @robert:funklause.de
Though that number is somewhat deceiving: Only 64% of all components' requirements are satisfied. meaning that we only packaged 64% of the stuff required to support all components | 15:18:36 |
| 29 Jun 2021 |
 Church | Hmm is there a package for hass_frontend yet? | 01:16:59 |
| @hexa:lossy.network | Church: it is in pkgs/servers/home-assistant/frontend.nix and directly callPackage'd from home-assistants derivation | 02:43:31 |
| Church | Odd running nixpkgs-unstable and that's not there... | 02:44:05 |
| Church | I am overriding the package def a bit | 02:44:11 |
| Church | That might be why | 02:44:13 |
| Church | Adding extra packages mainly | 02:44:24 |
| @hexa:lossy.network | heh | 02:45:31 |
| @hexa:lossy.network | can you explain more clearly what you are trying to achieve? | 02:45:39 |
| @hexa:lossy.network | fwiw: pkgs.home-assistant.python.pkgs.home-assistant-frontend | 02:46:56 |
| @hexa:lossy.network | dotlambda: if you would submit not-adjacent components it would be easier to apply them to my local branch and test them in one go | 13:28:30 |
| @hexa:lossy.network | as it is now they touch neighboring lines and the patchsets don't always apply cleanly and I can' be bothered to fix that up manually 😊 | 13:29:09 |
| dotlambda | Sorry, I'm aware of that but it's harder to keep track of which components still need to be done when it's not in order. | 13:33:11 |
| @hexa:lossy.network | yeah, i figured | 13:43:38 |
| dotlambda | What I mostly do is just setting componentTests to only those which are new (plus default_config and hue because it fails without iirc). | 13:46:34 |
| dotlambda | I resolved the merge conflicts now. | 13:47:47 |
| @hexa:lossy.network | yeah, hue is an oddball, because they require aiohue in some config test | 13:55:49 |
| 30 Jun 2021 |
| dotlambda | Heads-up: https://github.com/NixOS/nixpkgs/pull/128742 adds a package maintained by frenck | 07:23:00 |
|  walkah joined the room. | 16:16:55 |
| 1 Jul 2021 |
| dotlambda | HA will depend on https://pypi.org/project/mac-vendor-lookup/ in the next release. Problem is that there's only a wheel on PyPI and the release process downloads a list of MAC prefixes from http://standards-oui.ieee.org/oui/oui.txt. That file doesn't seem to be versioned, so it's hard for us to download. FreeBSD seems to just not install a prefix list: https://github.com/freebsd/freebsd-ports/blob/main/devel/py-mac-vendor-lookup/files/patch-setup.py, so users have to download the list after importing. HA doesn't do that so we will have to install some list. Any ideas? | 21:50:03 |
| dotlambda | The upstream PR for that change is https://github.com/home-assistant/core/pull/50429 btw. | 21:51:39 |
| dotlambda | "Nmap Tracker has fully transitioned to configuration via UI" :'( | 21:52:55 |
