aboutsummaryrefslogtreecommitdiffstats
path: root/community/git-lfs/fix-test-locks.patch
diff options
context:
space:
mode:
authorJakub Jirutka <jakub@jirutka.cz>2017-11-25 21:30:11 +0100
committerJakub Jirutka <jakub@jirutka.cz>2017-11-25 21:30:11 +0100
commit6e4543b2e2d547ade54148548ca85d0dd2e89784 (patch)
treec2d6a95ba5388df7d26975840bb04e6050d99e7a /community/git-lfs/fix-test-locks.patch
parentd954f31e7b000499d56432bf716dfeae53d4900e (diff)
downloadaports-6e4543b2e2d547ade54148548ca85d0dd2e89784.tar.bz2
aports-6e4543b2e2d547ade54148548ca85d0dd2e89784.tar.xz
community/git-lfs: move from testing
Diffstat (limited to 'community/git-lfs/fix-test-locks.patch')
-rw-r--r--community/git-lfs/fix-test-locks.patch13
1 files changed, 13 insertions, 0 deletions
diff --git a/community/git-lfs/fix-test-locks.patch b/community/git-lfs/fix-test-locks.patch
new file mode 100644
index 0000000000..dabbfce8a3
--- /dev/null
+++ b/community/git-lfs/fix-test-locks.patch
@@ -0,0 +1,13 @@
+This is probably a typo. I have no idea why it does not fail for upstream...
+
+--- a/test/test-locks.sh
++++ b/test/test-locks.sh
+@@ -100,7 +100,7 @@
+
+ for i in $(seq 1 5); do
+ git lfs lock --json "h_$i.dat" | tee lock.log
+- assert_server_lock "$reponame" "$(assert_lock "lock.log" "h_$1.dat")"
++ assert_server_lock "$reponame" "$(assert_lock "lock.log" "h_$i.dat")"
+ done
+
+ # The server will return, at most, three locks at a time