aboutsummaryrefslogtreecommitdiffstats
path: root/debian/patches/series
diff options
context:
space:
mode:
authorBryan Newbold <bnewbold@robocracy.org>2017-10-12 21:06:23 -0700
committerBryan Newbold <bnewbold@robocracy.org>2017-10-12 21:11:35 -0700
commit6921196b1de16fa296f70d12610f85dad8c298f4 (patch)
tree95c5fe5a6eedbe2ba191bd627e67a705def6e3a7 /debian/patches/series
parenta20a94bb8afd5391a92a0e3bdba441704ae5bf7b (diff)
downloadscm-6921196b1de16fa296f70d12610f85dad8c298f4.tar.gz
scm-6921196b1de16fa296f70d12610f85dad8c298f4.zip
bigrecy patch for 32-bit bignum failures
Cherry-picked a single commit from upstream. Turns out this bug (which was causing test failures and thus FTBFS on a subset of platforms) had been identified and fixed upstream a year ago, but had not made it's way into version control (CVS) or the Changelog. See also: http://lists.gnu.org/archive/html/scm-discuss/2017-10/msg00009.html
Diffstat (limited to 'debian/patches/series')
-rw-r--r--debian/patches/series1
1 files changed, 1 insertions, 0 deletions
diff --git a/debian/patches/series b/debian/patches/series
index 102a07f..2f25f43 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -4,3 +4,4 @@ texinfo5_fixes.patch
ppc64_short_int.patch
arm64_short_int.patch
hurd_maxpathlen.patch
+bigrecy_32bit_upstream.patch