Bug 1696319 - gnome-initial-setup ships with old translations
Summary: gnome-initial-setup ships with old translations
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-initial-setup
Version: 30
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rui Matos
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-04 14:20 UTC by Carmen Bianca Bakker
Modified: 2019-04-09 00:03 UTC (History)
3 users (show)

Fixed In Version: gnome-initial-setup-3.32.0-1.fc30
Clone Of:
Environment:
Last Closed: 2019-04-09 00:03:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Carmen Bianca Bakker 2019-04-04 14:20:06 UTC
Description of problem: Fedora 30 currently ships with gnome-initial-setup 3.30.0. This version contains old and incorrect translations [for Esperanto]. 3.32.0 contains new and updated translations.


Version-Release number of selected component (if applicable): 3.30.0


How reproducible: N/A


Steps to Reproduce:
1. N/A

Actual results: Bad translations


Expected results: Good translations


Additional info:

Comment 1 Fedora Update System 2019-04-05 14:21:01 UTC
gnome-initial-setup-3.32.0-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-d5ee65dbc5

Comment 2 Fedora Update System 2019-04-06 18:38:19 UTC
gnome-initial-setup-3.32.0-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d5ee65dbc5

Comment 3 Fedora Update System 2019-04-09 00:03:14 UTC
gnome-initial-setup-3.32.0-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.