> Red Hat or CentOS packages that have an epoch set can be problematic
> in this regard, since %{EPOCH} trumps %{VERSION}-%{RELEASE} when it
> comes to upgrades. I was surprised at how many packages have
> explicit epochs. On CentOS 4.0, some are quite high: aspell-en
> weighs in at 50! Try it yourself:
>
> # to sort by epoch
> rpm -qa --qf '%{EPOCH}: %{NAME}\n' | grep '^[0-9]' | sort -n
> # sort by package name
> rpm -qa --qf '%{EPOCH}: %{NAME}\n' | grep '^[0-9]' | sort -t' ' -k 2
>
> If you build your own packages, make sure that you set the epoch to
> the same level as the officially released packages; otherwise, your
> yum or up2date operations may mistakenly revert packages.
>
> --Paul Heinlein <heinlein@xxxxxxxxxx>
...and this is why I'll stick with this release. :) I don't know nothin' 'bout
birthin' no rpm from tarball! (And if you haven't seen Gone With The Wind,
that will make no sense). :)
--
<<JAV>>
