Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Puppet Users
Home
+ new post
About this group
Join this group
Message from discussion puppet thinks yum fails when it doesn't
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Jos Backus  
View profile  
 More options May 25 2008, 10:32 pm
From: Jos Backus <j...@catnook.com>
Date: Sun, 25 May 2008 19:32:16 -0700
Local: Sun, May 25 2008 10:32 pm
Subject: Re: [Puppet Users] Re: puppet thinks yum fails when it doesn't
Print | View thread | Show original | Report this message | Find messages by this author

On Sun, May 25, 2008 at 07:25:38PM -0500, Luke Kanies wrote:
> > Just so I understand you correctly: the yum provider works but the  
> > debug
> > output is misleading because of the limited provider testing  
> > functionality of
> > the confine system?

> Hmm, I don't think so.

Okay...

> That is, that line "Not suitable: false value" indicates that the  
> provider isn't suitable, it's just not very informative.

Right.

> I'm pretty confused as to why it says that and then goes on to work,  
> though.  This original problem kinda got lost in my goal of describing  
> how the 'confine' stuff works.  That'd be a good thing to figure out  
> the cause of.

Yes, that's puzzling as yum _is_ used by Puppet to install/upgrade packages on
CentOS.

Also, PuppetRedHatCentos mentions a related problem:

    With RHEL 5.0-5.2, rpm -q misreports a query of package.arch with a blank line
    and zero return code, even if it is installed. This means you can't use the
    package type to force the install of multiple architectures of packages
    because the provider barfs on the faulty input. Installation of the default
    architecture still works. Should be fixed in RHEL5.3.

I don't remember offhand seeing this problem on CentOS 5.1 x86_64 but it's
something to verify next week.

--
Jos Backus
jos at catnook.com


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google