-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
home-assistant: 2024.6.4 -> 2024.7.0 #324398
Conversation
Result of 1 package blacklisted:
60 packages failed to build:
1158 packages built:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR should target staging
, not staging-next
.
I think hexa knows what he is doing in that case :) |
Result of 1 package blacklisted:
12 packages failed to build:
1206 packages built:
|
Just out of curiosity, can you explain why |
Result of 1 package blacklisted:
8 packages failed to build:
1210 packages built:
|
@Pandapip1 This PR would usually go to master because it's not an actual mass rebuild—the number of rebuilds is inflated by Home Assistant tests. But since a lot of Python updates were made recently that are currently only in staging-next, it makes more sense to base on that until staging-next is merged into master. |
1218 rebuilds, 825 of which are tests, leaving 393 actual packages. I sent you a message on Matrix fwiw. |
Makes sense. Thanks for the explanation! |
Description of changes
https://www.home-assistant.io/blog/2024/07/03/release-20247/
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.