Bug #17127
Downgrade po4a to Stretch's 0.47-2
Start date:
Due date:
% Done:
100%
Description
It seems we won’t manage to do Bug #17005 by upgrading All The Things to po4a 0.55 in time for Tails 4.0, so for now let’s do it by ensuring all relevant systems run 0.47-2.
Subtasks
Related issues
Related to Tails - |
Resolved | ||
Blocks Tails - Feature #16209: Core work: Foundations Team | Confirmed |
History
#1 Updated by intrigeri 2019-10-06 05:43:36
- related to
Bug #17005: Upgrade to po4a 0.55 in Tails itself, in the Vagrant build box, on {translate,www}.lizard, and on RM's systems added
#2 Updated by intrigeri 2019-10-06 05:43:42
- blocks Feature #16209: Core work: Foundations Team added
#3 Updated by intrigeri 2019-10-06 05:47:36
- Status changed from Confirmed to In Progress
Applied in changeset commit:tails|ca4e0558230f8a30afb3c06909b0a2a1c8a73852.
#4 Updated by intrigeri 2019-10-06 05:48:30
- Feature Branch set to bugfix/17127-po4a-from-stretch
#5 Updated by intrigeri 2019-10-06 07:50:55
- Status changed from In Progress to Needs Validation
- Assignee deleted (
intrigeri)
Please review & merge into devel.
Note that we do not install po4a by default, so all that matters here is APT pinning that Additional Software will use.
I applied the changes made on this branch to a running Tails devel, then confirmed that apt update && apt install po4a
installs the intended version.
I did not bother:
- testing po4a in an image built from this branch, because I’ve been using that version of po4a on sid for months (as per the RM doc)
- looking at CI results apart of image build, because I don’t see how adding an APT source + pinning for a package we don’t install could affect Tails’ behavior
#6 Updated by segfault 2019-10-07 20:52:18
- Status changed from Needs Validation to Resolved
- % Done changed from 0 to 100
Applied in changeset commit:tails|a8159b6f7f2038bf3e4dd3924e32d0c25571ffea.