Launchpad itself

Move setup for local Soyuz into utilities

Bug #526462 reported by Jeroen T. Vermeulen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Jeroen T. Vermeulen
Launchpad itself 10.02

Bug Description

On https://dev.launchpad.net/Soyuz/HowToUseSoyuzLocally we have two scripts that one must run in order to get Soyuz working on a dev machine. They've now fallen out of compatibility with the LP codebase.

Move these scripts into the utilities directory, and add tests, to make sure they are maintained.

Tags: lp-soyuz qa-ok

Related branches

lp:~jtv/launchpad/bug-526462
Michael Nelson (community): Approve (code)
Diff: 347 lines (+338/-0)
2 files modified
lib/lp/soyuz/doc/sampledata-cleanup.txt (+22/-0)
utilities/soyuz-sampledata-cleanup.py (+316/-0)
Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit

Fixed in devel r10401 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/revision/10401>

Changed in soyuz:
status: In Progress → Fix Committed
Jeroen T. Vermeulen (jtv)
tags: added: qa-ok
Jeroen T. Vermeulen (jtv)
Changed in soyuz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.