Bug 127495 - libquicktime devel broken on x86-64
Summary: libquicktime devel broken on x86-64
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Other (show other bugs)
Version: Final
Hardware: x86-64 All
: P5 - None : Normal
Target Milestone: ---
Assignee: Gerd Hoffmann
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-11 07:45 UTC by Andreas Klein
Modified: 2006-01-27 16:27 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
error message when installing libquicktime devel on x86-64 (36.50 KB, image/png)
2005-10-11 07:46 UTC, Andreas Klein 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Klein 2005-10-11 07:45:08 UTC 
rpm libquicktime devel does not install on x86-64.
See yast2 sreenshot.
Comment 1 Andreas Klein 2005-10-11 07:46:20 UTC 
Created attachment 53600 [details]
error message when installing libquicktime devel on x86-64
Comment 2 Michael Gross 2005-10-11 14:02:13 UTC 
Looks like a problem with the package itself...
Comment 3 Gerd Hoffmann 2005-10-11 14:22:22 UTC 
Is this a fresh install or upgraade from 9.3?
Comment 4 Andreas Klein 2005-10-20 10:26:15 UTC 
It is a fresh installation.
Comment 5 Gerd Hoffmann 2005-10-20 12:13:16 UTC 
Hmm, not reproducable here.
What does "rpm -qf /usr/include/libquicktime" print?
Comment 6 Andreas Klein 2005-10-25 14:03:17 UTC 
donald:~ # rpm -qf /usr/include/libquicktime
error: file /usr/include/libquicktime: No such file or directory
Comment 7 Andreas Klein 2005-10-30 16:08:29 UTC 
Sorry, comment 4 was wrong. The problem only occurs on updated machines.
Comment 8 Gerd Hoffmann 2006-01-27 16:27:31 UTC 
Was probably a bad idea to replace a directory with a (compatibility) symlink, probably rpm tries to set the symlink before deleting the old directory (thats why it shows up on updates only).  Unfortunaly there is nothing I can do about that, even a you update package wouldn't fix the error at install time ...

Deinstalling and reinstalling the package should work as workaround.