Bug 57365 – Fails to build with pam-0.75-20

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 57365 - Fails to build with pam-0.75-20

Summary:	Fails to build with pam-0.75-20

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Raw Hide
Classification:	Retired
Component:	XFree86 (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Mike A. Harris
QA Contact:	David Lawrence
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-12-10 16:15 EST by Enrico Scholz
Modified:	2007-04-18 12:38 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-12-29 13:11:55 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

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

Groups: None (edit)

Description Enrico Scholz 2001-12-10 16:15:46 EST

Description of Problem:

When trying to rebuild XFree86-4.1.0-8 with installed pam-devel-0.75-20 I get:

| $ LANG=C rpm --rebuild XFree86-4.1.0-8.src.rpm 
| Installing XFree86-4.1.0-8.src.rpm
| error: failed build dependencies:
|         /lib/libpam.so   is needed by XFree86-4.1.0-8


pam-devel provides /usr/lib/libpam.so but not /lib/libpam.so.

Comment 1 Mike A. Harris 2001-12-29 13:11:50 EST

pam package *used* to provide /lib/libpam.so symlinks because 7.x
had it stored there.  It is not possible for me to make one single
XFree86 src.rpm package that compiles everywhere with any pam package.
The 4.1.0 packages will remain as they are, for 7.x compatibility.

When 4.2.0 is ready, I may change this, but IMHO it is a pam package
backward compatibility issue.

Comment 2 Mike A. Harris 2002-01-23 11:52:59 EST

Works for me in 4.1.0-15 ok using a build system with all updates
applied.

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