Bug 1361764 - Please update gettext in F23 to 0.19.8
Summary: Please update gettext in F23 to 0.19.8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gettext
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Daiki Ueno
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-30 07:49 UTC by Thomas Moschny
Modified: 2016-08-09 21:23 UTC (History)
4 users (show)

Fixed In Version: gettext-0.19.8.1-1.fc23
Clone Of:
Environment:
Last Closed: 2016-08-09 21:23:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Thomas Moschny 2016-07-30 07:49:29 UTC
Since 0.23.3, Shotwell uses gettext also for translating its .desktop files. With gettext 0.19.7 as present in F23, this fails for the Keyword= entry, leaving some binary garbage in that line and resulting in an invalid .desktop file.

With gettext 0.19.8 this works as expected.

So, would it be possible to update gettext in F23?

Comment 1 Thomas Moschny 2016-07-31 07:39:10 UTC
For the record, the bug that hits Shotwell's .desktop file is this:

http://savannah.gnu.org/bugs/?47991

Comment 2 Fedora Update System 2016-07-31 08:57:41 UTC
gettext-0.19.8.1-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-8f104bcafb

Comment 3 Fedora Update System 2016-08-01 20:54:21 UTC
gettext-0.19.8.1-1.fc23 has been pushed to the Fedora 23 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-2016-8f104bcafb

Comment 4 Fedora Update System 2016-08-09 21:23:27 UTC
gettext-0.19.8.1-1.fc23 has been pushed to the Fedora 23 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.