Skip to main content

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



------------------------------
Morten Hansen
IBM Danmark AS
------------------------------

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



------------------------------
Morten Hansen
IBM Danmark AS
------------------------------

I managed to fix the problem - since this post sent yesterday:

The error is regarding missing tagging of the libexec/git-core scripts distributed:
I have added "chtag -t -c iso8859-1 xxfilexx" to all scripts below and now "git submodule" works fine.
It seems the distributed git package contains this error.

So - I solved my problem - I will let you decide if the cicd git distribution needs an update.

/git/libexec/git-core$ ls -laT total 50048 drwxrwxr-- 2 EPLMOH SP64DS 8192 Oct 9 15:03 . drwxrwxr-- 3 EPLMOH SP64DS 8192 Oct 9 13:30 .. t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 49564 Oct 13 2023 git-add--interactive t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 38075 Oct 13 2023 git-archimport t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 8296 Oct 13 2023 git-bisect t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 14026 Oct 13 2023 git-cvsexportcommit t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 33196 Oct 13 2023 git-cvsimport t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 163808 Oct 13 2023 git-cvsserver t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 2242 Oct 13 2023 git-difftool--helper t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 16337 Oct 13 2023 git-filter-branch t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 22403 Oct 13 2023 git-instaweb t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 16407 Oct 13 2023 git-legacy-stash t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 2483 Oct 13 2023 git-merge-octopus t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 3701 Oct 13 2023 git-merge-one-file t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 950 Oct 13 2023 git-merge-resolve t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 10303 Oct 13 2023 git-mergetool t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 9201 Oct 13 2023 git-mergetool--lib t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 116 Oct 13 2023 git-p4 t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 2650 Oct 13 2023 git-parse-remote t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 3699 Oct 13 2023 git-quiltimport t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 29597 Oct 13 2023 git-rebase--preserve-merges t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 4127 Oct 13 2023 git-request-pull t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 59344 Oct 13 2023 git-send-email t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 2495 Oct 13 2023 git-sh-i18n t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 9302 Oct 13 2023 git-sh-setup t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 25975 Oct 13 2023 git-submodule t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 65582 Oct 13 2023 git-svn t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 4407 Oct 13 2023 git-web--browse


------------------------------
Morten Hansen
Advisory IT Specialist
IBM Danmark AS
Brøndby DK
------------------------------

I managed to fix the problem - since this post sent yesterday:

The error is regarding missing tagging of the libexec/git-core scripts distributed:
I have added "chtag -t -c iso8859-1 xxfilexx" to all scripts below and now "git submodule" works fine.
It seems the distributed git package contains this error.

So - I solved my problem - I will let you decide if the cicd git distribution needs an update.

/git/libexec/git-core$ ls -laT total 50048 drwxrwxr-- 2 EPLMOH SP64DS 8192 Oct 9 15:03 . drwxrwxr-- 3 EPLMOH SP64DS 8192 Oct 9 13:30 .. t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 49564 Oct 13 2023 git-add--interactive t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 38075 Oct 13 2023 git-archimport t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 8296 Oct 13 2023 git-bisect t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 14026 Oct 13 2023 git-cvsexportcommit t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 33196 Oct 13 2023 git-cvsimport t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 163808 Oct 13 2023 git-cvsserver t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 2242 Oct 13 2023 git-difftool--helper t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 16337 Oct 13 2023 git-filter-branch t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 22403 Oct 13 2023 git-instaweb t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 16407 Oct 13 2023 git-legacy-stash t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 2483 Oct 13 2023 git-merge-octopus t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 3701 Oct 13 2023 git-merge-one-file t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 950 Oct 13 2023 git-merge-resolve t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 10303 Oct 13 2023 git-mergetool t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 9201 Oct 13 2023 git-mergetool--lib t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 116 Oct 13 2023 git-p4 t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 2650 Oct 13 2023 git-parse-remote t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 3699 Oct 13 2023 git-quiltimport t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 29597 Oct 13 2023 git-rebase--preserve-merges t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 4127 Oct 13 2023 git-request-pull t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 59344 Oct 13 2023 git-send-email t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 2495 Oct 13 2023 git-sh-i18n t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 9302 Oct 13 2023 git-sh-setup t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 25975 Oct 13 2023 git-submodule t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 65582 Oct 13 2023 git-svn t ISO8859-1 T=on -rwxrwxr-- 1 EPLMOH SP64DS 4407 Oct 13 2023 git-web--browse


------------------------------
Morten Hansen
Advisory IT Specialist
IBM Danmark AS
Brøndby DK
------------------------------

Hi Morten,

I did not find this problem for either the git conda 
package or the SMPE installation of Rocket Open AppDev for Z.

Which version of the distribution are you using?

Thanks,
Alexander



------------------------------
Alexander Klochkov
QA
Rocket Internal - All Brands
Vilnius LT
------------------------------

Hi Morten,

I did not find this problem for either the git conda 
package or the SMPE installation of Rocket Open AppDev for Z.

Which version of the distribution are you using?

Thanks,
Alexander



------------------------------
Alexander Klochkov
QA
Rocket Internal - All Brands
Vilnius LT
------------------------------

Hi Alexander

thx for prompt reply. 
I am using v.2.26.2-82.
My local install was distributed via centralized IBM team from another site via tar file (I guess).
So I have not a local SMPE install here - and therefore I suspect the "missing" chtag's are in the distributed tar file somehow. At another local site we have found the same error. I have notified the IBM team about this......
Thx for checking - I guess its a local problem here then .... and its solved and looks fine now.

Thanks,
Morten 



------------------------------
Morten Hansen
Advisory IT Specialist
IBM Danmark AS
Brøndby DK
------------------------------

Hi Alexander

thx for prompt reply. 
I am using v.2.26.2-82.
My local install was distributed via centralized IBM team from another site via tar file (I guess).
So I have not a local SMPE install here - and therefore I suspect the "missing" chtag's are in the distributed tar file somehow. At another local site we have found the same error. I have notified the IBM team about this......
Thx for checking - I guess its a local problem here then .... and its solved and looks fine now.

Thanks,
Morten 



------------------------------
Morten Hansen
Advisory IT Specialist
IBM Danmark AS
Brøndby DK
------------------------------

final remark: I can see I added this question to wrong thread - it should have been a "Question".
It was my first post, so hope to make it correct next time....

Thanks,
Morten



------------------------------
Morten Hansen
Advisory IT Specialist
IBM Danmark AS
Brøndby DK
------------------------------