Bug 2001222 - /usr/bin/kajongg is a broken symlink, cannot easily run the app
Summary: /usr/bin/kajongg is a broken symlink, cannot easily run the app
Keywords:
Status: CLOSED DUPLICATE of bug 1973997
Alias: None
Product: Fedora
Classification: Fedora
Component: kajongg
Version: 34
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-04 13:28 UTC by Alexander Potashev
Modified: 2021-09-06 09:19 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-09-06 09:19:12 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Alexander Potashev 2021-09-04 13:28:10 UTC 
Description of problem:
/usr/bin/kajongg is a broken symlink, cannot easily run the app.

$ ls -l /usr/bin/kajongg
lrwxrwxrwx 1 root root 62 Jun 12  2020 /usr/bin/kajongg -> /builddir/build/BUILD/kajongg-20.04.1/share/kajongg/kajongg.py

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Yaroslav Sidlovsky 2021-09-04 13:30:55 UTC 
There is warnings about symlinks in build.log:
```
warning: absolute symlink: /usr/bin/kajongg -> /builddir/build/BUILD/kajongg-20.08.0/share/kajongg/kajongg.py
warning: absolute symlink: /usr/bin/kajonggserver -> /builddir/build/BUILD/kajongg-20.08.0/share/kajongg/kajonggserver.py
```

(see: https://kojipkgs.fedoraproject.org//packages/kajongg/20.08.0/2.fc34/data/logs/noarch/build.log).
Comment 2 Yaroslav Sidlovsky 2021-09-04 13:40:06 UTC 
Note that executable bit is not set for the "/usr/share/kajongg/kajongg.py" (and for "kajonggserver.py" too).
So fixing just symlink is not enough.
Comment 3 Yaroslav Sidlovsky 2021-09-04 13:47:48 UTC 
Package built for Fedora 34 also is affected by this issue.
Comment 4 Than Ngo 2021-09-06 09:19:12 UTC 

*** This bug has been marked as a duplicate of bug 1973997 ***
Note You need to log in before you can comment on or make changes to this bug.