Bug #12408

Cleanup dependency data for current modules

Added by Matt Robinson 4 months ago. Updated 2 months ago.

Status:Accepted Start date:02/03/2012
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:module site Spent time: -
Target version:-
Keywords: Affected URL:
Branch:
Votes: 0

Description

A bunch of modules already on the forge have dependency and version issues. We should then put constraints on the data so that we don’t get these problems again.

Pieter made a spreadsheet here

Version numbers need to be semantic:

rtyler/jenkins  0.1 {"name"=>"puppetlabs/stdlib", "version_requirement"=>">= 2.0.0"}
anselm/concatfile   1   {"name"=>"DavidSchmitten-common", "version_requirement"=>"1.0.0"}
anselm/concatfile   2   {"name"=>"DavidSchmitt-common", "version_requirement"=>"1.0.0"}

Version dependencies needs a consistent format:

puppetlabs/mrepo    0.1.1   {"name"=>"puppetlabs-apache>= 0.0.3"}
puppetlabs/mrepo    0.1.1   {"name"=>"puppetlabs/vcsrepo>= 0.0.3"}
puppetlabs/mrepo    0.1.1   {"name"=>"puppetlabs/stdlib>= 0.1.6"}
puppetlabs/mrepo    0.1.2   {"name"=>"puppetlabs-apache>= 0.0.3"}
puppetlabs/mrepo    0.1.2   {"name"=>"puppetlabs/vcsrepo>= 0.0.3"}
puppetlabs/mrepo    0.1.2   {"name"=>"puppetlabs/stdlib>= 0.1.6"}
ghoneycutt/hosts    1.0.0   {"name"=>"ghoneycutt/generic>= 1.0.0"}
lab42/postfix   0.0.2   {"name"=>"lab42/common", "repository"=>"http://forge.puppetlabs.com", "version_requirement"=>">= 0.0.1"}
lab42/postfix   0.0.1   {"name"=>"lab42/commit", "repository"=>"http://forge.puppetlabs.com", "version_requirement"=>">= 1.2.0"}

History

#1
Updated by Matt Robinson 4 months ago

  • Description updated (diff)

#2
Updated by Adrien Thebo 3 months ago

In my defense, the mrepo versioning was bad because of a bug in the puppet module tool generating incorrect metadata instead of failing. I’ve submitted https://github.com/puppetlabs/puppetlabs-mrepo/pull/4 with a corrected Modulefile.

#3
Updated by Daniel Pittman 2 months ago

  • Target version deleted (53)

#4
Updated by Matt Robinson 2 months ago

This needs to be done soon after PE 2.5 is released with the module tool, but can wait until after the other core puppet code changes are final. Until then, some modules will just not install with dependencies properly.

Also available in: Atom PDF