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

smmap and smmap2 on PyPI #44

Closed
11 tasks done
Harmon758 opened this issue Feb 23, 2020 · 1 comment
Closed
11 tasks done

smmap and smmap2 on PyPI #44

Harmon758 opened this issue Feb 23, 2020 · 1 comment
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 smmap.
v0.9.0 was the last release under the smmap package on PyPI prior to this happening.

In 2016, smmap2 was created to continue development for the library under a new package (09023b1), and every release since then has been with that package name. This has caused confusion (see #42 and #43) 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 smmap package name and have the smmap2 package simply be a mirror/dummy package that depends on and installs smmap, so as to maintain backwards compatibility.

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

  • Release a new version of GitDB, v3.0.3, as the gitdb2 package, to restrict the smmap2 version to < 3 (gitdb and gitdb2 on PyPI gitdb#59)
  • Release a new version, v3.0.0, as the smmap package
  • Create a smmap2 branch with a single setup.py that requires smmap
  • Release a new version, v3.0.0, of the smmap2 package from the smmap2 branch
  • Release a new version of GitDB, v4.0.0, as the gitdb package, that requires smmap rather than smmap2 (See gitdb and gitdb2 on PyPI gitdb#59)

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

  • 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 and gitdb2 on PyPI gitdb#59)
  • smmap v3.0.0 was released without a changelog
    smmap v3.0.1 has been tagged and released on PyPI to fix this
  • smmap2 branch improperly branches off of master and includes the entire smmap library
    The smmap2 branch has been force-pushed to 2422b98 to be properly set up for smmap2 to be a mirror package and the smmap2-v3.0.0 tag has been deleted
  • smmap2 v3.0.0 was released as the entire smmap library while still requiring smmap
    smmap2 v3.0.1 has been released on PyPI from the new smmap2 branch (2422b98)
    • smmap2 v3.0.0 has been deleted on PyPI
  • A new version of GitDB, v4.0.1, has been tagged and released on PyPI as the gitdb package, requiring smmap rather than smmap2 (See gitdb and gitdb2 on PyPI gitdb#59)

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.

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
12 tasks
ghost pushed a commit that referenced this issue Feb 23, 2020
@Byron
Change package name to 'smmap'; bump version to 3.0.0
541472d 
#44
@Byron
Copy link
Member

Byron commented Feb 23, 2020

@Harmon758 Please close this issue if you believe the ACs are fulfilled. Thank you - and thanks for setting up the instructions in the first place - couldn't have done it without you!

@Byron Byron removed their assignment Feb 23, 2020
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 25, 2020
Closed
tgbugs added a commit to tgbugs/tgbugs-overlay that referenced this issue Mar 12, 2020
@tgbugs
dev-python/{gitdb,smmap}2 temp fix for
d3af8b6 
the old pypi naming issue has been resolved, so an overhaul of the
various gitdb2/smmap2 dependents is probably in order

gitpython-developers/smmap#44
timokau added a commit to timokau/nixpkgs that referenced this issue Mar 14, 2020
@timokau
python.pkgs.smmap2: remove
e04fe98 
They were recently merged back together and smmap is the canonical
version:

gitpython-developers/smmap#44
jonringer pushed a commit to NixOS/nixpkgs that referenced this issue Mar 14, 2020
@timokau
python.pkgs.smmap2: remove
6c0fa33 
They were recently merged back together and smmap is the canonical
version:

gitpython-developers/smmap#44
@Tronyxsystem Tronyxsystem mentioned this issue Mar 2, 2021
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
@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