Merge lp:~jtv/launchpad/bug-572497 into lp:launchpad
| Status: | Merged | ||||
|---|---|---|---|---|---|
| Approved by: | Michael Hudson-Doyle on 2010-05-03 | ||||
| Approved revision: | no longer in the source branch. | ||||
| Merge reported by: | Jeroen T. Vermeulen | ||||
| Merged at revision: | not available | ||||
| Proposed branch: | lp:~jtv/launchpad/bug-572497 | ||||
| Merge into: | lp:launchpad | ||||
| Diff against target: |
139 lines (+30/-1) 2 files modified
database/schema/security.cfg (+1/-1) lib/lp/translations/tests/test_translationbuildapprover.py (+29/-0) |
||||
| To merge this branch: | bzr merge lp:~jtv/launchpad/bug-572497 | ||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Björn Tillenius (community) | release-critical | Approve on 2010-05-03 | |
| Michael Hudson-Doyle | Approve on 2010-05-03 | ||
| Canonical Launchpad Engineering | code | 2010-04-30 | Pending |
|
Review via email:
|
|||
Commit Message
Allow "fiera" db user to approve translation templates.
Description of the Change
= Bug 572497 =
We've finally gotten the build farm (formerly Soyuz) to dispatch a translation templates build job to a build farm slave; the slave to check out a bzr branch, run intltool on it to generate templates, roll the templates into a tarball, and send it back to the master; and the master to receive the tarball, upload it to the translations import queue, and attempt to approve the resulting entries.
That's where we ran into a database privilege problem—the database user in question is not allowed to read POTemplate. This is a newer addition: the uploads also go straight into approval, which requires read access to some extra tables.
Luckily we have a dedicated database group containing all the permissions needed for this (and a few more, but nothing that could possibly hurt).
I still need tests for this, so am filing this as Work In Progress for now. I can't invoke the build farm from the test suite, so it won't be too realistic. But I can add a unit test that runs the approval code we use here under the fiera database user.
To Q/A, go through the steps in https:/
Jeroen
| Jeroen T. Vermeulen (jtv) wrote : | # |

Okay, I've updated the test to run as the real database user. This reproduces the problem, and "make schema" then fixes the test.