Counterintuitive "outdated" translation imports
Bug #356196 reported by
Jeroen T. Vermeulen
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
High
|
Henning Eggers | ||
Bug Description
This is a follow-up to bug 331094, whose original description didn't quite get to the heart of the problem because our error messages weren't giving enough information.
The real problem is that sometimes it is expected that a file with an older timestamp be accepted.
For instance, a file may have been implicitly created by Launchpad, after which an upstream file with an older timestamp is uploaded for the first time. Or translators may upload translation files of their own ("user uploads") as a way of providing updates to imported ones. In that case, the new timestamp on the user upload should not interfere with the next import from a published source.
| Changed in rosetta: | |
| milestone: | none → 2.2.5 |
| Changed in rosetta: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in rosetta: | |
| assignee: | nobody → Henning Eggers (henninge) |
| Changed in rosetta: | |
| milestone: | 2.2.5 → 2.2.6 |
| Changed in rosetta: | |
| status: | Triaged → In Progress |
Revision history for this message
| Henning Eggers (henninge) wrote | #1 |
| Changed in rosetta: | |
| status: | In Progress → Fix Committed |
| Changed in rosetta: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in devel 8530.