NM key hassle

[Bill Crawford]

On Wednesday 11 March 2009 23:31:50 Tom Horsley wrote:
> On Thu, 12 Mar 2009 09:20:12 +1030
>
> Tim wrote:
> > > There's no reason to do any of these unless there's something actually
> > > wrong.
> >
> > Seconded.  When things are working fine, yum takes care of itself.
>
> The most suspicious thing I get is I often see something about
> "current <something or other> is newer than copy in repo, using
> current copy". I assume that is just an out of date repo, but
> I often see it several days in a row in my cron output (I have
> a downloadonly update run in cron every night so the packages
> will be there when I want to install). I always wonder when I
> see that same message for several days running just how long
> some repos stay out of sync or if I have a wacko copy with the
> wrong date I downloaded when some repo was busted.

This usually means that the timestamp is different, which suggest either a 
mirror using the wrong options to "rsync" or you hit it during a sync before 
the timestamp was fixed (rsync will update the file timestamp after it has 
sync-ed the contents). Have a look at the time on your local copy of the file, 
then look at the repodata directory on the mirror and see what the difference 
is; if it's an hour apart, there's a timezone issue somewhere :o)