Librarian-puppet update fails when executing librarian-puppet install works: stack level too deep

[escrivio]

Hello,

I am currently experiencing an odd and unexpected problem which I could not explain on our RHEL5.10 puppet-masters.
.
On one hand, when I first run librarian-puppet with "install" function, everything works and all my modules are downloaded on my puppet-master without complaining.

On the other hand, with the same Puppetfile, when I run librarian-puppet with "update" function, it fails with the following error messages (not the same at each execution).

The same symptom occurs even if we launch the "librarian-puppet clean" command to ensure that the environment does not contain any parasite file.

The only way to avoid the fail of librarian-puppet update is to reduce the number of "mod" declarations under 80 (at 81 modules it fails every time).

Could you help us to resolve this bug please ?

Thanking you for advance,

Following the environment specs, the verbose stdout of 'librarian-puppet update' command, the different error stacks (not the same at each execution), the relevant Puppetfile and Puppetfile.lock :

* Environment specs******

• Red Hat Enterprise Linux Server release 5.10 (Tikanga), Linux puppet 2.6.18-371.1.2.el5 cargo culted some docs from librarian-chef #1 SMP
• puppet 3.6.2 from Puppetlabs official repos
• ruby 1.8.7 (2013-06-27 patchlevel 374) [x86_64-linux]
• gem 1.8.25, json (1.8.1), librarian (0.1.2), librarian-puppet (1.0.2)

* Verbose stdout librarian-puppet update*******

[Librarian] Ruby Version: 1.8.7
[Librarian] Ruby Platform: x86_64-linux
[Librarian] Rubygems Version: 1.8.25
[Librarian] Librarian Version: 0.1.2
[Librarian] Librarian Adapter: puppet
[Librarian] Librarian Adapter Version: 1.0.2
[Librarian] Project: /etc/puppet
[Librarian] Specfile: Puppetfile
[Librarian] Lockfile: Puppetfile.lock
[Librarian] Git: /usr/bin/git
[Librarian] Git Version: 1.7.11.3
[Librarian] Git Environment Variables:
[Librarian]   (empty)
[Librarian] Pre-Cached Sources:
[Librarian] Post-Cached Sources:

[carlossg]

see issue #217