Bug 592721

Summary:	after yum downgrade ldconfig needs to be run manually
Product:	[Fedora] Fedora	Reporter:	Till Maas <opensource>
Component:	rpm	Assignee:	Panu Matilainen <pmatilai>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	12	CC:	ffesti, james.antill, jnovy, maxamillion, pmatilai, tim.lauridsen
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-12-03 14:40:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Till Maas 2010-05-16 14:41:48 UTC

Description of problem:
I installed a custom build pam_mount / libHX and after downgrading I had to run ldconfig manually to get pam_mount to work again.


Version-Release number of selected component (if applicable):
yum-3.2.27-3.fc12


How reproducible:
always


Steps to Reproduce:
1. build libHX-3.4-1.fc12 and pam_mount-2.1-1.fc12 using the SPECs from rawhide
2. install both
3. downgrade both
4. run /sbin/mount.crypt (untested, whether this really causes the error, but it should)


Actual results:
libHX.so.22: cannot open shared object file: No such file or directory


Expected results:
libHX.so.22 should be found, because it is provided by libHX.

Comment 1 seth vidal 2010-05-16 21:48:38 UTC

Panu,
 Does rpm.RPMPROB_FILTER_OLDPACKAGE disable scriptlet execution?

Comment 2 Panu Matilainen 2010-05-17 06:15:40 UTC

No, but rpm < 4.8.0 skips "redundant" -p /sbin/ldconfig scripts, which can cause problems when library version is decremented (such as on downgrade). I guess I should finally eliminate the broken ldconfig optimization out from F12 too.

Comment 3 Bug Zapper 2010-11-03 14:48:05 UTC

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Bug Zapper 2010-12-03 14:40:04 UTC

Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.