Issue #2043 has been updated by Daniel Pittman.

Status changed from In Topic Branch Pending Review to Tests Insufficient


----------------------------------------
Bug #2043: up2date provider should split off architecture to --arch parameter
https://projects.puppetlabs.com/issues/2043

Author: Derek Whayman
Status: Tests Insufficient
Priority: Normal
Assignee: James Cammarata
Category: package
Target version: 2.7.x
Affected Puppet version: 0.24.7
Keywords: communitypatch
Branch: https://github.com/jamtur01/puppet/tree/ticket/master/2043


Re: 
http://groups.google.com/group/puppet-dev/browse_thread/thread/5ce44b1541a1df8b

Just came across an issue where I had to install pam.i386 as well as
pam.x86_64 on a RHEL4 machine (via up2date).  With the yum provider
you can simply

package { "pam.i386": }

Because the underlying command is understood by yum
yum -y install pam.i386

With up to date this fails
up2date-nox -i pam.i386

You need to
up2date --arch=i386 pam

There has been a lot of discussion in the past (including myself)
about this, none of which came to a satisfactory conclusion.  Packages
are inherently tricky as you have "pam", "pam.i386" and "pam.x86_64"
which doesn't sit comfortably with Puppet's concept of unique
resources.

So what I propose is something much simpler, rather than solve that
problem simply permit the same kludge within up2date as within yum,
i.e. this patch.

The provider will determine if the name end in an architecture by way of a long 
regexp of known architectures.  Splitting off via the dots is unreliable as 
some package names do have a dot in them.

Regards,
Derek


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to