Bug 989891 - gimp-normalmap own wrong directory
Summary: gimp-normalmap own wrong directory
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gimp-normalmap
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Patrick Uiterwijk
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-30 06:43 UTC by Vasiliy Glazov
Modified: 2013-10-06 01:27 UTC (History)
2 users (show)

Fixed In Version: gimp-normalmap-1.2.3-6.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-06 01:27:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Vasiliy Glazov 2013-07-30 06:43:29 UTC
Description of problem:
Package gimp-normalmap own wrong directory
/usr/lib64/gimp/2.0/plug-ins

It not needed because this directory owned by gimp and gimp is dependency for gimp-normalmap.

Version-Release number of selected component (if applicable):
gimp-normalmap-1.2.3-4.fc20.x86_64

Please remove this directory from filelist.

Comment 1 Fedora Update System 2013-09-02 18:57:07 UTC
gimp-normalmap-1.2.3-6.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/gimp-normalmap-1.2.3-6.fc19

Comment 2 Fedora Update System 2013-09-03 22:24:43 UTC
Package gimp-normalmap-1.2.3-6.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gimp-normalmap-1.2.3-6.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-15704/gimp-normalmap-1.2.3-6.fc19
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2013-10-06 01:27:52 UTC
gimp-normalmap-1.2.3-6.fc19 has been pushed to the Fedora 19 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.