Issue #1238 has been updated by Ben Ford.
Matt Behrens wrote: ... > but there is a problem. The `asterisknow-version` package is a dependency of > several packages in that repository, and supplies a `centos-asterisk-11.repo` > that contains the `asterisk-11` repo itself. Now we have two identical > repos, one of which Puppet is managing, and the other managed by > `asterisknow-version`. (One could perhaps successfully argue that the > packages requiring `asterisknow-version` are a problem with the way the > repository is assembled; I might agree with you. But so it is.) This is just like when you manage a package that installs a default configuration file and then manage the file with the actual contents using Puppet. I've posted an explanation at https://gist.github.com/binford2k/7437064 ---------------------------------------- Bug #1238: strange yumrepo/package interaction https://projects.puppetlabs.com/issues/1238#change-99809 * Author: BMDan - * Status: Needs More Information * Priority: Normal * Assignee: Gerard Bernabeu * Category: yumrepo * Target version: 3.x * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- Yumrepo appears to be checking file existence before allowing the package command to complete, meaning that it creates a file containing only "[remi]" and "enabled=1", overwriting the file that the RPM installed. Manifests, additional debug output, etc., available upon request. Just tell me what you need to know. Workarounds especially welcomed. Puppet v. 0.24.4, running with --debug --test, on Ruby 1.8.6.114-1, compiled from source with default options. <pre> debug: //Node[default]/remi_enabled/Yumrepo[remi]/require: requires Package[remi-release-5-4.el5.remi] </pre> ... <pre> debug: Puppet::Type::Package::ProviderRpm: Not suitable: false value debug: Puppet::Type::Package::ProviderRpm: Executing '/bin/rpm -q remi-release-5-4.el5.remi --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}' debug: /Package[remi-release-5-4.el5.remi]: Changing ensure debug: /Package[remi-release-5-4.el5.remi]: 1 change(s) debug: Puppet::Type::Package::ProviderRpm: Executing '/bin/rpm -i --oldpackage http://rpms.famillecollet.com/el5.x86_64/remi-release-5-4.el5.remi.noarch.rpm' notice: /Package[remi-release-5-4.el5.remi]/ensure: created info: create new repo remi in file /etc/yum.repos.d/remi.repo debug: //Node[default]/remi_enabled/Yumrepo[remi]: Changing enabled debug: //Node[default]/remi_enabled/Yumrepo[remi]: 1 change(s) notice: //Node[default]/remi_enabled/Yumrepo[remi]/enabled: defined 'enabled' as '1' info: Filebucket[/var/lib/puppet/clientbucket]: Adding /etc/yum.repos.d/remi.repo(18f7009978e772c9c646b9410fa3a8b6) </pre> -- 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 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-bugs. For more options, visit https://groups.google.com/groups/opt_out.
