git submodule doesn't work in pure environment with ad-hoc git

  • Open
  • quality assurance status badge
Details
2 participants
  • Danny Milosavljevic
  • Maxim Cournoyer
Owner
unassigned
Submitted by
Danny Milosavljevic
Severity
normal
D
D
Danny Milosavljevic wrote on 3 Jan 2020 01:44
(address . bug-guix@gnu.org)
20200103014455.319781fd@scratchpost.org
/gnu/store/kyva0irr3khr01rs3v16nd5g4bzcgc95-git-2.24.1/libexec/git-core/.git-submodule-real: line 7: basename: command not found
/gnu/store/kyva0irr3khr01rs3v16nd5g4bzcgc95-git-2.24.1/libexec/git-core/.git-submodule-real: line 7: sed: command not found
/gnu/store/ah5pin2kr96c3fidjy39hzsy99riqi6s-profile/libexec/git-core/git-sh-setup: line 86: basename: command not found
/gnu/store/ah5pin2kr96c3fidjy39hzsy99riqi6s-profile/libexec/git-core/git-sh-setup: line 86: sed: command not found
/gnu/store/ah5pin2kr96c3fidjy39hzsy99riqi6s-profile/libexec/git-core/git-sh-setup: line 333: uname: command not found
/gnu/store/kyva0irr3khr01rs3v16nd5g4bzcgc95-git-2.24.1/libexec/git-core/.git-submodule-real: line 1121: sed: command not found
/gnu/store/kyva0irr3khr01rs3v16nd5g4bzcgc95-git-2.24.1/libexec/git-core/.git-submodule-real: line 1121: cmd_: command not found

It might make sense to refer to basename, sed and uname by direct store path.
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl4OjocACgkQ5xo1VCww
uqWiWQf/dVinN+zEb31B4sidX6Q8zx2u9xXWTJVCPwGAGFUw9L6lCM/K6nnnXn6Y
Iu1t7tRxBREpNJ0G1Sm3uvNA7ij1g69RtZCm5ngb32JdXCfE+scL70ed6Jt7VhuH
WQyTe+UcugRNJKYw0Lb9PZIFOzRP2mqxwMcdEYuLJ5So2XrggO0rTEcMIpSw+lRM
TZPTE1HCUpU7d9ujRFiIq6Ee03kFuQNc7Y39G4jrcCJEbDvtpugukArszlhrbvCN
m0M826DTpzNr7TNKt6gTe1+hO+0so47XpIfSjTvssc+fx/BRn4IMa2njI2KuUOaE
KRv0kbfQfvCD9QnsIIPIbn5kgG+q9Q==
=+WIc
-----END PGP SIGNATURE-----


M
M
Maxim Cournoyer wrote on 13 Jul 2022 15:51
(name . Danny Milosavljevic)(address . dannym@scratchpost.org)(address . 38883@debbugs.gnu.org)
87k08h15pj.fsf@gmail.com
Hi,

Danny Milosavljevic <dannym@scratchpost.org> writes:

Toggle quote (17 lines)
> /gnu/store/kyva0irr3khr01rs3v16nd5g4bzcgc95-git-2.24.1/libexec/git-core/.git-submodule-real:
> line 7: basename: command not found
> /gnu/store/kyva0irr3khr01rs3v16nd5g4bzcgc95-git-2.24.1/libexec/git-core/.git-submodule-real:
> line 7: sed: command not found
> /gnu/store/ah5pin2kr96c3fidjy39hzsy99riqi6s-profile/libexec/git-core/git-sh-setup:
> line 86: basename: command not found
> /gnu/store/ah5pin2kr96c3fidjy39hzsy99riqi6s-profile/libexec/git-core/git-sh-setup:
> line 86: sed: command not found
> /gnu/store/ah5pin2kr96c3fidjy39hzsy99riqi6s-profile/libexec/git-core/git-sh-setup:
> line 333: uname: command not found
> /gnu/store/kyva0irr3khr01rs3v16nd5g4bzcgc95-git-2.24.1/libexec/git-core/.git-submodule-real:
> line 1121: sed: command not found
> /gnu/store/kyva0irr3khr01rs3v16nd5g4bzcgc95-git-2.24.1/libexec/git-core/.git-submodule-real:
> line 1121: cmd_: command not found
>
> It might make sense to refer to basename, sed and uname by direct store path.

I just checked, and this is still reproducible:

Toggle snippet (10 lines)
~/src/jami-project [env]$ git submodule update
/gnu/store/0fnkx82byvr4l5h6cqvvy6667c8hyba2-git-2.36.1/libexec/git-core/.git-submodule-real: line 7: basename: command not found
/gnu/store/0fnkx82byvr4l5h6cqvvy6667c8hyba2-git-2.36.1/libexec/git-core/.git-submodule-real: line 7: sed: command not found
/gnu/store/m7ng7k4b0x5nw78r8g73xv3h6cindiwm-profile/libexec/git-core/git-sh-setup: line 86: basename: command not found
/gnu/store/m7ng7k4b0x5nw78r8g73xv3h6cindiwm-profile/libexec/git-core/git-sh-setup: line 86: sed: command not found
/gnu/store/m7ng7k4b0x5nw78r8g73xv3h6cindiwm-profile/libexec/git-core/git-sh-setup: line 308: uname: command not found
/gnu/store/0fnkx82byvr4l5h6cqvvy6667c8hyba2-git-2.36.1/libexec/git-core/.git-submodule-real: line 637: sed: command not found
/gnu/store/0fnkx82byvr4l5h6cqvvy6667c8hyba2-git-2.36.1/libexec/git-core/.git-submodule-real: line 637: cmd_: command not found

Thanks,

Maxim
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 38883@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 38883
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch