···2323 # branches (wip patches from tickets), but exports each commit as a separate
2424 # patch, so merge commits can lead to conflicts. Used if squashed == false.
2525 #
2626+ # The above is the preferred option. To use it, find a Trac ticket and pass the
2727+ # "Commit" field from the ticket as "rev", choosing "base" as an appropriate
2828+ # release tag, i.e. a tag that doesn't cause the patch to include a lot of
2929+ # unrelated changes. If there is no such tag (due to nonlinear history, for
3030+ # example), there are two other options, listed below.
3131+ #
2632 # 2) From GitHub's sagemath/sage repo. This lets us use a GH feature that allows
2733 # us to choose between a .patch file, with one patch per commit, or a .diff file,
2834 # which squashes all commits into a single diff. This is used if squashed ==
···117123 name = "sympy-1.9-update.patch";
118124 rev = "beed4e16aff32e47d0c3b1c58cb1e2f4c38590f8";
119125 sha256 = "sha256-3eJPfWfCrCAQ5filIn7FbzjRQeO9QyTIVl/HyRuqFtE=";
126126+ })
127127+128128+ # https://trac.sagemath.org/ticket/32797
129129+ (fetchSageDiff {
130130+ base = "9.5.beta7";
131131+ name = "pari-2.13.3-update.patch";
132132+ rev = "f5f7a86908daf60b25e66e6a189c51ada7e0a732";
133133+ sha256 = "sha256-H/caGx3q4KcdsyGe+ojV9bUTQ5y0siqM+QHgDbeEnbw=";
120134 })
121135 ];
122136