Closed
Bug 1241251
Opened 8 years ago
Closed 8 years ago
Move from peep to pip
Categories
(developer.mozilla.org Graveyard :: Code Cleanup, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jezdez, Unassigned)
References
Details
(Whiteboard: [specification][type:change])
What feature should be changed? Please provide the URL of the feature if possible. ================================================================================== Now that pip 8 is released we can move to it replacing peep What problems would this solve? =============================== This would make the use of hashes using official tools instead of homegrown tools Who would use this? =================== devs What would users see? ===================== n/a What would users do? What would happen as a result? =================================================== n/a Is there anything else we should know? ======================================
|
||
Comment 2•8 years ago
|
||
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/50d4ddc770332b89000bd98ab31c6719605dfea3 Fix bug 1241251 - Move from peep to pip8. https://github.com/mozilla/kuma/commit/631b60cbecd2c8dba1e67540cb37b2a260049c63 Bug 1241251 - Bumped pip version to 8.0.2 to work around SSL issue. https://github.com/mozilla/kuma/commit/05abdefcaba0a9a1b1a83e6f69bd2c0dbd5ed058 Merge pull request #3760 from mozilla/pip8 Fix bug 1241251 - Move from peep to pip8.
|
|
||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
|
||
Updated•4 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•