Closed Bug 760647 Opened 12 years ago Closed 11 years ago

Mozmill's setup_development.py doesnt always actually setup for development

Categories

(Testing Graveyard :: Mozmill, defect)

Product:
Testing Graveyard
Component:
Mozmill
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 905556

People

(Reporter: whimboo, Unassigned)

References

Details

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

This was a comment from Jeff on bug 759836 which will also apply to our Mozmill repository.

https://github.com/mozautomation/mozmill/blob/master/setup_development.py
*should* change into each directory, in dependency order, and run
`python setup.py develop`.
Whiteboard: [mentor=jhammel][lang=py]
I'm more than happy to help with this bug but I don't have resources to look up all the esoteric reasons that should involve this changing.   Noting also that AFAIK this has rarely (never?) been a problem IRL.
Whiteboard: [mentor=jhammel][lang=py]
With bug 905556 I updated the script with the version from mozbase. So this is a dupe.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.