From d632109cd5964f7d4baa408d517e44f801e1be8d Mon Sep 17 00:00:00 2001 From: Michael Vogt Date: Tue, 15 Nov 2005 14:18:07 +0100 Subject: * initial revision (after accidently killing it) --- help/C/Makefile.am | 7 + help/C/fdl-appendix.xml | 655 ++++++++++++ help/C/figures/authentication-add.png | Bin 0 -> 303198 bytes help/C/figures/authentication.png | Bin 0 -> 274684 bytes help/C/figures/download-progressbar.png | Bin 0 -> 208318 bytes help/C/figures/failed-repos.png | Bin 0 -> 243774 bytes help/C/figures/install-progress-terminal.png | Bin 0 -> 451335 bytes help/C/figures/install-progress.png | Bin 0 -> 133917 bytes help/C/figures/main-system-updates-available.png | Bin 0 -> 277960 bytes .../main-system-updates-summary-details.png | Bin 0 -> 368111 bytes help/C/figures/main-system-updates-summary.png | Bin 0 -> 308065 bytes help/C/figures/main-system-uptodate.png | Bin 0 -> 229559 bytes help/C/figures/main-view-monitor-update.png | Bin 0 -> 471026 bytes help/C/figures/main-view-update-detail.png | Bin 0 -> 356191 bytes help/C/figures/preferences-add-custom.png | Bin 0 -> 150488 bytes help/C/figures/preferences-add.png | Bin 0 -> 114050 bytes help/C/figures/preferences-edit.png | Bin 0 -> 116045 bytes help/C/figures/preferences-repos-changeinfo.png | Bin 0 -> 138955 bytes help/C/figures/preferences.png | Bin 0 -> 341184 bytes help/C/figures/reload-package-info.png | Bin 0 -> 250061 bytes help/C/figures/settings.png | Bin 0 -> 206450 bytes help/C/figures/synaptic-toggle-install-view.png | Bin 0 -> 319986 bytes help/C/legal.xml | 76 ++ help/C/update-manager-C.omf | 18 + help/C/update-manager-C.omf.out | 17 + help/C/update-manager.xml | 1070 ++++++++++++++++++++ help/Makefile.am | 1 + 27 files changed, 1844 insertions(+) create mode 100644 help/C/Makefile.am create mode 100644 help/C/fdl-appendix.xml create mode 100644 help/C/figures/authentication-add.png create mode 100644 help/C/figures/authentication.png create mode 100644 help/C/figures/download-progressbar.png create mode 100644 help/C/figures/failed-repos.png create mode 100644 help/C/figures/install-progress-terminal.png create mode 100644 help/C/figures/install-progress.png create mode 100644 help/C/figures/main-system-updates-available.png create mode 100644 help/C/figures/main-system-updates-summary-details.png create mode 100644 help/C/figures/main-system-updates-summary.png create mode 100644 help/C/figures/main-system-uptodate.png create mode 100644 help/C/figures/main-view-monitor-update.png create mode 100644 help/C/figures/main-view-update-detail.png create mode 100644 help/C/figures/preferences-add-custom.png create mode 100644 help/C/figures/preferences-add.png create mode 100644 help/C/figures/preferences-edit.png create mode 100644 help/C/figures/preferences-repos-changeinfo.png create mode 100644 help/C/figures/preferences.png create mode 100644 help/C/figures/reload-package-info.png create mode 100644 help/C/figures/settings.png create mode 100644 help/C/figures/synaptic-toggle-install-view.png create mode 100644 help/C/legal.xml create mode 100644 help/C/update-manager-C.omf create mode 100644 help/C/update-manager-C.omf.out create mode 100644 help/C/update-manager.xml create mode 100644 help/Makefile.am (limited to 'help') diff --git a/help/C/Makefile.am b/help/C/Makefile.am new file mode 100644 index 00000000..f1c36ffb --- /dev/null +++ b/help/C/Makefile.am @@ -0,0 +1,7 @@ +figdir = figures +docname = update-manager +lang = C +omffile = update-manager-C.omf +entities = fdl-appendix.xml legal.xml +include $(top_srcdir)/xmldocs.make +dist-hook: app-dist-hook diff --git a/help/C/fdl-appendix.xml b/help/C/fdl-appendix.xml new file mode 100644 index 00000000..23badd79 --- /dev/null +++ b/help/C/fdl-appendix.xml @@ -0,0 +1,655 @@ + + + + + + Version 1.1, March 2000 + + + 2000Free Software Foundation, Inc. + + + +
Free Software Foundation, Inc. 59 Temple Place, + Suite 330, Boston, MA + 02111-1307 USA
+ Everyone is permitted to copy and distribute verbatim copies of this + license document, but changing it is not allowed. + + + + GNU Free Documentation License + + + 0. PREAMBLE + + The purpose of this License is to make a manual, textbook, or + other written document free in the sense of + freedom: to assure everyone the effective freedom to copy and + redistribute it, with or without modifying it, either + commercially or noncommercially. Secondarily, this License + preserves for the author and publisher a way to get credit for + their work, while not being considered responsible for + modifications made by others. + + + + This License is a kind of copyleft, which means + that derivative works of the document must themselves be free in + the same sense. It complements the GNU General Public License, + which is a copyleft license designed for free software. + + + + We have designed this License in order to use it for manuals for + free software, because free software needs free documentation: a + free program should come with manuals providing the same + freedoms that the software does. But this License is not limited + to software manuals; it can be used for any textual work, + regardless of subject matter or whether it is published as a + printed book. We recommend this License principally for works + whose purpose is instruction or reference. + + + + 1. APPLICABILITY AND DEFINITIONS + + This License applies to any manual or other work that contains a + notice placed by the copyright holder saying it can be + distributed under the terms of this License. The + Document, below, refers to any such manual or + work. Any member of the public is a licensee, and is addressed + as you. + + + + A Modified Version of the Document means any work + containing the Document or a portion of it, either copied + verbatim, or with modifications and/or translated into another + language. + + + + A Secondary Section is a named appendix or a + front-matter section of the Document that deals exclusively + with the relationship of the publishers or authors of the + Document to the Document's overall subject (or to related + matters) and contains nothing that could fall directly within + that overall subject. (For example, if the Document is in part a + textbook of mathematics, a Secondary Section may not explain any + mathematics.) The relationship could be a matter of historical + connection with the subject or with related matters, or of + legal, commercial, philosophical, ethical or political position + regarding them. + + + + The Invariant Sections are certain Secondary Sections whose titles + are designated, as being those of Invariant Sections, in the + notice that says that the Document is released under this + License. + + + + The Cover Texts are certain short passages of + text that are listed, as Front-Cover Texts or Back-Cover Texts, + in the notice that says that the Document is released under this + License. + + + + A Transparent copy of the Document means a machine-readable + copy, represented in a format whose specification is available + to the general public, whose contents can be viewed and edited + directly and straightforwardly with generic text editors or (for + images composed of pixels) generic paint programs or (for + drawings) some widely available drawing editor, and that is + suitable for input to text formatters or for automatic + translation to a variety of formats suitable for input to text + formatters. A copy made in an otherwise Transparent file format + whose markup has been designed to thwart or discourage + subsequent modification by readers is not Transparent. A copy + that is not Transparent is called + Opaque. + + + + Examples of suitable formats for Transparent copies include + plain ASCII without markup, Texinfo input format, LaTeX input + format, SGML or XML using a publicly available DTD, and + standard-conforming simple HTML designed for human + modification. Opaque formats include PostScript, PDF, + proprietary formats that can be read and edited only by + proprietary word processors, SGML or XML for which the DTD + and/or processing tools are not generally available, and the + machine-generated HTML produced by some word processors for + output purposes only. + + + + The Title Page means, for a printed book, the + title page itself, plus such following pages as are needed to + hold, legibly, the material this License requires to appear in + the title page. For works in formats which do not have any title + page as such, Title Page means the text near the + most prominent appearance of the work's title, preceding the + beginning of the body of the text. + + + + + 2. VERBATIM COPYING + + You may copy and distribute the Document in any medium, either + commercially or noncommercially, provided that this License, the + copyright notices, and the license notice saying this License + applies to the Document are reproduced in all copies, and that + you add no other conditions whatsoever to those of this + License. You may not use technical measures to obstruct or + control the reading or further copying of the copies you make or + distribute. However, you may accept compensation in exchange for + copies. If you distribute a large enough number of copies you + must also follow the conditions in section 3. + + + + You may also lend copies, under the same conditions stated + above, and you may publicly display copies. + + + + + 3. COPYING IN QUANTITY + + If you publish printed copies of the Document numbering more than 100, + and the Document's license notice requires Cover Texts, you must enclose + the copies in covers that carry, clearly and legibly, all these + Cover Texts: Front-Cover Texts on the front cover, and + Back-Cover Texts on the back cover. Both covers must also + clearly and legibly identify you as the publisher of these + copies. The front cover must present the full title with all + words of the title equally prominent and visible. You may add + other material on the covers in addition. Copying with changes + limited to the covers, as long as they preserve the title of the + Document and satisfy these + conditions, can be treated as verbatim copying in other + respects. + + + + If the required texts for either cover are too voluminous to fit + legibly, you should put the first ones listed (as many as fit + reasonably) on the actual cover, and continue the rest onto + adjacent pages. + + + + If you publish or distribute Opaque copies of the Document numbering more than 100, + you must either include a machine-readable Transparent copy along with + each Opaque copy, or state in or with each Opaque copy a + publicly-accessible computer-network location containing a + complete Transparent copy of the Document, free of added + material, which the general network-using public has access to + download anonymously at no charge using public-standard network + protocols. If you use the latter option, you must take + reasonably prudent steps, when you begin distribution of Opaque + copies in quantity, to ensure that this Transparent copy will + remain thus accessible at the stated location until at least one + year after the last time you distribute an Opaque copy (directly + or through your agents or retailers) of that edition to the + public. + + + + It is requested, but not required, that you contact the authors + of the Document well before + redistributing any large number of copies, to give them a chance + to provide you with an updated version of the Document. + + + + + 4. MODIFICATIONS + + You may copy and distribute a Modified Version of the Document under the conditions of + sections 2 and 3 above, provided that you release + the Modified Version under precisely this License, with the + Modified Version filling the role of the Document, thus + licensing distribution and modification of the Modified Version + to whoever possesses a copy of it. In addition, you must do + these things in the Modified Version: + + + + + + + + Use in the Title + Page (and on the covers, if any) a title distinct + from that of the Document, and from those of + previous versions (which should, if there were any, be + listed in the History section of the Document). You may + use the same title as a previous version if the original + publisher of that version gives permission. + + + + + + + + + List on the Title + Page, as authors, one or more persons or entities + responsible for authorship of the modifications in the + Modified Version, + together with at least five of the principal authors of + the Document (all of + its principal authors, if it has less than five). + + + + + + + + State on the Title + Page the name of the publisher of the Modified Version, as the + publisher. + + + + + + + + Preserve all the copyright notices of the Document. + + + + + + + + Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + + + + + + + + Include, immediately after the copyright notices, a + license notice giving the public permission to use the + Modified Version under + the terms of this License, in the form shown in the + Addendum below. + + + + + + + + Preserve in that license notice the full lists of Invariant Sections and + required Cover + Texts given in the Document's license notice. + + + + + + + + Include an unaltered copy of this License. + + + + + + + + Preserve the section entitled History, and + its title, and add to it an item stating at least the + title, year, new authors, and publisher of the Modified Version as given on + the Title Page. If + there is no section entitled History in the + Document, create one + stating the title, year, authors, and publisher of the + Document as given on its Title Page, then add an item + describing the Modified Version as stated in the previous + sentence. + + + + + + + + Preserve the network location, if any, given in the Document for public access + to a Transparent + copy of the Document, and likewise the network locations + given in the Document for previous versions it was based + on. These may be placed in the History + section. You may omit a network location for a work that + was published at least four years before the Document + itself, or if the original publisher of the version it + refers to gives permission. + + + + + + + + In any section entitled Acknowledgements or + Dedications, preserve the section's title, + and preserve in the section all the substance and tone of + each of the contributor acknowledgements and/or + dedications given therein. + + + + + + + + Preserve all the Invariant + Sections of the Document, unaltered in their + text and in their titles. Section numbers or the + equivalent are not considered part of the section titles. + + + + + + + + Delete any section entitled + Endorsements. Such a section may not be + included in the Modified + Version. + + + + + + + + Do not retitle any existing section as + Endorsements or to conflict in title with + any Invariant + Section. + + + + + + + If the Modified Version + includes new front-matter sections or appendices that qualify as + Secondary Sections and + contain no material copied from the Document, you may at your + option designate some or all of these sections as invariant. To + do this, add their titles to the list of Invariant Sections in the + Modified Version's license notice. These titles must be + distinct from any other section titles. + + + + You may add a section entitled Endorsements, + provided it contains nothing but endorsements of your Modified Version by various + parties--for example, statements of peer review or that the text + has been approved by an organization as the authoritative + definition of a standard. + + + + You may add a passage of up to five words as a Front-Cover Text, and a passage + of up to 25 words as a Back-Cover Text, to the end of + the list of Cover Texts + in the Modified Version. + Only one passage of Front-Cover Text and one of Back-Cover Text + may be added by (or through arrangements made by) any one + entity. If the Document + already includes a cover text for the same cover, previously + added by you or by arrangement made by the same entity you are + acting on behalf of, you may not add another; but you may + replace the old one, on explicit permission from the previous + publisher that added the old one. + + + + The author(s) and publisher(s) of the Document do not by this License + give permission to use their names for publicity for or to + assert or imply endorsement of any Modified Version . + + + + + 5. COMBINING DOCUMENTS + + You may combine the Document + with other documents released under this License, under the + terms defined in section 4 + above for modified versions, provided that you include in the + combination all of the Invariant + Sections of all of the original documents, unmodified, + and list them all as Invariant Sections of your combined work in + its license notice. + + + + The combined work need only contain one copy of this License, + and multiple identical Invariant + Sections may be replaced with a single copy. If there are + multiple Invariant Sections with the same name but different + contents, make the title of each such section unique by adding + at the end of it, in parentheses, the name of the original + author or publisher of that section if known, or else a unique + number. Make the same adjustment to the section titles in the + list of Invariant Sections in the license notice of the combined + work. + + + + In the combination, you must combine any sections entitled + History in the various original documents, + forming one section entitled History; likewise + combine any sections entitled Acknowledgements, + and any sections entitled Dedications. You must + delete all sections entitled Endorsements. + + + + + 6. COLLECTIONS OF DOCUMENTS + + You may make a collection consisting of the Document and other documents + released under this License, and replace the individual copies + of this License in the various documents with a single copy that + is included in the collection, provided that you follow the + rules of this License for verbatim copying of each of the + documents in all other respects. + + + + You may extract a single document from such a collection, and + dispbibute it individually under this License, provided you + insert a copy of this License into the extracted document, and + follow this License in all other respects regarding verbatim + copying of that document. + + + + + 7. AGGREGATION WITH INDEPENDENT WORKS + + A compilation of the Document or its derivatives with + other separate and independent documents or works, in or on a + volume of a storage or distribution medium, does not as a whole + count as a Modified Version + of the Document, provided no compilation copyright is claimed + for the compilation. Such a compilation is called an + aggregate, and this License does not apply to the + other self-contained works thus compiled with the Document , on + account of their being thus compiled, if they are not themselves + derivative works of the Document. If the Cover Text requirement of section 3 is applicable to these + copies of the Document, then if the Document is less than one + quarter of the entire aggregate, the Document's Cover Texts may + be placed on covers that surround only the Document within the + aggregate. Otherwise they must appear on covers around the whole + aggregate. + + + + + 8. TRANSLATION + + Translation is considered a kind of modification, so you may + distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with + translations requires special permission from their copyright + holders, but you may include translations of some or all + Invariant Sections in addition to the original versions of these + Invariant Sections. You may include a translation of this + License provided that you also include the original English + version of this License. In case of a disagreement between the + translation and the original English version of this License, + the original English version will prevail. + + + + + 9. TERMINATION + + You may not copy, modify, sublicense, or distribute the Document except as expressly + provided for under this License. Any other attempt to copy, + modify, sublicense or distribute the Document is void, and will + automatically terminate your rights under this License. However, + parties who have received copies, or rights, from you under this + License will not have their licenses terminated so long as such + parties remain in full compliance. + + + + + 10. FUTURE REVISIONS OF THIS LICENSE + + The Free Software + Foundation may publish new, revised versions of the GNU + Free Documentation License from time to time. Such new versions + will be similar in spirit to the present version, but may differ + in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. + + + + Each version of the License is given a distinguishing version + number. If the Document + specifies that a particular numbered version of this License + or any later version applies to it, you have the + option of following the terms and conditions either of that + specified version or of any later version that has been + published (not as a draft) by the Free Software Foundation. If + the Document does not specify a version number of this License, + you may choose any version ever published (not as a draft) by + the Free Software Foundation. + + + + + Addendum + + To use this License in a document you have written, include a copy of + the License in the document and put the following copyright and + license notices just after the title page: + + +
+ + Copyright YEAR YOUR NAME. + + + Permission is granted to copy, distribute and/or modify this + document under the terms of the GNU Free Documentation + License, Version 1.1 or any later version published by the + Free Software Foundation; with the Invariant Sections being LIST + THEIR TITLES, with the Front-Cover Texts being LIST, + and with the Back-Cover + Texts being LIST. A copy of the license is included in + the section entitled GNU Free Documentation + License. + +
+ + + If you have no Invariant + Sections, write with no Invariant Sections + instead of saying which ones are invariant. If you have no + Front-Cover Texts, write + no Front-Cover Texts instead of + Front-Cover Texts being LIST; likewise for Back-Cover Texts. + + + + If your document contains nontrivial examples of program code, + we recommend releasing these examples in parallel under your + choice of free software license, such as the GNU General Public + License, to permit their use in free software. + + + + + diff --git a/help/C/figures/authentication-add.png b/help/C/figures/authentication-add.png new file mode 100644 index 00000000..004b3fa1 Binary files /dev/null and b/help/C/figures/authentication-add.png differ diff --git a/help/C/figures/authentication.png b/help/C/figures/authentication.png new file mode 100644 index 00000000..07227a2e Binary files /dev/null and b/help/C/figures/authentication.png differ diff --git a/help/C/figures/download-progressbar.png b/help/C/figures/download-progressbar.png new file mode 100644 index 00000000..9f096460 Binary files /dev/null and b/help/C/figures/download-progressbar.png differ diff --git a/help/C/figures/failed-repos.png b/help/C/figures/failed-repos.png new file mode 100644 index 00000000..01b0d0e9 Binary files /dev/null and b/help/C/figures/failed-repos.png differ diff --git a/help/C/figures/install-progress-terminal.png b/help/C/figures/install-progress-terminal.png new file mode 100644 index 00000000..06111c61 Binary files /dev/null and b/help/C/figures/install-progress-terminal.png differ diff --git a/help/C/figures/install-progress.png b/help/C/figures/install-progress.png new file mode 100644 index 00000000..699f6219 Binary files /dev/null and b/help/C/figures/install-progress.png differ diff --git a/help/C/figures/main-system-updates-available.png b/help/C/figures/main-system-updates-available.png new file mode 100644 index 00000000..24dc5481 Binary files /dev/null and b/help/C/figures/main-system-updates-available.png differ diff --git a/help/C/figures/main-system-updates-summary-details.png b/help/C/figures/main-system-updates-summary-details.png new file mode 100644 index 00000000..08860ec1 Binary files /dev/null and b/help/C/figures/main-system-updates-summary-details.png differ diff --git a/help/C/figures/main-system-updates-summary.png b/help/C/figures/main-system-updates-summary.png new file mode 100644 index 00000000..fefea5dd Binary files /dev/null and b/help/C/figures/main-system-updates-summary.png differ diff --git a/help/C/figures/main-system-uptodate.png b/help/C/figures/main-system-uptodate.png new file mode 100644 index 00000000..d8c10d5f Binary files /dev/null and b/help/C/figures/main-system-uptodate.png differ diff --git a/help/C/figures/main-view-monitor-update.png b/help/C/figures/main-view-monitor-update.png new file mode 100644 index 00000000..b8b2a80b Binary files /dev/null and b/help/C/figures/main-view-monitor-update.png differ diff --git a/help/C/figures/main-view-update-detail.png b/help/C/figures/main-view-update-detail.png new file mode 100644 index 00000000..d3f8f12c Binary files /dev/null and b/help/C/figures/main-view-update-detail.png differ diff --git a/help/C/figures/preferences-add-custom.png b/help/C/figures/preferences-add-custom.png new file mode 100644 index 00000000..97e709f6 Binary files /dev/null and b/help/C/figures/preferences-add-custom.png differ diff --git a/help/C/figures/preferences-add.png b/help/C/figures/preferences-add.png new file mode 100644 index 00000000..e77f7523 Binary files /dev/null and b/help/C/figures/preferences-add.png differ diff --git a/help/C/figures/preferences-edit.png b/help/C/figures/preferences-edit.png new file mode 100644 index 00000000..5d713264 Binary files /dev/null and b/help/C/figures/preferences-edit.png differ diff --git a/help/C/figures/preferences-repos-changeinfo.png b/help/C/figures/preferences-repos-changeinfo.png new file mode 100644 index 00000000..e1fbbd9e Binary files /dev/null and b/help/C/figures/preferences-repos-changeinfo.png differ diff --git a/help/C/figures/preferences.png b/help/C/figures/preferences.png new file mode 100644 index 00000000..e59f2c29 Binary files /dev/null and b/help/C/figures/preferences.png differ diff --git a/help/C/figures/reload-package-info.png b/help/C/figures/reload-package-info.png new file mode 100644 index 00000000..76156b2e Binary files /dev/null and b/help/C/figures/reload-package-info.png differ diff --git a/help/C/figures/settings.png b/help/C/figures/settings.png new file mode 100644 index 00000000..2084c2ef Binary files /dev/null and b/help/C/figures/settings.png differ diff --git a/help/C/figures/synaptic-toggle-install-view.png b/help/C/figures/synaptic-toggle-install-view.png new file mode 100644 index 00000000..be04d24e Binary files /dev/null and b/help/C/figures/synaptic-toggle-install-view.png differ diff --git a/help/C/legal.xml b/help/C/legal.xml new file mode 100644 index 00000000..ac97e1de --- /dev/null +++ b/help/C/legal.xml @@ -0,0 +1,76 @@ + + + Permission is granted to copy, distribute and/or modify this + document under the terms of the GNU Free Documentation + License (GFDL), Version 1.1 or any later version published + by the Free Software Foundation with no Invariant Sections, + no Front-Cover Texts, and no Back-Cover Texts. You can find + a copy of the GFDL at this link or in the file COPYING-DOCS + distributed with this manual. + + This manual is part of a collection of GNOME manuals + distributed under the GFDL. If you want to distribute this + manual separately from the collection, you can do so by + adding a copy of the license to the manual, as described in + section 6 of the license. + + + + Many of the names used by companies to distinguish their + products and services are claimed as trademarks. Where those + names appear in any GNOME documentation, and the members of + the GNOME Documentation Project are made aware of those + trademarks, then the names are in capital letters or initial + capital letters. + + + + DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED + UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE + WITH THE FURTHER UNDERSTANDING THAT: + + + + DOCUMENT IS PROVIDED ON AN "AS IS" BASIS, + WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR + IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES + THAT THE DOCUMENT OR MODIFIED VERSION OF THE + DOCUMENT IS FREE OF DEFECTS MERCHANTABLE, FIT FOR + A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE + RISK AS TO THE QUALITY, ACCURACY, AND PERFORMANCE + OF THE DOCUMENT OR MODIFIED VERSION OF THE + DOCUMENT IS WITH YOU. SHOULD ANY DOCUMENT OR + MODIFIED VERSION PROVE DEFECTIVE IN ANY RESPECT, + YOU (NOT THE INITIAL WRITER, AUTHOR OR ANY + CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY + SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER + OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS + LICENSE. NO USE OF ANY DOCUMENT OR MODIFIED + VERSION OF THE DOCUMENT IS AUTHORIZED HEREUNDER + EXCEPT UNDER THIS DISCLAIMER; AND + + + + UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL + THEORY, WHETHER IN TORT (INCLUDING NEGLIGENCE), + CONTRACT, OR OTHERWISE, SHALL THE AUTHOR, + INITIAL WRITER, ANY CONTRIBUTOR, OR ANY + DISTRIBUTOR OF THE DOCUMENT OR MODIFIED VERSION + OF THE DOCUMENT, OR ANY SUPPLIER OF ANY OF SUCH + PARTIES, BE LIABLE TO ANY PERSON FOR ANY + DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR + CONSEQUENTIAL DAMAGES OF ANY CHARACTER + INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS + OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR + MALFUNCTION, OR ANY AND ALL OTHER DAMAGES OR + LOSSES ARISING OUT OF OR RELATING TO USE OF THE + DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT, + EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF + THE POSSIBILITY OF SUCH DAMAGES. + + + + + + diff --git a/help/C/update-manager-C.omf b/help/C/update-manager-C.omf new file mode 100644 index 00000000..a4e6aabc --- /dev/null +++ b/help/C/update-manager-C.omf @@ -0,0 +1,18 @@ + + + + sean@inwords.co.za (Sean Wheller) + Update Manager Manual + 2005-03-04 + + + This document explains how to use the Update Manager. + manual + + + + + + + diff --git a/help/C/update-manager-C.omf.out b/help/C/update-manager-C.omf.out new file mode 100644 index 00000000..af5d465e --- /dev/null +++ b/help/C/update-manager-C.omf.out @@ -0,0 +1,17 @@ + + + + sean@inwords.co.za (Sean Wheller) + Update Manager Manual + 2005-03-04 + + + This document explains how to use the Update Manager. + manual + + + + + + + diff --git a/help/C/update-manager.xml b/help/C/update-manager.xml new file mode 100644 index 00000000..5d0875f3 --- /dev/null +++ b/help/C/update-manager.xml @@ -0,0 +1,1070 @@ + + + +]> + + + +
+ + + + Update Manager Manual + + 2005 + In Words + + + + + + + In Words Techdoc Solutions + + &legal; + + + + Sean + Wheller + + In Words +
+ sean@inwords.co.za +
+ + + + Jeff + Schering + Editor + + + + + + + + + + + + + + + + + + V0.0.1 + 06/03/2005 + + First version of the manual created in accordance + with Update Manager V0.37.1+svn20050301. Documentation Writer + sean@inwords.co.za + + + InWords Techdoc + Solutions + + + + + V0.0.2 + 26/03/2005 + + Edit of V0.0.1 to make some nodes shorter. + Editor jeffschering@gmail.com + + + InWords Techdoc + Solutions + + + + + V0.0.3 + 26/03/2005 + + Added Help, Add CD, Settings options. + sean@inwords.co.za + + + InWords Techdoc + Solutions + + + + + This manual explains how to use Update Manager an apt update + management application for the GNOME desktop created by the Ubuntu Linux + project. + + Feedback + + To report a bug or make a suggestion regarding this package or this + manual, send mail to ubuntu-users@lists.ubuntu.com. + + + + + + + Introduction + + Update Manager is a graphical interface to the + software update features of Advanced Packaging + Tool (APT). APT is a + command line tool for installing, updating, and removing software. + + Update Manager makes the task of checking for + and installing software updates as effortless as possible. + Update Manager keeps your system up-to-date + by checking Ubuntu's software repositories for new versions of installed + software. The new versions usually contain bug fixes and new features, but + may also contain security updates. Use Update Manager on a regular basis + to ensure that your system is as up-to-date and secure as possible. + + Update Manager decides which software needs to + be updated by comparing the version numbers of individual software files + on your computer with the software in one or more software repositories. + The software repositories are usually on remote network servers, but may + also be on a CD-ROM. Whenever Update Manager + notifies you that an update is available, you may choose to install the + update immediately, or to ignore the update. + + Update Manager has settings and preferences + which allow you to: set how often it checks for updates, add and remove + software repositories, and manage repository authentication keys. + + + Getting Started + + Installation + + Update Manager is installed as part of the + Ubuntu standard installation, and should already be on your system. The + application is known as Ubuntu Update + Manager. If you need to install Update + Manager, you can use Synaptic Package + Manager. Choose + System + Administration + Synaptic Package Manager + to start Synaptic. The package + you need to install is update-manager. + You may also install Update Manager from the command line using + apt-get. To install Update + Manager from the command line: + +sudo apt-get update-manager + + + Update Manager is dependent on the following + packages: 'python,' 'python-gnome2,' + 'python-apt,' 'synaptic,' and + 'lsb-release.' + + + Starting Update Manager + Choose + System + Administration + Ubuntu Update Manager + to start the application. Enter your password when + prompted. + You may also start Update Manager from + the command line: + +sudo update-manager + + + + Main Window + The Update Manager main window is used for + managing the update process and setting preferences. + When you open Update Manager, the main + window displays the list of packages that need to be installed to update + your computer. If your computer is up-to-date, the main window contains + only the message "Your system is up-to-date!" + + + + + + + Available Updates + + + + + + + Performing Updates + + Updating Your Computer + When you open Update Manager, the main + window displays the list of packages that need to be installed to update + your computer. If your computer is up-to-date, the main window contains + only the message "Your system is up-to-date!" + + + + + + + Available Updates + + + + By default, all packages are marked for installation. In most + cases you will install all of the packages right away. However, if there + are a large number of updates you may want to do only a few at a time. + To deselect a package, uncheck the + check box located on the left of each item + description. + To see additional information about a package, click on the + Details option + (see ) + When you are ready to install the selected packages, + click the Install button. + If Update Manager detects + packages that do not contain a verification signature, the + Summary dialog will be displayed. + The Summary dialog lists three groups of update + categories: + + + + NOT AUTHENTICATED + + + If a digital signature is not found for an update package, it is + labeled 'NOT AUTHENTICATED.' + + + + + To be upgraded + + + Packages that will be upgraded. + + + + + Unchanged + + + Packages that will not be upgraded due to dependency issues. + The packages will be upgraded in a future Update + Manager session, once the developers have + resolved the dependencies. + + + + This is the final point to check the upgrade before the installation + starts. If you are not happy with the upgrade, + click + Cancel to return to the list and modify the + upgrade. If you are happy with the upgrade, click + Apply. + + If a deselected package is required as a dependency for a selected + package, Update Manager may install the + deselected package to satisfy the dependency. + + + Update Manager will download all of the + selected packages before installing them. The entire process may take a + long time depending on the amount of data that needs to be downloaded, the + speed of your network connection, and the number of packages that need to + be installed. + Installation of the update packages will + only start once all packages have been downloaded. The + download progress can be monitored (see ). + + + Expanded Update Information + When an item is selected, additional information about an update + package and the enhancements it provides can be obtained by expanding + the Details option, located at the bottom of the + list. + + + + + + + Update Item Details + + + + For each update package the following information is available: + + + + Changes + + + The Changes tab displays the contents + of the packages ChangeLog file. This enables + the user to read about the changes contained in the update + package. + + + + + Description + + + A single update package may contain multiple programs. These + programs are related in some way and are therefore bundled into a + single package. The Description tab + displays a short description for each program contained by the + package. + + + + + + Monitoring Download Progress + When there are many packages in the update list, download can take a + considerable amount of time. In this case it can be useful to be able to + monitor the download progress. + A progress bar is automatically displayed when updates need to be + downloaded. Click the Show progress of + single files option to display an expanded view of + individual file download progress. + + + + + + + Monitoring Download Progress Bar + + + + Downloaded files are cached locally prior to installation. All files + must be downloaded in order for the installation stage to commence. The + cached files are automatically removed following successful installation + when the Automatically clean temporary packages + files option is checked (see ). + + If for any reason the network connection fails or times out, the + installation will not proceed. Update + Manager will automatically resume the download, from the + last successfully downloaded file, on the next attempt. + + + + Monitoring Installation Progress + It is common for software packages to use components belonging to + other pieces of software. This creates a dependency in the software that + uses external components. For this reason, installation of update + packages will only commence once all packages have been successfully + downloaded from the software repository (see ). The Update + Manager will take care to install packages in the required + sequence in order to satisfy any dependencies. + Once all update packages are downloaded installation will + automatically begin. During installation a progress bar, similar to that + of the download progress bar, is displayed. + + + + + + + Monitoring Installation Progress Bar + + + + During installation it is possible to view a verbose transcript of + installation operations by clicking the + Terminal option. This expands the dialog to + show terminal view. It is also possible to configure installation + progress to use Terminal Mode only, see . + + + + + + + Monitoring Installation Progress Bar and Terminal View + + + + + Do not terminate the installation process. This may lead to + corruption of installed programs and general system + instability. + + + + + Setting Preferences + The Update Manager + Preferences button displays the Software + Preferences dialog. From this dialog users can perform the + following tasks: + + + Manage software sources (see ). + + + Manage authentication keys (see ). + + + Manage settings (see ). + + + + Managing Software Sources + During installation of a distro, software repositories are + automatically added to the list of 'software sources.' + Typical sources added by the distro installation include the + installation source, update, and security repositories. Sources can be + added to and removed from the list and existing sources can be edited. + + The operations described here modify /etc/apt/sources.list using the Update + Manager graphical user interface. Software sources can + also be managed by making direct modifications in /etc/apt/sources.list. This is only + advised for advanced users. + + + Adding Software Sources + Software may be installed using various access methods: + + + + CD-ROM - Compact Disk Read Only Memory, + normally directly connected to the computer system and mounted + locally by the operating system. + + + + + + + FTP - File Transfer Protocol, a secure and + reliable protocol designed specifically for the purpose of + transferring large files across the Internet. + + + + HTTP - HyperText Transfer Protocol, commonly + used to request and receive Web pages, but can also be used for + file transfer. + + + + SMB - Server Management Block is used to + access shared resources on computers running Microsoft + Windows or Samba + Server. + + + + NFS - Network File System is used to access + shared resources on Linux/UNIX computers. + + + + Before software sources residing on SMB or NFS shares can be + defined, the share must be mounted by the local system. Access can + then be made via the local filesystem. For more information see + . + + A new software source can be defined by clicking + the Add button located on the + Software Preferences dialog. This will + display the Edit Repository dialog. + + + + + + + Adding Software Sources + + + + Complete the Edit Repository dialog to add + a new Software source. + + + + Repository + + + A drop-list containing known software sources. + + + + + Components + + + The Ubuntu software repository contains thousands of + software packages organized into four + 'components,' on the basis of the level of + support we can offer them, and whether or not they comply with + Free Software Philosophy. The components are called + 'main,' 'restricted,' + 'universe,' and + 'multiverse.' + Check the components you wish to include in the update list. + + + + Officially supported (main) + - The main distribution component contains applications that + are free software, can freely be redistributed and are fully + supported by the Ubuntu team. This includes the most popular + and most reliable open source applications available, much + of which is installed by default when you install Ubuntu. + Software in main includes a hand-selected list of + applications that the Ubuntu developers, community, and + users feel are important and that the Ubuntu security and + distribution team are willing to support. When you install + software from the main component you are assured that the + software will come with security updates and technical + support. We believe that the software in main includes + everything most people will need for a fully functional + desktop or Internet server running only open source + software. The licenses for software applications in main + must be free, but main may also may contain binary firmware + and selected fonts that cannot be modified without + permission from their authors. In all cases redistribution + is unencumbered. + + + + Restricted Copyright - The + restricted component is reserved for software that is very + commonly used, and which is supported by the Ubuntu team + even though it is not available under a completely free + license. Please note that it may not be possible to provide + complete support for this software since we are unable to + fix the software ourselves, but can only forward problem + reports to the actual authors. Some software from restricted + will be installed on Ubuntu CDs but is clearly separated to + ensure that it is easy to remove. We include this software + because it is essential in order for Ubuntu to run on + certain machines - typical examples are the binary drivers + that some video card vendors publish, which are the only way + for Ubuntu to run on those machines. By default, we will + only use open source software unless there is simply no + other way to install Ubuntu. The Ubuntu team works with such + vendors to accelerate the open-sourcing of their software to + ensure that as much software as possible is available under + a Free license. + + + + Community maintained + (Universe) - The universe component is a snapshot + of the free, open source, and Linux world. In universe you + can find almost every piece of open source software, and + software available under a variety of less open licenses, + all built automatically from a variety of public sources. + All of this software is compiled against the libraries and + using the tools that form part of main, so it should install + and work well with the software in main, but it comes with + no guarantee of security fixes and support. The universe + component includes thousands of pieces of software. Through + universe, users are able to have the diversity and + flexibility offered by the vast open source world on top of + a stable Ubuntu core. + + + + Non Free (Multiverse) - The + 'multiverse' component contains software + that is not free, which means the + licensing requirements of this software do not meet the + Ubuntu 'main' Component license Policy. + The onus is on you to verify your rights to use this + software and comply with the licensing terms of the + copyright holder. This software is not supported and usually + cannot be fixed or updated. Use it at your own risk. + + + + + + + + Creating Custom Software Sources + It is also possible to define custom software sources. + To define a custom software source click the + Custom button located on the Edit + Repository dialog. This will display a dialog in which + the custom repository can be defined using + apt command syntax. + Apt is an Advanced Packaging Tool and + front-end to dpkg the Debian Package + Management System. Once the apt line is entered + click the Add repository + button. + + + + + + + Creating Custom Software Sources + + + + The apt command syntax defines the + 'type,' 'location,' and + 'content' of the repository. Example of the command + syntax could look like this. + +deb ftp://archive.ubuntu.com/ubuntu/ hoary main restricted universe multiverse + + This example would define the software sources as a Debian source + at ubuntu.com containing the hoary release and using all components. + For definition of the components, see . + + + Removing Software Sources + Software sources can be removed from the sources list by selecting + the software source then clicking the + Remove button located on the + Software Preferences dialog. + Removal of a software source requires that the + apt file (/etc/apt/sources.list) that contains the a list of + software sources is updated. Before modifying this file + Update Manager prompts to confirm the + operation. If the operation is confirmed a backup copy is create in + /etc/apt/sources.list.save. + + + Editing Software Sources + To change the values defining a software source, select the source + record then click the edit button. This will display + the Edit Repository dialog. + + + + + + + Editing Software Sources + + + + + + + Type + + + Software sources may contain software in + 'Binary' or 'Source Code' + format. Select the option correlating to the repository + format. + + + + + URI + + + Enter a valid Uniform Resource Indicator + (URI). Following is a list of examples for + each of the possible access methods: + + + + + CD-ROM - + cdrom:[description_of_cd]/ + + + + + + + + FTP - + ftp://ftp.domain.ext/path/to/repository + + + + + HTTP - + http://www.domain.ext/path/to/repository + + + + + SMB - Works only when the computer is + already connected to an SMB share. To connect to SMB share + use the following command syntax from the shell + smbclient //hostname/sharename -U + username. + The SMB share is accessed from the local file system + once the local system is connected. + file://path/to/sharefile + + + + + NFS - Works only when the computer is + already connected to a NFS share. To connect the NFS share + must be mounted. NFS shares are mounted on the client side + using the mount command. The format of the command is as + follows: mount -o [options] [host]:[/remote/export] + [/local/directory] + + Once mounted Update Manager + can access the share using the following command + file://path/to/local/directory + + + + + If accessing a SMB or NFS shares by manually issuing the + mount commands, the file system must be + remounted manually after the system is rebooted. Failing to + remount will result in Update + Manager not being able to access the + resource. + + + + + + Distribution + + + The name of the distribution or name of the distribution + version. + + + + + Sections + + + The section of the distribution repository to access. + + + + + Comment + + + Add a comment to describe the repository. + + + + + Repositories defined using Synaptic, + another package management tool, are automatically displayed in the + Update Manager Software Sources + list. + + + + + Managing Authentication Keys + Authentication keys make it possible to verify the integrity of + update software. From the Authentication Keys + dialog it is possible to view and manage the list authentication keys. + Each key corresponds to a Software Source defined in the + Software Preference dialog (see ). Keys can be added and removed. In the + event of an error it is also possible to restore the default + authentication keys provided by the defined update repositories. + + + + + + + + Managing Authentication Keys + + + + + Adding Authentication Keys + Authentication keys are usually obtained from the software vendor + running the repository. Often the vendor will place a copy of the + authentication key on a key server, for example www.keyserver.net. The key + can then be retrieved using the command gpg + -recv-key. When the key resides on a key server the option + must be used to give the name of this + key server. + +gpg -recv-key --keyserver www.keyserver.net + + + If the key is fetched over a untrusted medium, like the + Internet, additional steps should be taken to verify the key. For + example, getting the fingerprint with a secure method such as by + phone, letter, or business card. Alternately you can check if the + key is signed with a known-good key. + + Once the key is downloaded, select it using the Choose + a key-file dialog that is displayed when the + Add button. + + + + + + + Adding Authentication Keys + + + + + + Removing Authentication Keys + Authentication keys can be removed by selecting a record item then + clicking the Remove + button. + + + Restoring Default Keys + During installation the default Ubuntu Authentication keys are + added to the Ubuntu GPG Keyring package. In + the even of a key being accidentally deleted it can be restored by + clicking the Restore default keys + button. + + + + Managing Settings + The Settings button, located on the + Software Preferences dialog, displays the + Settings dialog. From this interface users can + manage the behavior of the application and pre-update process. + + + + + + + Managing Settings + + + + The following options are available: + + User Interface + + + Show disabled software sources: - When checked + software sources that are not checked in the Software + Preferences dialog are displayed. When unchecked, + these items are not displayed in the list. + + + + Internet Updates + + + + + + Automatically check for software updates: + - When checked the Update interval in + days option is enabled. Update + Manager will poll all enabled software sources + for updates according to the value specified in the + scroll-box. + + + + Download upgradable packages: - When + checked Update Manager will + automatically download any available software update packages. + It will not install them until the user has defined the + installation list (see ). + + + + + + + Temporary files + + + Automatically clean temporary packages files: - + When checked the Clean interval in days option + is enabled. Update Manager automatically + removes any temporary files created by the upgrade process according + to the value specified in the scroll-box. + + + Set maximum size of the package cache: When checked the size of + the package cache is limited to the value specified in the Maximum size in + MB spin-box. + + + Delete old packages in the package cache: When checked cached + packaged with a date older than the value specified in the Maximum age in + days spin-box will be automatically purged from the cache. + + + + + Install Progress for Terminal View Only + It is also possible to configure the installation progress to use + only a terminal view. That is to say, no progress bar is displayed, only + a terminal view. + + + + + + + Monitoring Installation Progress + + + + + Do not terminate the installation process. This may lead to + corruption of installed programs and general system + instability. + + Changing between 'Progress Bar' and + 'Terminal View,' modes is managed via + Synaptic. To change modes proceed as + follows: + + + Start Synaptic by selecting + System + Administration + Synaptic Package Manager + from the Desktop menu system. + + + When prompted, enter your password. + + + From the main menu, select + Settings + Preferences + . The Preferences dialog is + displayed. + + + From the General tab, Apply + Changes group, check or + uncheck the Apply changes in terminal + window checkbox. + + + + + + + Synaptic Preferences - General Tab + + + + + + + Click + OK and exit + Synaptic. + + + + + + About Update Manager + The Update Manager was written by Michiel + Sikkes michiel@eyeopened.nl and Michael Vogt + michael.vogt@ubuntu.com as an + apt update manager for the GNOME Desktop of the + Ubuntu Linux distribution. The user manual was written by Sean Wheller + sean@inwords.co.za. + To report a bug or make a suggestion regarding this package or this + manual, send mail to ubuntu-users@lists.ubuntu.com. + &GFDL;
diff --git a/help/Makefile.am b/help/Makefile.am new file mode 100644 index 00000000..42ffacc2 --- /dev/null +++ b/help/Makefile.am @@ -0,0 +1 @@ +SUBDIRS = C -- cgit v1.2.3