summaryrefslogtreecommitdiffstats
path: root/debian/patches/spelling
diff options
context:
space:
mode:
Diffstat (limited to 'debian/patches/spelling')
-rw-r--r--debian/patches/spelling37
1 files changed, 37 insertions, 0 deletions
diff --git a/debian/patches/spelling b/debian/patches/spelling
new file mode 100644
index 0000000..c1cacd9
--- /dev/null
+++ b/debian/patches/spelling
@@ -0,0 +1,37 @@
+Description: Fix spelling errors reported by lintian
+Author: Valentin Vidic <Valentin.Vidic@CARNet.hr>
+Forwarded: not-needed
+Last-Update: 2018-02-18
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/agents/ironic/fence_ironic.py
++++ b/agents/ironic/fence_ironic.py
+@@ -110,7 +110,7 @@
+ options = check_input(device_opt, process_input(device_opt))
+
+ docs = {}
+- docs["shortdesc"] = "Fence agent for OpenStack's Ironic (Bare Metal as a service) service"
++ docs["shortdesc"] = "Fence agent for OpenStack's Ironic (Bare Metal as a service)"
+ docs["longdesc"] = "fence_ironic is a Fencing agent \
+ which can be used with machines controlled by the Ironic service. \
+ This agent calls the openstack CLI. \
+--- a/tests/data/metadata/fence_ironic.xml
++++ b/tests/data/metadata/fence_ironic.xml
+@@ -1,5 +1,5 @@
+ <?xml version="1.0" ?>
+-<resource-agent name="fence_ironic" shortdesc="Fence agent for OpenStack's Ironic (Bare Metal as a service) service" >
++<resource-agent name="fence_ironic" shortdesc="Fence agent for OpenStack's Ironic (Bare Metal as a service)" >
+ <longdesc>fence_ironic is a Fencing agent which can be used with machines controlled by the Ironic service. This agent calls the openstack CLI. WARNING! This fence agent is not intended for production use. Relying on a functional ironic service for fencing is not a good design choice.</longdesc>
+ <vendor-url>https://wiki.openstack.org/wiki/Ironic</vendor-url>
+ <parameters>
+--- a/tests/data/metadata/fence_kdump.xml
++++ b/tests/data/metadata/fence_kdump.xml
+@@ -3,7 +3,7 @@
+ <longdesc>fence_kdump is an I/O fencing agent to be used with the kdump
+ crash recovery service. When the fence_kdump agent is invoked,
+ it will listen for a message from the failed node that acknowledges
+-that the failed node it executing the kdump crash kernel.
++that the failed node is executing the kdump crash kernel.
+ Note that fence_kdump is not a replacement for traditional
+ fencing methods. The fence_kdump agent can only detect that a
+ node has entered the kdump crash recovery service. This allows the