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.

Sign up for GitHub

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

gitdb and gitdb2 on PyPI #59

Closed
12 tasks done
Harmon758 opened this issue Feb 23, 2020 · 0 comments
Closed
12 tasks done

gitdb and gitdb2 on PyPI #59

Harmon758 opened this issue Feb 23, 2020 · 0 comments
Assignees
@Harmon758

Comments

@Harmon758
Copy link
Member

Harmon758 commented Feb 23, 2020 •
edited
Loading

In 2015, access was lost to the PyPI account that owns gitdb.
v0.6.4 was the last release under the gitdb package on PyPI prior to this happening.

In 2016, gitdb2 was created to continue development for the library under a new package (38866bc), and every release since then has been with that package name. This has caused confusion (see #45, #47, #57, gitpython-developers/GitPython#983) and having an old, stale PyPI project is less than ideal.

Recently, the original PyPI account has been recovered.
The intention now is to transition back to using the original gitdb package name and have the gitdb2 package simply be a mirror/dummy package that depends on and installs gitdb, so as to maintain backwards compatibility.

Currently, these are the anticipated steps that need to be taken:

  • Release a new version, v3.0.3, as the gitdb2 package, that restricts the smmap2 version to < 3
    (See smmap and smmap2 on PyPI smmap#44)
  • Release a new version, v4.0.0, as the gitdb package; the only change from gitdb2 v3.0.3 should be to require smmap rather than smmap2 (smmap and smmap2 on PyPI smmap#44)
  • Create a gitdb2 branch with a single setup.py that requires gitdb
  • Release a new version, v4.0.0, of the gitdb2 package from the gitdb2 branch
    • Note Because I (@Byron) accidentally released step 2 in this list as package gitdb2 instead of gitdb, v4.0.0 of gitdb2 already existed. The change requested here is now in v4.0.1.

v4.0.0 for both packages should be functionally equivalent to gitdb2 v3.0.3, with gitdb2 v4.0.0 simply installing gitdb >= 4.0.0 and with gitdb v4.0.0 requiring smmap rather than smmap2 (gitpython-developers/smmap#44).

  • gitdb2 v3.0.3 was released with an erroneous and incomplete changelog
    gitdb2 v3.0.3.post1 has been tagged and released on PyPI to fix this
  • gitdb v4.0.0 was tagged with the wrong package name and released with an incomplete changelog and unbound smmap requirement version specifiers
    The master branch has been force-pushed to 253dfe7 and gitdb v4.0.1 has been tagged and released on PyPI
    • gitdb v4.0.0 has been deleted on PyPI
  • gitdb2 improperly branches off of the 4.0.0 tag and includes the entire GitDB library
    The gitdb2 branch has been force-pushed to d3bf396 to be properly set up for gitdb2 to be a mirror package and the gitdb2-4.0.0 and gitdb2-4.0.1 tags have been deleted
  • gitdb2 v4.0.0 was released as the entire GitDB library and without requiring gitdb
    gitdb2 v4.0.0 has been deleted on PyPI
  • gitdb2 v4.0.1 was released as the entire GitDB library while still requiring gitdb
    gitdb2 v4.0.2 has been released on PyPI from the new gitdb2 branch (d3bf396)
    • gitdb2 v4.0.1 has been deleted on PyPI
  • A new version of GitPython, v3.1.0, that requires gitdb rather than gitdb2, has been tagged (at first, gitpython-developers/GitPython@c859019 was tagged, but that commit forgot the version bump and as such, it has now been re-tagged to the version bump commit, gitpython-developers/GitPython@8c9da73) and released on PyPI

gitdb v4.0.1 and gitdb2 v4.0.2 should be functionally equivalent to gitdb2 v3.0.3 with gitdb v4.0.2 simply installing gitdb >= 4.0.1 and with gitdb v4.0.1 requiring smmap rather than smmap2 (gitpython-developers/smmap#44).

Note: @Byron was having issues with releases, so I was added as a maintainer for gitdb, gitdb2, smmap, and smmap2 on PyPI. Since there were already issues with the new signature key being used, I've released gitdb v4.0.1, gitdb2 v3.0.3.post1, gitdb2 v4.0.2, smmap v3.0.1, and smmap2 v3.0.1 without any signature keys. The intention is still for @Byron to release new versions with the proper signature key once he has access to it again.
@Harmon758 Harmon758 pinned this issue Feb 23, 2020
@Harmon758 Harmon758 mentioned this issue Feb 23, 2020
Closed
11 tasks
ghost pushed a commit that referenced this issue Feb 23, 2020
@Byron
Bump version to v3.0.3; update changelog
169dbcf 
#59
ghost pushed a commit that referenced this issue Feb 23, 2020
@Byron
Bump to v4.0.0; require smmap package
5f819b5 
#59
ghost pushed a commit that referenced this issue Feb 23, 2020
@Byron
Require gitdb (at least version 4)
92459d3 
#59
@Harmon758 Harmon758 mentioned this issue Feb 23, 2020
Closed
openstack-gerrit pushed a commit to openstack/requirements that referenced this issue Feb 24, 2020
@ianw @jharbott
Update gitdb to 4.0.1, gitdb2 to 4.0.2
7d5bea2 
The gitdb 4.0.0 release and gitdb2 4.0.1 release has been deleted from
PyPi and (if I'm reading [1] correctly, which is a big *if*) has been
replaced with 4.0.1 and 4.0.2 respectively.  [1]:

  gitdb v4.0.1 and gitdb2 v4.0.2 should be functionally equivalent to
  gitdb2 v3.0.3 with gitdb v4.0.2 simply installing gitdb >= 4.0.1 and
  with gitdb v4.0.1 requiring smmap rather than smmap2
  (gitpython-developers/smmap#44).

Additionally, it seems that gitdb now also requires smmap>=3.0.1.
This project is in a similar renaming phase, but 3.0.1 seems to be the
correct place to be [2]:

  v3.0.1 for both packages should be functionally equivalent to smmap2
  v2.0.5, with smmap2 v3.0.1 simply installing smmap >= 3.0.1.

Additionally additionally, there appears to be a problem with
cross-horizon-npm not obeying new constraints in it's job (possibly
this is the first time packages horizon cares about have broken?).
Since this blocks this change from merging, set the job to non-voting
until we can fix this in a follow-on.

[1] gitpython-developers/gitdb#59
[2] gitpython-developers/smmap#44

Change-Id: I268fb7e1dc753c82983736572b3df2f152f8cf51
openstack-gerrit pushed a commit to openstack/openstack that referenced this issue Feb 24, 2020
@ianw @openstack-gerrit
Update git submodules
c174fbe 
* Update requirements from branch 'master'
  - Update gitdb to 4.0.1, gitdb2 to 4.0.2
    
    The gitdb 4.0.0 release and gitdb2 4.0.1 release has been deleted from
    PyPi and (if I'm reading [1] correctly, which is a big *if*) has been
    replaced with 4.0.1 and 4.0.2 respectively.  [1]:
    
      gitdb v4.0.1 and gitdb2 v4.0.2 should be functionally equivalent to
      gitdb2 v3.0.3 with gitdb v4.0.2 simply installing gitdb >= 4.0.1 and
      with gitdb v4.0.1 requiring smmap rather than smmap2
      (gitpython-developers/smmap#44).
    
    Additionally, it seems that gitdb now also requires smmap>=3.0.1.
    This project is in a similar renaming phase, but 3.0.1 seems to be the
    correct place to be [2]:
    
      v3.0.1 for both packages should be functionally equivalent to smmap2
      v2.0.5, with smmap2 v3.0.1 simply installing smmap >= 3.0.1.
    
    Additionally additionally, there appears to be a problem with
    cross-horizon-npm not obeying new constraints in it's job (possibly
    this is the first time packages horizon cares about have broken?).
    Since this blocks this change from merging, set the job to non-voting
    until we can fix this in a follow-on.
    
    [1] gitpython-developers/gitdb#59
    [2] gitpython-developers/smmap#44
    
    Change-Id: I268fb7e1dc753c82983736572b3df2f152f8cf51
@Harmon758 Harmon758 mentioned this issue Feb 24, 2020
Open
@Harmon758 Harmon758 mentioned this issue Feb 24, 2020
Closed
wip-sync referenced this issue in NetBSD/pkgsrc-wip Mar 7, 2020
@0-wiz-0
py-git: update to 3.1.0.
cc95dab 
3.1.0
=====

* Switched back to using gitdb package as requirement
  (`gitdb#59 <https://github.com/gitpython-developers/gitdb/issues/59>`_)

3.0.9
=====

* Restricted GitDB (gitdb2) version requirement to < 4
* Removed old nose library from test requirements

Bugfixes
--------

* Changed to use UTF-8 instead of default encoding when getting information about a symbolic reference
  (`#774 <https://github.com/gitpython-developers/GitPython/issues/774>`_)
* Fixed decoding of tag object message so as to replace invalid bytes
  (`#943 <https://github.com/gitpython-developers/GitPython/issues/943>`_)

3.0.8
=====

* Added support for Python 3.8
* Bumped GitDB (gitdb2) version requirement to > 3

Bugfixes
--------

* Fixed Repo.__repr__ when subclassed
  (`#968 <https://github.com/gitpython-developers/GitPython/pull/968>`_)
* Removed compatibility shims for Python < 3.4 and old mock library
* Replaced usage of deprecated unittest aliases and Logger.warn
* Removed old, no longer used assert methods
* Replaced usage of nose assert methods with unittest

3.0.7
=====

Properly signed re-release of v3.0.6 with new signature
(See `#980 <https://github.com/gitpython-developers/GitPython/issues/980>`_)

3.0.6
=====

| Note: There was an issue that caused this version to be released to PyPI without a signature
| See the changelog for v3.0.7 and `#980 <https://github.com/gitpython-developers/GitPython/issues/980>`_

Bugfixes
--------

* Fixed warning for usage of environment variables for paths containing ``$`` or ``%``
  (`#832 <https://github.com/gitpython-developers/GitPython/issues/832>`_,
  `#961 <https://github.com/gitpython-developers/GitPython/pull/961>`_)
* Added support for parsing Git internal date format (@<unix timestamp> <timezone offset>)
  (`#965 <https://github.com/gitpython-developers/GitPython/pull/965>`_)
* Removed Python 2 and < 3.3 compatibility shims
  (`#979 <https://github.com/gitpython-developers/GitPython/pull/965>`_)
* Fixed GitDB (gitdb2) requirement version specifier formatting in requirements.txt
  (`#979 <https://github.com/gitpython-developers/GitPython/pull/965>`_)
timokau added a commit to timokau/nixpkgs that referenced this issue Mar 14, 2020
@timokau
python.pkgs.gitdb2: remove
0fae68c 
The two are now the same:
gitpython-developers/gitdb#59
jonringer pushed a commit to NixOS/nixpkgs that referenced this issue Mar 14, 2020
@timokau
python.pkgs.gitdb2: remove
6db65f8 
The two are now the same:
gitpython-developers/gitdb#59
@jaredbeck jaredbeck mentioned this issue Mar 20, 2020
Closed
@fangchenli fangchenli mentioned this issue Aug 20, 2020
Closed
@Panaetius Panaetius mentioned this issue Sep 8, 2020
Closed
@KSchopmeyer KSchopmeyer mentioned this issue Jan 8, 2023
Merged
@Harmon758 Harmon758 mentioned this issue May 28, 2023
Closed
tanaypf9 pushed a commit to tanaypf9/pf9-requirements that referenced this issue May 20, 2024
@ianw
Update gitdb to 4.0.1, gitdb2 to 4.0.2
0d112a6 
The gitdb 4.0.0 release and gitdb2 4.0.1 release has been deleted from
PyPi and (if I'm reading [1] correctly, which is a big *if*) has been
replaced with 4.0.1 and 4.0.2 respectively.  [1]:

  gitdb v4.0.1 and gitdb2 v4.0.2 should be functionally equivalent to
  gitdb2 v3.0.3 with gitdb v4.0.2 simply installing gitdb >= 4.0.1 and
  with gitdb v4.0.1 requiring smmap rather than smmap2
  (gitpython-developers/smmap#44).

Additionally, it seems that gitdb now also requires smmap>=3.0.1.
This project is in a similar renaming phase, but 3.0.1 seems to be the
correct place to be [2]:

  v3.0.1 for both packages should be functionally equivalent to smmap2
  v2.0.5, with smmap2 v3.0.1 simply installing smmap >= 3.0.1.

Additionally additionally, there appears to be a problem with
cross-horizon-npm not obeying new constraints in it's job (possibly
this is the first time packages horizon cares about have broken?).
Since this blocks this change from merging, set the job to non-voting
until we can fix this in a follow-on.

[1] gitpython-developers/gitdb#59
[2] gitpython-developers/smmap#44

Change-Id: I268fb7e1dc753c82983736572b3df2f152f8cf51
tanaypf9 pushed a commit to tanaypf9/pf9-requirements that referenced this issue May 20, 2024
@openstack-gerrit
Update patch set 2
4fd6dfb 
Patch Set 2:

gitdb2===4.0.1 does no longer exist and is breaking our CI. Can we either roll this back or bump it to 4.0.2?
gitpython-developers/gitdb#59

btw gitdb==4.0.0 probably does not exist either and should be bumped to 4.0.1?

Patch-set: 2
tanaypf9 pushed a commit to tanaypf9/pf9-requirements that referenced this issue May 20, 2024
@stephenfin
Bump gitdb2 upper constraint to 4.0.2
8782d23 
Per [1], 4.0.1 has been deleted because it was lacking proper signature
keys.

[1] gitpython-developers/gitdb#59

Change-Id: Id8ebe2962f3a099f343db1428dc846380f556fd9
Signed-off-by: Stephen Finucane <[email protected]>
tanaypf9 pushed a commit to tanaypf9/pf9-requirements that referenced this issue May 20, 2024
@ianw
Update gitdb to 4.0.1, gitdb2 to 4.0.2
9ab44f0 
The gitdb 4.0.0 release and gitdb2 4.0.1 release has been deleted from
PyPi and (if I'm reading [1] correctly, which is a big *if*) has been
replaced with 4.0.1 and 4.0.2 respectively.  [1]:

  gitdb v4.0.1 and gitdb2 v4.0.2 should be functionally equivalent to
  gitdb2 v3.0.3 with gitdb v4.0.2 simply installing gitdb >= 4.0.1 and
  with gitdb v4.0.1 requiring smmap rather than smmap2
  (gitpython-developers/smmap#44).

Additionally, it seems that gitdb now also requires smmap>=3.0.1.
This project is in a similar renaming phase, but 3.0.1 seems to be the
correct place to be [2]:

  v3.0.1 for both packages should be functionally equivalent to smmap2
  v2.0.5, with smmap2 v3.0.1 simply installing smmap >= 3.0.1.

[1] gitpython-developers/gitdb#59
[2] gitpython-developers/smmap#44

Change-Id: I268fb7e1dc753c82983736572b3df2f152f8cf51
tanaypf9 pushed a commit to tanaypf9/pf9-requirements that referenced this issue May 20, 2024
@ianw
Update gitdb to 4.0.1, gitdb2 to 4.0.2
7240eca 
The gitdb 4.0.0 release and gitdb2 4.0.1 release has been deleted from
PyPi and (if I'm reading [1] correctly, which is a big *if*) has been
replaced with 4.0.1 and 4.0.2 respectively.  [1]:

  gitdb v4.0.1 and gitdb2 v4.0.2 should be functionally equivalent to
  gitdb2 v3.0.3 with gitdb v4.0.2 simply installing gitdb >= 4.0.1 and
  with gitdb v4.0.1 requiring smmap rather than smmap2
  (gitpython-developers/smmap#44).

Additionally, it seems that gitdb now also requires smmap>=3.0.1.
This project is in a similar renaming phase, but 3.0.1 seems to be the
correct place to be [2]:

  v3.0.1 for both packages should be functionally equivalent to smmap2
  v2.0.5, with smmap2 v3.0.1 simply installing smmap >= 3.0.1.

[1] gitpython-developers/gitdb#59
[2] gitpython-developers/smmap#44

Change-Id: I268fb7e1dc753c82983736572b3df2f152f8cf51
tanaypf9 pushed a commit to tanaypf9/pf9-requirements that referenced this issue May 20, 2024
@ianw
Update gitdb to 4.0.1, gitdb2 to 4.0.2
3643ab6 
The gitdb 4.0.0 release and gitdb2 4.0.1 release has been deleted from
PyPi and (if I'm reading [1] correctly, which is a big *if*) has been
replaced with 4.0.1 and 4.0.2 respectively.

  gitdb v4.0.1 and gitdb2 v4.0.2 should be functionally equivalent to
  gitdb2 v3.0.3 with gitdb v4.0.2 simply installing gitdb >= 4.0.1 and
  with gitdb v4.0.1 requiring smmap rather than smmap2
  (gitpython-developers/smmap#44).

[1] gitpython-developers/gitdb#59

Change-Id: I268fb7e1dc753c82983736572b3df2f152f8cf51
tanaypf9 pushed a commit to tanaypf9/pf9-requirements that referenced this issue May 20, 2024
@ianw
Update gitdb to 4.0.1, gitdb2 to 4.0.2
169a986 
The gitdb 4.0.0 release and gitdb2 4.0.1 release has been deleted from
PyPi and (if I'm reading [1] correctly, which is a big *if*) has been
replaced with 4.0.1 and 4.0.2 respectively.  [1]:

  gitdb v4.0.1 and gitdb2 v4.0.2 should be functionally equivalent to
  gitdb2 v3.0.3 with gitdb v4.0.2 simply installing gitdb >= 4.0.1 and
  with gitdb v4.0.1 requiring smmap rather than smmap2
  (gitpython-developers/smmap#44).

Additionally, it seems that gitdb now also requires smmap>=3.0.1.
This project is in a similar renaming phase, but 3.0.1 seems to be the
correct place to be [2]:

  v3.0.1 for both packages should be functionally equivalent to smmap2
  v2.0.5, with smmap2 v3.0.1 simply installing smmap >= 3.0.1.

[1] gitpython-developers/gitdb#59
[2] gitpython-developers/smmap#44

Change-Id: I268fb7e1dc753c82983736572b3df2f152f8cf51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Harmon758 Harmon758

Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Byron @Harmon758