2
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
3
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
4
<!ENTITY legal SYSTEM "legal.xml">
5
<!ENTITY GFDL SYSTEM "fdl-appendix.xml">
7
<!--<?yelp:chunk-depth 4?>-->
9
(Do not remove this comment block.)
11
Last modified: March 26, 2005
13
Sean Wheller <sean@inwords.co.za>
14
Jeff Schering <jeffschering@gmail.com>
17
(translators put your name and email here)
19
<!-- =============Document Header ============================= -->
20
<article id="index" lang="en">
21
<!-- please do not change the id; for translations, change lang to -->
22
<!-- appropriate code -->
24
<title>Update Manager Manual</title>
27
<holder>In Words</holder>
29
<!-- translators: uncomment this:
33
<holder>ME-THE-TRANSLATOR (Latin translation)</holder>
37
<!-- An address can be added to the publisher information. If a role is
38
not specified, the publisher/author is the same for all versions of the
41
<!--<publishername> GNOME Documentation Project </publishername>-->
43
<ulink url="http://www.inwords.co.za">In Words Techdoc Solutions</ulink>
46
<!-- This file contains link to license for the documentation (GNU FDL), and
47
other legal stuff such as "NO WARRANTY" statement. Please do not change
51
<firstname>Sean</firstname>
52
<surname>Wheller</surname>
54
<orgname>In Words</orgname>
56
<email>sean@inwords.co.za</email>
60
<othercredit role="editor">
61
<firstname>Jeff</firstname>
62
<surname>Schering</surname>
63
<contrib>Editor</contrib>
65
<!-- This is appropriate place for other contributors: translators,
66
maintainers, etc. Commented out by default.
67
<othercredit role="translator">
68
<firstname>Latin</firstname>
69
<surname>Translator 1</surname>
71
<orgname>Latin Translation Team</orgname>
72
<address> <email>translator@gnome.org</email> </address>
74
<contrib>Latin translation</contrib>
78
<!-- According to GNU FDL, revision history is mandatory if you are -->
79
<!-- modifying/reusing someone else's document. If not, you can omit it. -->
80
<!-- Remember to remove the &manrevision; entity from the revision entries other
82
<!-- than the current revision. -->
83
<!-- The revision numbering system for GNOME manuals is as follows: -->
84
<!-- * the revision number consists of two components -->
85
<!-- * the first component of the revision number reflects the release version of the GNOME desktop. -->
86
<!-- * the second component of the revision number is a decimal unit that is incremented with each revision of the manual. -->
87
<!-- For example, if the GNOME desktop release is V2.x, the first version of the manual that -->
88
<!-- is written in that desktop timeframe is V2.0, the second version of the manual is V2.1, etc. -->
89
<!-- When the desktop release version changes to V3.x, the revision number of the manual changes -->
90
<!-- to V3.0, and so on. -->
93
<revnumber>V0.0.1</revnumber>
94
<date>06/03/2005</date>
96
<para role="author">First version of the manual created in accordance
97
with Update Manager V0.37.1+svn20050301. Documentation Writer
98
<email>sean@inwords.co.za</email>
100
<para role="publisher">
101
<ulink url="http://www.inwords.co.za">InWords Techdoc
107
<revnumber>V0.0.2</revnumber>
108
<date>26/03/2005</date>
110
<para role="author">Edit of V0.0.1 to make some nodes shorter.
111
Editor <email>jeffschering@gmail.com</email>
113
<para role="publisher">
114
<ulink url="http://www.inwords.co.za">InWords Techdoc
120
<revnumber>V0.0.3</revnumber>
121
<date>26/03/2005</date>
123
<para role="author">Added Help, Add CD, Settings options.
124
<email>sean@inwords.co.za</email>
126
<para role="publisher">
127
<ulink url="http://www.inwords.co.za">InWords Techdoc
133
<releaseinfo>This manual explains how to use Update Manager, an apt update
134
management application for the GNOME desktop created by the Ubuntu Linux
135
project.</releaseinfo>
137
<title>Feedback</title>
138
<!--<para>To report a bug or make a suggestion regarding this package or this
139
manual, follow the directions in the <ulink url="ghelp:gnome-feedback"
140
type="help">GNOME Feedback Page</ulink>. </para>-->
141
<para>To report a bug or make a suggestion regarding this package or this
142
manual, send mail to <email>ubuntu-users@lists.ubuntu.com</email>.</para>
143
<!-- Translators may also add here feedback address for translations -->
146
<!-- ============= Document Body ============================= -->
147
<!-- ============= Introduction ============================== -->
149
<title>Introduction</title>
151
<application>Update Manager</application> is a graphical interface to the
152
software update features of <application>Advanced Packaging
153
Tool</application> (<acronym>APT</acronym>). <acronym>APT</acronym> is a
154
command line tool for installing, updating, and removing software.</para>
156
<application>Update Manager</application> makes the task of checking for
157
and installing software updates as effortless as possible.
158
<application>Update Manager</application> keeps your system up-to-date
159
by checking Ubuntu's software repositories for new versions of installed
160
software. The new versions usually contain bug fixes and new features, but
161
may also contain security updates. Use Update Manager on a regular basis
162
to ensure that your system is as up-to-date and secure as possible.</para>
164
<application>Update Manager</application> decides which software needs to
165
be updated by comparing the version numbers of individual software files
166
on your computer with the software in one or more software repositories.
167
The software repositories are usually on remote network servers, but may
168
also be on a CD-ROM. Whenever <application>Update Manager</application>
169
notifies you that an update is available, you may choose to install the
170
update immediately, or to ignore the update.</para>
172
<application>Update Manager</application> has settings and preferences
173
which allow you to: set how often it checks for updates, add and remove
174
software repositories, and manage repository authentication keys. </para>
176
<sect1 id="getting-started">
177
<title>Getting Started</title>
178
<sect2 id="installation">
179
<title>Installation</title>
181
<application>Update Manager</application> is installed as part of the
182
Ubuntu standard installation, and should already be on your system. The
183
application is known as <application>Ubuntu Update
184
Manager</application>. If you need to install <application>Update
185
Manager</application>, you can use <application>Synaptic Package
186
Manager</application>. Choose <menuchoice>
187
<guimenu>System</guimenu>
188
<guisubmenu>Administration</guisubmenu>
189
<guimenuitem>Synaptic Package Manager</guimenuitem>
190
</menuchoice> to start <application>Synaptic</application>. The package
191
you need to install is <command>update-manager</command>.</para>
192
<para>You may also install Update Manager from the command line using
193
<command>apt-get</command>. To install <application>Update
194
Manager</application> from the command line:</para>
196
sudo apt-get update-manager
199
<application>Update Manager</application> is dependent on the following
200
packages: 'python,' 'python-gnome2,'
201
'python-apt,' 'synaptic,' and
202
'lsb-release.'</para>
204
<sect2 id="starting-update-manager">
205
<title>Starting Update Manager</title>
206
<para>Choose <menuchoice>
207
<guimenu>System</guimenu>
208
<guisubmenu>Administration</guisubmenu>
209
<guimenuitem>Ubuntu Update Manager</guimenuitem>
210
</menuchoice> to start the application. Enter your password when
212
<para>You may also start <application>Update Manager</application> from
213
the command line:</para>
218
<sect2 id="main-window">
219
<title>Main Window</title>
220
<para>The <application>Update Manager</application> main window is used for
221
managing the update process and setting preferences.</para>
222
<para>When you open <application>Update Manager</application>, the main
223
window displays the list of packages that need to be installed to update
224
your computer. If your computer is up-to-date, the main window contains
225
only the message "Your system is up-to-date!" </para>
229
<imagedata fileref="figures/main-system-updates-available.png"
233
<para>Available Updates</para>
239
<sect1 id="performing-updates">
240
<title>Performing Updates</title>
241
<sect2 id="updating">
242
<title>Updating Your Computer</title>
243
<para>When you open <application>Update Manager</application>, the main
244
window displays the list of packages that need to be installed to update
245
your computer. If your computer is up-to-date, the main window contains
246
only the message "Your system is up-to-date!" </para>
250
<imagedata fileref="figures/main-system-updates-available.png"
254
<para>Available Updates</para>
258
<para>By default, all packages are marked for installation. In most
259
cases you will install all of the packages right away. However, if there
260
are a large number of updates you may want to do only a few at a time.</para>
261
<para>To un-mark a package for installation, <action>clear</action> the check box
262
for the package.</para>
263
<para>To see additional information about a package, <action>click</action> on
264
<guibutton>Details</guibutton>.
265
(see <xref linkend="expanding-update-info"/>)</para>
266
<para>When you are ready to install the selected packages,
267
<action>click</action> on <guibutton>Install</guibutton>.</para>
268
<para>If <application>Update Manager</application> detects one or more
269
packages without a digital signature, the
270
<guilabel>Summary</guilabel> dialog is displayed.</para>
271
<para>The <guilabel>Summary</guilabel> dialog lists three groups of update
276
<emphasis role="bold">NOT AUTHENTICATED</emphasis>
279
<para>Packages without a digital signature.</para>
284
<emphasis role="bold">To be upgraded</emphasis>
287
<para>Packages that will be upgraded.</para>
292
<emphasis role="bold">Unchanged</emphasis>
295
<para>Packages that will not be upgraded due to dependency issues.
296
The packages will be upgraded in a future <application>Update
297
Manager</application> session, once the developers have
298
resolved the package dependencies.</para>
302
<para>If you do not want to install non-authenticated packages, click
303
<guibutton>Cancel</guibutton>. The <guilabel>Summary</guilabel>
304
dialog will close, and you can
305
deselect the packages in the <application>Update Manager</application>
308
<para>If a deselected package is required as a dependency for a selected
309
package, <application>Update Manager</application> will install the
310
deselected package to satisfy the dependency.</para>
313
<application>Update Manager</application> downloads all of the
314
selected packages before installing them. The entire process might take a
315
long time depending on the amount of data that needs to be downloaded, the
316
speed of your network connection, and the number of packages that need to
317
be installed. While downloading packages,
318
<application>Update Manager</application> displays a dialog box that
319
monitors the download progress. (See <xref
320
linkend="monitoring-download"/>).</para>
322
<sect2 id="expanding-update-info">
323
<title>Expanded Update Information</title>
324
<para>To see additional information about a package:</para>
327
<para>Click on the package in the main window.</para>
330
<para>Click on <guibutton>Details</guibutton>.A tabbed section
331
opens within the main window.</para>
334
<para>The tabs are as follows:</para>
338
<emphasis role="bold">Changes</emphasis>
341
<para>A list of the changes incorporated in the package. The list
342
is the contents of the <filename>ChangeLog</filename> file for the
348
<emphasis role="bold">Description</emphasis>
351
<para>A short description of each program in the package.</para>
356
<sect2 id="monitoring-download">
357
<title>Monitoring Download Progress</title>
358
<para><application>Update Manager</application> displays the
359
<guilabel>Installing updates</guilabel> window while the
360
packages are downloading. The progress bar in the
361
<guilabel>Installing updates</guilabel> window shows the progress
362
of the entire update.</para>
363
<para>To display the download progress of each package, click on
364
<guibutton>Show progress of single files</guibutton>.</para>
365
<para>To cancel the download, click <guibutton>Cancel</guibutton>.
367
<para>All files must be downloaded before <application>
368
Update Manager</application> can proceed to the installation stage. If
369
the network connections fails or if you cancel the download, the update
370
will not be installed.</para>
372
<para>To resume a canceled or failed download, click on Install in the
373
main window. <application>Update Manager</application> will resume the
374
download from the last successfully downloaded file.</para>
377
<sect2 id="monitoring-installation">
378
<title>Monitoring Installation Progress</title>
379
<para><application>Update Manager</application> displays the
380
<guilabel>Installation updates</guilabel> window while the updates are
381
being installed. The progress bar inside the <guilabel>Installation
382
updates</guilabel> window shows the progress of the entire installation.
384
<para>To display the installation progress of each package, click on
385
<guibutton>Terminal</guibutton>. The terminal view opens within the
386
window. The terminal view displays the unfiltered output of the Advanced
387
Packaging Tool (APT). APT is the tool that Update Manager uses to
388
perform the update.</para>
390
<para>Do not terminate the installation process. This may lead to
391
corruption of installed programs and general system
396
<sect1 id="setting-preferences">
397
<title>Setting Preferences</title>
398
<para>The <application>Update Manager</application>
399
<guibutton>Preferences</guibutton> button displays the <guilabel>Software
400
Preferences</guilabel> dialog. From this dialog you can perform the
401
following tasks:</para>
404
<para>Manage software sources (see <xref linkend="managing-sources"
408
<para>Manage authentication keys (see <xref
409
linkend="managing-authentication"/>).</para>
412
<para>Manage settings (see <xref linkend="managing-settings"/>).</para>
415
<sect2 id="managing-sources">
416
<title>Managing Software Sources</title>
417
<para>During installation of a distro, software repositories are
418
automatically added to the list of 'software sources.'
419
Typical sources added by the distro installation include the
420
installation source, update, and security repositories. Sources can be
421
added to and removed from the list and existing sources can be edited.</para>
423
<para>The operations described here modify <filename class="devicefile"
424
>/etc/apt/sources.list</filename> using the <application>Update
425
Manager</application> graphical user interface. Software sources can
426
also be managed by making direct modifications in <filename
427
class="devicefile">/etc/apt/sources.list</filename>. This is only
428
advised for advanced users.</para>
430
<sect3 id="adding-sources">
431
<title>Adding Software Sources</title>
432
<para>Software may be installed using various access methods:</para>
436
<emphasis>CD-ROM</emphasis> - Compact Disk Read Only Memory,
437
normally directly connected to the computer system and mounted
438
locally by the operating system.</para>
440
<!-- Currently unsupported see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=60910 -->
441
<!-- mvo: is handled with cdrom URIs -->
444
<emphasis>DVD</emphasis> - Digital Video Disk, normally directly
445
connected to the computer system and mounted locally by the
446
operating system.</para>
450
<emphasis>FTP</emphasis> - File Transfer Protocol, a secure and
451
reliable protocol designed specifically for the purpose of
452
transferring large files across the Internet.</para>
456
<emphasis>HTTP</emphasis> - HyperText Transfer Protocol, commonly
457
used to request and receive Web pages, but can also be used for
458
file transfer.</para>
462
<emphasis>SMB</emphasis> - Server Management Block is used to
463
access shared resources on computers running Microsoft
464
<trademark>Windows</trademark> or <application>Samba
465
Server</application>.</para>
469
<emphasis>NFS</emphasis> - Network File System is used to access
470
shared resources on Linux/UNIX computers.</para>
474
<para>Before software sources residing on SMB or NFS shares can be
475
defined, the share must be mounted by the local system. Access can
476
then be made via the local filesystem. For more information see
477
<xref linkend="editing-sources"/>.</para>
479
<para>A new software source can be defined by <action>clicking</action>
480
the <guibutton>Add</guibutton> button located on the
481
<guilabel>Software Preferences</guilabel> dialog. This will
482
display the <guilabel>Edit Repository</guilabel> dialog.</para>
486
<imagedata fileref="figures/preferences-add.png" format="PNG"/>
489
<para>Adding Software Sources</para>
493
<para>Complete the <guilabel>Edit Repository</guilabel> dialog to add
494
a new Software source.</para>
498
<emphasis role="bold">Repository</emphasis>
501
<para>A drop-list containing known software sources.</para>
506
<emphasis role="bold">Components</emphasis>
509
<para>The Ubuntu software repository contains thousands of
510
software packages organized into four
511
'components,' on the basis of the level of
512
support we can offer them, and whether or not they comply with
513
Free Software Philosophy. The components are called
514
'main,' 'restricted,'
515
'universe,' and
516
'multiverse.'</para>
517
<para>Check the components you wish to include in the update list.</para>
521
<emphasis role="bold">Officially supported (main)</emphasis>
522
- The main distribution component contains applications that
523
are free software, can freely be redistributed and are fully
524
supported by the Ubuntu team. This includes the most popular
525
and most reliable open source applications available, much
526
of which is installed by default when you install Ubuntu.
527
Software in main includes a hand-selected list of
528
applications that the Ubuntu developers, community, and
529
users feel are important and that the Ubuntu security and
530
distribution team are willing to support. When you install
531
software from the main component you are assured that the
532
software will come with security updates and technical
533
support. We believe that the software in main includes
534
everything most people will need for a fully functional
535
desktop or Internet server running only open source
536
software. The licenses for software applications in main
537
must be free, but main may also may contain binary firmware
538
and selected fonts that cannot be modified without
539
permission from their authors. In all cases redistribution
540
is unencumbered.</para>
544
<emphasis role="bold">Restricted Copyright</emphasis> - The
545
restricted component is reserved for software that is very
546
commonly used, and which is supported by the Ubuntu team
547
even though it is not available under a completely free
548
license. Please note that it may not be possible to provide
549
complete support for this software since we are unable to
550
fix the software ourselves, but can only forward problem
551
reports to the actual authors. Some software from restricted
552
will be installed on Ubuntu CDs but is clearly separated to
553
ensure that it is easy to remove. We include this software
554
because it is essential in order for Ubuntu to run on
555
certain machines - typical examples are the binary drivers
556
that some video card vendors publish, which are the only way
557
for Ubuntu to run on those machines. By default, we will
558
only use open source software unless there is simply no
559
other way to install Ubuntu. The Ubuntu team works with such
560
vendors to accelerate the open-sourcing of their software to
561
ensure that as much software as possible is available under
562
a Free license.</para>
566
<emphasis role="bold">Community maintained
567
(Universe)</emphasis> - The universe component is a snapshot
568
of the free, open source, and Linux world. In universe you
569
can find almost every piece of open source software, and
570
software available under a variety of less open licenses,
571
all built automatically from a variety of public sources.
572
All of this software is compiled against the libraries and
573
using the tools that form part of main, so it should install
574
and work well with the software in main, but it comes with
575
no guarantee of security fixes and support. The universe
576
component includes thousands of pieces of software. Through
577
universe, users are able to have the diversity and
578
flexibility offered by the vast open source world on top of
579
a stable Ubuntu core.</para>
583
<emphasis role="bold">Non Free (Multiverse)</emphasis> - The
584
'multiverse' component contains software
585
that is <emphasis>not free</emphasis>, which means the
586
licensing requirements of this software do not meet the
587
Ubuntu 'main' Component license Policy.
588
The onus is on you to verify your rights to use this
589
software and comply with the licensing terms of the
590
copyright holder. This software is not supported and usually
591
cannot be fixed or updated. Use it at your own risk.</para>
598
<sect3 id="create-custom-sources">
599
<title>Creating Custom Software Sources</title>
600
<para>It is also possible to define custom software sources.</para>
601
<para>To define a custom software source <action>click</action> the
602
<guibutton>Custom</guibutton> button located on the <guilabel>Edit
603
Repository</guilabel> dialog. This will display a dialog in which
604
the custom repository can be defined using
605
<application>apt</application> command syntax.
606
<application>Apt</application> is an Advanced Packaging Tool and
607
front-end to <application>dpkg</application> the Debian Package
608
Management System. Once the <guilabel>apt line</guilabel> is entered
609
<action>click</action> the <guibutton>Add repository</guibutton>
614
<imagedata fileref="figures/preferences-add-custom.png"
618
<para>Creating Custom Software Sources</para>
622
<para>The <application>apt</application> command syntax defines the
623
'type,' 'location,' and
624
'content' of the repository. Example of the command
625
syntax could look like this.</para>
627
<command>deb ftp://archive.ubuntu.com/ubuntu/ hoary main restricted universe multiverse</command>
629
<para>This example would define the software sources as a Debian source
630
at ubuntu.com containing the hoary release and using all components.
631
For definition of the components, see <xref linkend="managing-sources"
634
<sect3 id="remove-sources">
635
<title>Removing Software Sources</title>
636
<para>Software sources can be removed from the sources list by selecting
637
the software source then <action>clicking</action> the
638
<guibutton>Remove</guibutton> button located on the
639
<guilabel>Software Preferences</guilabel> dialog.</para>
640
<para>Removal of a software source requires that the
641
<application>apt</application> file (<filename class="devicefile"
642
>/etc/apt/sources.list</filename>) that contains the a list of
643
software sources is updated. Before modifying this file
644
<application>Update Manager</application> prompts to confirm the
645
operation. If the operation is confirmed a backup copy is create in
646
<filename class="devicefile"
647
>/etc/apt/sources.list.save</filename>.</para>
649
<sect3 id="editing-sources">
650
<title>Editing Software Sources</title>
651
<para>To change the values defining a software source, select the source
652
record then <action>click</action> the edit button. This will display
653
the <guilabel>Edit Repository</guilabel> dialog.</para>
657
<imagedata fileref="figures/preferences-edit.png" format="PNG"/>
660
<para>Editing Software Sources</para>
667
<emphasis role="bold">Type</emphasis>
670
<para>Software sources may contain software in
671
'Binary' or 'Source Code'
672
format. Select the option correlating to the repository
678
<emphasis role="bold">URI</emphasis>
681
<para>Enter a valid Uniform Resource Indicator
682
(<acronym>URI</acronym>). Following is a list of examples for
683
each of the possible access methods:</para>
687
<!-- mvo: we don't want users to add the cd manually
688
new CDs with ubuntu will be detected
689
automatically when inserted and it will prompt
690
for action (start package manager,
692
*mvo* either the sources edit window needs a "add-cdrom" butotn or the user needs to run synaptic
693
*froud* I would say add a "Add CDROM"
695
*mvo* I'll file a wishlist bug to myself
696
*mvo* update-manger should have "add-cdrom" is bug #7315
698
<emphasis>CD-ROM</emphasis> -
699
<command>cdrom:[description_of_cd]/</command>
702
<!-- Currently unsupported see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=60910 -->
703
<!-- mvo: is handled with cdrom URIs -->
706
<emphasis>DVD</emphasis> -
707
<command>dvd:[description_of_dvd]/</command>
712
<emphasis>FTP</emphasis> -
713
<command>ftp://ftp.domain.ext/path/to/repository</command>
718
<emphasis>HTTP</emphasis> -
719
<command>http://www.domain.ext/path/to/repository</command>
724
<emphasis>SMB</emphasis> - Works only when the computer is
725
already connected to an SMB share. To connect to SMB share
726
use the following command syntax from the shell
727
<command>smbclient //hostname/sharename -U
728
username</command>. </para>
729
<para>The SMB share is accessed from the local file system
730
once the local system is connected.
731
<command>file://path/to/sharefile</command>
736
<emphasis>NFS</emphasis> - Works only when the computer is
737
already connected to a NFS share. To connect the NFS share
738
must be mounted. NFS shares are mounted on the client side
739
using the mount command. The format of the command is as
740
follows: <command>mount -o [options] [host]:[/remote/export]
741
[/local/directory]</command>
743
<para>Once mounted <application>Update Manager</application>
744
can access the share using the following command
745
<command>file://path/to/local/directory</command>
750
<para>If accessing a SMB or NFS shares by manually issuing the
751
<command>mount</command> commands, the file system must be
752
remounted manually after the system is rebooted. Failing to
753
remount will result in <application>Update
754
Manager</application> not being able to access the
761
<emphasis role="bold">Distribution</emphasis>
764
<para>The name of the distribution or name of the distribution
770
<emphasis role="bold">Sections</emphasis>
773
<para>The section of the distribution repository to access.</para>
778
<emphasis role="bold">Comment</emphasis>
781
<para>Add a comment to describe the repository.</para>
786
<para>Repositories defined using <application>Synaptic</application>,
787
another package management tool, are automatically displayed in the
788
<application>Update Manager</application> Software Sources
793
<sect2 id="managing-authentication">
794
<title>Managing Authentication Keys</title>
795
<para>Authentication keys make it possible to verify the integrity of
796
update software. From the <guilabel>Authentication Keys</guilabel>
797
dialog it is possible to view and manage the list authentication keys.
798
Each key corresponds to a Software Source defined in the
799
<guilabel>Software Preference</guilabel> dialog (see <xref
800
linkend="managing-sources"/>). Keys can be added and removed. In the
801
event of an error it is also possible to restore the default
802
authentication keys provided by the defined update repositories.</para>
803
<!-- I am not sure how the keys are obtained -->
807
<imagedata fileref="figures/authentication.png" format="PNG"/>
810
<para>Managing Authentication Keys</para>
814
<sect3 id="adding-auth-keys">
815
<title>Adding Authentication Keys</title>
816
<para>Authentication keys are usually obtained from the software vendor
817
running the repository. Often the vendor will place a copy of the
818
authentication key on a key server, for example <ulink
819
url="http://www.keyserver.net">www.keyserver.net</ulink>. The key
820
can then be retrieved using the command <command>gpg
821
-recv-key</command>. When the key resides on a key server the option
822
<option>--keyserver</option> must be used to give the name of this
825
gpg -recv-key --keyserver www.keyserver.net
828
<para>If the key is fetched over a untrusted medium, like the
829
Internet, additional steps should be taken to verify the key. For
830
example, getting the fingerprint with a secure method such as by
831
phone, letter, or business card. Alternately you can check if the
832
key is signed with a known-good key.</para>
834
<para>Once the key is downloaded, select it using the <guilabel>Choose
835
a key-file</guilabel> dialog that is displayed when the
836
<guibutton>Add</guibutton> button.</para>
840
<imagedata fileref="figures/authentication-add.png" format="PNG"/>
843
<para>Adding Authentication Keys</para>
848
<sect3 id="remove-auth-keys">
849
<title>Removing Authentication Keys</title>
850
<para>Authentication keys can be removed by selecting a record item then
851
<action>clicking</action> the <guibutton>Remove</guibutton>
854
<sect3 id="restore-auth-keys">
855
<title>Restoring Default Keys</title>
856
<para>During installation the default Ubuntu Authentication keys are
857
added to the <application>Ubuntu GPG Keyring</application> package. In
858
the even of a key being accidentally deleted it can be restored by
859
clicking the <guibutton>Restore default keys</guibutton>
863
<sect2 id="managing-settings">
864
<title>Managing Settings</title>
865
<para>The <guibutton>Settings</guibutton> button, located on the
866
<guilabel>Software Preferences</guilabel> dialog, displays the
867
<guilabel>Settings</guilabel> dialog. From this interface you can
868
manage the behavior of the application and pre-update process.</para>
872
<imagedata fileref="figures/settings.png" format="PNG"/>
875
<para>Managing Settings</para>
879
<para>The following options are available:</para>
881
<title>User Interface</title>
884
<emphasis>Show disabled software sources:</emphasis> - When checked
885
software sources that are not checked in the <guilabel>Software
886
Preferences</guilabel> dialog are displayed. When unchecked,
887
these items are not displayed in the list.</para>
891
<title>Internet Updates</title>
897
<emphasis>Automatically check for software updates:</emphasis>
898
- When checked the <guilabel>Update interval in
899
days</guilabel> option is enabled. <application>Update
900
Manager</application> will poll all enabled software sources
901
for updates according to the value specified in the
906
<emphasis>Download upgradable packages:</emphasis> - When
907
checked <application>Update Manager</application> will
908
automatically download any available software update packages.
909
It will not install them until the user has defined the
910
installation list (see <xref linkend="performing-updates"
918
<title>Temporary files</title>
921
<emphasis>Automatically clean temporary packages files:</emphasis> -
922
When checked the <guilabel>Clean interval in days</guilabel> option
923
is enabled. <application>Update Manager</application> automatically
924
removes any temporary files created by the upgrade process according
925
to the value specified in the scroll-box.</para>
928
<para><emphasis>Set maximum size of the package cache:</emphasis> When checked the size of
929
the package cache is limited to the value specified in the <guibutton>Maximum size in
930
MB</guibutton> spin-box.</para>
933
<para><emphasis>Delete old packages in the package cache:</emphasis> When checked cached
934
packaged with a date older than the value specified in the <guibutton>Maximum age in
935
days</guibutton> spin-box will be automatically purged from the cache.</para>
939
<sect2 id="configure-terminal-only-view">
940
<title>Install Progress for Terminal View Only</title>
941
<para>It is also possible to configure the installation progress to use
942
only a terminal view. That is to say, no progress bar is displayed, only
943
a terminal view.</para>
947
<imagedata fileref="figures/main-view-monitor-update.png"
951
<para>Monitoring Installation Progress</para>
956
<para>Do not terminate the installation process. This may lead to
957
corruption of installed programs and general system
960
<para>Changing between 'Progress Bar' and
961
'Terminal View,' modes is managed via
962
<application>Synaptic</application>. To change modes proceed as
966
<para>Start <application>Synaptic</application> by selecting <menuchoice>
967
<guimenu>System</guimenu>
968
<guisubmenu>Administration</guisubmenu>
969
<guimenuitem>Synaptic Package Manager</guimenuitem>
970
</menuchoice> from the Desktop menu system. </para>
973
<para>When prompted, enter your password.</para>
976
<para>From the main menu, select <menuchoice>
977
<guimenu>Settings</guimenu>
978
<guimenuitem>Preferences</guimenuitem>
979
</menuchoice>. The <guilabel>Preferences</guilabel> dialog is
983
<para>From the <guibutton>General</guibutton> tab, <guilabel>Apply
984
Changes</guilabel> group, <action>check</action> or
985
<action>uncheck</action> the <guibutton>Apply changes in terminal
986
window</guibutton> checkbox.</para>
990
<imagedata fileref="figures/synaptic-toggle-install-view.png"
994
<para>Synaptic Preferences - General Tab</para>
1001
<action>Click</action>
1002
<guibutton>OK</guibutton> and exit
1003
<application>Synaptic</application>.</para>
1009
<title>About Update Manager</title>
1010
<para>The <application>Update Manager</application> was written by Michiel
1011
Sikkes <email>michiel@eyeopened.nl</email> and Michael Vogt
1012
<email>michael.vogt@ubuntu.com</email> as an
1013
<application>apt</application> update manager for the GNOME Desktop of the
1014
Ubuntu Linux distribution. The user manual was written by Sean Wheller
1015
<email>sean@inwords.co.za</email>.</para>
1016
<para>To report a bug or make a suggestion regarding this package or this
1017
manual, send mail to <email>ubuntu-users@lists.ubuntu.com</email>.</para>
1018
</sect1> &GFDL; </article>
added
removed
gnome/upstream/gnome/update-manager/C/update-manager.xml
