Language pack selection must be set automatically
Bug #148430 reported by
Carlos Perelló Marín
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
When a new language pack export is used in one of the Ubuntu distroseries we need to note it manually in Launchpad. Instead, that should be done automatically from the buildd once the package build is accepted in the archive.
Changed in rosetta: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in rosetta: | |
milestone: | 1.1.11 → 1.1.12 |
Changed in rosetta: | |
assignee: | nobody → carlos |
milestone: | 1.1.12 → 1.1.11 |
status: | Confirmed → In Progress |
Changed in rosetta: | |
assignee: | nobody → jtv |
Changed in rosetta: | |
milestone: | 1.1.12 → 1.2.1 |
Changed in rosetta: | |
assignee: | jtv → nobody |
milestone: | 1.2.1 → 1.2.2 |
Changed in rosetta: | |
assignee: | nobody → carlos |
Changed in rosetta: | |
status: | Confirmed → Incomplete |
Changed in rosetta: | |
milestone: | 1.2.2 → 1.2.3 |
Changed in rosetta: | |
status: | Incomplete → In Progress |
Changed in rosetta: | |
milestone: | 1.2.3 → 1.2.4 |
Changed in rosetta: | |
assignee: | carlos → nobody |
milestone: | 1.2.4 → none |
Changed in rosetta: | |
importance: | High → Low |
visibility: | private → public |
To post a comment you must log in.
Moved back to confirmed, after reviewing my logs I see that this needs some discussion with soyuz team based on a prototype callback that they would execute once a package is published.
That call back should get enough information to know the language pack that is being published and in which pocket and note it in our database.
I'm leaving 'Assigned to' field empty because I'm not around to handle this for 1.1.12 nor 1.2.1 but this is something we should implement as soon as possible to kill unneeded manual work that could produce broken language packs.