git.iko.soy/stackage
on master help sign in
Update links to this repo
5bdaafaAdam Bergmark
CURATORS.md+16−16
compare with master
unifiedsplit
@@ -17,12 +17,12 @@ The following is the current list of curators, in alphabetical order:
17This section sketches out at a high level how the entire Stackage build/curation
17This section sketches out at a high level how the entire Stackage build/curation
18process works:
18process works:
19
19
20−* [build-constraints.yaml](https://github.com/fpco/stackage/blob/master/build-constraints.yaml) specifies packages to be included in Stackage
20+* [build-constraints.yaml](https://github.com/commercialhaskell/stackage/blob/master/build-constraints.yaml) specifies packages to be included in Stackage
21* [stackage-curator](http://www.stackage.org/package/stackage-curator) combines build-constraints.yaml with the current state of Hackage to create a build plan for a Stackage Nightly
21* [stackage-curator](http://www.stackage.org/package/stackage-curator) combines build-constraints.yaml with the current state of Hackage to create a build plan for a Stackage Nightly
22* stackage-curator can check that build plan to ensure all version bounds are consistent
22* stackage-curator can check that build plan to ensure all version bounds are consistent
23− * The [Travis job](https://github.com/fpco/stackage/blob/master/.travis.yml) performs these two steps to provide immediate feedback on pull requests
23+ * The [Travis job](https://github.com/commercialhaskell/stackage/blob/master/.travis.yml) performs these two steps to provide immediate feedback on pull requests
24−* Docker Hub [builds](https://github.com/fpco/stackage/blob/master/Dockerfile) a [Docker image](https://registry.hub.docker.com/u/snoyberg/stackage/) for running builds
24+* Docker Hub [builds](https://github.com/commercialhaskell/stackage/blob/master/Dockerfile) a [Docker image](https://registry.hub.docker.com/u/snoyberg/stackage/) for running builds
25−* The stackage-build server (described below) is able to run automated builds using the [build.sh script](https://github.com/fpco/stackage/blob/master/automated/build.sh)
25+* The stackage-build server (described below) is able to run automated builds using the [build.sh script](https://github.com/commercialhaskell/stackage/blob/master/automated/build.sh)
26* When a new Nightly build is completed, it is uploaded to [the nightly repo](https://github.com/fpco/stackage-nightly)
26* When a new Nightly build is completed, it is uploaded to [the nightly repo](https://github.com/fpco/stackage-nightly)
27* Once a week, we run an LTS minor bump. Instead of using build-constraints.yaml, that job takes the previous LTS release, turns it into constraints, and then bumps the version numbers to the latest on Hackage, in accordance with the version bounds in the build plan. This plans are uploaded to [the LTS repo](https://github.com/fpco/lts-haskell)
27* Once a week, we run an LTS minor bump. Instead of using build-constraints.yaml, that job takes the previous LTS release, turns it into constraints, and then bumps the version numbers to the latest on Hackage, in accordance with the version bounds in the build plan. This plans are uploaded to [the LTS repo](https://github.com/fpco/lts-haskell)
28* Cutting a new LTS major release is essentially just a Stackage Nightly that gets rebuilt and uploaded as an LTS
28* Cutting a new LTS major release is essentially just a Stackage Nightly that gets rebuilt and uploaded as an LTS
@@ -34,7 +34,7 @@ author only added packages under his/her own name, merge it. If the
34build later fails (see [Adding Debian packages]), then block the
34build later fails (see [Adding Debian packages]), then block the
35package until it's fixed.
35package until it's fixed.
36
36
37−[Adding Debian packages]: https://github.com/fpco/stackage/blob/master/CURATORS.md#adding-debian-packages-for-required-system-tools-or-libraries
37+[Adding Debian packages]: https://github.com/commercialhaskell/stackage/blob/master/CURATORS.md#adding-debian-packages-for-required-system-tools-or-libraries
38
38
39If benchmarks, haddocks, or test suites fails at this point we
39If benchmarks, haddocks, or test suites fails at this point we
40typically also block the package until these issues are fixed. This in
40typically also block the package until these issues are fixed. This in
@@ -73,13 +73,13 @@ being included immediately. This also applies to when only benchmarks
73and tests are affected.
73and tests are affected.
74
74
75* Copy the stackage-curator output and create a new issue, see e.g
75* Copy the stackage-curator output and create a new issue, see e.g
76−https://github.com/fpco/stackage/issues/2108
76+https://github.com/commercialhaskell/stackage/issues/2108
77
77
78* Add a new entry under the "stackage upper bounds" section of `build-constraints.yaml`. For the above example it would be
78* Add a new entry under the "stackage upper bounds" section of `build-constraints.yaml`. For the above example it would be
79
79
80```yaml
80```yaml
81 "Stackage upper bounds":
81 "Stackage upper bounds":
82− # https://github.com/fpco/stackage/issues/2108
82+ # https://github.com/commercialhaskell/stackage/issues/2108
83 - pipes < 4.3.0
83 - pipes < 4.3.0
84```
84```
85
85
@@ -90,7 +90,7 @@ https://github.com/fpco/stackage/issues/2108
90
90
91Sometimes releases for different packages are tightly coupled. Then it
91Sometimes releases for different packages are tightly coupled. Then it
92can make sense to combine them into one issue, as in
92can make sense to combine them into one issue, as in
93−https://github.com/fpco/stackage/issues/2143.
93+https://github.com/commercialhaskell/stackage/issues/2143.
94
94
95If a dependency that is not explicitly in stackage is causing test or
95If a dependency that is not explicitly in stackage is causing test or
96benchmark failures you can skip or expect them to fail (see "Skipping
96benchmark failures you can skip or expect them to fail (see "Skipping
@@ -123,7 +123,7 @@ enough time to upgrade for this case as well.
123With the `pipes` example above there was later a new release of
123With the `pipes` example above there was later a new release of
124`pipes-safe` that required the **newer** version of `pipes`. You can
124`pipes-safe` that required the **newer** version of `pipes`. You can
125add that package to the same upper bounds section,
125add that package to the same upper bounds section,
126−(e.g. https://github.com/fpco/stackage/commit/6429b1eb14db3f2a0779813ef2927085fa4ad673)
126+(e.g. https://github.com/commercialhaskell/stackage/commit/6429b1eb14db3f2a0779813ef2927085fa4ad673)
127as we want to lift them simultaneously.
127as we want to lift them simultaneously.
128
128
129### Skipping tests and benchmarks
129### Skipping tests and benchmarks
@@ -149,7 +149,7 @@ dependencies and compile them.
149
149
150If there are no version bounds that would fix the issue or if you
150If there are no version bounds that would fix the issue or if you
151can't figure it out, file it
151can't figure it out, file it
152−(e.g. https://github.com/fpco/stackage/issues/2133) to ask the
152+(e.g. https://github.com/commercialhaskell/stackage/issues/2133) to ask the
153maintainer for help.
153maintainer for help.
154
154
155### Waiting for new releases
155### Waiting for new releases
@@ -228,7 +228,7 @@ docker rmi $(docker images -q)
228but `docker pull snoyberg/stackage:nightly` can also be run instead just to update the nightly image say.
228but `docker pull snoyberg/stackage:nightly` can also be run instead just to update the nightly image say.
229
229
230For a new GHC version you should also delete the cache directories on the stackage-build server to
230For a new GHC version you should also delete the cache directories on the stackage-build server to
231−force all packages to be rebuilt. See: [issue#746](https://github.com/fpco/stackage/issues/746). Eg:
231+force all packages to be rebuilt. See: [issue#746](https://github.com/commercialhaskell/stackage/issues/746). Eg:
232```
232```
233rm -r nightly/work/builds/nightly/
233rm -r nightly/work/builds/nightly/
234```
234```
@@ -241,7 +241,7 @@ following command:
241```
241```
242DIR=$(mktemp -d)
242DIR=$(mktemp -d)
243(cd $DIR \
243(cd $DIR \
244− && git clone https://github.com/fpco/stackage \
244+ && git clone https://github.com/commercialhaskell/stackage \
245 && cd stackage \
245 && cd stackage \
246 && docker build --tag snoyberg/stackage:nightly .)
246 && docker build --tag snoyberg/stackage:nightly .)
247rm -rf $DIR
247rm -rf $DIR
@@ -360,7 +360,7 @@ Then, clone the stackage repo, get the latest packages and run dependency
360resolution:
360resolution:
361
361
362```
362```
363−$ git clone git@github.com:fpco/stackage.git
363+$ git clone git@github.com:commercialhaskell/stackage.git
364$ stack update && stackage-curator check
364$ stack update && stackage-curator check
365```
365```
366
366
@@ -372,12 +372,12 @@ test suites and benchmarks, to check whether bounds can be lifted, and to get
372errors for builds, tests and benchmarks.
372errors for builds, tests and benchmarks.
373
373
374[the Linux binary]: https://s3.amazonaws.com/stackage-travis/stackage-curator/stackage-curator.bz2
374[the Linux binary]: https://s3.amazonaws.com/stackage-travis/stackage-curator/stackage-curator.bz2
375−[tell-me-when-its-released]: https://github.com/fpco/stackage/blob/master/CURATORS.md#waiting-for-new-releases
375+[tell-me-when-its-released]: https://github.com/commercialhaskell/stackage/blob/master/CURATORS.md#waiting-for-new-releases
376
376
377## Adding new curators
377## Adding new curators
378
378
3791. Add public ssh key to `~/.ssh/authorized_keys` on build server
3791. Add public ssh key to `~/.ssh/authorized_keys` on build server
380−2. Add to fpco/stackage project.
380+2. Add to commercialhaskell/stackage project.
381
381
382## Dealing with a new GHC release
382## Dealing with a new GHC release
383
383
@@ -401,4 +401,4 @@ After the first LTS release, the package pruning process may begin in the
401nightly build in order to move forward with getting the latest versions of
401nightly build in order to move forward with getting the latest versions of
402packages compatible with the new GHC release.
402packages compatible with the new GHC release.
403
403
404−[GHC upgrade note]: https://github.com/fpco/stackage/blob/master/MAINTAINERS.md#upgrading-to-a-new-ghc-version
404+[GHC upgrade note]: https://github.com/commercialhaskell/stackage/blob/master/MAINTAINERS.md#upgrading-to-a-new-ghc-version
DATA-FLOW.md+3−3
@@ -15,7 +15,7 @@ There are three inputs into the data flow:
15 Hackage provides both cabal file metadata (via the 00-index.tar file) and
15 Hackage provides both cabal file metadata (via the 00-index.tar file) and
16 tarballs of the individual packages.
16 tarballs of the individual packages.
17
17
18−* [build-constraints.yaml](https://github.com/fpco/stackage/blob/master/build-constraints.yaml)
18+* [build-constraints.yaml](https://github.com/commercialhaskell/stackage/blob/master/build-constraints.yaml)
19 is the primary Stackage input file. This is where package maintainers can add
19 is the primary Stackage input file. This is where package maintainers can add
20 packages to the Stackage package set. This also defines upper bounds, skipped
20 packages to the Stackage package set. This also defines upper bounds, skipped
21 tests, and a few other pieces of metadata.
21 tests, and a few other pieces of metadata.
@@ -60,7 +60,7 @@ The heart of running Stackage builds is the
60[stackage-curator](https://github.com/fpco/stackage-curator) tool. We run this
60[stackage-curator](https://github.com/fpco/stackage-curator) tool. We run this
61on a daily basis on the Stackage build server for Stackage Nightly, and on a
61on a daily basis on the Stackage build server for Stackage Nightly, and on a
62weekly basis for LTS Haskell. The build process is [highly
62weekly basis for LTS Haskell. The build process is [highly
63−automated](https://github.com/fpco/stackage/blob/master/automated/build.sh) and
63+automated](https://github.com/commercialhaskell/stackage/blob/master/automated/build.sh) and
64leverages Docker quite a bit.
64leverages Docker quite a bit.
65
65
66stackage-curator needs to know about the most recent versions of all packages,
66stackage-curator needs to know about the most recent versions of all packages,
@@ -80,7 +80,7 @@ By combining these constraints with the current package data, stackage-curator
80can generate a build plan and check it. (As an aside, this build plan
80can generate a build plan and check it. (As an aside, this build plan
81generation and checking also occurs every time you make a pull request to the
81generation and checking also occurs every time you make a pull request to the
82stackage repo.) If there are version bounds problems, one of the [Stackage
82stackage repo.) If there are version bounds problems, one of the [Stackage
83−curators](https://github.com/fpco/stackage/blob/master/CURATORS.md) will open
83+curators](https://github.com/commercialhaskell/stackage/blob/master/CURATORS.md) will open
84up a Github issue and will add upper bounds, temporarily block a package, or
84up a Github issue and will add upper bounds, temporarily block a package, or
85some other corrective action.
85some other corrective action.
86
86
README.md+5−5
@@ -16,12 +16,12 @@ Add your package
16
16
17We welcome all packages, provided:
17We welcome all packages, provided:
18
18
19−* The package author/maintainer agrees to the [maintainers agreement](https://github.com/fpco/stackage/blob/master/MAINTAINERS.md).
19+* The package author/maintainer agrees to the [maintainers agreement](https://github.com/commercialhaskell/stackage/blob/master/MAINTAINERS.md).
20* The package is buildable and testable from Hackage. We recommend [the Stack Travis script](https://docs.haskellstack.org/en/stable/travis_ci/), which ensures a package is not accidentally incomplete.
20* The package is buildable and testable from Hackage. We recommend [the Stack Travis script](https://docs.haskellstack.org/en/stable/travis_ci/), which ensures a package is not accidentally incomplete.
21* The package is compatible with the newest versions of all dependencies (You can find restrictive upper bounds by visiting http://packdeps.haskellers.com/feed?needle=PACKAGENAME).
21* The package is compatible with the newest versions of all dependencies (You can find restrictive upper bounds by visiting http://packdeps.haskellers.com/feed?needle=PACKAGENAME).
22* The package is compatible with the versions of libraries that ship with GHC ([more information on lenient lower bounds](https://www.fpcomplete.com/blog/2014/05/lenient-lower-bounds)).
22* The package is compatible with the versions of libraries that ship with GHC ([more information on lenient lower bounds](https://www.fpcomplete.com/blog/2014/05/lenient-lower-bounds)).
23
23
24−Full details on how to add and test a package can be found in the [maintainers agreement](https://github.com/fpco/stackage/blob/master/MAINTAINERS.md#adding-a-package).
24+Full details on how to add and test a package can be found in the [maintainers agreement](https://github.com/commercialhaskell/stackage/blob/master/MAINTAINERS.md#adding-a-package).
25
25
26__NOTE__: There is an approximate 30 minute delay between a package uploading
26__NOTE__: There is an approximate 30 minute delay between a package uploading
27to Hackage and being available to the Travis build script to check upper
27to Hackage and being available to the Travis build script to check upper
@@ -50,7 +50,7 @@ Stackage both easier and more secure:
50* [stackage-build-plan](https://github.com/fpco/stackage-build-plan) [![Build Status](https://travis-ci.org/fpco/stackage-build-plan.svg?branch=master)](https://travis-ci.org/fpco/stackage-build-plan)
50* [stackage-build-plan](https://github.com/fpco/stackage-build-plan) [![Build Status](https://travis-ci.org/fpco/stackage-build-plan.svg?branch=master)](https://travis-ci.org/fpco/stackage-build-plan)
51
51
52Curious how it all fits together? See the [Stackage data
52Curious how it all fits together? See the [Stackage data
53−flow](https://github.com/fpco/stackage/blob/master/DATA-FLOW.md).
53+flow](https://github.com/commercialhaskell/stackage/blob/master/DATA-FLOW.md).
54
54
55
55
56Build the package set
56Build the package set
@@ -60,7 +60,7 @@ Generally only the stackage build server run by the stackage curator
60team and people interested in incorporating stackage snapshots into an
60team and people interested in incorporating stackage snapshots into an
61OS distribution need to build the entire package set. If you're
61OS distribution need to build the entire package set. If you're
62interested in trying this yourself, please check out
62interested in trying this yourself, please check out
63−[the curator guide](https://github.com/fpco/stackage/blob/master/CURATORS.md),
63+[the curator guide](https://github.com/commercialhaskell/stackage/blob/master/CURATORS.md),
64though be aware that this is not a recommended practice and there
64though be aware that this is not a recommended practice and there
65likely will be problems you will need to debug yourself.
65likely will be problems you will need to debug yourself.
66
66
@@ -102,7 +102,7 @@ There are a number of answers to this question:
102 another update in the LTS 6 line
102 another update in the LTS 6 line
103* Sometimes we have upper bounds in place because other packages have
103* Sometimes we have upper bounds in place because other packages have
104 problems with newer versions of dependencies. Open up the
104 problems with newer versions of dependencies. Open up the
105− [build-constraints file](https://github.com/fpco/stackage/blob/master/build-constraints.yaml)
105+ [build-constraints file](https://github.com/commercialhaskell/stackage/blob/master/build-constraints.yaml)
106 and search for "Stackage upper bounds"
106 and search for "Stackage upper bounds"
107* Wired-in packages - those that ship with GHC and cannot be upgraded,
107* Wired-in packages - those that ship with GHC and cannot be upgraded,
108 and packages depending on them - are fixed to GHC versions. Common
108 and packages depending on them - are fixed to GHC versions. Common
become-a-curator.md+1−1
@@ -37,7 +37,7 @@ The current curator team consists of:
37We onboarded Luke as the newest member a few months ago and this
37We onboarded Luke as the newest member a few months ago and this
38helped us iron out and document the process further.
38helped us iron out and document the process further.
39
39
40−You can read the curator documentation here: https://github.com/fpco/stackage/blob/master/CURATORS.md
40+You can read the curator documentation here: https://github.com/commercialhaskell/stackage/blob/master/CURATORS.md
41
41
42To apply, please fill in this form: [REDACTED]
42To apply, please fill in this form: [REDACTED]
43
43
debian-bootstrap.sh+1−1
@@ -4,7 +4,7 @@
4# up-and-running on a freshly installed Debian-based system (including Ubuntu).
4# up-and-running on a freshly installed Debian-based system (including Ubuntu).
5
5
6# Quick start:
6# Quick start:
7−# wget -O - https://raw.github.com/fpco/stackage/master/debian-bootstrap.sh | bash -ex
7+# wget -O - https://raw.github.com/commercialhaskell/stackage/master/debian-bootstrap.sh | bash -ex
8
8
9# NOTE: Requires that GHC and Cabal are installed and on your PATH. For
9# NOTE: Requires that GHC and Cabal are installed and on your PATH. For
10# instructions, see:
10# instructions, see:
stackage/stackage.cabal+1−1
@@ -26,4 +26,4 @@ library
26
26
27source-repository head
27source-repository head
28 type: git
28 type: git
29− location: git://github.com/fpco/stackage.git
29+ location: git://github.com/commercialhaskell/stackage.git