Skip to content

(FM-4918) update modsync / Restrict Rake ~> 10.1 #153

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

Merged
merged 2 commits into from
Mar 14, 2016
Merged

(FM-4918) update modsync / Restrict Rake ~> 10.1 #153

merged 2 commits into from
Mar 14, 2016

Conversation

ferventcoder
Copy link
Contributor

Beaker needs a version of Rake less than
11 due to using `last_comment' in
rake_task.rb:62. Reduce the version of Rake
down to the same dependency that Beaker does
as a development dependency.

Paired with Glenn Sarti <glenn.sarti at puppetlabs dot com>

@ferventcoder
Copy link
Contributor Author

@Iristyle ping - these could really be pulled in.

@ferventcoder
Copy link
Contributor Author

Three commits - this will need squashed down.

@ferventcoder
Copy link
Contributor Author

@puppetlabs/windows ModSync

@ferventcoder ferventcoder changed the title (maint) update modulesync files (FM-4918) update modsync / Restrict Rake ~> 10.1 Mar 11, 2016
@ferventcoder
Copy link
Contributor Author

This is not going to fix the issue at hand yet - that is rodjek/rspec-puppet#361. But for some reason it affects rspec-puppet at 2.3.0 through 2.3.2 (and likely more, I haven't dug in too deep yet).

Original break here: https://travis-ci.com/puppetlabs/puppetlabs-sqlserver/jobs/34981476

gem 'rspec', '~>3.0.0', :require => false
gem 'rake', '~>10.1', :require => false
gem 'rspec', '~>3.0', :require => false
#gem 'rspec-puppet', '2.3.0', :require => false
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dropped this in here for a minute.

@ferventcoder ferventcoder changed the title (FM-4918) update modsync / Restrict Rake ~> 10.1 {WIP}(FM-4918) update modsync / Restrict Rake ~> 10.1 Mar 12, 2016
Beaker needs a version of Rake less than
11 due to using `last_comment' in
rake_task.rb:62. Reduce the version of Rake
down to the same dependency that Beaker does
as a development dependency.

Paired with Glenn Sarti <glenn.sarti at puppetlabs dot com>

Puppet v4 needs facts to not be symbols, otherwise it causes
rspec-puppet to fail with `expected Puppet::Error with message
matching /expects a value for parameter 'admin_user'/, got
<Puppet::Error: Unsupported data type: 'Symbol'`.

Paired with David Schmitt
@ferventcoder ferventcoder changed the title {WIP}(FM-4918) update modsync / Restrict Rake ~> 10.1 (FM-4918) update modsync / Restrict Rake ~> 10.1 Mar 14, 2016
- gem: puppet-lint
- gem: puppetlabs_spec_helper
version: '~>0.10.3'
- gem: puppet_facts
- gem: mocha
version: '~>0.10.5'
- gem: pry
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know that it's in the development group, but should we be requiring pry by default?

Nevermind, it's coming from modulesync.

glennsarti added a commit that referenced this pull request Mar 14, 2016
(FM-4918) update modsync / Restrict Rake ~> 10.1
@glennsarti glennsarti merged commit b532b89 into puppetlabs:master Mar 14, 2016
@ferventcoder ferventcoder deleted the maint/master/modsync-changes branch March 14, 2016 17:50
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