Bug 88813 – installing libxml2 source installs SPEC with incorrect name

Bug 88813 - installing libxml2 source installs SPEC with incorrect name

Summary:	installing libxml2 source installs SPEC with incorrect name

Status:	CLOSED DUPLICATE of bug 86118

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	libxml2 (Show other bugs)
Sub Component:
Version:	9
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Daniel Veillard
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-04-14 11:13 EDT by Scott Sibert
Modified:	2007-04-18 12:53 EDT (History)
CC List:	0 users

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

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Scott Sibert 2003-04-14 11:13:10 EDT

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
When you install libxml2-2.5.4-1.src.rpm on i386 platform, it installs the 
spec as libxml.spec (overwriting the spec from libxml) instead of libxml2.spec.

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

How reproducible:
Always

Steps to Reproduce:
1. Install libxml2-2.5.4-1.src.rpm
2. Look in /usr/src/redhat/SPECS/
3.
    

Actual Results:  SPEC created as libxml.spec

Expected Results:  SPEC created as libxml2.spec

Additional info:

If you install both libxml and libxml2, the spec that exists will be the one 
from the package that installed last, leading to possibly confusing errors.

Comment 1 Daniel Veillard 2003-04-14 11:47:47 EDT

Fixed in any version post 2.5.4, duplicate of bug #86118,

Daniel

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

Comment 2 Red Hat Bugzilla 2006-02-21 13:52:40 EST

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.