Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #1466

closed

package version discrepancy in pypi API causes problems for sync

Added by mhrivnak over 8 years ago. Updated about 5 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Python:
Platform Release:
Target Release - Python:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

Package "numpy" at version 1.10.0.post2 has a version discrepancy. Looking in PKG_INFO, we clearly see:

Version: 1.10.0.post2

But when querying the pypi API as such:

curl https://pypi.python.org/pypi/numpy/json/

We find the version represented as simply "1.10.0":

        "1.10.0": [
            {
                "has_sig": true, 
                "upload_time": "2015-10-07T19:47:09", 
                "comment_text": "", 
                "python_version": "source", 
                "url": "https://pypi.python.org/packages/source/n/numpy/numpy-1.10.0.post2.tar.gz", 
                "md5_digest": "5594d8c5c006db8901fca585a29f3620", 
                "downloads": 53995, 
                "filename": "numpy-1.10.0.post2.tar.gz", 
                "packagetype": "sdist", 
                "size": 4082399
            },

During a sync, this makes it difficult to know if pulp already has that package. It appears the only option is to actually download it and inspect it, unless we are comfortable ripping the version out of the filename. For now, I will proceed with downloading the package, and handling the possibility that a NotUniqueError will be raised when saving.

Related issues

Related to Python Support - Issue #1465: All versions in pulp get associated during sync, even if not in remote feedCLOSED - CURRENTRELEASEmhrivnakActions
Actions
Copy link
 #1

Updated by mhrivnak over 8 years ago

  • Related to Issue #1465: All versions in pulp get associated during sync, even if not in remote feed added
Actions
Copy link
 #2

Updated by mhrivnak over 8 years ago

  • Triaged changed from No to Yes
Actions
Copy link
 #3

Updated by amacdona@redhat.com almost 6 years ago

  • Status changed from NEW to CLOSED - CURRENTRELEASE

When we bumped to pulp_python 2.0, we changed the natural key to filename, so we x.y.z.post2 is handled as a separate package from x.y.z and will not raise a uniqueness constraint.

Actions
Copy link
 #4

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added
Actions
Send by e-mail Copy link

Also available in: Atom PDF