netmanagers / puppet-varnish

[UNMAINTAINED] Puppet module to manage varnish
3 stars 9 forks source link

Issue with librarian-puppet and v2.1.0 #8

Open benpriestman opened 10 years ago

benpriestman commented 10 years ago

This could be a librarian-puppet bug, but I'm only seeing it with this module.

Trying to use librarian puppet to install the version 2.1.0 of this module from the forge. On a clean machine and with this new version as the only module defined in Puppetfile, I get:

'[vagrant@node1 vagrant]$ librarian-puppet install --verbose [Librarian] Ruby Version: 1.8.7 [Librarian] Ruby Platform: x86_64-linux [Librarian] Rubygems Version: 1.3.7 [Librarian] Librarian Version: 0.0.24 [Librarian] Librarian Adapter: puppet [Librarian] Project: /vagrant [Librarian] Specfile: Puppetfile [Librarian] Lockfile: Puppetfile.lock [Librarian] Git: /usr/bin/git [Librarian] Git Version: git version 1.7.1 [Librarian] Git Environment Variables: Librarian [Librarian] Pre-Cached Sources: [Librarian] Post-Cached Sources: [Librarian] [:forge, "http://forge.puppetlabs.com", {}] [Librarian] Scheduling netmanagers/varnish (= 2.1.0) http://forge.puppetlabs.com [Librarian] Resolving netmanagers/varnish (= 2.1.0) http://forge.puppetlabs.com [Librarian] No known prior constraints [Librarian] Checking manifests [Librarian] Checking netmanagers/varnish/2.1.0 http://forge.puppetlabs.com

[Librarian] Scheduling example42/puppi (>= 2.0.0) http://forge.puppetlabs.com [Librarian] Scheduling puppetlabs/stdlib (>= 2.2.0) http://forge.puppetlabs.com [Librarian] Scheduling puppetlabs/stdlib (>= 2.2.0) http://forge.puppetlabs.com [Librarian] Resolving example42/puppi (>= 2.0.0) http://forge.puppetlabs.com [Librarian] No known prior constraints [Librarian] Checking manifests [Librarian] Checking example42/puppi/2.1.7 http://forge.puppetlabs.com [Librarian] Resolving puppetlabs/stdlib (>= 2.2.0) http://forge.puppetlabs.com [Librarian] No known prior constraints [Librarian] Checking manifests [Librarian] Checking puppetlabs/stdlib/4.1.0 http://forge.puppetlabs.com [Librarian] Resolving puppetlabs/stdlib (>= 2.2.0) http://forge.puppetlabs.com [Librarian] Accords with all prior constraints [Librarian] Resolved puppetlabs/stdlib (>= 2.2.0) http://forge.puppetlabs.com at puppetlabs/stdlib/4.1.0 http://forge.puppetlabs.com [Librarian] Resolved puppetlabs/stdlib (>= 2.2.0) http://forge.puppetlabs.com [Librarian] Resolved example42/puppi (>= 2.0.0) http://forge.puppetlabs.com at example42/puppi/2.1.7 http://forge.puppetlabs.com [Librarian] Resolved example42/puppi (>= 2.0.0) http://forge.puppetlabs.com [Librarian] Resolved netmanagers/varnish (= 2.1.0) http://forge.puppetlabs.com at netmanagers/varnish/2.1.0 http://forge.puppetlabs.com [Librarian] Resolved netmanagers/varnish (= 2.1.0) http://forge.puppetlabs.com [Librarian] Bouncing Puppetfile.lock [Librarian] lockfile_text: FORGE remote: http://forge.puppetlabs.com specs: example42/puppi (2.1.7) netmanagers/varnish (2.1.0) example42/puppi (>= 2.0.0) puppetlabs/stdlib (>= 2.2.0) puppetlabs/stdlib (>= 2.2.0) puppetlabs/stdlib (4.1.0)

DEPENDENCIES netmanagers/varnish (= 2.1.0)

[Librarian] bounced_lockfile_text: FORGE remote: http://forge.puppetlabs.com specs: example42/puppi (2.1.7) netmanagers/varnish (2.1.0) example42/puppi (>= 2.0.0) puppetlabs/stdlib (>= 2.2.0) puppetlabs/stdlib (4.1.0)

DEPENDENCIES netmanagers/varnish (= 2.1.0)

Cannot bounce Puppetfile.lock!'

With the previous version, I get:

`[vagrant@node1 vagrant]$ librarian-puppet install --verbose [Librarian] Ruby Version: 1.8.7 [Librarian] Ruby Platform: x86_64-linux [Librarian] Rubygems Version: 1.3.7 [Librarian] Librarian Version: 0.0.24 [Librarian] Librarian Adapter: puppet [Librarian] Project: /vagrant [Librarian] Specfile: Puppetfile [Librarian] Lockfile: Puppetfile.lock [Librarian] Git: /usr/bin/git [Librarian] Git Version: git version 1.7.1 [Librarian] Git Environment Variables: Librarian [Librarian] Pre-Cached Sources: [Librarian] Post-Cached Sources: [Librarian] [:forge, "http://forge.puppetlabs.com", {}] [Librarian] Scheduling netmanagers/varnish (= 2.0.0) http://forge.puppetlabs.co m [Librarian] Resolving netmanagers/varnish (= 2.0.0) http://forge.puppetlabs.com [Librarian] No known prior constraints [Librarian] Checking manifests [Librarian] Checking netmanagers/varnish/2.1.0 http://forge.puppetlabs.com

[Librarian] Backtracking from netmanagers/varnish/2.1.0 http://forge.puppetlabs.com [Librarian] Checking netmanagers/varnish/2.0.0 http://forge.puppetlabs.com

[Librarian] Scheduling example42/puppi (>= 2.0.0) http://forge.puppetlabs.com [Librarian] Resolving example42/puppi (>= 2.0.0) http://forge.puppetlabs.com [Librarian] No known prior constraints [Librarian] Checking manifests [Librarian] Checking example42/puppi/2.1.7 http://forge.puppetlabs.com [Librarian] Resolved example42/puppi (>= 2.0.0) http://forge.puppetlabs.com at example42/puppi/2.1.7 http://forge.puppetlabs.com [Librarian] Resolved example42/puppi (>= 2.0.0) http://forge.puppetlabs.com [Librarian] Resolved netmanagers/varnish (= 2.0.0) http://forge.puppetlabs.com at netmanagers/varnish/2.0.0 http://forge.puppetlabs.com [Librarian] Resolved netmanagers/varnish (= 2.0.0) http://forge.puppetlabs.com [Librarian] Bouncing Puppetfile.lock [Librarian] Pre-Cached Sources: [Librarian] Post-Cached Sources: [Librarian] [:forge, "http://forge.puppetlabs.com", {}]`

I suspect that this may be something to do with the duplicate entries for puppetlabs/stdlib in the Modulefile (and, possibly the space between '=>' and the version number). It's difficult to test without publishing to the forge, though.

Any ideas?

javierbertoli commented 10 years ago

I don't use librarian-puppet, so I can't really help you much there. On the other hand, having the entries duplicated in the Modulefile needed to be fixed, so I corrected that and uploaded a new semver to the forge.

Please give it a try and let me know if this issue can be closed or needs any more investigation.