Story #137
closed
Story #1883: As a user, I can sync and publish all package types
As a user, I can publish repositories that contain wheel packages
Status:
CLOSED - CURRENTRELEASE
Description
Currently, we only publish sdist packages. We should add the ability to publish packages that contain wheel (bdist) packages as well. Deliverables:
- Modify the publisher to support wheel packages. There may be little to change here.
- Write tests.
- Write release notes.
- Write a getting started doc example of how to use pip to install a bdist package from Pulp.
Note that #135 has the task of creating the wheel type, so it must be done first.
- Sprint Candidate set to Yes
- Sprint Candidate changed from Yes to No
- Parent issue set to #1883
- Status changed from NEW to ASSIGNED
- Assignee set to amacdona@redhat.com
- Status changed from ASSIGNED to MODIFIED
Once 135 was completed, this story did not require any additional changes.
- Status changed from MODIFIED to POST
amacdona@redhat.com wrote:
Once 135 was completed, this story did not require any additional changes.
I think I moved this to POST when #135 went to POST, but probably the correct solution was to close this as a duplicate? I'm not really sure what to do here. Maybe I'll just ref the same commit in #135 for this and mark this as MODIFIED, since I assume the story will help with verifying functionality?
- Status changed from POST to MODIFIED
2.0-dev is now being included in Platform 2.13 builds again, returning this to a testable state. Note that any smash tests related to this issue should not be run prior to 2.13.0; this is tracked in pulp-smash issue https://github.com/PulpQE/pulp-smash/issues/588.
- Platform Release set to 2.13.0
- Status changed from MODIFIED to 5
- Status changed from 5 to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
Change sync code to use new model
Adds some fields that were necessary for sync, syncs in the new way, and heavily modify docblocks to explain.
closes #135