New upstream translations of k3b not imported to Rosetta
Bug #58556 reported by
Jannick Kuhr
This bug report is a duplicate of:
Bug #58526: Koffice and K3b translations are not imported into Rosetta.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Undecided
|
Unassigned | ||
| k3b-i18n (Ubuntu) |
In Progress
|
Medium
|
Martin Pitt | ||
Bug Description
The new upstream translations for k3b have not been imported to Rosetta. The k3b version in edgy is 0.12.17 (23.08.2006) but the upstream translations are older. Probably this is caused by the circumstance that the translations are not in the source of k3b, but in a separate package (k3b-i18n-
This seems similar to me like the problems with koffice: https:/
Please fix these issues and ensure that in the next releases the import works out of the box.
Revision history for this message
| Martin Pitt (pitti) wrote | #1 |
| Changed in k3b-i18n: | |
| assignee: | nobody → pitti |
| importance: | Untriaged → Medium |
| status: | Unconfirmed → In Progress |
To post a comment you must log in.
Package was promoted, now it needs seeding (I can't connect to bazaar.lp.n ATM) and a no-change upload for rebuild.