GHC 2018-11-02

2018-11-02 14:09:00, https://git.io/fxpeM in Homebrew/homebrew-core

Switching to the auto-generated tarball for now, in case the tarball is updated.

2018-11-02 14:04:40, https://git.io/fxpeD in Homebrew/homebrew-core

Sure. https://github.com/stedolan/jq/issues/1352#issuecomment-435390228

2018-11-02 14:04:10, https://git.io/fxpey in stedolan/jq

@wtlangford The tarball https://github.com/stedolan/jq/releases/download/jq-1.6/jq-1.6.tar.gz is a little weird:

```console
$ tar tf jq-1.6.tar.gz
./._jq-1.6
jq-1.6/
jq-1.6/._.github
jq-1.6/.github/
jq-1.6/._.gitmodules
jq-1.6/.gitmodules
jq-1.6/._.travis.yml
jq-1.6/.travis.yml
jq-1.6/._appveyor.yml
jq-1.6/appveyor.yml
jq-1.6/._AUTHORS
jq-1.6/AUTHORS
jq-1.6/._build
jq-1.6/build/
jq-1.6/._ChangeLog
jq-1.6/ChangeLog
jq-1.6/._compile-ios.sh
jq-1.6/compile-ios.sh
jq-1.6/._config
jq-1.6/config/
jq-1.6/._configure.ac
jq-1.6/configure.ac
jq-1.6/._COPYING
jq-1.6/COPYING
...
```

Also it doesn't contain a `configure` script, which was part of previous release tarballs. It would be nice to not have to run `autoreconf` for a release.

2018-11-02 14:01:05, https://git.io/fxpeS in Homebrew/homebrew-core

git-cinnabar 0.5.0
==================

- [x] Have you followed the [guidelines for contributing](https://github.com/Homebrew/homebrew-core/blob/master/CONTRIBUTING.md)?
- [x] Have you checked that there aren't other open [pull requests](https://github.com/Homebrew/homebrew-core/pulls) for the same formula update/change?
- [x] Have you built your formula locally with `brew install --build-from-source <formula>`, where `<formula>` is the name of the formula you're submitting?
- [x] Does your build pass `brew audit --strict <formula>` (after doing `brew install <formula>`)?

-----

2018-11-02 13:25:01, https://git.io/fxxbp in Homebrew/homebrew-core

Unfortunately, the "release tarball" contains a bunch of random trash (every file has a `._*` counterpart), but no `configure` is to be found.

2018-11-02 13:15:17, https://git.io/fxxbj in Homebrew/homebrew-core

Sorry, no, there's no reason for this. In fact, I updated these resource blocks with my semi-automated tool, but I happened to use a wrong Python and picked up a bunch of cached old versions. This is now corrected.