From 489d8949b83cb0196eca99f049aac3b760f60fb7 Mon Sep 17 00:00:00 2001 From: Lars Wirzenius Date: Wed, 13 Jul 2016 22:01:50 +0300 Subject: Fix typos, from Andrea Gelmini --- yarns/0030-basics.yarn | 2 +- yarns/0080-verify.yarn | 2 +- yarns/9000-implements.yarn | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) (limited to 'yarns') diff --git a/yarns/0030-basics.yarn b/yarns/0030-basics.yarn index 147fc13c..226ec2a8 100644 --- a/yarns/0030-basics.yarn +++ b/yarns/0030-basics.yarn @@ -67,7 +67,7 @@ We need to ensure Obnam can handle anything it encounters, on any supported platform. That is the purpose of the scenarios in this section. There are some limitations, though: the test suite is not run as the `root` user, and thus we don't deal with filesystem objects -that require priviledged operations such as device node creation. We +that require privileged operations such as device node creation. We also don't, in these scenarios, handle multiple filesystem types: the test suite should, instead, be run multiple types, with `TMPDIR` set to point at a different filesystem type each time: we leave that to diff --git a/yarns/0080-verify.yarn b/yarns/0080-verify.yarn index 1859abe4..1d33cf15 100644 --- a/yarns/0080-verify.yarn +++ b/yarns/0080-verify.yarn @@ -42,7 +42,7 @@ Verify notices when live data file has been appended to ------------------------------------------------------- In March, 2015, Thomas Waldemann noticed that `obnam verify` would -fail to notice if the live data file had been appened to. This +fail to notice if the live data file had been appended to. This regression test catches the problem. SCENARIO verify file that has been appended to diff --git a/yarns/9000-implements.yarn b/yarns/9000-implements.yarn index a1f313bf..1ae52444 100644 --- a/yarns/9000-implements.yarn +++ b/yarns/9000-implements.yarn @@ -258,7 +258,7 @@ Scenarios involving encryption may also use a private keyring directory. add_to_config "$MATCH_1" encrypt-with "$MATCH_2" -Encryption scenarions, at least, also need users that pretend to be +Encryption scenarios, at least, also need users that pretend to be someone else. IMPLEMENTS GIVEN a user (\S+) calling themselves (\S+) @@ -433,7 +433,7 @@ Check that there are no checkpoint generations. IMPLEMENTS THEN user (\S+) sees no checkpoint generations in repository (\S+) run_obnam "$MATCH_1" generations -r "$DATADIR/$MATCH_2" \ > "$DATADIR/generation.list" - if grep checkoint "$DATADIR/generation.list" + if grep checkpoint "$DATADIR/generation.list" then echo "Can see checkpoint generations!" 1>&2 exit 1 @@ -671,7 +671,7 @@ Some tests won't work correctly when `root` is running them. test "$(id -u)" != 0 For testing FUSE stuff, we need to check that the relevant stuff is -avaialble. Previously, we did this by checking that the user running +available. Previously, we did this by checking that the user running the test suite was in the group `fuse`, but that turns out to have been a Debianism (removed in the Debian `jessie` release). A better check is to check that the `fusermount` command is available. -- cgit v1.2.1