This is an automated email from the git hooks/post-receive script.
adsb pushed a commit to branch master
in repository lintian.
commit 630309bd16f0a9ea6ce1d1b1aa6b16fab0feaa70
Author: Adam D. Barratt <a...@adam-barratt.org.uk>
Date: Mon Dec 25 18:24:06 2017 +0300
triggers.desc: English review
---
checks/triggers.desc | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/checks/triggers.desc b/checks/triggers.desc
index fba8d56..c6c881a 100644
--- a/checks/triggers.desc
+++ b/checks/triggers.desc
@@ -10,10 +10,10 @@ Certainty: possible
Info: The package has a trigger that Lintian does not recognise in its
control file.
.
- The package may be uninstallable if dpkg does not support the trigger.
+ The package may be uninstallable, if dpkg does not support the trigger.
.
If this is a new type of trigger, then Lintian may simply be out of date.
- Please verify if the latest version of Lintian know of the trigger or file
+ Please verify if the latest version of Lintian knows of the trigger, or file
a bug against Lintian.
Ref: deb-triggers(5)
@@ -21,16 +21,16 @@ Tag: uses-implicit-await-trigger
Severity: normal
Certainty: possible
Info: The listed trigger is present in the control file of the package.
- The trigger is an await trigger, which may be not obvious from its name.
+ The trigger is an await trigger, which may not be obvious from its name.
.
- Await triggers puts rather strong requirements on dpkg that often lead
+ Await triggers place rather strong requirements on dpkg that often lead
to trigger cycles due to changes in other packages.
.
- If the package does not need the guarantees that dpkg provide to await
+ If the package does not need the guarantees that dpkg provides to await
triggers, please use the "-noawait" variant of the trigger. This is often
the case for packages that use the trigger to compile a form of cache.
.
- If the package do need the guarantees provided by dpkg, then please
+ If the package does need the guarantees provided by dpkg, then please
document the rationale in a comment above the trigger and use the
"-await" variant of the trigger to avoid this warning.
Ref: deb-triggers(5), #774559
@@ -45,11 +45,11 @@ Info: The package repeats the same trigger. There should
be no reason to
the last declaration will be the effective one.
.
This tag is also triggered if the package has an <tt>activate</tt> trigger
- for something it also declares an <tt>interest</tt>. The only (but rather
- unlikely) reason to do this is if another package <i>also</i> has an
- also declares an <tt>interest</tt> and this package need to activate that
+ for something on which it also declares an <tt>interest</tt>. The only (but
+ rather unlikely) reason to do this is if another package <i>also</i>
+ declares an <tt>interest</tt> and this package needs to activate that
other package. If the package is using it for this exact purpose, then
- please use a lintian override to state this.
+ please use a Lintian override to state this.
.
Please remove any duplicate definitions.
Ref: deb-triggers(5), #698723
--
Alioth's /usr/local/bin/git-commit-notice on
/srv/git.debian.org/git/lintian/lintian.git
