Bug 609748 - qt translations broken
qt translations broken
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: qt (Show other bugs)
12
All Linux
low Severity medium
: ---
: ---
Assigned To: Ngo Than
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-30 21:02 EDT by Kevin Kofler
Modified: 2010-07-13 03:43 EDT (History)
7 users (show)

See Also:
Fixed In Version: qt-4.6.3-8.fc12
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-13 03:39:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Kevin Kofler 2010-06-30 21:02:55 EDT
Description of problem:
The translations in qt are all empty files.

Version-Release number of selected component (if applicable):
qt-4.6.2-20.fc12.i686

How reproducible:
Always

Steps to Reproduce:
1. ls -l /usr/share/qt4/translations/
  
Actual results:
Files have 0 length.

Expected results:
Files have non-zero length.
Comment 1 Rex Dieter 2010-06-30 22:06:02 EDT
Seems ok for the latest build on my box,
qt-4.6.3-7.fc13.x86_64
Comment 2 Kevin Kofler 2010-06-30 23:01:11 EDT
I guess this is fixed in 4.6.3 then.
Comment 3 Fedora Update System 2010-07-12 09:13:44 EDT
qt-4.6.3-8.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/qt-4.6.3-8.fc12
Comment 4 Fedora Update System 2010-07-12 09:14:17 EDT
qt-4.6.3-8.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/qt-4.6.3-8.fc13
Comment 5 Fedora Update System 2010-07-13 03:39:26 EDT
qt-4.6.3-8.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 6 Fedora Update System 2010-07-13 03:43:01 EDT
qt-4.6.3-8.fc12 has been pushed to the Fedora 12 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.