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 revisions ignored #78

Closed
vbabiy opened this issue Mar 15, 2011 · 4 comments
Closed

Git revisions ignored #78

vbabiy opened this issue Mar 15, 2011 · 4 comments
Labels
auto-locked Outdated issues that have been locked by automation type: bug A confirmed bug or unintended behavior

Comments

@vbabiy
Copy link
Contributor

vbabiy commented Mar 15, 2011

pip currently ignores git commit revisions (unless they are the full SHA1 of a branch or tag) which results in pip installing whatever git clone pulls down instead of checking out the specified revision.

I may have bungled my pull request, but I've fixed this issue in my fork => http://bitbucket.org/jsma/pip/changeset/9a7c74d5f403


@vbabiy
Copy link
Contributor Author

vbabiy commented Mar 15, 2011

In case pull requests are ignored, here are my notes from my request (patch
attached):

I've fixed an issue with the git backend. It was ignoring commit SHA1's and
always installing the tip of a package.

The main bug was that it would only do a checkout if rev_options != checked_rev
(http://bitbucket.org/ianb/pip/src/31ab9bbc9c7f/pip/vcs/git.py#cl-124).

The check_rev_options() method would always return the rev argument
unmodified if it wasn't the full SHA1 of a tag or branch. Partial SHA1's of
tags or branches would fail the if rev in revisions test, also returning
rev unmodified
(http://bitbucket.org/ianb/pip/src/31ab9bbc9c7f/pip/vcs/git.py#cl-87).
This meant it would never pass the inequality test.


Original Comment By: John-Scott Atlakson

@vbabiy
Copy link
Contributor Author

vbabiy commented Mar 15, 2011

Hi jsma, Your patch has been applied to my py2x fork. I hope it will be merged
soon. I added some other tests and saw you solved two issues :)

Thanks!


Original Comment By: Hugo Lopes Tavares

@vbabiy
Copy link
Contributor Author

vbabiy commented Mar 15, 2011

Issue #155 was marked as a duplicate of this issue.

-revision-is


Original Comment By: Hugo Lopes Tavares

@vbabiy
Copy link
Contributor Author

vbabiy commented Mar 15, 2011

  • Changed status from open to resolved.

Original Comment By: Hugo Lopes Tavares

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 6, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2019
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation type: bug A confirmed bug or unintended behavior
Projects
None yet
Development

No branches or pull requests

1 participant