Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISSUE-316: Unable to upgrade module through "puppet module upgrade" #317

Closed
wants to merge 7 commits into from
Closed

Conversation

luisosses
Copy link

No description provided.

@jenkinsadmin
Copy link

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

Luis Osses Lopez added 6 commits June 16, 2015 08:18
By adding a new parameter to the init class, will be possible to switch between versions of the different repository manager modules.
(Only implemented for Debian)

Backward compatibility is still preserved
By adding a new parameter to the init class, will be possible to switch between versions of the different repository manager modules.
(Only implemented for Debian)

Backward compatibility is still preserved
By adding a new parameter to the init class, will be possible to switch between versions of the different repository manager modules.
(Only implemented for Debian)

Backward compatibility is still preserved
…enkins into issue_316

Conflicts:
	manifests/init.pp
	metadata.json
@luisosses
Copy link
Author

Closing this one as the Puppetlabs-apt module was updated to handle Sources with backward compatibility

@luisosses luisosses closed this Jun 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants