-
Notifications
You must be signed in to change notification settings - Fork 44
Closed
Description
I updated to v1.1.0 via
pip install --user -U git-up
and just tried it out in my repo. I got the following:
Traceback (most recent call last):
File "/home/mu/.local/bin/git-up", line 9, in <module>
load_entry_point('git-up==1.1.0', 'console_scripts', 'git-up')()
File "/home/mu/.local/bin/gitup.py", line 552, in run
gitup = GitUp()
File "/home/mu/.local/bin/gitup.py", line 110, in __init__
self.load_config()
File "/home/mu/.local/bin/gitup.py", line 408, in load_config
value = self.config(key)
File "/home/mu/.local/bin/gitup.py", line 423, in config
return self.git.config('git-up.{0}'.format(key))
AttributeError: 'GitUp' object has no attribute 'git'
Am I missing a dependency or so?
Activity
msiemens commentedon Oct 7, 2013
Strange, I've tested it and it worked. Gonna investigate right now.
Hotfix for a stupid error 💥 (closes #7)
msiemens commentedon Oct 7, 2013
Please try re-installing
git-up
. If pip doesn't want to, please report here and I'll release the fix as a new version (now I've just updated v1.1.0)martin-ueding commentedon Oct 7, 2013
pip does not update since it has the current version. A new version would probably be easier.
msiemens commentedon Oct 7, 2013
Okay, new version should be released in some minutes.
msiemens commentedon Oct 7, 2013
So, v1.1.1 is released. I hope, all problems are fixed, finally.
martin-ueding commentedon Oct 7, 2013
Okay, I did
pip install --user -U git-up
, it updated, butgit-up --version
gives me:In the
/home/mu/.local/bin/git-up
, I see a reference to 1.1.0, is that correct?msiemens commentedon Oct 7, 2013
No, there is still something messed up. I updated using the same command and got
GitUp version is: v1.1.1
. What is the output ofpip install --user -U git-up
? In addition, what doespip show git-up
say?martin-ueding commentedon Oct 7, 2013
Output of
mu:~ pip install --user -U git-up
:Output of
pip show git-up
:msiemens commentedon Oct 7, 2013
Seems like you're using an old version of pip. Older versions of pip are known for funky behaviour when trying to upgrade packages (see #4 a similar problem). Could you try removing pip's build dir (
/tmp/pip-build-*
,~/.pip
,~/tmp/pip-build-*
) and then re-run the install-command?martin-ueding commentedon Oct 7, 2013
I rebooted the computer, and tried it again. It works now, and
git up
works for my project without any remotes. Thank you for your work!
http://martin-ueding.de/#pk_campaign=Email
msiemens commentedon Oct 7, 2013
No problem, you're welcome :)