eix versions before eix-0.9.4 have a bug in the --nocolor option which causes eix to leak escape codes for coloring. Puppet needs to parse eix output and is affected by this bug. The bug is solved in 0.9.4 Please update the puppet ebuild to require eix-0.9.4 or higher. Reproducible: Always Steps to Reproduce: 1.eix --nocolor eix > test.tmp 2.vi test.tmp 3. Sample output: [I] app-portage/eix Available versions: 0.8.8^[[0m 0.9.1^[[0m ~0.9.2^[[0m ~0.9.3^[[0m ~0.9.4^[[0m ~0.9.6^[[0m ~0.9.7^[[0m Installed: 0.9.1(10:24:00 06/04/07)(-sqlite) Homepage: http://eix.sourceforge.net Description: Small utility for searching ebuilds with indexing for fast results Actual Results: Sample output above shows escape codes for coloring at the end of the version-numbers Expected Results: Because of the --nocolor option no escape codes for coloring should be present Puppet parses the output to determine version of a package. It compares the output from eix with a user-specified version in a puppet manifest file. Because of the escape-codes in eix output puppet always believes that the incorrect version of a package is installed and starts merging the correct version. This results in repeated emerges of defined packages in puppet-manifests With the default schedule in puppet this results in reinstalling every defined package with a specific version every half hour
done in puppet-0.23.0
Thank you
