Re: RPM doesn't do as it is told.

[Vidiot <vidiot cm nu>]

>Maybe you need to complain TO Red Hat instead of simply mouthing off.

Complaining on the mail list will let others know that following the
instructions, as written, will result in failure.

>As noted on the errata itself:
>
>	Mail problems with errata to faq-maintainer.

I will now.  Mailing problems to the faq-maintainer would not have solved the
problem.  "Mouthing off" on the mail list resulted in information that can
be sent to the maintainer, so that I can also suggest a fix.  Just sending
a messgae saying that it is broke is not helpful.

>>They also need to answer why there is a catch 22 situation for stuff
>>like this.  That is what --force is supposed to do, which it didn't.
>
>No, that's what *you* think "--force" is supposed to do.  You are
>simply incorrect in your understanding.  "Force" is used as in "force
>the replacement of existing files and packages", not as in "force the
>breaking of dependencies".  Perhaps you'd prefer something more precise,
>like "--force-replacing-files-and-packages-but-dont-break-dependencies"
>instead?  =)

Read what you just wrote: "Force" is used as in "force the replacement of
existing files and packages."

Excuse me, but that is exactly what I was trying to do, replace existing
files and packages.  By your own definition, force doesn't "force."  Your
long --force definition needs to have that information in the man page.  If
you look at --force, and the three options it is equal to, it DOES NOT
say that it will not break dependencies.  It implies exactly what I thought
it would do.  If --force won't break dependencies, the man page should say
so and reference the reader to --nodeps.

Who do I send man page fixes to?  Since you work for Redhat, maybe you
could pass along the fix to the RPM man page maintainer, as you probably
know who that is.  I certainly don't.

>>A user should not have to uninstall a package in order to upgrade it.
>>That is what -U (Upgrade) is all about.  It isn't an upgrade if you have
>>to uninstall first.
>
>Duh.

Gee, I think there was agreement there.

You have to keep in mind that you know how RPM works, at least I assume that
you do, but there are many others who do not.  When the instructions on the
web sites fail, one looks at the man page.  The first option that gives a
hint that it will do the job is --force, which it obviously doesn't.  The
--nodeps is further down the man page, not seen on an 80x24 Xterm.

I hope you can understand the problem from a newuser viewpoint.  I've been
using Linux for years, but normally gor the sources and recompiled and
installed.  It is only recently that I have been dealing with RPMs for
upgrades and it hasn't been a pleasant experience.  Once one figures out
the idiosyncrocies, it will go smoother.

MB
-- 
e-mail: vidiot cm nu
        [Where do you think Microsoft would be today if they waited]
        [until their software worked?     (Hyperion Bay - 10/12/98)]
Visit - URL:http://www.vidiot.com/  (Your link to Star Trek and UPN)