Test suite failure (missing file in hackage tarball)

[DanBurton]

As seen on the stackage build server:

Failures:

  test/Data/YamlSpec.hs:67:
  1) Data.Yaml.Data.Yaml encode/decode files with non-ASCII names
       uncaught exception: ParseException (InvalidYaml (Just (YamlException "Yaml file not found: test/resources/accent\233/foo.yaml")))

I was able to reproduce locally like so:

$ stack unpack yaml-0.8.18.2
$ cd yaml-0.8.18.2/
$ stack init --resolver nightly-2016-08-31
$ stack test

[snoyberg]

0.8.18.3 should solve this.

[DanBurton]

I'm seeing the same error with 0.8.18.3

[snoyberg]

OK, we need to leave the test disabled for now then. This is a bug in stack unpack (the same bug in the tar package), so we'll need to wait for a new Stack release to fix it. Can I recommend we move this to the stackage issue tracker at this point, since there's nothing we can do in yaml?

[snoyberg]

And it looks like the bug exists in cabal unpack as well, I'll open an issue there.

[snoyberg]

And it turns out that Hackage does not actually support packages which have non-ASCII filenames anyway, I get the following error:

Uploading yaml-0.8.18.4.tar.gz... unhandled status code: 400
Error: Invalid package

The package tarball contains an entry with a non-ASCII file name. For portability, package tarballs should contain only ASCII file names (e.g. not UTF8 encoded Unicode).
Upload failed on yaml-0.8.18.4.tar.gz

I'll work around this in the test suite itself.

[snoyberg]

Alright, should actually be put to rest now.