On Tuesday, August 14, 2012 9:07:39 AM UTC-5, trey85stang wrote:
Well no go with metadata_expire or a yum clean all after updating the
repo. This appears to be a bug of some sort. Debugging output shows
before any packages checked this output:
debug: Prefetching yum resources for
Well no go with metadata_expire or a yum clean all after updating the
repo. This appears to be a bug of some sort. Debugging output shows
before any packages checked this output:
debug: Prefetching yum resources for package
debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm
dohh... I just realized this host had 2.6 installed... not 2.7.
Everything works fine on 2.7.
On Tuesday, August 14, 2012 9:07:39 AM UTC-5, trey85stang wrote:
Well no go with metadata_expire or a yum clean all after updating the
repo. This appears to be a bug of some sort. Debugging
Thanks for the replies. I will give them metadata_expire option a try and
if that doesnt work.. ill just execute a yum clean all with every internal
repo update.
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the
On Tuesday, August 7, 2012 5:46:31 PM UTC-5, trey85stang wrote:
Hey All,
I have an issue I need help working around or determining if it is a
bug
the issue is as follows, I have a custom repo(s) that has all my software
for a specific version release in it. A new version gets a
