[yum-commits] 2 commits - docs/yum.8 yumcommands.py

Ville Skyttä scop at osuosl.org
Wed Dec 14 22:19:56 UTC 2011


 docs/yum.8     |   18 +++++++++---------
 yumcommands.py |    6 +++---
 2 files changed, 12 insertions(+), 12 deletions(-)

New commits:
commit 7d6f6b55ad4cc6c0308112e893dfc2bbae8fbe8f
Author: Ville Skyttä <ville.skytta at iki.fi>
Date:   Tue Dec 13 23:13:18 2011 +0200

    Man page spelling fixes.

diff --git a/docs/yum.8 b/docs/yum.8
index 499da41..6cc0411 100644
--- a/docs/yum.8
+++ b/docs/yum.8
@@ -94,7 +94,7 @@ glob and any matches are then installed\&. If the name starts with an
 command\&. If the name starts with a - character, then a search is done within
 the transaction and any matches are removed. If the name is a file, then install works
 like localinstall\&. If the name doesn't match a package, then package
-"provides" are searched (Eg. "_sqlitecache.so()(64bit)") as are
+"provides" are searched (e.g. "_sqlitecache.so()(64bit)") as are
 filelists (Eg. "/usr/bin/yum"). Also note that for filelists, wildcards will
 match multiple packages\&.
 .IP 
@@ -114,7 +114,7 @@ changes, for example: upgrading from somelinux 8.0 to somelinux 9.
 
 Note that "\fBupdate\fP" works on installed packages first, and only if there
 are no matches does it look for available packages. The difference is most
-noticable when you do "\fBupdate\fP foo-1-2" which will act exactly as
+noticeable when you do "\fBupdate\fP foo-1-2" which will act exactly as
 "\fBupdate\fP foo" if foo-1-2 is installed. You can use the "\fBupdate-to\fP"
 if you'd prefer that nothing happen in the above case.
 .IP 
@@ -227,7 +227,7 @@ to only remove packages which aren't required by something else.
 
 "\fBgroup info\fP" is used to give the description and package list of a group (and which type
 those packages are marked as). Note that you can use the yum-filter-data and
-yum-list-data plugins to get/use the data the other way around (Ie. what
+yum-list-data plugins to get/use the data the other way around (i.e. what
 groups own packages need updating). If you pass the \-v option, to enable verbose
 mode, then the package names are matched against installed/available packages
 similar to the list command.
@@ -298,8 +298,8 @@ package counts/etc. will be zeroed out).
 .IP "\fBversion\fP"
 Produces a "version" of the rpmdb, and of the enabled repositories if "all" is
 given as the first argument. You can also specify version groups in the
-version-groups config. file. If you pass \-v, for verbose mode, more
-information is listed. The version is calculated by taking a sha1 hash of the
+version-groups configuration file. If you pass \-v, for verbose mode, more
+information is listed. The version is calculated by taking an SHA1 hash of the
 packages (in sorted order), and the checksum_type/checksum_data entries from
 the yumdb. Note that this rpmdb version is now also used significantly within
 yum (esp. in yum history).
@@ -349,9 +349,9 @@ downgraded.
 
 The undo/redo commands act on the specified transaction, undo'ing or repeating
 the work of that transaction. While the rollback command will undo all
-transactions upto the point of the specified transaction. For example, if you
+transactions up to the point of the specified transaction. For example, if you
 have 3 transactions, where package A; B and C where installed respectively.
-Then "undo 1" will try to remove pacakge A, "redo 1" will try to install package
+Then "undo 1" will try to remove package A, "redo 1" will try to install package
 A (if it is not still installed), and "rollback 1" will try to remove packages
 B and C. Note that after a "rollback 1" you will have a fourth transaction,
 although the ending rpmdb version (see: yum version) should be the same in
@@ -363,7 +363,7 @@ takes a package (with wildcards).
 The stats command shows some statistics about the current history DB.
 
 The sync commands allows you to change the rpmdb/yumdb data stored for any
-installed packages, to whaever is in the current rpmdb/yumdb (this is mostly
+installed packages, to whatever is in the current rpmdb/yumdb (this is mostly
 useful when this data was not stored when the package went into the history DB).
 
 In "history list" you can change the behaviour of the 2nd column via. the
@@ -451,7 +451,7 @@ Sets the error level to [number] Practical range 0 \- 10. 0 means print only cri
 .br
 Configuration Option: \fBerrorlevel\fP
 .IP "\fB\-\-rpmverbosity=[name]\fP" 
-Sets the debug level to [name] for rpm scriplets. 'info' is the default, other
+Sets the debug level to [name] for rpm scriptlets. 'info' is the default, other
 options are: 'critical', 'emergency', 'error', 'warn' and 'debug'.
 .br
 Configuration Option: \fBrpmverbosity\fP
commit c8de09ff181bbb1f00fec4cc70f91564272ceba9
Author: Ville Skyttä <ville.skytta at iki.fi>
Date:   Tue Dec 13 23:10:35 2011 +0200

    Fix command docstring copy-pastos.

diff --git a/yumcommands.py b/yumcommands.py
index 36b19b3..2526fda 100644
--- a/yumcommands.py
+++ b/yumcommands.py
@@ -495,7 +495,7 @@ def _list_cmd_calc_columns(base, ypl):
 
 class InfoCommand(YumCommand):
     """A class containing methods needed by the cli to execute the
-    update command.
+    info command.
     """
 
     def getNames(self):
@@ -1115,7 +1115,7 @@ class ProvidesCommand(YumCommand):
 
 class CheckUpdateCommand(YumCommand):
     """A class containing methods needed by the cli to execute the
-    update command.
+    check-update command.
     """
 
     def getNames(self):
@@ -1274,7 +1274,7 @@ class SearchCommand(YumCommand):
 
 class UpgradeCommand(YumCommand):
     """A class containing methods needed by the cli to execute the
-    update command.
+    upgrade command.
     """
 
     def getNames(self):


More information about the Yum-commits mailing list