blob: c091df0256cbc42b06662bb1bd35fba26afb285b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
|
#use wml::debian::template title="Errata for Debian 2.0 on x86 machines"
#use wml::debian::translation-check translation="f717b317b4078efe7128451d15dac1cb8f53b330" maintainer="galaxico"
<h3>Installation</h3>
<p>There are no reported errata in the installation process.
<h3>Upgrade</h3>
<p>The Debian 2.0 CD images included a version of cd_autoup.sh that has a few
bugs. The bugs are relatively harmless, and simply
result in a few of the packages that were meant to be installed by cd_autoup.sh
not being installed. The next dselect run should sort it out.
<p>Even so, upgrades should be done using the
<a href="http://archive.debian.org/debian/dists/hamm/main/upgrade-i386/cd_autoup.sh">fixed
version of autoup.sh</a>. The 2.0 r1 CDs don't have this problem.
<h3>Packages</h3>
<p>The following are problems with software upgrades that you should be careful of:
<ul>
<li>(Jul 24) There is a Y2K problem in the version of CVS in 2.0. A fixed version
will be released to slink as soon as the author releases a new version.
<li>(Jul 24) A security bug in svgalib was discovered too late to allow the fix
into 2.0. If you use svgalib you should upgrade to the version in unstable.
It should be available in a few days.
<li>(Jul 24) There is a security hole in cfingerd, though Debian is not vulnerable as
shipped. You need to turn on certain options in the config file to allow
the vulnerability. To be safe, upgrade to the version in slink.
</ul>
|
