diff options
| author | Michael Vogt <egon@top> | 2005-11-15 14:18:07 +0100 |
|---|---|---|
| committer | Michael Vogt <egon@top> | 2005-11-15 14:18:07 +0100 |
| commit | d632109cd5964f7d4baa408d517e44f801e1be8d (patch) | |
| tree | c1acf5f14bcfa183951c260a52e5560610f3a988 /help | |
| download | python-apt-d632109cd5964f7d4baa408d517e44f801e1be8d.tar.gz | |
* initial revision (after accidently killing it)
Diffstat (limited to 'help')
27 files changed, 1844 insertions, 0 deletions
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 @@ +<!-- + The GNU Free Documentation License 1.1 in DocBook + Markup by Eric Baudais <baudais@okstate.edu> + Maintained by the GNOME Documentation Project + http://developer.gnome.org/projects/gdp + Version: 1.0.1 + Last Modified: Nov 16, 2000 +--> + +<appendix id="fdl"> + <appendixinfo> + <releaseinfo> + Version 1.1, March 2000 + </releaseinfo> + <copyright> + <year>2000</year><holder>Free Software Foundation, Inc.</holder> + </copyright> + <legalnotice id="fdl-legalnotice"> + <para> + <address>Free Software Foundation, Inc. <street>59 Temple Place, + Suite 330</street>, <city>Boston</city>, <state>MA</state> + <postcode>02111-1307</postcode> <country>USA</country></address> + Everyone is permitted to copy and distribute verbatim copies of this + license document, but changing it is not allowed. + </para> + </legalnotice> + </appendixinfo> + <title>GNU Free Documentation License</title> + + <sect1 id="fdl-preamble"> + <title>0. PREAMBLE</title> + <para> + The purpose of this License is to make a manual, textbook, or + other written document <quote>free</quote> 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. + </para> + + <para> + This License is a kind of <quote>copyleft</quote>, 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. + </para> + + <para> + 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. + </para> + </sect1> + <sect1 id="fdl-section1"> + <title>1. APPLICABILITY AND DEFINITIONS</title> + <para id="fdl-document"> + 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 + <quote>Document</quote>, below, refers to any such manual or + work. Any member of the public is a licensee, and is addressed + as <quote>you</quote>. + </para> + + <para id="fdl-modified"> + A <quote>Modified Version</quote> 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. + </para> + + <para id="fdl-secondary"> + A <quote>Secondary Section</quote> is a named appendix or a + front-matter section of the <link + linkend="fdl-document">Document</link> 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. + </para> + + <para id="fdl-invariant"> + The <quote>Invariant Sections</quote> are certain <link + linkend="fdl-secondary"> Secondary Sections</link> whose titles + are designated, as being those of Invariant Sections, in the + notice that says that the <link + linkend="fdl-document">Document</link> is released under this + License. + </para> + + <para id="fdl-cover-texts"> + The <quote>Cover Texts</quote> are certain short passages of + text that are listed, as Front-Cover Texts or Back-Cover Texts, + in the notice that says that the <link + linkend="fdl-document">Document</link> is released under this + License. + </para> + + <para id="fdl-transparent"> + A <quote>Transparent</quote> copy of the <link + linkend="fdl-document"> Document</link> 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 <quote>Transparent</quote> is called + <quote>Opaque</quote>. + </para> + + <para> + 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. + </para> + + <para id="fdl-title-page"> + The <quote>Title Page</quote> 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, <quote>Title Page</quote> means the text near the + most prominent appearance of the work's title, preceding the + beginning of the body of the text. + </para> + </sect1> + + <sect1 id="fdl-section2"> + <title>2. VERBATIM COPYING</title> + <para> + You may copy and distribute the <link + linkend="fdl-document">Document</link> 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 <link + linkend="fdl-section3">section 3</link>. + </para> + + <para> + You may also lend copies, under the same conditions stated + above, and you may publicly display copies. + </para> + </sect1> + + <sect1 id="fdl-section3"> + <title>3. COPYING IN QUANTITY</title> + <para> + If you publish printed copies of the <link + linkend="fdl-document">Document</link> numbering more than 100, + and the Document's license notice requires <link + linkend="fdl-cover-texts">Cover Texts</link>, 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 + <link linkend="fdl-document">Document</link> and satisfy these + conditions, can be treated as verbatim copying in other + respects. + </para> + + <para> + 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. + </para> + + <para> + If you publish or distribute <link + linkend="fdl-transparent">Opaque</link> copies of the <link + linkend="fdl-document">Document</link> numbering more than 100, + you must either include a machine-readable <link + linkend="fdl-transparent">Transparent</link> 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. + </para> + + <para> + It is requested, but not required, that you contact the authors + of the <link linkend="fdl-document">Document</link> well before + redistributing any large number of copies, to give them a chance + to provide you with an updated version of the Document. + </para> + </sect1> + + <sect1 id="fdl-section4"> + <title>4. MODIFICATIONS</title> + <para> + You may copy and distribute a <link + linkend="fdl-modified">Modified Version</link> of the <link + linkend="fdl-document">Document</link> under the conditions of + sections <link linkend="fdl-section2">2</link> and <link + linkend="fdl-section3">3</link> 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: + </para> + + <orderedlist numeration="upperalpha"> + <listitem> + + + <para> + Use in the <link linkend="fdl-title-page">Title + Page</link> (and on the covers, if any) a title distinct + from that of the <link + linkend="fdl-document">Document</link>, 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. + </para> + + </listitem> + + <listitem> + + + <para> + List on the <link linkend="fdl-title-page">Title + Page</link>, as authors, one or more persons or entities + responsible for authorship of the modifications in the + <link linkend="fdl-modified">Modified Version</link>, + together with at least five of the principal authors of + the <link linkend="fdl-document">Document</link> (all of + its principal authors, if it has less than five). + </para> + + </listitem> + + <listitem> + + <para> + State on the <link linkend="fdl-title-page">Title + Page</link> the name of the publisher of the <link + linkend="fdl-modified">Modified Version</link>, as the + publisher. + </para> + + </listitem> + + <listitem> + + <para> + Preserve all the copyright notices of the <link + linkend="fdl-document">Document</link>. + </para> + + </listitem> + + <listitem> + + <para> + Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + </para> + + </listitem> + + <listitem> + + <para> + Include, immediately after the copyright notices, a + license notice giving the public permission to use the + <link linkend="fdl-modified">Modified Version</link> under + the terms of this License, in the form shown in the + Addendum below. + </para> + + </listitem> + + <listitem> + + <para> + Preserve in that license notice the full lists of <link + linkend="fdl-invariant"> Invariant Sections</link> and + required <link linkend="fdl-cover-texts">Cover + Texts</link> given in the <link + linkend="fdl-document">Document's</link> license notice. + </para> + + </listitem> + + <listitem> + + <para> + Include an unaltered copy of this License. + </para> + + </listitem> + + <listitem> + + <para> + Preserve the section entitled <quote>History</quote>, and + its title, and add to it an item stating at least the + title, year, new authors, and publisher of the <link + linkend="fdl-modified">Modified Version </link>as given on + the <link linkend="fdl-title-page">Title Page</link>. If + there is no section entitled <quote>History</quote> in the + <link linkend="fdl-document">Document</link>, 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. + </para> + + </listitem> + + <listitem> + + <para> + Preserve the network location, if any, given in the <link + linkend="fdl-document">Document</link> for public access + to a <link linkend="fdl-transparent">Transparent</link> + 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 <quote>History</quote> + 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. + </para> + + </listitem> + + <listitem> + + <para> + In any section entitled <quote>Acknowledgements</quote> or + <quote>Dedications</quote>, 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. + </para> + + </listitem> + + <listitem> + + <para> + Preserve all the <link linkend="fdl-invariant">Invariant + Sections</link> of the <link + linkend="fdl-document">Document</link>, unaltered in their + text and in their titles. Section numbers or the + equivalent are not considered part of the section titles. + </para> + + </listitem> + + <listitem> + + <para> + Delete any section entitled + <quote>Endorsements</quote>. Such a section may not be + included in the <link linkend="fdl-modified">Modified + Version</link>. + </para> + + </listitem> + + <listitem> + + <para> + Do not retitle any existing section as + <quote>Endorsements</quote> or to conflict in title with + any <link linkend="fdl-invariant">Invariant + Section</link>. + </para> + + </listitem> + </orderedlist> + + <para> + If the <link linkend="fdl-modified">Modified Version</link> + includes new front-matter sections or appendices that qualify as + <link linkend="fdl-secondary">Secondary Sections</link> 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 <link + linkend="fdl-invariant">Invariant Sections</link> in the + Modified Version's license notice. These titles must be + distinct from any other section titles. + </para> + + <para> + You may add a section entitled <quote>Endorsements</quote>, + provided it contains nothing but endorsements of your <link + linkend="fdl-modified">Modified Version</link> 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. + </para> + + <para> + You may add a passage of up to five words as a <link + linkend="fdl-cover-texts">Front-Cover Text</link>, and a passage + of up to 25 words as a <link + linkend="fdl-cover-texts">Back-Cover Text</link>, to the end of + the list of <link linkend="fdl-cover-texts">Cover Texts</link> + in the <link linkend="fdl-modified">Modified Version</link>. + 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 <link linkend="fdl-document">Document</link> + 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. + </para> + + <para> + The author(s) and publisher(s) of the <link + linkend="fdl-document">Document</link> do not by this License + give permission to use their names for publicity for or to + assert or imply endorsement of any <link + linkend="fdl-modified">Modified Version </link>. + </para> + </sect1> + + <sect1 id="fdl-section5"> + <title>5. COMBINING DOCUMENTS</title> + <para> + You may combine the <link linkend="fdl-document">Document</link> + with other documents released under this License, under the + terms defined in <link linkend="fdl-section4">section 4</link> + above for modified versions, provided that you include in the + combination all of the <link linkend="fdl-invariant">Invariant + Sections</link> of all of the original documents, unmodified, + and list them all as Invariant Sections of your combined work in + its license notice. + </para> + + <para> + The combined work need only contain one copy of this License, + and multiple identical <link linkend="fdl-invariant">Invariant + Sections</link> 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. + </para> + + <para> + In the combination, you must combine any sections entitled + <quote>History</quote> in the various original documents, + forming one section entitled <quote>History</quote>; likewise + combine any sections entitled <quote>Acknowledgements</quote>, + and any sections entitled <quote>Dedications</quote>. You must + delete all sections entitled <quote>Endorsements.</quote> + </para> + </sect1> + + <sect1 id="fdl-section6"> + <title>6. COLLECTIONS OF DOCUMENTS</title> + <para> + You may make a collection consisting of the <link + linkend="fdl-document">Document</link> 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. + </para> + + <para> + 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. + </para> + </sect1> + + <sect1 id="fdl-section7"> + <title>7. AGGREGATION WITH INDEPENDENT WORKS</title> + <para> + A compilation of the <link + linkend="fdl-document">Document</link> 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 <link linkend="fdl-modified">Modified Version</link> + of the Document, provided no compilation copyright is claimed + for the compilation. Such a compilation is called an + <quote>aggregate</quote>, 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 <link + linkend="fdl-cover-texts">Cover Text</link> requirement of <link + linkend="fdl-section3">section 3</link> 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. + </para> + </sect1> + + <sect1 id="fdl-section8"> + <title>8. TRANSLATION</title> + <para> + Translation is considered a kind of modification, so you may + distribute translations of the <link + linkend="fdl-document">Document</link> under the terms of <link + linkend="fdl-section4">section 4</link>. Replacing <link + linkend="fdl-invariant"> Invariant Sections</link> 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. + </para> + </sect1> + + <sect1 id="fdl-section9"> + <title>9. TERMINATION</title> + <para> + You may not copy, modify, sublicense, or distribute the <link + linkend="fdl-document">Document</link> 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. + </para> + </sect1> + + <sect1 id="fdl-section10"> + <title>10. FUTURE REVISIONS OF THIS LICENSE</title> + <para> + The <ulink type="http" + url="http://www.gnu.org/fsf/fsf.html">Free Software + Foundation</ulink> 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 <ulink + type="http" + url="http://www.gnu.org/copyleft">http://www.gnu.org/copyleft/</ulink>. + </para> + + <para> + Each version of the License is given a distinguishing version + number. If the <link linkend="fdl-document">Document</link> + specifies that a particular numbered version of this License + <quote>or any later version</quote> 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. + </para> + </sect1> + + <sect1 id="fdl-using"> + <title>Addendum</title> + <para> + 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: + </para> + + <blockquote> + <para> + Copyright YEAR YOUR NAME. + </para> + <para> + 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 <link + linkend="fdl-invariant">Invariant Sections</link> being LIST + THEIR TITLES, with the <link + linkend="fdl-cover-texts">Front-Cover Texts</link> being LIST, + and with the <link linkend="fdl-cover-texts">Back-Cover + Texts</link> being LIST. A copy of the license is included in + the section entitled <quote>GNU Free Documentation + License</quote>. + </para> + </blockquote> + + <para> + If you have no <link linkend="fdl-invariant">Invariant + Sections</link>, write <quote>with no Invariant Sections</quote> + instead of saying which ones are invariant. If you have no + <link linkend="fdl-cover-texts">Front-Cover Texts</link>, write + <quote>no Front-Cover Texts</quote> instead of + <quote>Front-Cover Texts being LIST</quote>; likewise for <link + linkend="fdl-cover-texts">Back-Cover Texts</link>. + </para> + + <para> + 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 <ulink type="http" + url="http://www.gnu.org/copyleft/gpl.html"> GNU General Public + License</ulink>, to permit their use in free software. + </para> + </sect1> +</appendix> + + diff --git a/help/C/figures/authentication-add.png b/help/C/figures/authentication-add.png Binary files differnew file mode 100644 index 00000000..004b3fa1 --- /dev/null +++ b/help/C/figures/authentication-add.png diff --git a/help/C/figures/authentication.png b/help/C/figures/authentication.png Binary files differnew file mode 100644 index 00000000..07227a2e --- /dev/null +++ b/help/C/figures/authentication.png diff --git a/help/C/figures/download-progressbar.png b/help/C/figures/download-progressbar.png Binary files differnew file mode 100644 index 00000000..9f096460 --- /dev/null +++ b/help/C/figures/download-progressbar.png diff --git a/help/C/figures/failed-repos.png b/help/C/figures/failed-repos.png Binary files differnew file mode 100644 index 00000000..01b0d0e9 --- /dev/null +++ b/help/C/figures/failed-repos.png diff --git a/help/C/figures/install-progress-terminal.png b/help/C/figures/install-progress-terminal.png Binary files differnew file mode 100644 index 00000000..06111c61 --- /dev/null +++ b/help/C/figures/install-progress-terminal.png diff --git a/help/C/figures/install-progress.png b/help/C/figures/install-progress.png Binary files differnew file mode 100644 index 00000000..699f6219 --- /dev/null +++ b/help/C/figures/install-progress.png diff --git a/help/C/figures/main-system-updates-available.png b/help/C/figures/main-system-updates-available.png Binary files differnew file mode 100644 index 00000000..24dc5481 --- /dev/null +++ b/help/C/figures/main-system-updates-available.png diff --git a/help/C/figures/main-system-updates-summary-details.png b/help/C/figures/main-system-updates-summary-details.png Binary files differnew file mode 100644 index 00000000..08860ec1 --- /dev/null +++ b/help/C/figures/main-system-updates-summary-details.png diff --git a/help/C/figures/main-system-updates-summary.png b/help/C/figures/main-system-updates-summary.png Binary files differnew file mode 100644 index 00000000..fefea5dd --- /dev/null +++ b/help/C/figures/main-system-updates-summary.png diff --git a/help/C/figures/main-system-uptodate.png b/help/C/figures/main-system-uptodate.png Binary files differnew file mode 100644 index 00000000..d8c10d5f --- /dev/null +++ b/help/C/figures/main-system-uptodate.png diff --git a/help/C/figures/main-view-monitor-update.png b/help/C/figures/main-view-monitor-update.png Binary files differnew file mode 100644 index 00000000..b8b2a80b --- /dev/null +++ b/help/C/figures/main-view-monitor-update.png diff --git a/help/C/figures/main-view-update-detail.png b/help/C/figures/main-view-update-detail.png Binary files differnew file mode 100644 index 00000000..d3f8f12c --- /dev/null +++ b/help/C/figures/main-view-update-detail.png diff --git a/help/C/figures/preferences-add-custom.png b/help/C/figures/preferences-add-custom.png Binary files differnew file mode 100644 index 00000000..97e709f6 --- /dev/null +++ b/help/C/figures/preferences-add-custom.png diff --git a/help/C/figures/preferences-add.png b/help/C/figures/preferences-add.png Binary files differnew file mode 100644 index 00000000..e77f7523 --- /dev/null +++ b/help/C/figures/preferences-add.png diff --git a/help/C/figures/preferences-edit.png b/help/C/figures/preferences-edit.png Binary files differnew file mode 100644 index 00000000..5d713264 --- /dev/null +++ b/help/C/figures/preferences-edit.png diff --git a/help/C/figures/preferences-repos-changeinfo.png b/help/C/figures/preferences-repos-changeinfo.png Binary files differnew file mode 100644 index 00000000..e1fbbd9e --- /dev/null +++ b/help/C/figures/preferences-repos-changeinfo.png diff --git a/help/C/figures/preferences.png b/help/C/figures/preferences.png Binary files differnew file mode 100644 index 00000000..e59f2c29 --- /dev/null +++ b/help/C/figures/preferences.png diff --git a/help/C/figures/reload-package-info.png b/help/C/figures/reload-package-info.png Binary files differnew file mode 100644 index 00000000..76156b2e --- /dev/null +++ b/help/C/figures/reload-package-info.png diff --git a/help/C/figures/settings.png b/help/C/figures/settings.png Binary files differnew file mode 100644 index 00000000..2084c2ef --- /dev/null +++ b/help/C/figures/settings.png diff --git a/help/C/figures/synaptic-toggle-install-view.png b/help/C/figures/synaptic-toggle-install-view.png Binary files differnew file mode 100644 index 00000000..be04d24e --- /dev/null +++ b/help/C/figures/synaptic-toggle-install-view.png 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 @@ + <legalnotice id="legalnotice"> + <para> + 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 <ulink type="help" + url="ghelp:fdl">link</ulink> or in the file COPYING-DOCS + distributed with this manual. + </para> + <para> 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. + </para> + + <para> + 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. + </para> + + <para> + DOCUMENT AND MODIFIED VERSIONS OF THE DOCUMENT ARE PROVIDED + UNDER THE TERMS OF THE GNU FREE DOCUMENTATION LICENSE + WITH THE FURTHER UNDERSTANDING THAT: + + <orderedlist> + <listitem> + <para>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 + </para> + </listitem> + <listitem> + <para>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. + </para> + </listitem> + </orderedlist> + </para> + </legalnotice> + 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 @@ +<?xml version="1.0" standalone="no"?> +<omf> + <resource> + <creator>sean@inwords.co.za (Sean Wheller) </creator> + <title>Update Manager Manual </title> + <date>2005-03-04 </date> + <version identifier="0.0.1" date="2005-03-04" description="First Release"/> + <subject category="System|Administration"/> + <description> This document explains how to use the Update Manager. </description> + <type>manual </type> + <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/> + <identifier url=""/> + <language code="C"/> + <relation seriesid="e7ae3bcc-8ce0-11d9-8fa9-d1fb3a9076bb"/> + <rights type="GNU FDL" license.version="1.1" license="http://www.gnu.org/licenses/fdl.html" + holder="In Words"/> + </resource> +</omf> 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 @@ +<?xml version="1.0" standalone="no"?> +<omf> + <resource> + <creator>sean@inwords.co.za (Sean Wheller) </creator> + <title>Update Manager Manual </title> + <date>2005-03-04 </date> + <version identifier="0.0.1" date="2005-03-04" description="First Release"/> + <subject category="System|Administration"/> + <description> This document explains how to use the Update Manager. </description> + <type>manual </type> + <format mime="text/xml" dtd="-//OASIS//DTD DocBook XML V4.1.2//EN"/> + <identifier url="file:/tmp/lala/share/gnome/help/update-manager/C/update-manager.xml"/> + <language code="C"/> + <relation seriesid="e7ae3bcc-8ce0-11d9-8fa9-d1fb3a9076bb"/> + <rights type="GNU FDL" license.version="1.1" license="http://www.gnu.org/licenses/fdl.html" holder="In Words"/> + </resource> +</omf> 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 @@ +<?xml version="1.0"?> +<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" + "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [ + <!ENTITY legal SYSTEM "legal.xml"> + <!ENTITY GFDL SYSTEM "fdl-appendix.xml"> +]> +<?yelp:chunk-depth 4?> +<!-- + (Do not remove this comment block.) + Version: 0.0.3 + Last modified: March 26, 2005 + Maintainers: + Sean Wheller <sean@inwords.co.za> + Jeff Schering <jeffschering@gmail.com> + + Translators: + (translators put your name and email here) +--> +<!-- =============Document Header ============================= --> +<article id="index" lang="en"> + <!-- please do not change the id; for translations, change lang to --> + <!-- appropriate code --> + <articleinfo> + <title>Update Manager Manual</title> + <copyright> + <year>2005</year> + <holder>In Words</holder> + </copyright> + <!-- translators: uncomment this: + + <copyright> + <year>2000</year> + <holder>ME-THE-TRANSLATOR (Latin translation)</holder> + </copyright> + + --> + <!-- An address can be added to the publisher information. If a role is + not specified, the publisher/author is the same for all versions of the + document. --> + <publisher> + <!--<publishername> GNOME Documentation Project </publishername>--> + <publishername> + <ulink url="http://www.inwords.co.za">In Words Techdoc Solutions</ulink> + </publishername> + </publisher> &legal; + <!-- This file contains link to license for the documentation (GNU FDL), and + other legal stuff such as "NO WARRANTY" statement. Please do not change + any of this. --> + <authorgroup> + <author> + <firstname>Sean</firstname> + <surname>Wheller</surname> + <affiliation> + <orgname>In Words</orgname> + <address> + <email>sean@inwords.co.za</email> + </address> + </affiliation> + </author> + <othercredit role="editor"> + <firstname>Jeff</firstname> + <surname>Schering</surname> + <contrib>Editor</contrib> + </othercredit> + <!-- This is appropriate place for other contributors: translators, + maintainers, etc. Commented out by default. + <othercredit role="translator"> + <firstname>Latin</firstname> + <surname>Translator 1</surname> + <affiliation> + <orgname>Latin Translation Team</orgname> + <address> <email>translator@gnome.org</email> </address> + </affiliation> + <contrib>Latin translation</contrib> + </othercredit> +--> + </authorgroup> + <!-- According to GNU FDL, revision history is mandatory if you are --> + <!-- modifying/reusing someone else's document. If not, you can omit it. --> + <!-- Remember to remove the &manrevision; entity from the revision entries other +--> + <!-- than the current revision. --> + <!-- The revision numbering system for GNOME manuals is as follows: --> + <!-- * the revision number consists of two components --> + <!-- * the first component of the revision number reflects the release version of the GNOME desktop. --> + <!-- * the second component of the revision number is a decimal unit that is incremented with each revision of the manual. --> + <!-- For example, if the GNOME desktop release is V2.x, the first version of the manual that --> + <!-- is written in that desktop timeframe is V2.0, the second version of the manual is V2.1, etc. --> + <!-- When the desktop release version changes to V3.x, the revision number of the manual changes --> + <!-- to V3.0, and so on. --> + <revhistory> + <revision> + <revnumber>V0.0.1</revnumber> + <date>06/03/2005</date> + <revdescription> + <para role="author">First version of the manual created in accordance + with Update Manager V0.37.1+svn20050301. Documentation Writer + <email>sean@inwords.co.za</email> + </para> + <para role="publisher"> + <ulink url="http://www.inwords.co.za">InWords Techdoc + Solutions</ulink> + </para> + </revdescription> + </revision> + <revision> + <revnumber>V0.0.2</revnumber> + <date>26/03/2005</date> + <revdescription> + <para role="author">Edit of V0.0.1 to make some nodes shorter. + Editor <email>jeffschering@gmail.com</email> + </para> + <para role="publisher"> + <ulink url="http://www.inwords.co.za">InWords Techdoc + Solutions</ulink> + </para> + </revdescription> + </revision> + <revision> + <revnumber>V0.0.3</revnumber> + <date>26/03/2005</date> + <revdescription> + <para role="author">Added Help, Add CD, Settings options. + <email>sean@inwords.co.za</email> + </para> + <para role="publisher"> + <ulink url="http://www.inwords.co.za">InWords Techdoc + Solutions</ulink> + </para> + </revdescription> + </revision> + </revhistory> + <releaseinfo>This manual explains how to use Update Manager an apt update + management application for the GNOME desktop created by the Ubuntu Linux + project.</releaseinfo> + <legalnotice> + <title>Feedback</title> + <!--<para>To report a bug or make a suggestion regarding this package or this + manual, follow the directions in the <ulink url="ghelp:gnome-feedback" + type="help">GNOME Feedback Page</ulink>. </para>--> + <para>To report a bug or make a suggestion regarding this package or this + manual, send mail to <email>ubuntu-users@lists.ubuntu.com</email>.</para> + <!-- Translators may also add here feedback address for translations --> + </legalnotice> + </articleinfo> + <!-- ============= Document Body ============================= --> + <!-- ============= Introduction ============================== --> + <sect1 id="intro"> + <title>Introduction</title> + <para> + <application>Update Manager</application> is a graphical interface to the + software update features of <application>Advanced Packaging + Tool</application> (<acronym>APT</acronym>). <acronym>APT</acronym> is a + command line tool for installing, updating, and removing software.</para> + <para> + <application>Update Manager</application> makes the task of checking for + and installing software updates as effortless as possible. + <application>Update Manager</application> 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.</para> + <para> + <application>Update Manager</application> 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 <application>Update Manager</application> + notifies you that an update is available, you may choose to install the + update immediately, or to ignore the update.</para> + <para> + <application>Update Manager</application> 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. </para> + </sect1> + <sect1 id="getting-started"> + <title>Getting Started</title> + <sect2 id="installation"> + <title>Installation</title> + <para> + <application>Update Manager</application> is installed as part of the + Ubuntu standard installation, and should already be on your system. The + application is known as <application>Ubuntu Update + Manager</application>. If you need to install <application>Update + Manager</application>, you can use <application>Synaptic Package + Manager</application>. Choose <menuchoice> + <guimenu>System</guimenu> + <guisubmenu>Administration</guisubmenu> + <guimenuitem>Synaptic Package Manager</guimenuitem> + </menuchoice> to start <application>Synaptic</application>. The package + you need to install is <command>update-manager</command>.</para> + <para>You may also install Update Manager from the command line using + <command>apt-get</command>. To install <application>Update + Manager</application> from the command line:</para> +<programlisting> +sudo apt-get update-manager +</programlisting> + <para> + <application>Update Manager</application> is dependent on the following + packages: 'python,' 'python-gnome2,' + 'python-apt,' 'synaptic,' and + 'lsb-release.'</para> + </sect2> + <sect2 id="starting-update-manager"> + <title>Starting Update Manager</title> + <para>Choose <menuchoice> + <guimenu>System</guimenu> + <guisubmenu>Administration</guisubmenu> + <guimenuitem>Ubuntu Update Manager</guimenuitem> + </menuchoice> to start the application. Enter your password when + prompted.</para> + <para>You may also start <application>Update Manager</application> from + the command line:</para> +<programlisting> +sudo update-manager +</programlisting> + </sect2> + <sect2 id="main-window"> + <title>Main Window</title> + <para>The <application>Update Manager</application> main window is used for + managing the update process and setting preferences.</para> + <para>When you open <application>Update Manager</application>, 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!" </para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/main-system-updates-available.png" + format="PNG"/> + </imageobject> + <caption> + <para>Available Updates</para> + </caption> + </mediaobject> + </screenshot> + </sect2> + </sect1> + <sect1 id="performing-updates"> + <title>Performing Updates</title> + <sect2 id="updating"> + <title>Updating Your Computer</title> + <para>When you open <application>Update Manager</application>, 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!" </para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/main-system-updates-available.png" + format="PNG"/> + </imageobject> + <caption> + <para>Available Updates</para> + </caption> + </mediaobject> + </screenshot> + <para>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.</para> + <para>To deselect a package, <action>uncheck</action> the + <guibutton>check box</guibutton> located on the left of each item + description. </para> + <para>To see additional information about a package, <action>click</action> on the + <guibutton>Details</guibutton> option + (see <xref linkend="expanding-update-info"/>)</para> + <para>When you are ready to install the selected packages, + <action>click</action> the <guibutton>Install</guibutton> button.</para> + <para>If <application>Update Manager</application> detects + packages that do not contain a verification signature, the + <interface>Summary</interface> dialog will be displayed.</para> + <para>The <interface>Summary</interface> dialog lists three groups of update + categories:</para> + <variablelist> + <varlistentry> + <term> + <emphasis role="bold">NOT AUTHENTICATED</emphasis> + </term> + <listitem> + <para>If a digital signature is not found for an update package, it is + labeled 'NOT AUTHENTICATED.'</para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <emphasis role="bold">To be upgraded</emphasis> + </term> + <listitem> + <para>Packages that will be upgraded.</para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <emphasis role="bold">Unchanged</emphasis> + </term> + <listitem> + <para>Packages that will not be upgraded due to dependency issues. + The packages will be upgraded in a future <application>Update + Manager</application> session, once the developers have + resolved the dependencies.</para> + </listitem> + </varlistentry> + </variablelist> + <para>This is the final point to check the upgrade before the installation + starts. If you are not happy with the upgrade, + <action>click</action> + <guibutton>Cancel</guibutton> to return to the list and modify the + upgrade. If you are happy with the upgrade, <action>click</action> + <guibutton>Apply</guibutton>.</para> + <note> + <para>If a deselected package is required as a dependency for a selected + package, <application>Update Manager</application> may install the + deselected package to satisfy the dependency.</para> + </note> + <para> + <application>Update Manager</application> 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. </para> + <para>Installation of the update packages will + only start once all packages have been downloaded. The + download progress can be monitored (see <xref + linkend="monitoring-download"/>).</para> + </sect2> + <sect2 id="expanding-update-info"> + <title>Expanded Update Information</title> + <para>When an item is selected, additional information about an update + package and the enhancements it provides can be obtained by expanding + the <guibutton>Details</guibutton> option, located at the bottom of the + list.</para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/main-view-update-detail.png"/> + </imageobject> + <caption> + <para>Update Item Details</para> + </caption> + </mediaobject> + </screenshot> + <para>For each update package the following information is available:</para> + <variablelist> + <varlistentry> + <term> + <emphasis role="bold">Changes</emphasis> + </term> + <listitem> + <para>The <guibutton>Changes</guibutton> tab displays the contents + of the packages <filename>ChangeLog</filename> file. This enables + the user to read about the changes contained in the update + package.</para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <emphasis role="bold">Description</emphasis> + </term> + <listitem> + <para>A single update package may contain multiple programs. These + programs are related in some way and are therefore bundled into a + single package. The <guibutton>Description</guibutton> tab + displays a short description for each program contained by the + package.</para> + </listitem> + </varlistentry> + </variablelist> + </sect2> + <sect2 id="monitoring-download"> + <title>Monitoring Download Progress</title> + <para>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.</para> + <para>A progress bar is automatically displayed when updates need to be + downloaded. <action>Click</action> the <guibutton>Show progress of + single files</guibutton> option to display an expanded view of + individual file download progress.</para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/download-progressbar.png" format="PNG"/> + </imageobject> + <caption> + <para>Monitoring Download Progress Bar</para> + </caption> + </mediaobject> + </screenshot> + <para>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 <guibutton>Automatically clean temporary packages + files</guibutton> option is checked (see <xref + linkend="managing-settings"/>).</para> + <note> + <para>If for any reason the network connection fails or times out, the + installation will not proceed. <application>Update + Manager</application> will automatically resume the download, from the + last successfully downloaded file, on the next attempt.</para> + </note> + </sect2> + <sect2 id="monitoring-installation"> + <title>Monitoring Installation Progress</title> + <para>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 <xref + linkend="monitoring-download"/>). The <application>Update + Manager</application> will take care to install packages in the required + sequence in order to satisfy any dependencies.</para> + <para>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.</para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/install-progress.png" format="PNG"/> + </imageobject> + <caption> + <para>Monitoring Installation Progress Bar</para> + </caption> + </mediaobject> + </screenshot> + <para>During installation it is possible to view a verbose transcript of + installation operations by <action>clicking</action> the + <guibutton>Terminal</guibutton> option. This expands the dialog to + show terminal view. It is also possible to configure installation + progress to use Terminal Mode only, see <xref + linkend="configure-terminal-only-view"/>.</para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/install-progress-terminal.png" + format="PNG"/> + </imageobject> + <caption> + <para>Monitoring Installation Progress Bar and Terminal View</para> + </caption> + </mediaobject> + </screenshot> + <caution> + <para>Do not terminate the installation process. This may lead to + corruption of installed programs and general system + instability.</para> + </caution> + </sect2> + </sect1> + <sect1 id="setting-preferences"> + <title>Setting Preferences</title> + <para>The <application>Update Manager</application> + <guibutton>Preferences</guibutton> button displays the <interface>Software + Preferences</interface> dialog. From this dialog users can perform the + following tasks:</para> + <itemizedlist> + <listitem> + <para>Manage software sources (see <xref linkend="managing-sources" + />).</para> + </listitem> + <listitem> + <para>Manage authentication keys (see <xref + linkend="managing-authentication"/>).</para> + </listitem> + <listitem> + <para>Manage settings (see <xref linkend="managing-settings"/>).</para> + </listitem> + </itemizedlist> + <sect2 id="managing-sources"> + <title>Managing Software Sources</title> + <para>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.</para> + <note> + <para>The operations described here modify <filename class="devicefile" + >/etc/apt/sources.list</filename> using the <application>Update + Manager</application> graphical user interface. Software sources can + also be managed by making direct modifications in <filename + class="devicefile">/etc/apt/sources.list</filename>. This is only + advised for advanced users.</para> + </note> + <sect3 id="adding-sources"> + <title>Adding Software Sources</title> + <para>Software may be installed using various access methods:</para> + <itemizedlist> + <listitem> + <para> + <emphasis>CD-ROM</emphasis> - Compact Disk Read Only Memory, + normally directly connected to the computer system and mounted + locally by the operating system.</para> + </listitem> + <!-- Currently unsupported see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=60910 --> + <!-- mvo: is handled with cdrom URIs --> + <!--<listitem> + <para> + <emphasis>DVD</emphasis> - Digital Video Disk, normally directly + connected to the computer system and mounted locally by the + operating system.</para> + </listitem>--> + <listitem> + <para> + <emphasis>FTP</emphasis> - File Transfer Protocol, a secure and + reliable protocol designed specifically for the purpose of + transferring large files across the Internet.</para> + </listitem> + <listitem> + <para> + <emphasis>HTTP</emphasis> - HyperText Transfer Protocol, commonly + used to request and receive Web pages, but can also be used for + file transfer.</para> + </listitem> + <listitem> + <para> + <emphasis>SMB</emphasis> - Server Management Block is used to + access shared resources on computers running Microsoft + <trademark>Windows</trademark> or <application>Samba + Server</application>.</para> + </listitem> + <listitem> + <para> + <emphasis>NFS</emphasis> - Network File System is used to access + shared resources on Linux/UNIX computers.</para> + </listitem> + </itemizedlist> + <note> + <para>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 + <xref linkend="editing-sources"/>.</para> + </note> + <para>A new software source can be defined by <action>clicking</action> + the <guibutton>Add</guibutton> button located on the + <interface>Software Preferences</interface> dialog. This will + display the <interface>Edit Repository</interface> dialog.</para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/preferences-add.png" format="PNG"/> + </imageobject> + <caption> + <para>Adding Software Sources</para> + </caption> + </mediaobject> + </screenshot> + <para>Complete the <interface>Edit Repository</interface> dialog to add + a new Software source.</para> + <variablelist> + <varlistentry> + <term> + <emphasis role="bold">Repository</emphasis> + </term> + <listitem> + <para>A drop-list containing known software sources.</para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <emphasis role="bold">Components</emphasis> + </term> + <listitem> + <para>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.'</para> + <para>Check the components you wish to include in the update list.</para> + <itemizedlist> + <listitem> + <para> + <emphasis role="bold">Officially supported (main)</emphasis> + - 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.</para> + </listitem> + <listitem> + <para> + <emphasis role="bold">Restricted Copyright</emphasis> - 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.</para> + </listitem> + <listitem> + <para> + <emphasis role="bold">Community maintained + (Universe)</emphasis> - 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.</para> + </listitem> + <listitem> + <para> + <emphasis role="bold">Non Free (Multiverse)</emphasis> - The + 'multiverse' component contains software + that is <emphasis>not free</emphasis>, 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.</para> + </listitem> + </itemizedlist> + </listitem> + </varlistentry> + </variablelist> + </sect3> + <sect3 id="create-custom-sources"> + <title>Creating Custom Software Sources</title> + <para>It is also possible to define custom software sources.</para> + <para>To define a custom software source <action>click</action> the + <guibutton>Custom</guibutton> button located on the <interface>Edit + Repository</interface> dialog. This will display a dialog in which + the custom repository can be defined using + <application>apt</application> command syntax. + <application>Apt</application> is an Advanced Packaging Tool and + front-end to <application>dpkg</application> the Debian Package + Management System. Once the <guilabel>apt line</guilabel> is entered + <action>click</action> the <guibutton>Add repository</guibutton> + button.</para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/preferences-add-custom.png" + format="PNG"/> + </imageobject> + <caption> + <para>Creating Custom Software Sources</para> + </caption> + </mediaobject> + </screenshot> + <para>The <application>apt</application> command syntax defines the + 'type,' 'location,' and + 'content' of the repository. Example of the command + syntax could look like this.</para> + <programlisting> +<command>deb ftp://archive.ubuntu.com/ubuntu/ hoary main restricted universe multiverse</command> + </programlisting> + <para>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 <xref linkend="managing-sources" + />.</para> + </sect3> + <sect3 id="remove-sources"> + <title>Removing Software Sources</title> + <para>Software sources can be removed from the sources list by selecting + the software source then <action>clicking</action> the + <guibutton>Remove</guibutton> button located on the + <interface>Software Preferences</interface> dialog.</para> + <para>Removal of a software source requires that the + <application>apt</application> file (<filename class="devicefile" + >/etc/apt/sources.list</filename>) that contains the a list of + software sources is updated. Before modifying this file + <application>Update Manager</application> prompts to confirm the + operation. If the operation is confirmed a backup copy is create in + <filename class="devicefile" + >/etc/apt/sources.list.save</filename>.</para> + </sect3> + <sect3 id="editing-sources"> + <title>Editing Software Sources</title> + <para>To change the values defining a software source, select the source + record then <action>click</action> the edit button. This will display + the <interface>Edit Repository</interface> dialog.</para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/preferences-edit.png" format="PNG"/> + </imageobject> + <caption> + <para>Editing Software Sources</para> + </caption> + </mediaobject> + </screenshot> + <variablelist> + <varlistentry> + <term> + <emphasis role="bold">Type</emphasis> + </term> + <listitem> + <para>Software sources may contain software in + 'Binary' or 'Source Code' + format. Select the option correlating to the repository + format.</para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <emphasis role="bold">URI</emphasis> + </term> + <listitem> + <para>Enter a valid Uniform Resource Indicator + (<acronym>URI</acronym>). Following is a list of examples for + each of the possible access methods:</para> + <itemizedlist> + <listitem> + <para> + <!-- mvo: we don't want users to add the cd manually + new CDs with ubuntu will be detected + automatically when inserted and it will prompt + for action (start package manager, + upgrade from it) + *mvo* either the sources edit window needs a "add-cdrom" butotn or the user needs to run synaptic + *froud* I would say add a "Add CDROM" + *mvo* yeah + *mvo* I'll file a wishlist bug to myself + *mvo* update-manger should have "add-cdrom" is bug #7315 + --> + <emphasis>CD-ROM</emphasis> - + <command>cdrom:[description_of_cd]/</command> + </para> + </listitem> + <!-- Currently unsupported see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=60910 --> + <!-- mvo: is handled with cdrom URIs --> + <!--<listitem> + <para> + <emphasis>DVD</emphasis> - + <command>dvd:[description_of_dvd]/</command> + </para> + </listitem>--> + <listitem> + <para> + <emphasis>FTP</emphasis> - + <command>ftp://ftp.domain.ext/path/to/repository</command> + </para> + </listitem> + <listitem> + <para> + <emphasis>HTTP</emphasis> - + <command>http://www.domain.ext/path/to/repository</command> + </para> + </listitem> + <listitem> + <para> + <emphasis>SMB</emphasis> - 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 + <command>smbclient //hostname/sharename -U + username</command>. </para> + <para>The SMB share is accessed from the local file system + once the local system is connected. + <command>file://path/to/sharefile</command> + </para> + </listitem> + <listitem> + <para> + <emphasis>NFS</emphasis> - 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: <command>mount -o [options] [host]:[/remote/export] + [/local/directory]</command> + </para> + <para>Once mounted <application>Update Manager</application> + can access the share using the following command + <command>file://path/to/local/directory</command> + </para> + </listitem> + </itemizedlist> + <note> + <para>If accessing a SMB or NFS shares by manually issuing the + <command>mount</command> commands, the file system must be + remounted manually after the system is rebooted. Failing to + remount will result in <application>Update + Manager</application> not being able to access the + resource.</para> + </note> + </listitem> + </varlistentry> + <varlistentry> + <term> + <emphasis role="bold">Distribution</emphasis> + </term> + <listitem> + <para>The name of the distribution or name of the distribution + version.</para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <emphasis role="bold">Sections</emphasis> + </term> + <listitem> + <para>The section of the distribution repository to access.</para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <emphasis role="bold">Comment</emphasis> + </term> + <listitem> + <para>Add a comment to describe the repository.</para> + </listitem> + </varlistentry> + </variablelist> + <note> + <para>Repositories defined using <application>Synaptic</application>, + another package management tool, are automatically displayed in the + <application>Update Manager</application> Software Sources + list.</para> + </note> + </sect3> + </sect2> + <sect2 id="managing-authentication"> + <title>Managing Authentication Keys</title> + <para>Authentication keys make it possible to verify the integrity of + update software. From the <interface>Authentication Keys</interface> + dialog it is possible to view and manage the list authentication keys. + Each key corresponds to a Software Source defined in the + <interface>Software Preference</interface> dialog (see <xref + linkend="managing-sources"/>). 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.</para> + <!-- I am not sure how the keys are obtained --> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/authentication.png" format="PNG"/> + </imageobject> + <caption> + <para>Managing Authentication Keys</para> + </caption> + </mediaobject> + </screenshot> + <sect3 id="adding-auth-keys"> + <title>Adding Authentication Keys</title> + <para>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 <ulink + url="http://www.keyserver.net">www.keyserver.net</ulink>. The key + can then be retrieved using the command <command>gpg + -recv-key</command>. When the key resides on a key server the option + <option>--keyserver</option> must be used to give the name of this + key server.</para> + <programlisting> +gpg -recv-key --keyserver www.keyserver.net + </programlisting> + <note> + <para>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.</para> + </note> + <para>Once the key is downloaded, select it using the <interface>Choose + a key-file</interface> dialog that is displayed when the + <guibutton>Add</guibutton> button.</para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/authentication-add.png" format="PNG"/> + </imageobject> + <caption> + <para>Adding Authentication Keys</para> + </caption> + </mediaobject> + </screenshot> + </sect3> + <sect3 id="remove-auth-keys"> + <title>Removing Authentication Keys</title> + <para>Authentication keys can be removed by selecting a record item then + <action>clicking</action> the <guibutton>Remove</guibutton> + button.</para> + </sect3> + <sect3 id="restore-auth-keys"> + <title>Restoring Default Keys</title> + <para>During installation the default Ubuntu Authentication keys are + added to the <application>Ubuntu GPG Keyring</application> package. In + the even of a key being accidentally deleted it can be restored by + clicking the <guibutton>Restore default keys</guibutton> + button.</para> + </sect3> + </sect2> + <sect2 id="managing-settings"> + <title>Managing Settings</title> + <para>The <guibutton>Settings</guibutton> button, located on the + <interface>Software Preferences</interface> dialog, displays the + <interface>Settings</interface> dialog. From this interface users can + manage the behavior of the application and pre-update process.</para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/settings.png" format="PNG"/> + </imageobject> + <caption> + <para>Managing Settings</para> + </caption> + </mediaobject> + </screenshot> + <para>The following options are available:</para> + <itemizedlist> + <title>User Interface</title> + <listitem> + <para> + <emphasis>Show disabled software sources:</emphasis> - When checked + software sources that are not checked in the <interface>Software + Preferences</interface> dialog are displayed. When unchecked, + these items are not displayed in the list.</para> + </listitem> + </itemizedlist> + <itemizedlist> + <title>Internet Updates</title> + <listitem> + <para> + <itemizedlist> + <listitem> + <para> + <emphasis>Automatically check for software updates:</emphasis> + - When checked the <guilabel>Update interval in + days</guilabel> option is enabled. <application>Update + Manager</application> will poll all enabled software sources + for updates according to the value specified in the + scroll-box.</para> + </listitem> + <listitem> + <para> + <emphasis>Download upgradable packages:</emphasis> - When + checked <application>Update Manager</application> will + automatically download any available software update packages. + It will not install them until the user has defined the + installation list (see <xref linkend="performing-updates" + />).</para> + </listitem> + </itemizedlist> + </para> + </listitem> + </itemizedlist> + <itemizedlist> + <title>Temporary files</title> + <listitem> + <para> + <emphasis>Automatically clean temporary packages files:</emphasis> - + When checked the <guilabel>Clean interval in days</guilabel> option + is enabled. <application>Update Manager</application> automatically + removes any temporary files created by the upgrade process according + to the value specified in the scroll-box.</para> + </listitem> + <listitem> + <para><emphasis>Set maximum size of the package cache:</emphasis> When checked the size of + the package cache is limited to the value specified in the <guibutton>Maximum size in + MB</guibutton> spin-box.</para> + </listitem> + <listitem> + <para><emphasis>Delete old packages in the package cache:</emphasis> When checked cached + packaged with a date older than the value specified in the <guibutton>Maximum age in + days</guibutton> spin-box will be automatically purged from the cache.</para> + </listitem> + </itemizedlist> + </sect2> + <sect2 id="configure-terminal-only-view"> + <title>Install Progress for Terminal View Only</title> + <para>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.</para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/main-view-monitor-update.png" + format="PNG"/> + </imageobject> + <caption> + <para>Monitoring Installation Progress</para> + </caption> + </mediaobject> + </screenshot> + <caution> + <para>Do not terminate the installation process. This may lead to + corruption of installed programs and general system + instability.</para> + </caution> + <para>Changing between 'Progress Bar' and + 'Terminal View,' modes is managed via + <application>Synaptic</application>. To change modes proceed as + follows:</para> + <procedure> + <step> + <para>Start <application>Synaptic</application> by selecting <menuchoice> + <guimenu>System</guimenu> + <guisubmenu>Administration</guisubmenu> + <guimenuitem>Synaptic Package Manager</guimenuitem> + </menuchoice> from the Desktop menu system. </para> + </step> + <step> + <para>When prompted, enter your password.</para> + </step> + <step> + <para>From the main menu, select <menuchoice> + <guimenu>Settings</guimenu> + <guimenuitem>Preferences</guimenuitem> + </menuchoice>. The <interface>Preferences</interface> dialog is + displayed.</para> + </step> + <step> + <para>From the <guibutton>General</guibutton> tab, <guilabel>Apply + Changes</guilabel> group, <action>check</action> or + <action>uncheck</action> the <guibutton>Apply changes in terminal + window</guibutton> checkbox.</para> + <screenshot> + <mediaobject> + <imageobject> + <imagedata fileref="figures/synaptic-toggle-install-view.png" + format="PNG"/> + </imageobject> + <caption> + <para>Synaptic Preferences - General Tab</para> + </caption> + </mediaobject> + </screenshot> + </step> + <step> + <para> + <action>Click</action> + <guibutton>OK</guibutton> and exit + <application>Synaptic</application>.</para> + </step> + </procedure> + </sect2> + </sect1> + <sect1 id="about"> + <title>About Update Manager</title> + <para>The <application>Update Manager</application> was written by Michiel + Sikkes <email>michiel@eyeopened.nl</email> and Michael Vogt + <email>michael.vogt@ubuntu.com</email> as an + <application>apt</application> update manager for the GNOME Desktop of the + Ubuntu Linux distribution. The user manual was written by Sean Wheller + <email>sean@inwords.co.za</email>.</para> + <para>To report a bug or make a suggestion regarding this package or this + manual, send mail to <email>ubuntu-users@lists.ubuntu.com</email>.</para> + </sect1> &GFDL; </article> 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 |
