search for: nosignature

...l5 [root@puppet tmp]# cat /etc/issue CentOS release 5 (Final) Here''s the output of puppetd --debug: notice: Starting catalog run debug: Loaded state in 0.01 seconds debug: Prefetching rpm resources for package debug: Puppet::Type::Package::ProviderRpm: Executing ''/bin/rpm -qa --nosignature --nodigest --qf ''} '''' debug: Prefetching parsed resources for mount debug: Prefetching yum resources for package debug: Puppet::Type::Package::ProviderYum: Executing ''/bin/rpm -qa --nosignature --nodigest --qf ''} '''' debug: Puppet::Type:...

..."). But when I specify a local path in my variable (like "/home/test/rpms/mycustom.rpm") it doesn''t get used: ..snip.. Debug: Prefetching yum resources for package > Debug: Executing ''/bin/rpm --version'' > Debug: Executing ''/bin/rpm -qa --nosignature --nodigest --qf ''%{NAME} > %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} > '''' > Debug: Executing ''/bin/rpm -q collectd --nosignature --nodigest --qf > %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} > '' > Debug:...

Hi! Using (among others) the pretty old SuSE8.1, I cant get puppet to install packages. The rpm programms bahaviour was changed somewhen between versions 3 and 4 (sry, don´t know exactly when) and the old version does not support the "--nosignature" and "--nodigest" params and "--oldpackage" is purely an update parameter so when trying to install a package I allways get a "oldpackage must only be supplied while updating" or alike. I tried tinkering a little with the rpm.rb, moving "--oldpackage"...

...args: blocking=yes dovecot userdb: driver: passwd args: blocking=yes socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: fs:storage=102400 trash: /etc/dovecot/trash.conf sieve: ~/.dovecot.sieve dspam: /usr/sbin/dspam:Spam:nosignature:Trash:users autocreate: Spam I.e., I use the same mail_location for both POP3 and IMAP. However, mails are delivered to ~/Mail/inbox and seems to be invisible to both my IMAP and POP3 client (Thunderbird). Any input appreciated /Lars

Hi there, When installing R on linux 8.0, I got the following error message: rpm -i /mnt/cdrom/linux/8.x/R-1.6.2-1.i386.rpm error: /mnt/cdrom/linux/8.x/R-1.6.2-1.i386.rpm: V3 DSA signature: BAD, key ID 97d3544e error: /mnt/cdrom/linux/8.x/R-1.6.2-1.i386.rpm cannot be installed Any suggestions as what I did wrong? Thanks in advance. Wenyan [[alternate HTML version deleted]]

Hi, this work makes supermin use the rpm library instead of invoking rpm directly. This, together with a needed refactoring of the dependency resolution, should help in make supermin faster on rpm-based systems. Surely the patches will still need polishing, especially for behaviours of newly added stuff, but at least it's a good starting point. Noting that you need rpm-devel on most of rpm

...t-snmp]: 1 change(s) debug: Package[net-snmp](provider=yum): Ensuring => 5.3.2.2 debug: Puppet::Type::Package::ProviderYum: Executing ''/usr/bin/yum -d 0 -e 0 -y install net-snmp-5.3.2.2'' *(1)* debug: Puppet::Type::Package::ProviderYum: Executing ''/bin/rpm -q net-snmp --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH} '' *(2)* err: //Node[client.example.com]/snmp::base/Package[net-snmp]/ensure: change from 5.3.2.2-7.el5_4.2 to 5.3.2.2 failed: Could not update: Failed to update to version *5.3.2.2*, got version *5.3.2.2-7.el5_4....

Hi all, Not sure if this is a bug in puppet, yum, or just something I''m doing wrong. I''m trying to use puppet to update a package to a particular version and exec a command when that update is applied. The problem is, puppet calls yum which successfully updates the package, but puppet then thinks the update has failed and hence doesn''t trigger the exec. Next

...---------------------- Major changes for this version are: * The up2date options "--undo" and "--list-rollbacks" are now deprecated. You must use "yum remove <pkg_name>" or "rpm -e <pkg_name>" to remove packages, or "rpm -Uvh --oldpackage --nosignature --nodigest <pkg_name>" to revert to an older package. * CentOS-4.5 contains a Xen kernel that is now supported as a paravirtualized (PV) Guest, but it cannot be used as a dom0. There are issues with erratic mouse movements in PV Guests that will be corrected in future updates. You can...

...---------------------- Major changes for this version are: * The up2date options "--undo" and "--list-rollbacks" are now deprecated. You must use "yum remove <pkg_name>" or "rpm -e <pkg_name>" to remove packages, or "rpm -Uvh --oldpackage --nosignature --nodigest <pkg_name>" to revert to an older package. * CentOS-4.5 contains a Xen kernel that is now supported as a paravirtualized (PV) Guest, but it cannot be used as a dom0. There are issues with erratic mouse movements in PV Guests that will be corrected in future updates. You can...

I too have been pushed into Puppet 3.0. Clients and PuppetMaster are now at 3.0.0. Not sure if this is a version change or syntax error that I am experiencing. We''ll use ''ntp'' as the example and the "build" host is a VM. The old way: class baseline::ntpd { package { "ntp": ensure => $virtual ? { physical => present,

Hello, Why the following lines doesn''t work? cron { "app" : command => ""nice -n -10 /usr/bin/php /var/www/public_html/rotinas/rotinas.php 2>&1>> /var/log/app.log", environment => "PATH=$PATH", user => root, hour => ''*'', minute =>

...---------------------- Major changes for this version are: * The up2date options "--undo" and "--list-rollbacks" are now deprecated. You must use "yum remove <pkg_name>" or "rpm -e <pkg_name>" to remove packages, or "rpm -Uvh --oldpackage --nosignature --nodigest <pkg_name>" to revert to an older package. * CentOS-4.5 contains a Xen kernel that is now supported as a paravirtualized (PV) Guest, but it cannot be used as a dom0. There are issues with erratic mouse movements in PV Guests that will be corrected in future updates. You can...

...es not exist debug: Creating default schedules debug: Loaded state in 0.01 seconds debug: Prefetching yum resources for package debug: Puppet::Type::Package::ProviderYum: Executing ''/bin/rpm -- version'' debug: Puppet::Type::Package::ProviderYum: Executing ''/bin/rpm -qa -- nosignature --nodigest --qf ''%{NAME} %|EPOCH?{%{EPOCH}}:{0}| % {VERSION} %{RELEASE} %{ARCH} '''' debug: Puppet::Type::Package::ProviderYum: Executing ''/usr/bin/python / usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py'' info: Applying configuration versi...

I''ve seen mention of this error in several places, with different causes. So before I posted here, I attempted to resolve this on my own. I corrected the change from puppet:///files to puppet:/// in my manifests *.pp files. No changes were made to the auth.conf file, and I did note in the ChangeLog that: Auth.conf differentiates between names and IPs – There’s a new allow_ip