Bug 455021 - tor-lsb installation fails on x86_64
tor-lsb installation fails on x86_64
Status: CLOSED DUPLICATE of bug 375361
Product: Fedora
Classification: Fedora
Component: tor (Show other bugs)
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Enrico Scholz
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-07-11 10:44 EDT by Sameh Attia
Modified: 2008-07-20 07:55 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-07-20 07:55:05 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
libdir fix for x86_64 platforms (511 bytes, patch)
2008-07-11 10:44 EDT, Sameh Attia
no flags Details | Diff

  None (edit)
Description Sameh Attia 2008-07-11 10:44:15 EDT
Description of problem:
When installing the below version using apt-get the installation fails with the
following error.

/var/tmp/rpm-tmp.20506: line 1: /usr/lib/lsb/install_initd: No such file or
error: %post(tor-lsb- scriptlet failed, exit status 127

Also this happens when removing it too.

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

How reproducible:
Just install the tor package and the error above will appear or you can remove
it too and will happen.

Steps to Reproduce:
Actual results:
Error message.

Expected results:
Installs cleanly.

Additional info:
I guessed it should be a problem with the spec file in the post and preun
sections which does not account for x86_64 platforms where the lsb scripts are
under /usr/lib64 not /usr/lib of i38t6 platforms. So I did download the SRPM and
modified the spec file and attached a patch that fixes this problem.
Comment 1 Sameh Attia 2008-07-11 10:44:15 EDT
Created attachment 311586 [details]
libdir fix for x86_64 platforms
Comment 2 Enrico Scholz 2008-07-20 07:55:05 EDT

*** This bug has been marked as a duplicate of 375361 ***

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