-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Update nix pin with make nixpkgs
#4630
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
Conversation
|
Hi @hswong3i. Thanks for your PR. I'm waiting for a cri-o member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: hswong3i The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Codecov Report
@@ Coverage Diff @@
## master #4630 +/- ##
=======================================
Coverage 43.80% 43.80%
=======================================
Files 109 109
Lines 11358 11358
=======================================
Hits 4975 4975
Misses 5909 5909
Partials 474 474 |
|
Looks like systemd minimal did not build for arm: |
bb4a9eb to
0a93252
Compare
0a93252 to
0161bf2
Compare
0161bf2 to
90d29cd
Compare
8eb090d to
ac4deb3
Compare
@saschagrunert pinning with branch |
Isn't it already on the 20.09 channel? |
ac4deb3 to
6c286fe
Compare
6c286fe to
0cc435c
Compare
0cc435c to
b814ea9
Compare
Original rev goes to branch New rev goes to branch |
|
LGTM |
|
LGTM |
|
We cannot merge this one because the static build still fails: |
x86_64-linux is totally fine for my local build, where aarch64-linux support seems introduced by 4ff8662, would you mind to fix it onward? |
|
We ship those arm binaries continuously, so we have to find out what in nixpkgs was breaking the build and fix it there before bumping them here. :) |
May you give a try with remove gitMinimal? Seems Perl is being triggered by that. Sorry I didn’t use aarch64-linux so couldn’t comment too much for that :-( |
Can you remove the dependency from this PR? I think we fixed that git dependency issue a while ago. |
|
@saschagrunert I had tried for multiple methods:
My key founding from here are:
IMHO:
|
772d34e to
aa72a8a
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: hswong3i The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
ec8518d to
80cf89d
Compare
eaaec76 to
3daf32b
Compare
|
This patch might bring us further: diff --git a/nix/default-arm64.nix b/nix/default-arm64.nix
index a75d94921..f3a427acd 100644
--- a/nix/default-arm64.nix
+++ b/nix/default-arm64.nix
@@ -30,8 +30,10 @@ let
"--enable-confdir=/etc"
"--enable-usbdropdir=/var/lib/pcsc/drivers"
"--disable-libsystemd"
+ "--disable-libudev"
+ "--disable-libusb"
];
- buildInputs = [ pkgs.python3 pkgs.udev pkgs.dbus pkgs.systemd ];
+ buildInputs = [ pkgs.python3 pkgs.dbus ];
});
systemd = (static pkg.systemd).overrideAttrs (x: {
outputs = [ "out" "dev" ]; |
3daf32b to
32a8e80
Compare
@saschagrunert much better now, dependencies build successfully, just some local error? |
|
That's not good, it means that we did not build pkg-config for the correct architecture: |
45e8197 to
c6c5de4
Compare
- Bugfix `make nixpkgs` which pin with branch `nixos-21.05` - Code lint with `nixpkgs-fmt` - Code sync between x86\_64 and aarch64 Signed-off-by: Wong Hoi Sing Edison <[email protected]>
c6c5de4 to
7246ba1
Compare
What type of PR is this?
What this PR does / why we need it:
make nixpkgswhich pin with branchnixos-21.05nixpkgs-fmtWhich issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?