Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 116541 - Package depends on kill in wrong location
Package depends on kill in wrong location
Product: Fedora
Classification: Fedora
Component: redhat-lsb (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Florian La Roche
Depends On:
Blocks: FC2Target
  Show dependency treegraph
Reported: 2004-02-22 21:44 EST by Brian Bruns
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-02-26 17:36:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Modified redhat-lsb.spec file with proper path for kill (6.50 KB, text/plain)
2004-02-23 20:49 EST, Brian Bruns
no flags Details

  None (edit)
Description Brian Bruns 2004-02-22 21:44:48 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)

Description of problem:
redhat-lsb depends on the 'kill' binary in the wrong location.  It is 
expecting kill to be provided as /usr/bin/kill, and not /bin/kill.

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

How reproducible:

Steps to Reproduce:
1. Install redhat-lsb-1.3-1 package from FC development packages

Actual Results:  RPM refuses to install, because /usr/bin/kill is 

Expected Results:  Package should install cleanly

Additional info:
Comment 1 Brian Bruns 2004-02-23 20:49:49 EST
Created attachment 97970 [details]
Modified redhat-lsb.spec file with proper path for kill

I forgot to upload this yesterday.  Heres the modified spec file which fixes
the problem.
Comment 2 Stefan Hoelldampf 2004-03-06 15:20:31 EST
The problem still exists in Raw Hide, the current version
redhat-lsb-1.3-1 depends on /usr/bin/kill and conflicts with the
lastest coreutils package.

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