ghc-persistent-template-2.1.8.1-2.4

- disable %{ix86} build

- Update to version 2.1.8.1 revision 0 with cabal2obs.

- update to 2.1.8.1
  * fix a bad Eq instance /= definition for Key when mpsGenetric=True

-update to 2.1.8
  * Support for GHC 8
  * aeson 0.11
  * transformers 0.5

- update to 2.1.6

- update to 2.1.5

- initial commit

- Update persistent-template to version 2.12.0.0.
  [#]# 2.12.0.0
  * Decomposed `HaskellName` into `ConstraintNameHS`, `EntityNameHS`, `FieldNameHS`. Decomposed `DBName` into `ConstraintNameDB`, `EntityNameDB`, `FieldNameDB` respectively. [#1174](https://github.com/yesodweb/persistent/pull/1174)
  * [#1214](https://github.com/yesodweb/persistent/pull/1214):
  * This package was asborbed into `persistent` itself.

- Update persistent-template to version 2.9.1.0 revision 1.
  Upstream has revised the Cabal build instructions on Hackage.

- disable %{ix86} build

- Update persistent-template to version 2.9.1.0.
  [#]# 2.9.1.0
  * [#1145](https://github.com/yesodweb/persistent/pull/1148)
  * Fix a bug where the `SqlType` for a shared primary key was being
    incorrectly set to `SqlString` instead of whatever the target primary key
    sql type was.
  * [#1151](https://github.com/yesodweb/persistent/pull/1151)
  * Automatically generate `SymbolToField` instances for datatypes, allowing
    `OverloadedLabels` to be used with the `EntityField` type.
  [#]# 2.9
  * Always use the "stock" strategy when deriving Show/Read for keys [#1106](https://github.com/yesodweb/persistent/pull/1106)
  * This fixes a regression from 2.8.0, which started using the `newtype` strategy when deriving `Show`/`Read` for keys
  * In practice, this means that from 2.8.0–2.8.3.1, for the following schema:
  ```
  Person
  name Text
  CustomPrimary
  anInt Int
  Primary anInt
  name Text
  ```
  `PersonKey 1` would show as `"SqlBackendKey {unSqlBackendKey = 1}"`
  and `CustomPrimaryKey 1` would show as `"1"`
  This was generally poor for debugging and logging, since all tables keys would print the same. For Persistent < 2.8.0 and > 2.8.3.1, they instead will show as:
  `"PersonKey {unPersonKey = SqlBackendKey {unSqlBackendKey = 1}}"`
  and `"CustomPrimaryKey {unCustomPrimaryKey = 1}"`
  This could be a breaking change if you have used `Show` on a key, wrote that string into some persistent storage like a database, and are trying to `Read` it back again later.
  [#]# 2.8.3.1
  * Allow aeson 1.5. [#1085](https://github.com/yesodweb/persistent/pull/1085)
  [#]# 2.8.3.0
  * Add `Lift` instances for the cascade types. [#1060](https://github.com/yesodweb/persistent/pull/1060)
  * Use `DeriveLift` to implement all `Lift` instances. Among other benefits,
    this provides implementations of `liftTyped` on `template-haskell-2.16` (GHC
    8.10) or later. [#1064](https://github.com/yesodweb/persistent/pull/1064)

- Update persistent-template to version 2.8.2.3 revision 2.
  Upstream has revised the Cabal build instructions on Hackage.

- Update persistent-template to version 2.8.2.3 revision 1.
  Upstream has revised the Cabal build instructions on Hackage.

- Add _constraints with 6GB min disk space for ppc64/ppc64le

- Replace %setup -q with the more modern %autosetup macro.

- Add persistent-template at version 2.8.2.3.