Closed Bug 1110299 Opened 10 years ago Closed 8 years ago

version-control-tool's pip install requirements file should use HTTPS paths for ReviewBoard packages

Categories

(MozReview Graveyard :: General, defect, P3)

Product:
MozReview Graveyard
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: emorley, Unassigned)

References

Details

vagrant@precise32:/vagrant$ ./create-test-environment
Requirement already up-to-date: pip in ./venv/lib/python2.7/site-packages
Cleaning up...
http://downloads.reviewboard.org/releases/Djblets/0.8/ uses an insecure transport scheme (http). Consider using https if downloads.reviewboard.org has it available
http://downloads.reviewboard.org/releases/django-evolution/0.7/ uses an insecure transport scheme (http). Consider using https if downloads.reviewboard.org has it available
Requirement already up-to-date: Django==1.6.7 in ./venv/lib/python2.7/site-packages (from -r test-requirements.txt (line 5))
...

Ideally they should either be published on PyPI or else mirrored on an HTTPS capable Mozilla property.
Summary: version-control-tool's test-requirements should use HTTPS paths for ReviewBoard packages → version-control-tool's pip install requirements file should use HTTPS paths for ReviewBoard packages
Priority: -- → P2
We have too many P1s, so I'm spreading out the priorities.  P3 -> P4, P2 -> P3, and some portion of P1s will become P2.
Priority: P2 → P3
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Developer Services → MozReview
Blocks: 1328441
You need to log in before you can comment on or make changes to this bug.