Stackage: hspec 2.3.2

[bergmark]

Also blocked by #1902

hspec-2.3.2 (Simon Hengel [email protected] @sol) is out of bounds for:

• [ ] clay-0.11 (>=2.2.0 && < 2.3). Sebastiaan Visser [email protected] @sebastiaanvisser. @sebastiaanvisser
• [ ] drawille-0.1.0.6 (>=1.11 && < 2.3). Pedro Tacla Yamada tacla.[email protected] @yamadapc. @yamadapc
• [ ] fgl-5.5.3.0 (>=2.1 && < 2.3). Ivan Miljenovic Ivan.[email protected] @ivan-m. @haskell
• [ ] fgl-arbitrary-0.2.0.2 (>=2.1 && < 2.3). Ivan Miljenovic Ivan.[email protected] @ivan-m. @haskell
• [ ] hackernews-1.0.0.0 (==2.2.*). David Johnson djohnson.[email protected] @dmjio. @dmjio
• [ ] hjsonpointer-1.0.0.1 (==2.2.*). Ian Grant Jeffries [email protected] @seagreen. @seagreen
• [ ] hjsonschema-1.2.0.1 (==2.2.*). Ian Grant Jeffries [email protected] @seagreen. @seagreen
• [ ] hpio-0.8.0.3 (>=2.1.7 && < 2.3). Drew Hess [email protected] @dhess. @dhess
• [ ] map-syntax-0.2.0.1 (>=2.2.3 && < 2.3). No maintainer. @mightybyte
• [x] multistate-0.7.1.1 (< 2.3). Lennart Spitzner [email protected] @lspitzner. @lspitzner
• [ ] newtype-generics-0.4.1 (>=2.1 && < 2.3). No maintainer. @jcristovao
• [ ] next-ref-0.1.0.2 (>=2 && < 2.3). Jonathan Fischoff [email protected]. @skedgeme
• [ ] point-octree-0.5.5.3 (==2.2.3). Michael Litchard [email protected] @mlitchard. @mgajda @mlitchard
• [x] tasty-hspec-1.1.3 (>=2 && < 2.3). Mitchell Rosen [email protected] @mitchellwrosen. @mitchellwrosen
• [ ] web-routes-th-0.22.5 (==2.2.*). Jeremy Shaw [email protected] @stepcut. @stepcut

[mitchellwrosen]

FYI:

[~] hackage-diff --mode=parsehs hspec ./hspec-2.2.4 ./hspec-2.3.2
Processing ./hspec-2.2.4...
  Parsing Test.Hspec
  Parsing Test.Hspec.Core
  Parsing Test.Hspec.Discover
  Parsing Test.Hspec.Formatters
  Parsing Test.Hspec.HUnit
  Parsing Test.Hspec.QuickCheck
  Parsing Test.Hspec.Runner
Processing ./hspec-2.3.2...
  Parsing Test.Hspec
  Parsing Test.Hspec.Core
  Parsing Test.Hspec.Discover
  Parsing Test.Hspec.Formatters
  Parsing Test.Hspec.HUnit
  Parsing Test.Hspec.QuickCheck
  Parsing Test.Hspec.Runner

--- Diff for | ./hspec-2.2.4 → ./hspec-2.3.2 | ---

· Test.Hspec
· Test.Hspec.Core
· Test.Hspec.Discover
· Test.Hspec.Formatters
· Test.Hspec.HUnit
· Test.Hspec.QuickCheck
· Test.Hspec.Runner

[+ Added] [- Removed] [× Modified] [· Unmodified]

But... no diff between 2.2.4 and 2.3.2? I wonder if hackage-diff is wrong?

[mitchellwrosen]

updated metadata for tasty-hspec-1.1.3

[lspitzner]

updated metadata for multistate-0.7.1.1

[bergmark]

The diff between 2.3.2 and 2.2.4 can be seen here http://hdiff.luite.com/cgit/hspec/diff?id=2.3.2&id2=2.2.4

[jcristovao]

I've released newtype-generics 0.4.2 & 0.5, both with updated dependencies (which I hope are ok!)

[dhess]

FIxed in hpio-0.8.0.4.

[ivan-m]

fgl and fgl-arbitrary now work with hspec-2.3.*, but no release have been made as yet (as I'd like to merge some more changes in first).

[DanBurton]

Stackage nightly builds will soon move to hspec-2.3.2.

The following test suites will be skipped until they are updated to hspec-2.3.*:

hspec-2.3.2 (Simon Hengel [e-mail] @sol) is out of bounds for:

• avers-0.0.17.0 (>=2.2.3 && < 2.3). Tomas Carnecky @wereHamster. @wereHamster. Used by: test-suite
• clay-0.12 (>=2.2.0 && < 2.3). Sebastiaan Visser [e-mail] @sebastiaanvisser. @sebastiaanvisser. Used by: test-suite
• drawille-0.1.0.6 (>=1.11 && < 2.3). Pedro Tacla Yamada [e-mail] @yamadapc. @yamadapc. Used by: test-suite
• fgl-5.5.3.0 (>=2.1 && < 2.3). Ivan Miljenovic [e-mail] @ivan-m. @haskell. Used by: test-suite
• fgl-arbitrary-0.2.0.2 (>=2.1 && < 2.3). Ivan Miljenovic [e-mail] @ivan-m. @haskell. Used by: test-suite
• next-ref-0.1.0.2 (>=2 && < 2.3). Jonathan Fischoff [e-mail]. @skedgeme. Used by: test-suite

[wereHamster]

Would it be possible to notify me sooner that there is a compatibility problem with one of my packages? This issue has been open for more than a month, but you only notified me yesterday that you're going to disable the tests. And just four hours later you actually did the commit. That's not enough time for me to react.

[DanBurton]

Sorry about that, @wereHamster. It's a rare circumstance when a package doesn't get the original notification, and I neglected to notice that such was the case here.

[bergmark]

We have #1104 filed for this (edit: or at least parts of this), but I don't think it has gotten further than the wishing stage yet.