Typos in evms strings (dapper)

[Malcolm Parsons]

plugins/s390/390segmgr.c:2573
"Use this function to format a dasd device prior to use."
s/dasd/DASD/

plugins/s390/options.c:2233
"Start Logical Block Aaddress"
s/Aa/A/

plugins/xfs/fs_xfs.c:1251
"Location of exteral journal"
s/exteral/external/

ui/gtk/help.c:56
"This dialog window allows you to create a compatibility volume.
A compatibility volume does not add EVMS meta-data to the object to
use for the volume. Unlike native EVMS volumes, there is no
opportunity to given the volume a persistent name. The name the
volume will use is generated from the storage object's name.

To create the compatibility volume, select one
of the topmost storage objects in the selection list and
click the 'Create' button."
s/given/give/

ui/gtk/help.c:470
"This dialog window allows you to remove a file system and
its associated File System Interface Module (FSIM) from a volume.

This operation is typically initiated if you intend to apply
a new file system or start over with a empty file system using
the same FSIM. Another reason to remove a file system may be to
have the FSIM remove any of its meta-data that might allow it
to be recognized or mountable by a file system driver.

Note that the actual disk operations will occur when you
commit changes made in this application."
s/a empty/an empty/

ui/gtk/main_window.c:1918
"Add a EVMS feature to an EVMS volume"
s/a EVMS/an EVMS/

ui/gtk/move.c:265
"The the logical disk is scheduled to be replaced."
s/The the/The/

ui/gtk/move.c:270
"The the storage object is scheduled to be replaced."
s/The the/The/

ui/ncurses/menu.c:1723
"Convert a Compatibility Volume to a EVMS Volume"
s/a EVMS/an EVMS/

ui/ncurses/menu.c:1730
Convert a EVMS Volume to a Compatibility Volume
s/a EVMS/an EVMS/

[Daniel Hahler (blueyed)]

Thanks for your patch. I've forwarded it upstream.

[Ian Weisser (ian-weisser)]

The patch was accepted by upstream...but only after the final version of evms was brought into Debian and then Ubuntu. So marking 'Invalid' since a release version of the fix seems unlikely at this time.

For LTS releases, an SRU is possible; however it is unlikely since these typos do not seems to affect the stability of the program. If there is any interest in pursuing an SRU, the instructions are at https://wiki.ubuntu.com/StableReleaseUpdates