On Feb 15, 2013, at 1:45 PM, jcbollinger <[email protected]> wrote:
> Curiouser and curiouser. The "1:" is an epoch number, as you probably
> recognize. I was a bit surprised that Puppet would require you to include
> it, but very surprised to find out that it fails even if you do. I do think
> it likely that the epoch number is what's tripping up Puppet, but that
> doesn't make it any less a bug. I recommend you file a ticket.
Check the epoch of the two packages. The epoch overrides all other version
comparison logic. If they have the same epoch, RPM considers them to be the
same version. I had that problem with the Oracle JDK RPMs. They all have the
epoch set to 2000, so it's impossible to either upgrade or install both
versions concurrently. I think "rpm -qip <package>" will show it, but if not
you can do "rpm -qp --queryformat='%{EPOCH}\n' <package>".
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
