[coyotos-dev] build error
Jonathan S. Shapiro
shap at eros-os.com
Mon Jun 18 15:44:37 EDT 2007
On Mon, 2007-06-18 at 11:37 -0700, Charles Landau wrote:
> At 10:48 AM -0400 6/18/07, Jonathan S. Shapiro wrote:
> >This smells a lot like you haven't got the latest libsherpa installed.
> >When was the last time you ran 'yum update'?
>
> I had run:
> yum update coyotos-i386-xenv
> and it reported:
> Could not find update match for coyotos-i386-xenv
> No Packages marked for Update/Obsoletion
You should simply be able to run 'yum update'. And of course, for CapROS
you would have wanted capros-i386-xenv.
What is a bit disturbing here is that an unqualified 'yum update' didn't
catch these.
capros-i386-xenv is a "virtual" package. It exists purely to get all of
the necessary dependencies installed. the capros-i386-xenv package
itself doesn't get updated unless we add/drop a package. For this
reason, updating almost never accomplishes anything.
You want to be in the habit of running 'yum update' at least weekly to
get security updates to your linux install. If you are at the end of a
slow link, you may wish to consider running (as root):
chkconfig yum-updatesd on
and then either reboot or type
service yum-updatesd start
This will cause packages to be downloaded in the background. They won't
be installed until you run 'yum update', but at least they will be
prefetched.
Fedora generally checks if updates are called for each time you log in.
If you are in the habit (as I am) of leaving your development machine
logged in most of the time, this check doesn't get run often enough, and
it becomes important to update by hand.
shap
--
Jonathan S. Shapiro, Ph.D.
Managing Director
The EROS Group, LLC
More information about the coyotos-dev
mailing list