Bug 88816 - installing source RPM installs SPEC with wrong name
Summary: installing source RPM installs SPEC with wrong name
Status: CLOSED DUPLICATE of bug 87402
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: openssl096   
(Show other bugs)
Version: 9
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: Brian Brock
URL:
Whiteboard: triage|leonardjo|closed|duplicate
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-04-14 15:32 UTC by Scott Sibert
Modified: 2007-04-18 16:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 18:52:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Scott Sibert 2003-04-14 15:32:31 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
Installing the source RPM installs the SPEC as openssl.spec instead of 
openssl096.spec.  This actually also is a problem in openssl096b which does 
the same thing of installing its SPEC as openssl.spec instead of 
openssl096b.spec.  If you install all three openssl source packages, the spec 
that exists is from the last RPM installed.  This could lead to confusing 
errors when compiling sources.

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

How reproducible:
Always

Steps to Reproduce:
1. Install openssl096-0.9.6-15.src.rpm
2. Look in /usr/src/redhat/SPECS
3.
    

Actual Results:  openssl.spec

Expected Results:  openssl096.spec

Additional info:

openssl, openssl096 and openssl096b source packages all write their SPEC as 
openssl.spec, thus overwriting each other.

Comment 1 Leonard den Ottolander 2004-11-13 18:25:33 UTC

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

Comment 2 Red Hat Bugzilla 2006-02-21 18:52:40 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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