Bug 877840 - /sbin/ldconfig: relative path `1' used to build cache
Summary: /sbin/ldconfig: relative path `1' used to build cache
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: dmraid
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: LVM and device-mapper development team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 677744 879418 882991 893384 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-19 02:13 UTC by Ralf Corsepius
Modified: 2013-05-13 07:24 UTC (History)
14 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-12 00:13:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ralf Corsepius 2012-11-19 02:13:09 UTC
Description of problem:

During an attempt to upgrade a f17 installation to current f18, following the procedures described in https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum#Fedora_17_-.3E_Fedora_18

I am facing the following postun-scriptlet failure:
...
 Cleanup    : dmraid-1.0.0.rc16-16.fc17.i686                                                                                                                                   2065/3585 
Non-fatal POSTUN scriptlet failure in rpm package dmraid-1.0.0.rc16-16.fc17.i686
  Cleanup    : prelink-0.4.6-5.fc17.i686                                                                                                                                        2066/3585 
/sbin/ldconfig: relative path `1' used to build cache
warning: %postun(dmraid-1.0.0.rc16-16.fc17.i686) scriptlet failed, exit status 1

Comment 1 Adam Tkac 2012-11-26 15:53:23 UTC
*** Bug 677744 has been marked as a duplicate of this bug. ***

Comment 2 Adam Tkac 2012-11-26 15:54:37 UTC
*** Bug 879418 has been marked as a duplicate of this bug. ***

Comment 3 Adam Tkac 2012-11-26 15:57:15 UTC
There is very simple fix for this annoying issue. You can use either remove the "# 1. Main package" comment from dmraid.spec or remove the "-p" switch from the %postun scriptlet.

Comment 4 Fedora Update System 2012-11-28 09:36:04 UTC
dmraid-1.0.0.rc16-18.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/dmraid-1.0.0.rc16-18.fc18

Comment 5 Fedora Update System 2012-11-28 21:11:43 UTC
Package dmraid-1.0.0.rc16-18.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dmraid-1.0.0.rc16-18.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-19295/dmraid-1.0.0.rc16-18.fc18
then log in and leave karma (feedback).

Comment 6 Peter Rajnoha 2012-12-03 15:56:08 UTC
*** Bug 882991 has been marked as a duplicate of this bug. ***

Comment 7 Peter Rajnoha 2013-01-09 10:05:14 UTC
*** Bug 893384 has been marked as a duplicate of this bug. ***

Comment 8 Fedora Update System 2013-01-12 00:13:55 UTC
dmraid-1.0.0.rc16-18.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Pay87 2013-05-11 19:52:22 UTC
I still got the failure message while updating:

warning: %postun(dmraid-1.0.0.rc16-17.fc18.x86_64) scriptlet failed, exit status 1
Non-fatal POSTUN scriptlet failure in rpm package dmraid-1.0.0.rc16-17.fc18.x86_64

Comment 10 Peter Rajnoha 2013-05-13 07:24:41 UTC
(In reply to comment #9)
> I still got the failure message while updating:
> 
> warning: %postun(dmraid-1.0.0.rc16-17.fc18.x86_64) scriptlet failed, exit
> status 1
> Non-fatal POSTUN scriptlet failure in rpm package
> dmraid-1.0.0.rc16-17.fc18.x86_64

POSTUN scriptlets are run from old packages on update to new packages.

So if you're updating to dmraid-1.0.0.rc16-18.fc18, you still get the error message from the previous one dmraid-1.0.0.rc16-17.fc18.x86_64.

So what you see is OK. The error will be gone completely only if updating to (future) dmraid-1.0.0.rc16-19.fc18 and higher.


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