Log message:
devel/ruby-rspec-expectations: update to 3.9.1

Update ruby-rspec-expectations to 3.9.1.

### 3.9.1 / 2020-03-13
[Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.9.0...v3.9.1)

Bug Fixes:

* Issue an improved warning when using `respond_to(...).with(n).arguments` and ignore
  the warning when using with `have_attributes(...)`. (Jon Rowe, #1164)

Log message:
devel/ruby-rspec-expectations: update to 3.9.0

Update ruby-rspec-expectations to 3.9.0.

pkgsr change: Add "USE_LANGUAGES=	# none".

### 3.9.0 / 2019-10-02
[Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.8.5...v3.9.0)

Enhancements:

* The `respond_to` matcher now uses the signature from `initialize` to validate \ 
checks
  for `new` (unless `new` is non standard). (Jon Rowe, #1072)
* Generated descriptions for matchers now use `is expected to` rather than \ 
`should` in
  line with our preferred DSL. (Pete Johns, #1080, rspec/rspec-core#2572)
* Add the ability to re-raise expectation errors when matching
  with `match_when_negated` blocks. (Jon Rowe, #1130)
* Add a warning when an empty diff is produce due to identical inspect output.
  (Benoit Tigeot, #1126)

### 3.8.6 / 2019-10-07

Bug Fixes:

* Revert #1125 due to the change being incompatible with our semantic versioning
  policy.

### 3.8.5 / 2019-10-02
[Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.8.4...v3.8.5)

Bug Fixes:

* Prevent unsupported implicit block expectation syntax from being used.
  (Phil Pirozhkov, #1125)

### 3.8.4 / 2019-06-10
[Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.8.3...v3.8.4)

Bug Fixes:

* Prevent false negatives when checking objects for the methods required to run the
  the `be_an_instance_of` and `be_kind_of` matchers. (Nazar Matus, #1112)

Log message:
devel/ruby-rspec-expectations: update to 3.8.3

### 3.8.3 / 2019-04-20
[Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.8.2...v3.8.3)

Bug Fixes:

* Prevent composed `all` matchers from leaking into their siblings leading to \ 
duplicate
  failures. (Jamie English, #1086)
* Prevent objects which change their hash on comparison from failing change checks.
  (Phil Pirozhkov, #1110)
* Issue an `ArgumentError` rather than a `NoMethodError` when `be_an_instance_of` and
  `be_kind_of` matchers encounter objects not supporting those methods.
  (Taichi Ishitani, #1107)

Log message:
devel/ruby-rspec-expectations: update to 3.8.2

### 3.8.2 / 2018-10-09
[Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.8.1...v3.8.2)

Bug Fixes:

* Change `include` matcher to rely on a `respond_to?(:include?)` check rather \ 
than a direct
  Hash comparison before calling `to_hash` to convert to a hash. (Jordan Owens, \ 
#1073)
* Prevent unexpected call stack jumps from causing an obscure error \ 
(`IndexError`), and
  replace that error with a proper informative message. (Jon Rowe, #1076)

### 3.8.1 / 2018-08-06
[Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.8.0...v3.8.1)

Bug Fixes:

* Fix regression in `include` matcher so stopped
  `expect(hash.with_indifferent_access).to include(:symbol_key)`
  from working. (Eito Katagiri, #1069)

### 3.8.0 / 2018-08-04
[Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.7.0...v3.8.0)

Enhancements:

* Improve failure message of `change(receiver, :message)` by including the
  receiver as `SomeClass#some_message`. (Tomohiro Hashidate, #1005)
* Improve `change` matcher so that it can correctly detect changes in
  deeply nested mutable objects (such as arrays-of-hashes-of-arrays).
  The improved logic uses the before/after `hash` value to see if the
  object has been mutated, rather than shallow duping the object.
  (Myron Marston, #1034)
* Improve `include` matcher so that pseudo-hash objects (e.g. objects
  that decorate a hash using a `SimpleDelegator` or similar) are treated
  as a hash, as long as they implement `to_hash`. (Pablo Brasero, #1012)
* Add `max_formatted_output_length=` to configuration, allowing changing
  the length at which we truncate large output strings.
  (Sam Phippen #951, Benoit Tigeot #1056)
* Improve error message when passing a matcher that doesn't support block
  expectations to a block based `expect`. (@nicktime, #1066)

Log message:
devel/ruby-rspec-expectations: update to 3.7.0

### 3.7.0 / 2017-10-17
[Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.6.0...v3.7.0)

Enhancements:

* Improve compatibility with `--enable-frozen-string-literal` option
  on Ruby 2.3+. (Pat Allan, #997)

Log message:
Follow some redirects.

Log message:
Update ruby-rspec-expectations to 3.6.0.

### 3.6.0 / 2017-05-04
[Full \ 
Changelog](http://github.com/rspec/rspec-expectations/compare/v3.6.0.beta2...v3.6.0)

Enhancements:

* Treat NoMethodError as a failure for comparison matchers. (Jon Rowe, #972)
* Allow for scoped aliased and negated matchers--just call
  `alias_matcher` or `define_negated_matcher` from within an example
  group. (Markus Reiter, #974)
* Improve failure message of `change` matcher with block and `satisfy` matcher
  by including the block snippet instead of just describing it as `result` or
  `block` when Ripper is available. (Yuji Nakayama, #987)

Bug Fixes:

* Fix `yield_with_args` and `yield_successive_args` matchers so that
  they compare expected to actual args at the time the args are yielded
  instead of at the end, in case the method that is yielding mutates the
  arguments after yielding. (Alyssa Ross, #965)

### 3.6.0.beta2 / 2016-12-12
[Full \ 
Changelog](http://github.com/rspec/rspec-expectations/compare/v3.6.0.beta1...v3.6.0.beta2)

Bug Fixes:

* Using the exist matcher on `File` no longer produces a deprecation warning.
  (Jon Rowe, #954)

### 3.6.0.beta1 / 2016-10-09
[Full \ 
Changelog](http://github.com/rspec/rspec-expectations/compare/v3.5.0...v3.6.0.beta1)

Bug Fixes:

* Fix `contain_exactly` to work correctly with ranges. (Myron Marston, #940)
* Fix `change` to work correctly with sets. (Marcin Gajewski, #939)

Log message:
Update ruby-rspec-expectations to 3.5.0.

### 3.5.0 / 2016-07-01
[Full \ 
Changelog](http://github.com/rspec/rspec-expectations/compare/v3.5.0.beta4...v3.5.0)

**No user facing changes since beta4**

### 3.5.0.beta4 / 2016-06-05
[Full \ 
Changelog](http://github.com/rspec/rspec-expectations/compare/v3.5.0.beta3...v3.5.0.beta4)

Bug Fixes:

* Fix `include` matcher so that it provides a valid diff for hashes. (Yuji \ 
Nakayama, #916)

### 3.5.0.beta3 / 2016-04-02
[Full \ 
Changelog](http://github.com/rspec/rspec-expectations/compare/v3.5.0.beta2...v3.5.0.beta3)

Enhancements:

* Make `rspec/expectations/minitest_integration` work on Minitest::Spec
  5.6+. (Myron Marston, #904)
* Add an alias `having_attributes` for `have_attributes` matcher.
  (Yuji Nakayama, #905)
* Improve `change` matcher error message when block is mis-used.
  (Alex Altair, #908)

### 3.5.0.beta2 / 2016-03-10
[Full \ 
Changelog](http://github.com/rspec/rspec-expectations/compare/v3.5.0.beta1...v3.5.0.beta2)

Enhancements:

* Add the ability to raise an error on encountering false positives via
  `RSpec::Configuration#on_potential_false_positives = :raise`. (Jon Rowe, #900)
* When using the custom matcher DSL, support new
  `notify_expectation_failures: true` option for the `match` method to
  allow expectation failures to be raised as normal instead of being
  converted into a `false` return value for `matches?`. (Jon Rowe, #892)

Bug Fixes:

* Allow `should` deprecation check to work on `BasicObject`s. (James Coleman, #898)

### 3.5.0.beta1 / 2016-02-06
[Full \ 
Changelog](http://github.com/rspec/rspec-expectations/compare/v3.4.0...v3.5.0.beta1)

Enhancements:

* Make `match_when_negated` in custom matcher DSL support use of
  expectations within the match logic. (Chris Arcand, #789)

Bug Fixes:

* Return `true` as expected from passing negated expectations
  (such as `expect("foo").not_to eq "bar"`), so they work
  properly when used within a `match` or `match_when_negated`
  block. (Chris Arcand, #789)

Log message:
Update ruby-rspec-expectations to 3.4.0.

### 3.4.0 / 2015-11-11
[Full Changelog](http://github.com/rspec/rspec-expectations/compare/v3.3.1...v3.4.0)

Enhancements:

* Warn when `RSpec::Matchers` is included in a superclass after it has
  already been included in a subclass on MRI 1.9, since that situation
  can cause uses of `super` to trigger infinite recursion. (Myron Marston, #816)
* Stop rescuing `NoMemoryError`, `SignalExcepetion`, `Interrupt` and
  `SystemExit`. It is dangerous to interfere with these. (Myron Marston, #845)
* Add `#with_captures` to the
  [match \ 
matcher](https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers/match-matcher)
  which allows a user to specify expected captures when matching a regex
  against a string. (Sam Phippen, #848)
* Always print compound failure messages in the multi-line form. Trying
  to print it all on a single line didn't read very well. (Myron Marston, #859)

Bug Fixes:

* Fix failure message from dynamic predicate matchers when the object
  does not respond to the predicate so that it is inspected rather
  than relying upon it's `to_s` -- that way for `nil`, `"nil"` is
  printed rather than an empty string. (Myron Marston, #841)
* Fix SystemStackError raised when diffing an Enumerable object
  whose `#each` includes the object itself. (Yuji Nakayama, #857)

Log message:
Add SHA512 digests for distfiles for devel category

Issues found with existing distfiles:
	distfiles/eclipse-sourceBuild-srcIncluded-3.0.1.zip
	distfiles/fortran-utils-1.1.tar.gz
	distfiles/ivykis-0.39.tar.gz
	distfiles/enum-1.11.tar.gz
	distfiles/pvs-3.2-libraries.tgz
	distfiles/pvs-3.2-linux.tgz
	distfiles/pvs-3.2-solaris.tgz
	distfiles/pvs-3.2-system.tgz
No changes made to these distinfo files.

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.