** Description changed: - [ Impact ] + [ Impact ] - * The Ubuntu translations of package descriptions (Translation-*) for resolute were never refreshed from the ddtp-translations template. As a result, apt on non-English locales shows stale or missing translated - descriptions for resolute. - * Cause: the update workflow depended on bzr. Launchpad deprecated bzr far enough that the process stopped working. The steps and documentation now avoid bzr, and the translations can be refreshed manually. - * The package only builds a custom tarball. Launchpad publishing uses that tarball to export translations to https://archive.ubuntu.com/ubuntu/dists/resolute/$component/i18n/. Uploading it is the only way to get the refreshed translations into the archive. + * The Ubuntu translations of package descriptions (Translation-*) for resolute were never refreshed from the ddtp-translations template. As a result, apt on non-English locales shows stale or missing translated descriptions for resolute. + * Cause: the update workflow depended on bzr. Launchpad deprecated bzr far enough that the process stopped working. The steps and documentation now avoid bzr, and the translations can be refreshed manually. + * The package only builds a custom tarball. Launchpad publishing uses that tarball to export translations to https://archive.ubuntu.com/ubuntu/dists/resolute/$component/i18n/. Uploading it is the only way to get the refreshed translations into the archive. - [ Test Plan ] + [ Test Plan ] - * Start from a clean resolute system or container with a non-English locale, for example: - `sudo apt install locales && sudo locale-gen fr_FR.UTF-8` - `export LANG=fr_FR.UTF-8 LANGUAGE=fr` - * Before the update: `sudo apt update && apt-cache show <package>`, using a package that is known to have a DDTP translation. The `Description` is English only, or the translation is outdated or missing. - * After the update is published and the i18n index is refreshed: `sudo apt update && apt-cache show <package>`. - Expected: the `Description` is translated into the selected locale. - Actual (before the fix): English or stale text. - * Check that `sudo apt update` reports no errors or warnings about `Translation-*` files (hash mismatch, malformed or missing index entries). - * Check the files directly: `curl -I https://archive.ubuntu.com/ubuntu/dists/resolute/main/i18n/Translation-fr.xz` returns HTTP 200. + * Start from a clean resolute system or container with a non-English locale, for example: + `sudo apt install locales && sudo locale-gen fr_FR.UTF-8` + `export LANG=fr_FR.UTF-8 LANGUAGE=fr` + * Before the update: `sudo apt update && apt-cache show <package>`, using a package that is known to have a DDTP translation. The `Description` is English only, or the translation is outdated or missing. + * After the update is published and the i18n index is refreshed: `sudo apt update && apt-cache show <package>`. + Expected: the `Description` is translated into the selected locale. + Actual (before the fix): English or stale text. + * Check that `sudo apt update` reports no errors or warnings about `Translation-*` files (hash mismatch, malformed or missing index entries). + * Check the files directly: `curl -I https://archive.ubuntu.com/ubuntu/dists/resolute/main/i18n/Translation-fr.xz` returns HTTP 200. - [ Where problems could occur ] + [ Where problems could occur ] - * Wrong, buggy, or outdated translations could reach users. This only affects the text shown for descriptions. - * Invalid or malformed translation data could make apt behave incorrectly on non-English locales. Examples are `apt update` failing or warning on `Translation-*` files, `apt-cache show` and `apt search` erroring - or printing garbled output, and hash or size mismatches against the Release file. Any locale with a published translation could be affected, not just one. - * Mitigation: the package contains data only and no executable code, so there is no runtime or behavioral regression. apt ignores or falls back to English when a translation is missing. The tarball is generated by - the updated, documented process, and the result can be checked after publication. - * There is no phased rollout. The outcome is archive publication, so a bad upload reaches all users at once. It can be fixed by uploading a corrected package. + * Wrong, buggy, or outdated translations could reach users. This only affects the text shown for descriptions. + * Invalid or malformed translation data could make apt behave incorrectly on non-English locales. Examples are `apt update` failing or warning on `Translation-*` files, `apt-cache show` and `apt search` erroring + or printing garbled output, and hash or size mismatches against the Release file. Any locale with a published translation could be affected, not just one. + * Mitigation: the package contains data only and no executable code, so there is no runtime or behavioral regression. apt ignores or falls back to English when a translation is missing. The tarball is generated by + the updated, documented process, and the result can be checked after publication. + * There is no phased rollout. The outcome is archive publication, so a bad upload reaches all users at once. It can be fixed by uploading a corrected package. - [ Other Info ] + [ Other Info ] - * The workflow and documentation were updated to drop bzr, so future + * The workflow and documentation were updated to drop bzr, so future refreshes do not need it.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2172351 Title: Resolute has no ddtp translations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddtp-translations/+bug/2172351/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
