Bug 677749 - postun scriptlet failure
Summary: postun scriptlet failure
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: rpcbind
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-15 18:02 UTC by Rahul Sundaram
Modified: 2014-10-23 18:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-23 18:18:01 UTC
Type: ---

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

Description Rahul Sundaram 2011-02-15 18:02:49 UTC 
Description of problem:

 Cleanup    : rpcbind-0.2.0-9.fc15.x86_64                                                                                                         2348/3556 
Non-fatal POSTUN scriptlet failure in rpm package rpcbind
  Cleanup    : passwdqc-1.2.2-1.fc15.x86_64                                                                                                        2349/3556 
warning: %postun(rpcbind-0.2.0-9.fc15.x86_64) scriptlet failed, exit status 1
  Cleanup    : ftp-0.17-51.fc12.x86_64                                                                                                             2350/3556 
  Cleanup    : libproxy-bin-0.4.6-3.fc15.x86_64
Comment 1 Fedora End Of Life 2013-04-03 17:42:25 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Comment 2 Steve Dickson 2014-10-23 18:18:01 UTC 
I am unable to reproduce these in f20 or f21....
Note You need to log in before you can comment on or make changes to this bug.