I've pushed ahead a bit further and this is what I'm finding.
The three RPMs that are causing problems for me are gmc, pine, and userdrake.
The first time I tried to update them, I got the "hard drive thrashing and X
frozen" behaviour. The second time (after rebuilding the RPM database), I got
the "package_name already installed message" despite the fact that it was
still showing up in the "available but not yet installed" list.
What I ended up doing was "rpm -q package_name" so that both versions of the
package were named. Then "rpm -e package_name_version_number" to explicitly
delete each version. Then ran Update again and installed the updated version.
This worked but, of course, shouldn't have been necessary.
M.
On Thursday 29 March 2001 16:48, Jim Nuytens wrote:
> On Thu, 29 Mar 2001 10:11:16 -0800, Michael O'Henly wrote:
>
> (all the sorrid details of Mandrake Update weirdness snipped for
> brevity)
>
> Well, I was going to ask the same question. I've got a similar
> situation going on with Corporate Server 1.0.1.
>
> I did an upgrade from 1.0 to 1.0.1. When it was finished, I brought the
> system up as normal and decided to run Mandrake Update just to see if
> there was anyting I missed.
>
> In the list of updates available are the 2.2.16 kernal RPMs. This is
> very weird because the currently installed kernel (via selecting
> upgrade during the install) is 2.2.17. It used to be 2.2.15.
>
> Anyone want to venture a quess as to why I'm seeing updates for the
> 2.2.16 kernel?
>
> Oh, and I'm also seeing other packages showing up like Mike described.
--
Michael O'Henly
TENZO Design
