Skip to content
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.19.2 -> 2.20.1 #52575

Closed
wants to merge 3 commits into from
Closed

Conversation

dtzWill
Copy link
Member

@dtzWill dtzWill commented Dec 20, 2018

https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.20.1.txt
https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.20.0.txt

Motivation for this change

Commits can (should?) be squashed, but wanted to show the path taken
and be sure to draw attention to the git-sh-i18n bits.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

Not sure what the i18n patch is for,
dropping it for now since tests pass w/o it.

Tests pass, woo :).
gettext-posion test fails, bah.

Snippet:

```
t0205-gettext-poison.sh ............................
not ok 1 - sanity: $GIT_INTERNAL_GETTEXT_SH_SCHEME" is poison
not ok 2 - gettext: our gettext() fallback has poison semantics
not ok 3 - eval_gettext: our eval_gettext() fallback has poison semantics
Dubious, test returned 1 (wstat 256, 0x100)
Failed 3/3 subtests
```
@rht
Copy link
Member

rht commented Dec 23, 2018

I made an upgrade to an older version (2.20.0, #51806), encountered 2 test errors,

  1. t0205-gettext-poison.sh
  2. t5801-remote-helpers.sh

@dtzWill did all the tests pass on your machine?

@dtzWill
Copy link
Member Author

dtzWill commented Dec 23, 2018

Yep, they pass for borg too it appears?

@dtzWill
Copy link
Member Author

dtzWill commented Dec 23, 2018

  • helpers: see adjusted patch
  • gettext-poison: see commits re:git-sh-i18n: it seems to work if we leave it alone, including updating patch to apply-- I'm unclear what this was ever intended to accomplish so perhaps there are use cases impacted by this not caught by git's tests (perhaps NixOS-specific?).

@rht rht mentioned this pull request Dec 23, 2018
10 tasks
@rht
Copy link
Member

rht commented Dec 23, 2018

From git-archaeology, this is the cause of the gettext patch being added: #13047.

@dtzWill
Copy link
Member Author

dtzWill commented Dec 29, 2018

Hmm, can't reproduce? But not sure I understand the problem -- the example git commands are all referencing invalid upstreams/revisions, yes?

Anyone want to weigh in, or is this good to go?

@rht
Copy link
Member

rht commented Dec 29, 2018

One fix that I have thought of is to modify the gettext patch so that it points to '${gettext}' when not in test environment, but leave the script to search from $PATH when it is in test environment.

@dtzWill
Copy link
Member Author

dtzWill commented Feb 25, 2019

2.21.0 is out, updating to it is just the normal version/hash bump on top of this.

@nixos-discourse
Copy link

This pull request has been mentioned on Nix community. There might be relevant details there:

https://discourse.nixos.org/t/nixos-19-03-feature-freeze/1950/37

@dtzWill
Copy link
Member Author

dtzWill commented Feb 25, 2019

dtzWill@94d5f77 for example.

@@ -42,7 +42,7 @@ stdenv.mkDerivation {

patches = [
./docbook2texi.patch
./git-sh-i18n.patch
#./git-sh-i18n.patch
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this line (and the patch) be removed instead?

@rht
Copy link
Member

rht commented Feb 25, 2019

cc: @zimbatm for the gettext patch.

@dtzWill
Copy link
Member Author

dtzWill commented Feb 26, 2019

Looks like someone tackled the i18n patch properly, closing in favor of that PR: #56376 .

@dtzWill dtzWill closed this Feb 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants