Open-source Languages & Tools for z/OS

 View Only

 Use of "git submodule" on z/OS fails - returns: fatal - Maybe git-submodule is broken?

Morten Hansen's profile image
Morten Hansen posted 10-09-2024 05:08

I have git v.2.26.2-82 installed on uss, and it works fine until now for "usual" git commands like git clone, branch, commit, merge etc.

I now
try "git submodule" for the first time and it returns this error :
(my userid is EPLMOH)
bash EPLMOH@MVSS:~/work/DSC$ git submodule status
fatal: 'submodule' appears to be a git command, but we were not able to execute it. Maybe git-submodule is broken?

I have this $PATH:
/bin:
/usr/lpp/java/J8.0_64/bin:
/usr/lpp/ported/python/bin:
/bin: /usr/lpp/java2140/J1.4/bin:
/usr/lpp/Printsrv/bin:
/usr/lpp/Tivoli/tsm/client/ba/bin/:
/usr/lpp/wmqi/bin/:
/usr/lpp/lotus/bin:
/usr/lpp/lotus/bin/tools:
/local/eposd/notesdata:
/usr/local/bin:
.:
/_PRDS/ZOAUTIL/SBGYZFS/bin:
/u/eplmoh:
/usr/lpp:
/usr/lpp/IBM/MVSS/UssTools/git/usr/lpp/Rocket/rsusr/ported/bin/: <---- git
/usr/lpp/IBM/MVSS/UssTools/git/usr/lpp/Rocket/rsusr/ported/libexec/git-core: <---- git
/usr/lpp/ported/apache-ant/bin:
/usr/lpp/ported/autoconf/bin:
/usr/lpp/ported/automake/bin:

Actual path to git via "type -p" - so I am using the correct one
bash EPLMOH@MVSS:~/work$ type -p git
/usr/lpp/IBM/MVSS/UssTools/git/usr/lpp/Rocket/rsusr/ported/bin/git

It looks like all git modules in the git package  that are "real" modules - do not work. And all symbolic links are actually functioning....
bash EPLMOH@MVSS:/usr/lpp/IBM/MVSS/UssTools/git/usr/lpp/Rocket/rsusr/ported/libexec/git-core$ ls -laT total 739824 drwxr-xr-x 3 BPXROOT OMVS 8192 Oct 13 2023 . drwxr-xr-x 3 BPXROOT OMVS 8192 Oct 13 2023 .. - untagged T=off -rwxr-xr-x 1 BPXROOT OMVS 24825856 Oct 13 2023 git lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-add -> git - untagged T=off -rwxr-xr-x 1 BPXROOT OMVS 49564 Oct 13 2023 git-add--interactive lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-am -> git lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-annotate -> git lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-apply -> git - untagged T=off -rwxr-xr-x 1 BPXROOT OMVS 38075 Oct 13 2023 git-archimport lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-archive -> git - untagged T=off -rwxr-xr-x 1 BPXROOT OMVS 8296 Oct 13 2023 git-bisect <------------- not ok lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-bisect--helper -> git lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-blame -> git lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-branch -> git lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-bundle -> git lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-cat-file -> git lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-check-attr -> git - untagged T=off -rwxr-xr-x 1 BPXROOT OMVS 25975 Oct 13 2023 git-submodule <------------ not ok lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-submodule--helper -> git - untagged T=off -rwxr-xr-x 1 BPXROOT OMVS 65582 Oct 13 2023 git-svn lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-switch -> git lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-symbolic-ref -> git lrwxrwxrwx 1 10546 OMVS 3 Oct 13 2023 git-tag -> git <------------ ok

eks:
bash EPLMOH@MVSS:/usr/lpp/IBM/MVSS/UssTools/git/usr/lpp/Rocket/rsusr/ported/libexec/git-core$ git bisect <------------ works not fatal: 'bisect' appears to be a git command, but we were not able to execute it. Maybe git-bisect is broken? bash EPLMOH@MVSS:~/work/DSC$ git tag <-------------- works fine error: cannot run less: EDC5129I No such file or directory. bash EPLMOH@MVSS:~/work/DSC$


My question is:
as file git-submodule contains a bash shell script - should this file and other ones be -untagged ?
Or should they be tagged with "chtag -t -c iso8859-1 ..file" ?
and is this file tagging included in the ported Rocket install procedure so that it is not completed somehow ?

TIA, Morten