-
Notifications
You must be signed in to change notification settings - Fork 21
(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
(FM-4918) update modsync / Restrict Rake ~> 10.1 #153
Conversation
@Iristyle ping - these could really be pulled in. |
Three commits - this will need squashed down. |
@puppetlabs/windows ModSync |
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 |
There was a problem hiding this comment.
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.
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
- gem: puppet-lint | ||
- gem: puppetlabs_spec_helper | ||
version: '~>0.10.3' | ||
- gem: puppet_facts | ||
- gem: mocha | ||
version: '~>0.10.5' | ||
- gem: pry |
There was a problem hiding this comment.
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.
(FM-4918) update modsync / Restrict Rake ~> 10.1
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>