| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
Once again, thanks to the many who responded or are "lurking on the
list" (and responded quickly I might add):
Mark Ferlatte
Thein Vu
Mark Neill
Casper Pedersen
bishop
Red Lloyd
Brian Wilson
Darrell Parlee
Matthew MacIntyre
Joshua Franklin
Donald Altman
kwylie
Stu Tomlinson
Yura Pismerov
Scott Kruger
Caleb Jordan
Warren Togami, and,
Kid
Throughout, my comments are in {}.
Solution to the first problem:
Specify both rpms on the same line, "rpm won't let the RPM database be
inconsistent, so you need to give it
enough information to maintain that consistency." "rpm will get smart
and realize you're installing the needed dependency."
rpm -Fvh krb5-devel-1.2.2-12.i386.rpm krb5-libs-1.2.2-12.i386.rpm
For the second general question, I received a great deal of advice that
I will put to good use:
- "Of course, the best route is to use Debian, since they have a
superior
package manager, but that's a whole nother subject :)"
- "What I do is just download everything in the appropriate updates
folder from
the ftp site, and update accordingly. Red Hat always removes the
older
packages when a new one arrives (as you noticed), which leaves only the
newest
updates to apply. The order of installation, in the vast majority of
cases,
isn't that important."
- "Now, for simpler updates, you might try apt-rpm from
http://freshrpms.net/apt
The only problem with it is that there are relatively few mirrors and
they really focus on the latest (i.e., 7.2) release.
There is of course also the RedHat up2date service, but I'm assuming
from
your post that you're not subscribed to that."
- "As for the Red Hat errata, I have discussed the lack of references
with
them before. There is an "Obsoletes" field on the errata web page,
but
they do not consistenly fill it in when an errata replaces an older
errata
with a different number. The "Obsoletes" field gives a reference to
the
older errata that is being replaced. When I complained, one of the
comments that they made was that few people go through the errata pages
in
chronological order so they don't get much feedback about the pages.
I have also suggested to them that they should add an "Obsoleted By"
field
so there is a forward reference. I want that field because I often
see
references to specific Red Hat Security Advisories. If I go to that
advisory, there is no easy way to find out if there is another later
advisory that has replaced this one.
I suggest that you send an email to Red Hat commenting on the poor
state of
backward and forward references in the errata. If enough people
complain
they may change it."
- "up2date is OK if you *only* use RH bits and pieces, it can cause you
to run
around in circles if you use Ximian's desktop / red-carpet as well
though.
One trick you might want to try would be to gather all the updated rpms
in
one place, and just do:
rpm -Fvh *.rpm
and let RPM figure out all the issues.
One problem you might have with this is if an updated package is now
two
packages where it used to be one - "F" only upgrades packages
currently
installed, so would fail on that (redhat typically do this when
upgrading
libraries, but keeping the old one around for backwards compatibility
and
dependancy resolution).
You could use "rpm -Uvh *.rpm" which would upgrade _or install_ all
packages - so anything you have in that directory that isn't already
installed would get installed. Use only if you know you only have the
upgrades you need in that directory."
- "-Uhv --nodeps
And don't worry, everything will be ok."
- "1) I highly recommend moving directly to 7.2. The 7.0 release was
really crappy.
2) After an install, I generally download all of the updates and
do an
rpm -Uvh *.rpm and then try to deal with the dependencies from
there.
Generally this method is very good at avoiding dependency problems
within a group (such as kde, krb5, ...)" {based on one of the
previous comments, I think
that you need to download only the updates that you need so that
you aren't installing
stuff you do not need}
- "Two questions:
1. Why Red Hat 7.0? You will have considerably less problems with
the
latest version 7.2, although you are right, 7.0 will work fine
after
patching. {when I started this process, some of the other software
that we
needed to install had 7.0 as one of its dependencies, although I
was checking
the varous sites out yesterday and they may all work ok under 7.2
now}
2. Have you tried up2date? You can create a free RHN account and
use
the one free entitlement to update your machine automatically. The
old
version of Red Hat had some initial problems with up2date so you
may
need to upgrade that package before running it, but after that it
should
be very problem free and easy.
Run "rhn_register" to create your RHN account.
Then "up2date" in X to run the GUI version, or "up2date -u" to do
an
automatic upgrade of all installed packages.
Again I highly recommend Red Hat 7.2 with up2date, but it is your
choice."
Thanks once again everyone,
Dave
>>> "Dave Warchol" <Warchol@harthosp.org> 04/08/02 01:57PM >>>
Hello Managers:
I am building a RH7.0 web server and have one immediate
problem and a general question about the process of building a system
that is patched up to date. I installed 7.0 from the CD's, no problem.
My approach is to apply all of the Red Hat Errata (General Advisories,
Bug Fixes and Enhancements) in ascending date order of release, I am
assuming that this is a logical approach. The immediate problem is in
upgrading from krb5-devel and krb5-libs -1.2.1-8 to 1.2.2-12, as
follows:
[root@hclxtstest01 rh70_errata]# rpm -qa | grep krb5
krb5-devel-1.2.1-8
krb5-libs-1.2.1-8
[root@hclxtstest01 rh70_errata]# rpm -Fvh krb5-devel-1.2.2-12.i386.rpm
error: failed dependencies:
krb5-libs = 1.2.2-12 is needed by krb5-devel-1.2.2-12
[root@hclxtstest01 rh70_errata]# rpm -Fvh krb5-libs-1.2.2-12.i386.rpm
error: failed dependencies:
krb5-libs = 1.2.1 is needed by krb5-devel-1.2.1-8
[root@hclxtstest01 rh70_errata]#
I'm not sure how to proceed. Do I freshen -libs with --nodeps and
then
freshen -devel? It is a catch-22. Any advice is appreciated.
On a general note. When applying the errata in ascending date order I
find that the rpm's described in the detailed documentation on Red
Hat's
site are not always there, having been replaced by newer versions,
usually described in a later errata. Sometimes in the later errata
there is mention of the newer errata superceding an earlier one
(sometimes not). It gets somewhat confusing. Is a better approach to
use Red Hat's up2date? Any experiences with up2date? I have had more
experience with Solaris where the approach has been to lay down the
base
OS and then apply all of the recommend patches, historically, for me,
this has been a relatively painless experience.
Thanks much,
Dave
submissions: LinuxManagers@linuxmanagers.org
subscribe/unsubscribe:
http://www.linuxmanagers.org/mailman/listinfo/linuxmanagers
_______________________________________________
LinuxManagers mailing list - http://www.linuxmanagers.org
submissions: LinuxManagers@linuxmanagers.org
subscribe/unsubscribe: http://www.linuxmanagers.org/mailman/listinfo/linuxmanagers
[Home] [Kernel List] [Linux SCSI] [Video 4 Linux] [Linux Admin] [Yosemite News] [Motherboards]