Conversation
|
Not sure why nixpkgs-review is failing to build when nix-build directly on the package.nix worked as expected. Investigating now |
17.6.0 or 17.6.1? |
|
AFAIK there is no gitlab-runner 17.6.1 release, so 17.6.0 should be fine. |
|
Updated to version 17.6.0 |
|
|
|
@bkp5190 : Some strange test fails: on linux x86... do these passthru test work on your machine? |
Yes they do, the other run is attached from linux x86 |
|
@bkp5190 17.9.1 is out now with a few security fixes, so it would be good to get this PR updated to 17.9.1. If you don't have time, I'm happy to provide a diff? @leona-ya gitlab-runner is significantly out of date (we're on 17.2 from 2024-10-22, 4+ months) - it would be great if you could re-review this, so that this package can be updated, especially given recent runner security updates in 17.9.0/17.9.1. |
|
Last time I checked this was very broken on darwin :c I tried to fix it, but it needed like 5+ fixes. Maybe now it's right to first merge this and then fix on darwin.. |
|
I propose a switch to make as upstream does: leona-ya@9bb4e9b |
Yea a diff would be greatly appreciated! I have not looked at these changes in a while, thanks. |
@leona-ya Thank you! I think this change makes a lot of sense! do you think it would be best to open a new PR with those changes (I can take care of this)? perhaps if @bkp5190 has the spare time we could push that change to this branch and then update the title? either way, I definitely think using make and mirroring more closely the upstream build approach would be good for reducing nixpkgs maintainer burden |
|
I opened a PR with my changes + a few patches to fix build on aarch64-linux and darwin |
Changelog:
https://gitlab.com/gitlab-org/gitlab-runner/blob/v17.5.3/CHANGELOG.md
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-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.