Merge lp:~jtv/launchpad/bug-448019 into lp:launchpad
Proposed by
Jeroen T. Vermeulen
Status: | Merged |
---|---|
Approved by: | Eleanor Berger |
Approved revision: | no longer in the source branch. |
Merged at revision: | not available |
Proposed branch: | lp:~jtv/launchpad/bug-448019 |
Merge into: | lp:launchpad |
Diff against target: |
52 lines 2 files modified
lib/lp/translations/doc/potemplate.txt (+10/-7) lib/lp/translations/model/potemplate.py (+5/-3) |
To merge this branch: | bzr merge lp:~jtv/launchpad/bug-448019 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Eleanor Berger (community) | code | Approve | |
Review via email: mp+13171@code.launchpad.net |
To post a comment you must log in.
= Bug 448019 =
See the bug report for what the problem is, what it costs us, and how I
fixed it. I hope it will also take a lot of wind out of the sails of
bug 447754. This is pretty much a 5-minute fix that'll save us some
real operational time, even if it's not perfect.
In a nutshell, when a translations import approval hits a conflict, this
branch logs not just the translation domain that multiple templates lay
a claim to, as we do now; but also the display names of those templates.
For Ubuntu packages that will include the Ubuntu release series, source
package name, and template name (which is a slightly different thing
from its domain).
== Tests ==
{{{
./bin/test -vv -t potemplate.txt
}}}
Since the logging already happened, and was already tested, I can just displayname
update an existing test. That test is actually for products rather than
packages, so not a great illustration of the real-world problem we see
happening. This is not the place to second-guess POTemplate.
though.
== Demo and Q/A ==
Q/A is annoyingly hard to set up. Only Soyuz does uploads without
specifying a source package name. Luckily we just added a script to
re-upload a package's translations, and there's an obscure case in the
approver that we can use to tickle the problem.
On staging (seriously kids, don't try this on production) do the rosetta/ reupload- translations. py -s intrepid -p k3b-i18n rosetta- approve- imports. py -vvv
following:
* Pick some arbitrary template in Intrepid, and on its +admin page,
set its translation domain to "k3b". There are now two templates in
separate Intrepid source packages with that domain.
* Run scripts/
to re-upload the latest translations tarball for this package.
* Run cronscripts/
That last script run will try to approve queue entries for k3b-i18n. A
special case in the approver says that uploads for this package are to
be redirected to other packages, based on template domain matching. The
attempt to do this will run into the clash between the two k3b templates
and log a more helpful message than before.
No lint. Thank you for reviewing!
Jeroen