I have previously used Endeavour os with dwm and had little to no problems with it. I was using someone elses bootstrap script to set up the basic features of the system and I decided recently that I would do it myself from scratch.
I am however experiencing problems with a script has to call git clone. It seems like it just gets stuck and doesn’t actually clone or do anything. The program in particular is the doom emacs install script. I have tried many things but cannot figure out what is going on. I have internet access, I can go on github.com, I can clone repos by myself ( occasionally this fails and I have to re-initiate). I have tried other scripts as well and the problem still persists, leading me to believe it is my system.
Any ideas on what to do? let me know and I will provide any additional details. I am on a clean endeavour os build without a desktop, with dwm installed and alacritty as my terminal.
I have moved the topic to applications since it is a related bug on either git clone or the specific script and not a bug on the ISO or the EndeavourOS apps.
Yes i have taken this into account an moved .emacs.d out of the way before cloning. In fact the initial clone works normally most of the times. I just installed ubuntu out of curiosity to see if it would work and it still didn’t. It seems to be a problem when a script calls git clone or tries to clone something from a repo. Its think it might have to do with the speed, it might be downloading so slow that it fails. However if i go on speedtest.net or download a file directly from a browser my speed is upwards of 500 mbps so it should not have any problems regarding speed. I have tried updating the arch mirrorlist as well and this did not help anything.
Ok I deleted .emac.d again and the initial clone has stopped working . I am stuck at Cloning into “/home/user/.emacs.d” ill wait to see if there is an error message.
Troubleshooting that is more of a network troubleshooting process than a system troubleshooting process. Could be your router/firewall config or something your ISP is doing.
As a workaround, you could always just download the zip and unpack it to the proper directory.