Bug 59388 - Latest errata upgrade fails to install
Latest errata upgrade fails to install
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: foomatic (Show other bugs)
7.2
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-02-06 15:53 EST by Kambiz Aghaiepour
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-02-06 15:53:20 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)

  None (edit)
Description Kambiz Aghaiepour 2002-02-06 15:53:15 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.9-21 i686)

Description of problem:
The latest errata upgrade fails with:
1:foomatic       error: unpacking of archive failed on file
/usr/share/foomatic/db/compiled: cpio rename failed - Is a directory

I was able to work around it by:

# cd /usr/share/
# mv foomatic foomatic-
# rpm -Uvh foo*rpm


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


How reproducible:
Didn't try

Steps to Reproduce:
1. The system was running roswell. 
2.  It was upgraded using standard upgrade procedure
3.  Registered in RHN
4.  up2date -d -f -u
5.  cd /var/spool/up2date
6.  rpm -Uvh *.rpm

Everything upgraded except foomatic and kdebase, both with the above cpio error.

	

Additional info:
Comment 1 Tim Waugh 2002-02-06 17:07:35 EST
From a clean Red Hat Linux 7.2 installation, all the current updates apply
cleanly. (Verified earlier today.)

Perhaps you had installed some packages that were not official errata?
Comment 2 Kambiz Aghaiepour 2002-02-06 18:08:09 EST
Did you have foomatic installed before applying errata?  Specifically, I had
problems with:

foomatic-1.1-0.20011018.7

as an errata to a 7.2 box.  (leaving as CLOSED, but please respond)
Comment 3 Tim Waugh 2002-02-06 18:15:20 EST
Yes, I did.  I was testing a foomatic/printconf errata candidate (not yet
released), and part of that test was a clean 7.2 install (including foomatic),
an update to latest errata (including foomatic-1.1-0.20011018.7), a test print,
and an upgrade to the errata candidate packages.  No cpio errors here.

/usr/share/foomatic/db/compiled is a symlink here.

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