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

Update apt::source to match with new method #423

Closed
wants to merge 1 commit into from
Closed

Update apt::source to match with new method #423

wants to merge 1 commit into from

Conversation

EmilienM
Copy link
Contributor

@EmilienM EmilienM commented Jan 6, 2016

puppetlabs-apt recently did some changes that brings warnings when we
run puppetlabs-rabbitmq, because we need to update the way we consume
apt module.

$include_src is deprecated and will be removed in the next major
release, please use $include => { 'src' => false } instead

$key_source is deprecated and will be removed in the next major release,
please use $key => { 'source' =>
http://www.rabbitmq.com/rabbitmq-signing-key-public.asc } instead.

This patch aims to update the way we use puppetlabs-apt to match with
upstream and avoid warnings in our catalog.

@hunner
Copy link
Member

hunner commented Jan 6, 2016

Does this require a bump in metadata.json, or will it still work with apt 1.8.0?

@EmilienM
Copy link
Contributor Author

EmilienM commented Jan 7, 2016

@hunner yes, but 2.x.x has been released in 2015-04. I suppose people update their manifests from time to time? Maybe I'm wrong. Feel free to merge it or not.

FWIW, Puppet OpenStack CI is running 2.2.x serie:
https://github.com/openstack/puppet-openstack-integration/blob/master/Puppetfile#L117-L119

@hunner
Copy link
Member

hunner commented Jan 14, 2016

I want to merge this, but it would require a 6.0.0 release of rabbitmq. While we're at it, what other changes do we want to make to the module?

@hunner
Copy link
Member

hunner commented Jan 19, 2016

Could you also increase the lower bound of puppetlabs-apt in metadata.json to >= 2.0.0? Since it won't work with 1.8.x

@EmilienM
Copy link
Contributor Author

@hunner done

@hunner hunner added this to the 6.0.0 milestone Jan 21, 2016
@dhoppe
Copy link
Member

dhoppe commented Feb 19, 2016

👍

@eputnam
Copy link
Member

eputnam commented Feb 17, 2017

hi @EmilienM , could you please rebase?

@EmilienM
Copy link
Contributor Author

@eputnam done.

puppetlabs-apt recently did some changes that brings warnings when we
run puppetlabs-rabbitmq, because we need to update the way we consume
apt module.

$include_src is deprecated and will be removed in the next major
release, please use $include => { 'src' => false } instead

$key_source is deprecated and will be removed in the next major release,
please use $key => { 'source' =>
http://www.rabbitmq.com/rabbitmq-signing-key-public.asc } instead.

This patch aims to update the way we use puppetlabs-apt to match with
upstream and avoid warnings in our catalog.

Also bump puppetlabs-apt to >= 2.0.0.
@hunner
Copy link
Member

hunner commented Apr 13, 2017

Merged in #497

@hunner hunner closed this Apr 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants