Bug 184503 - Amaya refuses to execute because of broken symlink
Summary: Amaya refuses to execute because of broken symlink
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: amaya
Version: rawhide
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Aurelien Bompard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-03-09 12:07 UTC by Joachim Frieben
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-03-12 13:04:50 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
"amaya-9.1-11.fc5" file list (80.41 KB, text/plain)
2006-03-09 12:07 UTC, Joachim Frieben
no flags Details

Description Joachim Frieben 2006-03-09 12:07:15 UTC
Created attachment 125869 [details]
"amaya-9.1-11.fc5" file list

Comment 1 Joachim Frieben 2006-03-09 12:07:15 UTC
Description of problem:
Amaya refuses to execute because of broken symlink. The symbolic link
"amaya-gtk" is wrong and points nowhere:

  "amaya-gtk -> /usr/lib/Amaya-*/gtk/bin/amaya"
                              ^^^

Version-Release number of selected component (if applicable):
amaya-9.1-11.fc5

How reproducible:
Always

Steps to Reproduce:
1. Execute "amaya"
  
Actual results:
Shell reports "amaya: Command not found."

Expected results:
Amaya should execute as expected.

Additional info:
Apart from this bug in the spec file, it is puzzling that different
version numbers (8.7.2 and 9.1) appear in the package (see attached
file list). Moreover, the current release is already 9.4 and not 9.1.

Comment 2 Joachim Frieben 2006-03-09 12:22:57 UTC
Once, the symlink link is set correctly:

   "amaya-gtk -> /usr/lib/Amaya-8.7.2/gtk/bin/amaya",

the program can be started. However, "Help -> About Amaya" reports it
to be version 8.7.2 and not even 9.1.

Comment 3 Aurelien Bompard 2006-03-12 13:04:50 UTC
Fixed in release 12, thanks.


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