@@ -23,8 +23,10 @@ process works:
2323
2424The typical story on pull requests is: If Travis accepts it and the
2525author only added packages under his/her own name, merge it. If the
26−build later fails (see "Adding Debian packages for required system tools or libraries"),
27−then block the package until it's fixed.
26+build later fails (see [Adding Debian packages]), then block the
27+package until it's fixed.
28+
29+[Adding Debian packages]: https://github.com/fpco/stackage/blob/master/CURATORS.md#adding-debian-packages-for-required-system-tools-or-libraries
2830
2931If benchmarks, haddocks, or test suites fails at this point we
3032typically also block the package until these issues are fixed. This in
@@ -177,8 +179,14 @@ the maintainers of those packages.
177179
178180### Adding Debian packages for required system tools or libraries
179181Additional (non-Haskell) system libraries or tools should be added to `stackage/debian-bootstrap.sh`.
180−Committing the changes to a branch should trigger a DockerHub. Normally only the `nightly` branch needs to be updated
181−since new packages are not added to the current lts release.
182+After you've committed those changes, merging them into the `nightly` branch should
183+trigger a DockerHub build. Simply run:
184+
185+```bash
186+ $ git checkout nightly
187+ $ git merge master
188+ $ git push
189+```
182190
183191Use [Ubuntu Package content search](http://packages.ubuntu.com/) to determine which package provides particular dev files (it defaults to xenial which is the version used to build Nightly).
184192