Bug 726262 - /usr/include/openjpeg changed from directory to soft-link
Summary: /usr/include/openjpeg changed from directory to soft-link
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openjpeg
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaromír Cápík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-28 01:05 UTC by David Juran
Modified: 2016-02-01 01:55 UTC (History)
6 users (show)

Fixed In Version: openjpeg-1.4-11.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-17 00:58:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Juran 2011-07-28 01:05:46 UTC
Description of problem:
Between openjpeg-devel-1.3-10.f14 (on Fedora 14) and openjpeg-devel-1.4-6.fc15 (in Fedora 15) /usr/include/openjpeg changed form being a directory into a symlink. Unfortunately rpm (or maybe the underlying cpio) can't handle such a change (see bug 447156) but it needs to be done in a %pretransaction script or similar.

Version-Release number of selected component (if applicable):
openjpeg-devel-1.4-6.fc15

How reproducible:
Every time

Steps to Reproduce:
1. Upgrade openjpeg-devel-1.3-10.f14 to openjpeg-devel-1.4-6.fc15

  
Actual results:
Updating   : openjpeg-devel-1.4-6.fc15.x86_64                                                                                                                               882/3609 
Error unpacking rpm package openjpeg-devel-1.4-6.fc15.x86_64
error: unpacking of archive failed on file /usr/include/openjpeg: cpio: rename

Comment 1 Fedora Admin XMLRPC Client 2012-01-11 10:38:40 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Jaromír Cápík 2012-02-01 16:47:55 UTC
Hello David.

I became a new openjpeg component owner.

Even if F14 is out of support, I'm going to fix it, since it could be considered an F15 (and possibly F16) bug.

Thanks for reporting.

Regards,
Jaromir.

Comment 3 Rex Dieter 2012-02-01 16:53:48 UTC
Hi, mind fixing this in master/ branch first, then merging the changes back to older branches?

Unless you consider this worth fixing only in f15?

Comment 4 Jaromír Cápík 2012-02-01 18:26:26 UTC
Hello Rex.

I fixed f15 separately and then did the change in master and merged to f16. The git repo doesn't look well when the same changes in f16 & f17 are done separately. If there's no problem with merging the master to f15, then I'll be happy to do that. I thought it was omitted on purpose and that's why I didn't merge the f16/f17 changes to f15.

Regards,
Jaromir.

Comment 5 Fedora Update System 2012-02-01 18:55:43 UTC
openjpeg-1.4-11.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/openjpeg-1.4-11.fc15

Comment 6 Fedora Update System 2012-02-01 18:56:35 UTC
openjpeg-1.4-11.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/openjpeg-1.4-11.fc16

Comment 7 Jaromír Cápík 2012-02-01 19:08:08 UTC
Rex, we could eventually rebase the repo since all the branches are equal now. I'll do that with future changes.

Comment 8 Fedora Update System 2012-02-02 17:23:05 UTC
Package openjpeg-1.4-11.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing openjpeg-1.4-11.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1170/openjpeg-1.4-11.fc15
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2012-02-17 00:58:54 UTC
openjpeg-1.4-11.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2012-03-01 09:33:48 UTC
openjpeg-1.4-11.fc15 has been pushed to the Fedora 15 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.