Package: puppet Version: 0.24.5-3 Severity: normal We recently stumbled on a bug unrelated to puppet where a bunch of armel ruby binary modules are installed in the wrong path. Unfortunately, one of the affected modules happened to be one we were using in a new fact. The LoadError exception took down puppetd on all the armel machines as a result. This should be avoidable by catching exceptions and logging them, rather than letting them kill puppetd.
Cheers, -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: ia64 Kernel: Linux 2.6.28.4-dsa-mckinley (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.utf8) Shell: /bin/sh linked to /bin/bash Versions of packages puppet depends on: ii adduser 3.110 add and remove users and groups ii facter 1.5.1-0.1 a library for retrieving facts fro ii libopenssl-ruby 4.2 OpenSSL interface for Ruby ii libruby [libxmlrpc-ruby] 4.2 Libraries necessary to run Ruby 1. ii libshadow-ruby1.8 1.4.1-8 Interface of shadow password for R ii libxmlrpc-ruby 4.2 transitional dummy package ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip ii ruby 4.2 An interpreter of object-oriented Versions of packages puppet recommends: ii rdoc 4.2 Generate documentation from ruby s puppet suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
