Get slave-side pottery code onto the build-farm slave
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Henning Eggers |
Bug Description
The slave-side pottery code must be installed on the slave systems.
The easiest way to get this done is to move it into the launchpad-buildd package, which is built from lib/canonical/
Some manual testing will be needed to make sure the paths are right; we can't automate realistic integration-testing between the server and build-farm slaves. To get a realistic slave environment, build the .deb in lib/canonical/
Related branches
- Paul Hummer (community): Approve (code)
-
Diff: 136 lines (+26/-12)7 files modifiedlib/canonical/buildd/README (+1/-0)
lib/canonical/buildd/debian/rules (+10/-1)
lib/canonical/buildd/generate_translation_templates.py (+5/-2)
lib/canonical/buildd/translationtemplates.py (+1/-1)
lib/lp/translations/pottery/buildd.py (+7/-6)
lib/lp/translations/tests/test_pottery_detect_intltool.py (+1/-1)
scripts/rosetta/pottery-generate-intltool.py (+1/-1)
Changed in rosetta: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Henning Eggers (henninge) |
milestone: | none → 10.02 |
Changed in rosetta: | |
status: | In Progress → Fix Committed |
This bug was mentioned in stable r10411 <http:// bazaar. launchpad. net/~launchpad- pqm/launchpad/ stable/ revision/ 10411>