Skip to content

/ gitdb

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

Jump to bottom

No README.md and no hint athat this replaces gitdb #57

Closed
nkadel opened this issue Feb 17, 2020 · 4 comments
Closed

No README.md and no hint athat this replaces gitdb #57

nkadel opened this issue Feb 17, 2020 · 4 comments
Labels
acknowledged

Comments

@nkadel
Copy link

@nkadel nkadel commented Feb 17, 2020

Updating the gitdb module is understandable, but changing the package name to "gitdb2" while actually installing modules named "gitdb" is confusing. Doing so without any hint that this module overhaps deployments of gitdb is dangerous: this showed up when I was trying to RPM building this software for AWX deployment and saw the conflicts.
@Harmon758
Copy link
Member

@Harmon758 Harmon758 commented Feb 17, 2020

A request to recover the PyPI account that owns gitdb has been made recently.
If the account is successfully recovered, I'd like to transition back to using the original gitdb package name and have gitdb2 simply be a mirror package.
Otherwise, if the request fails, I'll update the documentation accordingly.
@nkadel
Copy link
Author

@nkadel nkadel commented Feb 18, 2020

Good thanks! It confused me quite a lot when I was trying to RPM package it for the awx dependency.
@Harmon758 Harmon758 mentioned this issue Feb 23, 2020
Closed
12 of 12 tasks complete
@Harmon758
Copy link
Member

@Harmon758 Harmon758 commented Feb 23, 2020

This should now be resolved with the changes detailed in #59.
gitdb is now the name of the package again, with gitdb2 just being a mirror package that requires gitdb.
@Harmon758 Harmon758 closed this Feb 23, 2020
@nkadel
Copy link
Author

@nkadel nkadel commented Feb 24, 2020

Great, I'm glad you could resolve that.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
acknowledged
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@nkadel @Harmon758