 | | | ES3 update 8 has severe problems with | ES3 update 8 has severe problems with 2006-07-24 - By orrie
Back
Leinweber, James <jiml@(protected)> writes:
>
> On any server with the "pvm" package installed, which seems to creep
> in by default, running "up2date -u" on 2006-July-20 (See http://uly-20.ora-code.com) dies with the
> message:
>
> error: unpacking of archive failed on file
> /usr/share/pvm3/bin/LINUXI386: cpio: rename failed - Is a directory
>
> This leaves the system in a very unfortunate state, with the updates
> partially applied, and about 50 RPM's missing in action, including
> rather important things such as "openssh-server". With a lot of
> hand work using "rpm", 'find ... -name "*.rpm*" -print' and the like I
> was able to get a couple of systems past that. Examples of the kind
> of things that helped me the most are:
>
> # clean large objects out of /usr to avoid undue *.rpmnew files
> # and /usr mis-estimates of available space
> # people who use them reinstall with rpm -i or up2date afterwards
>
> rpm -e psgml apel-xemacs emacs emacs-leim xemacs xemacs-el \
> xemacs-info openoffice.org openoffice.org-i18n openoffice.org-libs
>
> In a fairly clean /var/spool/up2date or other hand directory with
> only the downloaded update 8 rpm files:
>
> rm pvm*
> rpm -Fvh --force up2date*rpm rpm*rpm
> rm up2date* rpm*
> rpm -Fvh kernel-{util,doc,source}*rpm
> rm kernel-{util,doc,source}*rpm
> rpm -Uvh --force *.rpm
> up2date -p
> up2date kernel-utils kernel # or kernel-smp, or whatever
>
> This may leave you with about 900 *.rpmorig or *.rpmnew conflicts to
> resolve, particularly if you have squid installed, but less than a
> dozen are real, so doing something like:
>
> find /etc /usr -type f -ctime -1 -name "*.rpm*" -print |
> while read f; do if cmp -s $f ${f%.rpm*}; then rm $f; fi; done
>
> may improve the situation a lot.
>
>
> a) is anyone else having this problem?
>
> b) BEWARE! You probably want to avoid running "up2date" on systems
> with "pvm" installed unless you are a masochist.
>
> c) applying update 8 using Redhat Network went very smoothly for me on
> a system which didn't have "pvm" installed.
>
> I note that
> rpm -q --whatrequires pvm
> didn't suggest any dependencies, so those of us not doing parallel
> distributed programming may want to do "rpm -e pvm; up2date -p" as
> a workaround before trying to apply update 8.
>
We have over 250 RedHat WS 3 update 8 systems running and all of the ones which
had the pvm package failed in a similar manner to yours. Furthermore, if you
remove the pvm package with an "rpm -e pvm" and then try to reinstall it with an
"up2date -i pvm", you will receive the following. You also receive this same
error when trying to install pvm on a WS 3 update 8 system which did not have
pvm installed previously. It appears this package was not properly built before
being added. Anyone else receive similar results?
orrie@(protected) > up2date -i pvm
Fetching Obsoletes list for channel: rhel-i386-ws-3...
Fetching rpm headers...
########################################
Name Version Rel
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -----
pvm 3.4.5 6_EL3 i386
Testing package set / solving RPM inter-dependencies...
########################################
pvm-3 (See http://pvm-3.ora-code.com).4.5-6_EL3.i386.rpm: ########################## Done.
Preparing ########################################### [100%]
Installing...
1:pvm ########################################### [100%]
error: unpacking of archive failed on file /usr/share/pvm3/bin/LINUXI386: cpio:
rename
There was a fatal RPM install error. The message was:
There was a rpm unpack error installing the package: pvm-3 (See http://pvm-3.ora-code.com).4.5-6_EL3
Orrie
--
Taroon-list mailing list
Taroon-list@(protected)
https://www.redhat.com/mailman/listinfo/taroon-list
|
|
|