Skip to main content

Git pull codepage problem using example git env w/ bash installed

  • October 24, 2016
  • 3 replies
  • 1 view
A
  • Anonymous

Thanks for the great work on the port! Minor issue below.

In the example env, the bash prereq is appended not preptended to your path. On our systems, we have a globally installed bash in our paths.

It looks like $GIT_SHELL is not used when you do a simple “git pull”.

The result for me was a failure to do a simple “git pull” after cloning a repository, because my global bash was used and it choked on the ascii “.git” returned here:

git pull
/u/WASTST1/opt/libexec/git-core/git-sh-setup: line 342: cd: ��Ȏ: EDC5129I No such file or directory.
Unable to determine absolute path of git directory

I flipped the order of the PATH update in the git environment variable script and things worked fine, but ideally those the prereqs would not have to be in my interactive PATH.

    3 replies

    A
    • Anonymous
    • 0 replies
    • October 24, 2016

    Thanks for the great work on the port! Minor issue below.

    In the example env, the bash prereq is appended not preptended to your path. On our systems, we have a globally installed bash in our paths.

    It looks like $GIT_SHELL is not used when you do a simple “git pull”.

    The result for me was a failure to do a simple “git pull” after cloning a repository, because my global bash was used and it choked on the ascii “.git” returned here:

    git pull
    /u/WASTST1/opt/libexec/git-core/git-sh-setup: line 342: cd: ��Ȏ: EDC5129I No such file or directory.
    Unable to determine absolute path of git directory

    I flipped the order of the PATH update in the git environment variable script and things worked fine, but ideally those the prereqs would not have to be in my interactive PATH.

    I don’t understand the comment, “In the example env, the bash prereq is appended not pretended to your path.”.

    The release note indicates that the specific prereq versions of bash and perl must be installed into the same directory as the git installation directory, and then that directory prepended to PATH. This will put the prereq version of bash on your path. Am I missing something?

    Regarding GIT_SHELL: I’m not sure what that’s actually used for. I’ll have to check with the primary developer and get back to you.

    We plan to iron out some of these issues over time, but it’s a fairly complex problem. The goal is to have a complete set of open source tools that fully implement enhanced ASCII support, so that users can always run with _BPXK_AUTOCVT=ON and work seamlessly in a mixed ASCII/EBCDIC environment. For many tools this is straightforward, but there are often complications when tools pipe their output to other tools (which happens a lot with git, both internally and when used in scripts).

    The way I currently tend to work with git is to have a separate shell running that I use for git commands, and do all my other work in shells that do not have git and its prereqs on PATH. This can be done either with multiple login windows or (as I do) with multiple shell buffers in emacs.

    A
    • Anonymous
    • 0 replies
    • October 24, 2016

    Thanks for the great work on the port! Minor issue below.

    In the example env, the bash prereq is appended not preptended to your path. On our systems, we have a globally installed bash in our paths.

    It looks like $GIT_SHELL is not used when you do a simple “git pull”.

    The result for me was a failure to do a simple “git pull” after cloning a repository, because my global bash was used and it choked on the ascii “.git” returned here:

    git pull
    /u/WASTST1/opt/libexec/git-core/git-sh-setup: line 342: cd: ��Ȏ: EDC5129I No such file or directory.
    Unable to determine absolute path of git directory

    I flipped the order of the PATH update in the git environment variable script and things worked fine, but ideally those the prereqs would not have to be in my interactive PATH.

    I see my issue now. the README.ZOS and the release notes PDF differ with respect to how the PATH is modified. I started with the REDME.ZOS based example for my environment setup.

    A
    • Anonymous
    • 0 replies
    • October 25, 2016

    Thanks for the great work on the port! Minor issue below.

    In the example env, the bash prereq is appended not preptended to your path. On our systems, we have a globally installed bash in our paths.

    It looks like $GIT_SHELL is not used when you do a simple “git pull”.

    The result for me was a failure to do a simple “git pull” after cloning a repository, because my global bash was used and it choked on the ascii “.git” returned here:

    git pull
    /u/WASTST1/opt/libexec/git-core/git-sh-setup: line 342: cd: ��Ȏ: EDC5129I No such file or directory.
    Unable to determine absolute path of git directory

    I flipped the order of the PATH update in the git environment variable script and things worked fine, but ideally those the prereqs would not have to be in my interactive PATH.

    I was able to get our distro of apache http server w/ bundled PCRE, lua, expat, and pcre building on z/OS with the beta and able to commit as well. Great work!

    My .gitattributes when it was all said and done:

    # src, scripts
    *.c working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    *.h working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    *.sh working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    *.pl working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    *.mak working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    *.awk working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    .mk working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    Makefile working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    Makefile.     working-tree-encoding=ibm-1047 git-encoding=iso8859-1

    # autotools
    *.in working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    *.ac working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    configure working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    *.m4 working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    config.sub working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    config.guess working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    depcomp working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    *-sh working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    .layout working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    buildconf working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    build/     working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    PrintPath working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    mkinstalldirs working-tree-encoding=ibm-1047 git-encoding=iso8859-1

    # IHS-isms
    *.c.z working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    .h.z working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    apbase/     working-tree-encoding=ibm-1047 git-encoding=iso8859-1
    mime.types working-tree-encoding=ibm-1047 git-encoding=iso8859-1


    Terms & ConditionsAccessibility statement