| 29 Jun 2021 |
 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 |
| dotlambda | Maybe we can ask https://linuxnet.ca/ieee/oui/ to provide a versioned file | 22:05:22 |
| dotlambda | We should also tell upstream, i.e. Home Assistant, that relying on outdated data (from April 2020) is not the smartest idea. | 22:09:08 |
 CRTified | Oh wow, the code doesn't even update the vendor list, so it's always the build-time version that's used 🤔 | 22:11:11 |
| dotlambda | In reply to @schnecfk:ruhr-uni-bochum.de
Oh wow, the code doesn't even update the vendor list, so it's always the build-time version that's used 🤔 That's what I meant with "HA doesn't do that" | 22:11:47 |
| CRTified | I mean, the mechanism to just update the list is there, even described in the project description | 22:11:51 |
| CRTified | Oh, I thought that it was meant completely FreeBSD-specific | 22:13:23 |
| CRTified | * Oh, I thought that it was meant completely FreeBSD-specific, nvm then | 22:13:26 |
| dotlambda | CRTified I won't file an upstream about this any time soon so please go ahead and do so if you feel like it. | 22:14:33 |
| dotlambda | * CRTified I won't file an upstream issue about this any time soon so please go ahead and do so if you feel like it. | 22:15:21 |
| CRTified | Not really in a condition to do so, sorry 😕 | 22:21:56 |
| CRTified | So it would probably stay on my todo for a long time, too. But given the move to UI-only config I also don't know whether I'll maintain my HA-config that much or whether I'll just pin nixpkgs to a working version and wait for a suitable alternative | 22:23:02 |
| @hexa:lossy.network |
Last-Modified: Thu, 01 Jul 2021 22:01:33 GMT
| 23:59:54 |
| 2 Jul 2021 |
| @hexa:lossy.network | sounds like a version to me 🤣 | 00:00:01 |
