Closed Bug 1116543 Opened 9 years ago Closed 9 years ago

vagrant up fails because of peep errors

Categories

(Input Graveyard :: Code Quality, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

Details

(Whiteboard: u=dev c=vagrant p=1 s=input.2014q4)

+++ This bug was initially created as a clone of Bug #1116489 +++

When going through the docs here:

http://fjord.readthedocs.org/en/latest/getting_started.html

The vm fails to provision. The version of peep.py doesn't work with the version of pip installed from the 14.04 package archive.

The error (typing this by hand) is this:

Traceback (most recent call last):
  File "./peep", line 59, in <module>
    from pip.log import logger
ImportError: No module named log


This prevents provisioning of the vm.
This is a quick fix since we're using an older version of peep. So the only issue is this logging issue.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Actually, it was more than a logging issue.

Since we're only using peep in Vagrant vm for contributors and we're not using it in server environments, I'm going to take advantage of the fact we can peg pip to an older version we know works without endangering anything.

In a PR: https://github.com/mozilla/fjord/pull/426
Goofy fix landed in master: https://github.com/mozilla/fjord/commit/1d608c4064f4e9fb12a7a861d88210c0229360d2

We don't need to deploy this, so I'm marking it FIXED now.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.