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
git: 2.16.2 -> 2.17.0 #38636
git: 2.16.2 -> 2.17.0 #38636
Conversation
Pinging @peti, @the-kenny and @wmertens as maintainers. I did my best to port the patches, but I cannot possibly (locally) compile the 500+ packages that depend on git. |
@GrahamcOfBorg build gitAndTools.git-annex |
No attempt on aarch64-linux (full log) The following builds were skipped because they don't evaluate on aarch64-linux: gitAndTools.git-annex Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: gitAndTools.git-annex Partial log (click to expand)
|
Success on x86_64-darwin (full log) Attempted: gitAndTools.git-annex Partial log (click to expand)
|
I think this broke a bunch of stuff.
|
@LnL7, it would be helpful to know how to reproduce that error. |
Sorry, was busy with other stuff. I ran into this with git init /tmp/foo
# Before
nix run -f https://github.com/NixOS/nixpkgs/archive/c78c7645478ba95f8c654ed79e63a6e7f715c82d.tar.gz git -c git -C /tmp/foo add -p
No changes.
# After
nix run -f https://github.com/NixOS/nixpkgs/archive/1cdcc19218a45f460d9e13bc930f271ed81b5fa7.tar.gz git -c git -C /tmp/foo add -p
Can't locate Git.pm in @INC (you may need to install the Git module) (@INC contains: /nix/store/nkcj1l3cbx3p0ahiy2cc7qbl5d8hqwky-git-2.17.0/lib/perl5/site_perl /nix/store/cfffjc7p8fs9psfbkjc4pcajz15vd367-perl-libwww-perl-6.15/lib/perl5/site_perl/5.24.3/darwin-2level /nix/store/cfffjc7p8fs9psfbkjc4pcajz15vd367-perl-libwww-perl-6.15/lib/perl5/site_perl/5.24.3 /nix/store/cfffjc7p8fs9psfbkjc4pcajz15vd367-perl-libwww-perl-6.15/lib/perl5/site_perl /nix/store/amxjz63msjakpy8x77flsv2d6gn5x67k-perl-URI-1.73/lib/perl5/site_perl/5.24.3/darwin-2level /nix/store/amxjz63msjakpy8x77flsv2d6gn5x67k-perl-URI-1.73/lib/perl5/site_perl/5.24.3 /nix/store/amxjz63msjakpy8x77flsv2d6gn5x67k-perl-URI-1.73/lib/perl5/site_perl /nix/store/bvhv30kdbr1kv82jmi0dq3ri7dxy3dp8-perl-TermReadKey-2.37/lib/perl5/site_perl/5.24.3/darwin-2level /nix/store/bvhv30kdbr1kv82jmi0dq3ri7dxy3dp8-perl-TermReadKey-2.37/lib/perl5/site_perl/5.24.3 /nix/store/bvhv30kdbr1kv82jmi0dq3ri7dxy3dp8-perl-TermReadKey-2.37/lib/perl5/site_perl /nix/store/5spv9lcjwyliipv0yqiv5g8vz0g93v8s-perl-5.24.3/lib/perl5/site_perl/5.24.3/darwin-2level /nix/store/5spv9lcjwyliipv0yqiv5g8vz0g93v8s-perl-5.24.3/lib/perl5/site_perl/5.24.3 /nix/store/5spv9lcjwyliipv0yqiv5g8vz0g93v8s-perl-5.24.3/lib/perl5/5.24.3/darwin-2level /nix/store/5spv9lcjwyliipv0yqiv5g8vz0g93v8s-perl-5.24.3/lib/perl5/5.24.3 .) at /nix/store/nkcj1l3cbx3p0ahiy2cc7qbl5d8hqwky-git-2.17.0/libexec/git-core/.git-add--interactive-wrapped line 7.
BEGIN failed--compilation aborted at /nix/store/nkcj1l3cbx3p0ahiy2cc7qbl5d8hqwky-git-2.17.0/libexec/git-core/.git-add--interactive-wrapped line 7. |
@layus, is there a quick and easy way to fix this issue? If not, we'll have to revert I suppose. |
Looked into this a little bit, the location of the perl libs has moved so the wrappers are not pointing to the right location.
|
Reverted in e4fd054. |
This reverts commit 5d65b4e, because it broke git-add. See #38636 (comment) for details.
Ok, Thanks @peti for reverting in the meantime. It worked on NixOS because of PERL5LIB var that was set, referencing the installed git. To reproduce, I had to call The issue is that git moved to a handwritten perl install, and moved the default install path in the meantime. I decided to install perl files to the old location ( @LnL7 I was able to reproduce your bug and fix it, but would you mind testing this again ? |
@dtzWill Now, how would you have avoided it ? I was indeed quite ashamed by this abysmal performance but could not find a perfect way to avoid it in the future. GitHub search really failed me here. "git 2.17" did not give anything meaningful. It turns out that "git 2.17.0" does. Even better would be to search for "git 2.17.0 in:title", but it gives about the same results. So this could be seen as my mistake, at least partially. We could write a bot to detect identical PRs. It should be quite simple, and entertaining. Another way to look at it could be to have better tests. I think people are afraid of them because they can discard a whole valid package compilation. This means we need more tests, and we need to make them independent from packages compilation. See the excellent talk from @Profpatsch at NixCon: "Test ALL the things" (youtube) (slides) /cc @Profpatsch because this could be seen as a good use-case or example. |
I'm not sure, sorry for any implications it was a failure on your part (specifically or otherwise). That said, this round got the issue more attention and some excellent investigation, so maybe it was for the best? 😁 Sounds like a bot would be best for detecting duplicate PR's, I certainly don't think you did anything wrong given your search query. Would this be a reasonable feature for @GrahamcOfBorg to grow? I agree tests would help here (catch the broken behavior). I believe I've seen that talk, but will look again to make sure and revisit its points :). |
Yes, the previous two PRs could have been transformed into tests preventing
the broken behavior.
…On Thu, Apr 12, 2018, 1:39 AM Will Dietz, ***@***.***> wrote:
@dtzWill <https://github.com/dtzWill> Now, how would you have avoided it
? I was indeed quite ashamed by this abysmal performance but could not find
a perfect way to avoid it in the future.
I'm not sure, sorry for any implications it was a failure on your part
(specifically or otherwise).
I was just frustrated, hopefully understandably so, that my mistake
(missing the perl problems) failed to prevent others from wasting time on
it, repeatedly. It seems like something that could be avoided, although as
you point out it's difficult to identify any particular point of failure.
That said, this round got the issue more attention and some excellent
investigation, so maybe it was for the best? 😁
------------------------------
Sounds like a bot would be best for detecting duplicate PR's, I certainly
don't think you did anything wrong given your search query. Would this be a
reasonable feature for @GrahamcOfBorg <https://github.com/GrahamcOfBorg>
to grow?
------------------------------
I agree tests would help here (catch the broken behavior). I believe I've
seen that talk, but will look again to make sure and revisit its points :).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#38636 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AADWlgkIxt5njm897oHBIkPVkOuNWWflks5tnpRGgaJpZM4TMHIk>
.
|
Yes, I had the same idea but did not dare write it here 😉. As a bonus, here is an ASCII art of our epic mess. See how the staging/master sync merges reverted "git: 2.16.2 -> 2.16.3" ? hash | git version | commit message * 281775bb1a0 2.16.3 git: 2.16.2 -> 2.16.3 | * 2ddba49f59c 2.17.0 git: fix perl libs path | * ad076ff7ce5 2.17.0 git: 2.16.3 -> 2.17.0 | * 260194193c3 2.16.3 git: 2.16.2 -> 2.16.3 |/ * ee6894ca129 2.16.2 Merge staging into master |\ | * 0aa59a08d65 2.17.0 Merge master into staging | |\ | * | 2bb28e1f019 2.16.3 Revert "git: 2.16.3 -> 2.17.0" | * | 3bd496faa88 2.17.0 git: 2.16.3 -> 2.17.0 | * | 2b29239eff3 2.16.3 Revert "git: 2.16.3 -> 2.17.0" | * | dee77f7e433 2.17.0 git: 2.16.3 -> 2.17.0 | * | dcaea58eb72 2.16.3 git: 2.16.2 -> 2.16.3 * | | e4fd05449ed 2.16.2 git: revert "2.16.2 -> 2.17.0" | |/ |/| * | 5d65b4ebeb6 2.17.0 git: 2.16.2 -> 2.17.0 |/ * b34274d3638 2.16.2 git: 2.16.1 -> 2.16.2 |
This is a security update, see [1]. It is not backported from master because master is at 2.17.x after NixOS#38636. [1] https://github.com/git/git/blob/master/Documentation/RelNotes/2.17.1.txt
It seems that git 2.17 is still broken on darwin:
|
Don't suppose 2.17.1 is any better? If not, we may want to disable the tests on Darwin, or at least that one. Wonder why it fails? :) |
2.17.1 is also failing on Darwin. However, git-scm provides only 2.17.0 for
macOS as a download binary
On 31. May 2018, at 12:55, Will Dietz <notifications@github.com> wrote:
Don't suppose 2.17.1 is any better? If not, we may want to disable the
tests on Darwin, or at least that one. Wonder why it fails? :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#38636 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAJS-AcCi9GJV2rwRv_i8G2V8KMBJuyIks5t38wvgaJpZM4TMHIk>
.
|
I’ve got actually more failures with 2.17.1:
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/add-bin-bash-to-avoid-unnecessary-pain/5673/38 |
Also refreshed and fixed the patch queue.
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)