Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily

[Joshua Partlow (JIRA)]

Title: Message Title

Joshua Partlow commented on an issue   Re: zypper should always be the default package provider for Suse osfamily I did not have any luck installing yum on the sles10 instance available from our vmpooler, (the link in this ticket is for Suse11+, and another I found expected Python 2.5, while we have 2.4). I did get Puppet itself running. While no warnings are issued, the following output does seem to indicate that rug might still have preference? t6xi4700fzwxpen:~/puppet # puppet resource package grep --debug ... Debug: Package python-tk found in both rug and zypper; skipping the zypper version Debug: Package gpg-pubkey found in both rug and zypper; skipping the zypper version Debug: Package python-devel found in both rug and zypper; skipping the zypper version Debug: Package libidn-devel found in both rug and zypper; skipping the zypper version package { 'grep': ensure => '2.5.1a-20.20.44.1', } Add Comment   Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily zypper package manager should always be the default package provider for Suse osfamily. Additionally, this prevents puppet agent from moaning about the presence of multiple package providers if others are also installed (e.g. Yum) along with zypper. In this case, Puppet will default to the first provider it finds, which does not happen to be the same... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.