Bug 1258110 - gedit rpm creates directory /usr/@DATADIRNAME@/...
gedit rpm creates directory /usr/@DATADIRNAME@/...
Product: Fedora
Classification: Fedora
Component: gedit (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
: 1266749 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2015-08-29 03:45 EDT by Sutóczki Miklós
Modified: 2015-12-02 13:17 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-12-02 10:09:35 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sutóczki Miklós 2015-08-29 03:45:05 EDT
Description of problem:
gedit creates directory /usr/@DATADIRNAME@/locale/ and installs a lot of files (looks like gedit localization files) to its subdirs. Removing gedit deletes all the files, but remains /usr/@DATADIRNAME@/locale/ and many empty directories under it.

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

Fedora 21 x86_64

How reproducible:


Steps to Reproduce:

$ yum install gedit

$ rpm -ql gedit

Actual results:


Expected results:


Additional info:

Similar to https://bugzilla.redhat.com/show_bug.cgi?id=1222131
Comment 1 Ilja Sekler 2015-09-20 12:50:08 EDT
This seems to be a bug in intltool-0.50.2 used on a build system where the gedit package has been built.

To fix the issue for me, I updated intltool to the version 0.51.0 generated from intltool-0.51.0-1.fc22.src.rpm on my Fedora 21 system and then rebuilt gedit-3.14.4-1.fc21.x86_64 from its source RPM using this updated intltool.

Any plans to give some love to Fedora 21 build machines?
Comment 2 Ilja Sekler 2015-09-20 15:40:43 EDT
Actually, I think this bug could be duped to https://bugzilla.redhat.com/show_bug.cgi?id=1206156 as the intltool patch mentioned there would fix the gedit packaging issue.
Comment 3 c72578 2015-10-23 08:11:17 EDT
*** Bug 1266749 has been marked as a duplicate of this bug. ***
Comment 4 c72578 2015-10-23 08:15:13 EDT
Patched rpms for testing are available here:

Patch used from:
Comment 5 Fedora End Of Life 2015-11-04 05:03:26 EST
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2015-12-02 10:09:44 EST
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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