Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

git-up failed #17

Closed
kecksk0enig opened this issue Sep 11, 2014 · 12 comments
Closed

git-up failed #17

kecksk0enig opened this issue Sep 11, 2014 · 12 comments

Comments

@kecksk0enig
Copy link

I Installed git-up as user

$ git-up
`git fetch` failed

Here's what git said:

fatal: No such remote or remote group: .

normal git fetch / git pull works as expected

@msiemens
Copy link
Owner

What version of PyGitUp are you using?

@kecksk0enig
Copy link
Author

sorry for the late reply
I did try with v 1.1.4 and today also with 1.1.4

Both did fail with above quoted errormessage

@msiemens
Copy link
Owner

Could you try reruning git-up with the environment variable GIT_PYTHON_TRACE set to full? (On Linux: GIT_PYTHON_TRACE=full git-up). And maybe also the list of git remotes (the result of git remote -v) and the git version you're running (git --version).

@kecksk0enig
Copy link
Author

Heres what git says

$ GIT_PYTHON_TRACE=full git-up
git config git-up.rebase.auto -> 1
git config git-up.rebase.log-hook -> 1
git config git-up.bundler.rbenv -> 1
git config git-up.bundler.check -> 1
git config git-up.bundler.autoinstall -> 1
git config git-up.updates.check -> 1
git config git-up.fetch.prune -> 1
git config git-up.bundler.local -> 1
git config git-up.fetch.all -> 1
git config git-up.rebase.arguments -> 1
git version -> 0; stdout: 'git version 1.7.9.5'
git fetch failed

Here's what git said:

fatal: No such remote or remote group: .

Am 26.11.2014 um 18:00 schrieb Markus Siemens:

Could you try reruning |git-up| with the environment variable
|GIT_PYTHON_TRACE=full|? (On Linux: |GIT_PYTHON_TRACE=full git-up|). And
maybe also the list of git remotes (the result of |git remote -v|) and
the git version you're running (|git --version|).


Reply to this email directly or view it on GitHub
#17 (comment).

@msiemens
Copy link
Owner

Somehow the command line of git fetch is not included. Could you rerun it with GIT_PYTHON_TRACE=1 instead of full? That should include it.

@kecksk0enig
Copy link
Author

$ GIT_PYTHON_TRACE=1 git-up
git status --porcelain --untracked-files=no
git config git-up.rebase.auto
git config git-up.rebase.log-hook
git config git-up.bundler.rbenv
git config git-up.bundler.check
git config git-up.bundler.autoinstall
git config git-up.updates.check
git config git-up.fetch.prune
git config git-up.bundler.local
git config git-up.fetch.all
git config git-up.rebase.arguments
git version
git fetch --multiple --prune origin .
git fetch failed

Here's what git said:

fatal: No such remote or remote group: .

@msiemens
Copy link
Owner

msiemens commented Dec 3, 2014

I've almost located the bug. Could you paste the result of calling git fetch --multiple --prune origin (without a dot at the end)?

@kecksk0enig
Copy link
Author

That seems to work:
$ git fetch --multiple --prune origin
Fetching origin
remote: Counting objects: 80, done.
remote: Compressing objects: 100% (29/29), done.
remote: Total 46 (delta 16), reused 0 (delta 0)
Unpacking objects: 100% (46/46), done.
From some.urle.com:project
2db346d..db50beb develop -> origin/develop
x deleted -> origin/blubbblah

@msiemens
Copy link
Owner

msiemens commented Dec 4, 2014

I think we're very close to fixing this.

  1. I've pushed a commit that should fix the bug. Can you confirm this? You'll need to clone the repository, check out the dev branch and install it via python setup.py install.
  2. From what I can see, your repository seems to have branches with both local tracking branches and remote tracking branches. Is that correct?

@kecksk0enig
Copy link
Author

both correct, now working 👍

@msiemens
Copy link
Owner

Great! I'll release an update within the next few days then.

@msiemens
Copy link
Owner

I've just released version v1.2.0 where the fix is included :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants