Can't clone a repo - linux


#1

I’m having problems simply cloning a repo on a fresh install of 1.23.3 on Gentoo linux 4.18.0-rc6.

  1. ‘Alt-g =’
  2. Clone From: https://github.com/cockytrumpet/openrazer.git
    To directory: /home/adam/github/openrazer

unable

git-shell-out-strategy.js:256 git:git -c color.ui=false -c color.status=false -c color.showBranch=false -c color.diff=false -c color.branch=false rev-parse --resolve-git-dir /home/adam/github/openrazer/.git in /home/adam/github/openrazer
git-shell-out-strategy.js:257 exit status 128
git-shell-out-strategy.js:258 stdout
git-shell-out-strategy.js:259
git-shell-out-strategy.js:260 stderr
git-shell-out-strategy.js:261 15:39:20.636555 git.c:344 trace: built-in: git ‘rev-parse’ ‘–resolve-git-dir’ ‘/home/adam/github/openrazer/.git’
fatal: not a gitdir ‘/home/adam/github/openrazer/.git’

If I git init in that directory and try again, I get

This directory already contains a git repository.

I feel like I’m missing something obvious here.


#2

Delete the .git/ folder and try again. If it doesn’t work, delete the folder a second time, open a terminal in ~/github/ and try git clone https://github.com/cockytrumpet/openrazer.git. If that works, we’ll know for sure that the problem is with Atom.


#3

After erroring, Atom leaves behind an empty ~/github/openrazer directory. Cloning from the command line worked fine.


#4

Are you sure that you’re looking with hidden files enabled? Your file manager might hide dotfiles, and ls won’t show them unless you use ls -a.


#5

Yep, I just reproduced it again to be sure.

total 8
drwxr-xr-x 2 adam adam 4096 Aug 2 20:45 .
drwxr-xr-x 3 adam adam 4096 Aug 2 20:45 …


#6

If I clone from the command line, then try to work with the project in Atom I have other git issues. I made a change and staged it. Trying to commit gave me

commit

event-logger.js:99 workspace watcher @ .git: focus triggered
git-shell-out-strategy.js:256 git:git -c color.ui=false -c color.status=false -c color.showBranch=false -c color.diff=false -c color.branch=false status --porcelain=v2 --branch --untracked-files=all --ignore-submodules=dirty -z in /home/adam/github/openrazer
git-shell-out-strategy.js:256 git:git -c color.ui=false -c color.status=false -c color.showBranch=false -c color.diff=false -c color.branch=false diff --no-prefix --no-renames --diff-filter=u --staged – README.md in /home/adam/github/openrazer
git-shell-out-strategy.js:256 git:git -c color.ui=false -c color.status=false -c color.showBranch=false -c color.diff=false -c color.branch=false diff --no-prefix --no-renames --diff-filter=u --staged – README.md in /home/adam/github/openrazer
git-shell-out-strategy.js:257 exit status 0
git-shell-out-strategy.js:258 stdout
git-shell-out-strategy.js:259 diff --git README.md README.md
index 295a55e…a36d33a 100644
— README.md
+++ README.md
@@ -41,6 +41,7 @@ The below devices are fully feature supported by OpenRazer which means all avail
| Razer Blade Pro FullHD (2017) | 1532:022F |
| Razer Blade Stealth (Late 2017) | 1532:0232 |
| Razer Blade 15 (2018) | 1532:0233 |
+| :slight_smile:

Mice

| Device | USB VID:PID |

git-shell-out-strategy.js:260 stderr
git-shell-out-strategy.js:261 21:14:28.288966 git.c:344 trace: built-in: git ‘diff’ ‘–no-prefix’ ‘–no-renames’ ‘–diff-filter=u’ ‘–staged’ ‘–’ ‘README.md’

git-shell-out-strategy.js:256 git:git -c color.ui=false -c color.status=false -c color.showBranch=false -c color.diff=false -c color.branch=false log --pretty=%H%x00%B%x00 --no-abbrev-commit -1 HEAD – in /home/adam/github/openrazer
git-shell-out-strategy.js:257 exit status 0
git-shell-out-strategy.js:258 stdout
git-shell-out-strategy.js:259 17402b4d988f48b5fb8f9b2e55e470e219b0a4daAdd keymapping for RB15
Update README.md to support RB15

git-shell-out-strategy.js:260 stderr
git-shell-out-strategy.js:261 21:14:28.282568 git.c:344 trace: built-in: git ‘log’ ‘–pretty=%H%x00%B%x00’ ‘–no-abbrev-commit’ ‘-1’ ‘HEAD’ ‘–’

git-shell-out-strategy.js:256 git:git -c color.ui=false -c color.status=false -c color.showBranch=false -c color.diff=false -c color.branch=false status --porcelain=v2 --branch --untracked-files=all --ignore-submodules=dirty -z in /home/adam/github/openrazer
git-shell-out-strategy.js:257 exit status 0
git-shell-out-strategy.js:258 stdout
git-shell-out-strategy.js:259 # branch.oid 17402b4d988f48b5fb8f9b2e55e470e219b0a4da# branch.head master# branch.upstream origin/master# branch.ab +0 -01 M. N… 100644 100644 100644 295a55ea4dd8f14f72917681b78c48f1f95b4180 a36d33ae229e3b24110b2756717a3c44eef7527e README.md
git-shell-out-strategy.js:260 stderr
git-shell-out-strategy.js:261 21:14:28.270899 git.c:344 trace: built-in: git ‘status’ ‘–porcelain=v2’ ‘–branch’ ‘–untracked-files=all’ ‘–ignore-submodules=dirty’ ‘-z’


#7

Someone who uses Linux more might have some insight. These errors are things I’ve never seen.


#8

Don’t think I’ve seen this before - one thing I did notice in your initial description:

on a fresh install of 1.23.3 on Gentoo linux 4.18.0-rc6.

The latest release version of Atom is 1.29, is it possible to install that on Gentoo? Also how are you installing Atom on Gentoo?


#9

echo “app-editors/atom ~amd64” > /etc/portage/package.accept_keywords/atom && emerge -va atom

I was using what was available in the portage tree. I also tried using a more up-to-date ebuild from an overlay (1.27.2) but had the same issues.

I chose to abondon the convenience of portage keeping atom up to date for me and built if from source. 1.31.0-dev-3e97867f3 seems great so far!