Closed zoechi closed 1 month ago
It looks like for some reason pydantic 1.10.14 is dragged in as dependency event though pydantic 2.6.3 is now the default. I don't know Nix or Python well enough to figure out what exactly goes wrong.
nixpkgs overrides pydantic
to pydantic_1
. Perhaps it's because hass pins intellifire4py to an ancient version..? I'm not really sure since it does seem to build fine with pydantic 2 here.
This won't really get maintainer attention unless they are tagged:
$ nix eval --impure --expr 'with import <nixpkgs> {}; map (builtins.getAttr "github") home-assistant.meta.maintainers'
[ "fabaff" "mweinelt" "Mic92" ]
@fabaff @mweinelt @Mic92
aiogithubapi pins sigstore<2, but that was unpinned in 38f34c95cbec82aaf4471731ff926b624f096d2f.
Steps To Reproduce
Steps to reproduce the behavior:
Build log
Additional context
It started failing yesterday. It built fine a day before. It looks like for some reason
pydantic
1.10.14 is dragged in as dependency event thoughpydantic
2.6.3 is now the default. I don't know Nix or Python well enough to figure out what exactly goes wrong.It looks like
github
it's required for HACS (Home-Assistant Community Store) add-on, probably others as well.Notify maintainers
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.Add a :+1: reaction to issues you find important.