lenny/pt_PT/issues.po

# SOME DESCRIPTIVE TITLE
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: release-notes 5.0\n"
"POT-Creation-Date: 2008-08-07 07:57+0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: ENCODING"

# type: Content of: <chapter><title>
#: en/issues.dbk:9
msgid "Issues to be aware of for &releasename;"
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:11
msgid "Potential problems"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:13
msgid ""
"Sometimes, changes have side-effects we cannot reasonably avoid, or we "
"expose bugs somewhere else.  We document here the issues we are aware of.  "
"Please also read the errata, the relevant packages' documentation, bug "
"reports and other information mentioned in <xref linkend=\"morereading\"/> ."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:19
msgid "Problems with devices related to udev"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:21
msgid ""
"Although <systemitem role=\"package\">udev</systemitem> has been tested "
"extensively, you may experience minor problems with some devices that will "
"need to be fixed.  The most common problems are changed permission and/or "
"ownership of a device.  In some cases a device may not be created by default "
"(e.g.  <filename>/dev/video</filename> and <filename>/dev/radio</filename>)."
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:28
msgid ""
"<systemitem role=\"package\">udev</systemitem> provides configuration "
"mechanisms to deal with these issues.  See <citerefentry> "
"<refentrytitle>udev</refentrytitle> <manvolnum>8</manvolnum> </citerefentry> "
"and <filename>/etc/udev</filename> for further information."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:36
msgid "Some applications may no longer work with a 2.4 kernel"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:38
msgid ""
"Some applications in &releasename; may no longer work with a 2.4 kernel, for "
"example because they require <literal>epoll()</literal> support, which is "
"not available in 2.4 kernels.  Such applications may either not work at all "
"or not work correctly until the system has been rebooted with a 2.6 kernel."
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:44
msgid ""
"One example is the HTTP proxy <systemitem "
"role=\"package\">squid</systemitem>."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:49
msgid "Certain network sites cannot be reached by TCP"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:51
msgid ""
"Since 2.6.17, Linux aggressively uses TCP window scaling which is specified "
"in RFC 1323.  Some servers have a broken behavior, and announce wrong window "
"sizes for themselves.  For more details, please see the bug reports <ulink "
"url=\"http://bugs.debian.org/381262\">#381262</ulink>, <ulink "
"url=\"http://bugs.debian.org/395066\">#395066</ulink>, <ulink "
"url=\"http://bugs.debian.org/401435\">#401435</ulink>."
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:59
msgid ""
"There are usually two workarounds to these problems: either revert the "
"maximum allowed TCP window sizes to a smaller value (preferable) or turn off "
"TCP window scaling altogether (deprecated).  See the example commands in the "
"<ulink "
"url=\"http://www.debian.org/devel/debian-installer/errata\">debian-installer "
"errata page</ulink>."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:68
msgid "Automatic poweroff stops working"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:70
msgid ""
"On some older systems, <literal>shutdown -h</literal> may not power off the "
"system anymore (but just stop it).  This happens because apm needs to be "
"used there.  Adding <literal>acpi=off apm=power_off</literal> to the "
"kernel's command line, e.g.  in <systemitem "
"role=\"package\">grub</systemitem> or <systemitem "
"role=\"package\">lilo</systemitem> configuration files should fix this "
"issue.  Please see bug <ulink "
"url=\"http://bugs.debian.org/390547\">#390547</ulink> for additional "
"information."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:81
msgid "Slower updates of APT package index files"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:83
msgid ""
"By default, the &releasename; version of <command>apt</command> uses a new "
"way to update APT package index files (when you run <literal>aptitude "
"update</literal>) which downloads differences files (instead of the full "
"package index file) called <literal>pdiff</literal>.  This new feature "
"should use less bandwidth and be faster for most systems.  Unfortunately, it "
"can also have the opposite effect of making the updates slower on systems "
"with fast network connections (or a very nearby mirror) which are "
"infrequently updated, as it might take more time for the system to merge the "
"differences files than to download a full package index.  It is possible to "
"disable this feature by adding <literal>Acquire::Pdiffs false;</literal> to "
"the <filename>/etc/apt/apt.conf</filename> configuration file."
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:96
msgid ""
"This change mostly affects users of the <emphasis>unstable</emphasis> and "
"<emphasis>testing</emphasis> branch of &debian;, due to the changing nature "
"of these archives.  Users of &releasename; will notice this feature mainly "
"when updating their package status for the security archive."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:104
msgid "ACPI support disabled for some HP laptop models in &releasename; kernel"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:106
msgid ""
"Certain models of HP laptops have an ACPI BIOS that is incompatible with the "
"Linux &kernelversion; kernel shipped in &releasename;, which would prevent "
"the fans from spinning up leading to unnecessary heat stress.  Also, fans "
"might not work after the system is suspended.  The kernel therefore disables "
"ACPI support internally when it detects certain ACPI BIOS versions.  Models "
"known to be affected by this change include the HP nx6125, nx6120, nx6325, "
"nc6120 and nc6000 models."
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:114
msgid ""
"Users who require ACPI support on these systems may install a Linux 2.6.19 "
"or later kernel.  Please see Debian bug <ulink "
"url=\"http://bugs.debian.org/404143\">#404143</ulink> and <ulink "
"url=\"http://bugs.debian.org/400488\">#400488</ulink>, and Linux Kernel's "
"bugs <ulink "
"url=\"http://bugzilla.kernel.org/show_bug.cgi?id=5534\">#5534</ulink> and "
"<ulink url=\"http://bugzilla.kernel.org/show_bug.cgi?id=7122\">#7122</ulink> "
"for additional information."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:125
msgid "Asynchronous network initialization may cause unpredictable behavior"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:127
msgid ""
"On systems which use <systemitem role=\"package\">udev</systemitem> to load "
"drivers for network interfaces, it is possible due to the asynchronous "
"nature of <systemitem role=\"package\">udev</systemitem> that the network "
"driver will not be loaded before <command>/etc/init.d/networking</command> "
"runs on system boot.  Although including <literal>allow-hotplug</literal> to "
"<filename>/etc/network/interfaces</filename> (in addition to "
"<literal>auto</literal>) will ensure that the network interface is enabled "
"once it becomes available, there is no guarantee that this will finish "
"before the boot sequence begins to start network services, some of which may "
"not behave correctly in the absence of the network interface."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:141
msgid "Trouble when using WPA secured wireless networks"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:143
msgid ""
"In &oldreleasename;, the <systemitem "
"role=\"package\">wpasupplicant</systemitem> package was set up as a system "
"service, configured via <filename>/etc/default/wpasupplicant</filename> and "
"a user-provided <filename>/etc/wpasupplicant.conf</filename>."
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:149
msgid ""
"In &releasename;, <filename>/etc/init.d/wpasupplicant</filename> has been "
"dropped and the Debian package now integrates with "
"<filename>/etc/network/interfaces</filename>, similar to other packages such "
"as <systemitem role=\"package\">wireless-tools</systemitem>.  This means "
"<systemitem role=\"package\">wpasupplicant</systemitem> no longer provides a "
"system service directly."
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:157
msgid ""
"For information on configuring wpasupplicant please refer to "
"<filename>/usr/share/doc/wpasupplicant/README.modes.gz</filename>, which "
"gives examples for <filename>/etc/network/interfaces</filename> files.  "
"Updated information about the usage of the <systemitem "
"role=\"package\">wpasupplicant</systemitem> package in Debian can be found "
"in the <ulink url=\"http://wiki.debian.org/WPA\">Debian Wiki</ulink>."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:167
msgid "Problems with non-ASCII characters in filenames"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:169
msgid ""
"Mounting vfat, ntfs or iso9660 file systems with files that include "
"non-ASCII characters in their filenames will give failures when one tries to "
"use the filenames unless mounting is done with the utf8 option.  An "
"indication might be the following failure: 'Invalid or incomplete multibyte "
"or wide character'.  A possible solution is to use "
"<literal>defaults,utf8</literal> as mount options for vfat, ntfs and iso9660 "
"file systems when they contain filenames with non-ASCII characters."
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:178
msgid ""
"Note that the Linux kernel does not support case-insensitive filename "
"handling for vfat when the <literal>utf8</literal> option is used."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:184
msgid "Sound stops working"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:186
msgid ""
"In rare cases the sound might stop working after the upgrade.  If this "
"happens, go through the alsa checklist: run <command>alsaconf</command> as "
"root user, add your user to the <literal>audio</literal> group, use "
"alsamixer and make sure levels are up and it is unmuted, make sure arts or "
"esound stopped, make sure OSS modules unloaded, make sure speakers are on, "
"check whether the command <literal>cat /dev/urandom &gt; /dev/dsp</literal> "
"works for root."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:198
msgid "Upgrading to a 2.6 kernel"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:200
msgid ""
"The 2.6 kernel series contains major changes from the 2.4 series.  Modules "
"have been renamed and a lot of drivers have been partially or sometimes "
"almost completely rewritten.  Upgrading to a 2.6 kernel from an earlier "
"version is therefore not a process to be undertaken lightly.  This section "
"aims to make you aware of some of the issues you may face."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:207
msgid ""
"If you compile your own kernel from source, make sure you install "
"<systemitem role=\"package\">module-init-tools</systemitem> before you "
"reboot with the 2.6 kernel.  This package replaces <systemitem "
"role=\"package\">modutils</systemitem> for 2.6 kernels.  If you install one "
"of the Debian <systemitem role=\"package\">linux-image</systemitem> "
"packages, this package will be installed automatically because of "
"dependencies."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:215
msgid ""
"If you use <emphasis>LVM</emphasis>, you should also install <systemitem "
"role=\"package\">lvm2</systemitem> before you reboot as the 2.6 kernel does "
"not directly support LVM1.  To access LVM1 volumes, the compatibility layer "
"of <systemitem role=\"package\">lvm2</systemitem> (the dm-mod module) is "
"used.  You can leave <systemitem role=\"package\">lvm10</systemitem> "
"installed; the init scripts will detect which kernel is used and execute the "
"appropriate version."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:223
msgid ""
"If you have entries in the <filename>/etc/modules</filename> file (the list "
"of modules to be loaded during system boot), be aware that some module names "
"may have changed.  If this happens you will have to update this file with "
"the new module names."
msgstr ""

# type: Content of: <chapter><section><para><footnote>
#: en/issues.dbk:229
msgid ""
"For some SATA disk controllers, the device assigned to a drive and its "
"partitions may change from <filename>/dev/hdX</filename> to "
"<filename>/dev/sdX</filename>.  If this happens, you will have to modify "
"your <filename>/etc/fstab</filename> and bootloader configuration "
"accordingly.  Unless these changes are made correctly, your system may not "
"boot correctly<footnote>"
msgstr ""

# type: Content of: <chapter><section><para><footnote><para>
#: en/issues.dbk:234
msgid ""
"It will boot the kernel but will fail when trying to mount the root file "
"system and will abort with an error <emphasis>waiting for root file "
"system</emphasis> followed by <emphasis>unable to mount /dev/hdX ..not "
"found</emphasis>.  You can use the <command>initramfs</command> shell to fix "
"this issue, after you identify the newly assigned device names in the kernel "
"boot messages or by reviewing the contents of "
"<filename>/dev/disk/</filename>."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:240
msgid "</footnote>."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:243
msgid ""
"Once you have installed your 2.6 kernel, but before you reboot, make sure "
"you have a recovery method.  First, make sure that the bootloader "
"configuration has entries for both the new kernel and the old, working 2.4 "
"kernel.  You should also ensure you have a rescue floppy or CD-ROM to hand, "
"in case misconfiguration of the bootloader prevents you from booting the old "
"kernel."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:250
msgid "Keyboard configuration"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:252
msgid ""
"The most invasive change in the 2.6 kernels is a fundamental change of the "
"input layer.  This change makes all keyboards look like normal PC "
"keyboards.  This means that if you currently have a different type of "
"keyboard selected (e.g.  a USB-MAC or Sun keyboard), you will very likely "
"end up with a non-working keyboard after rebooting with the new 2.6 kernel."
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:259
msgid ""
"If you can SSH into the box from another system, you can resolve this issue "
"by running <literal>dpkg-reconfigure console-data</literal>, choosing the "
"option Select keymap from full list and selecting a pc keyboard."
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:264
msgid ""
"If your console keyboard is affected, you will probably also need to "
"reconfigure your keyboard for the X Window System.  You can do this either "
"by running <literal>dpkg-reconfigure xserver-xorg</literal> or by editing "
"<filename>/etc/X11/xorg.conf</filename> directly.  Don't forget to read the "
"documentation referred to in <xref linkend=\"nownownow\"/> ."
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:271
msgid ""
"This issue is unlikely to affect the &arch-title; architecture as all PS/2 "
"and most USB keyboards will already be configured as a normal PC keyboard."
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:276
msgid ""
"Note that if you are using a USB keyboard, this may be configured as either "
"a \"normal\" PC keyboard or as a USB-MAC keyboard. In the first case you "
"will not be affected by this issue."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:283
msgid "Mouse configuration"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:285
msgid ""
"Again because of the changes in the input layer, you may have to reconfigure "
"the X Window System and <systemitem role=\"package\">gpm</systemitem> if "
"your mouse is not working after upgrading to a 2.6 kernel.  The most likely "
"cause is that the device which gets the data from the mouse has changed.  "
"You may also need to load different modules."
msgstr ""

# type: Content of: <chapter><section><section><title>
#: en/issues.dbk:294
msgid "Sound configuration"
msgstr ""

# type: Content of: <chapter><section><section><para>
#: en/issues.dbk:296
msgid ""
"For the 2.6 kernel series the ALSA sound drivers are recommended over the "
"older OSS sound drivers.  ALSA sound drivers are provided as modules by "
"default.  In order for sound to work, the ALSA modules appropriate for your "
"sound hardware need to be loaded.  In general this will happen automatically "
"if you have, in addition to the <systemitem "
"role=\"package\">alsa-base</systemitem> package, either the <systemitem "
"role=\"package\">hotplug</systemitem> package or the <systemitem "
"role=\"package\">discover</systemitem> package installed.  The <systemitem "
"role=\"package\">alsa-base</systemitem> package also blacklists OSS modules "
"to prevent <command>hotplug</command> and <command>discover</command> from "
"loading them.  If you have OSS modules listed in "
"<filename>/etc/modules</filename>, you should remove them."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:313
msgid "XFree86 to X.Org transition"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:315
msgid ""
"The transition to X.Org involves some structural changes.  In case all "
"installed packages are from Debian and also included in &releasename;, the "
"upgrade should work without problems.  However, experience has shown that "
"there are a few changes to be aware of, as they can potentially cause issues "
"during the upgrade."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:322
msgid ""
"The most important change is that <filename>/usr/X11R6/bin</filename> has "
"been dropped and only remains as a symlink to "
"<filename>/usr/bin</filename>.  This means the directory has to be empty at "
"the time the new packages are installed.  The new packages conflict with "
"most packages that used <filename>/usr/X11R6/bin</filename>, but in some "
"cases manual intervention may be needed.  Please remember to not run the "
"distribution upgrade from within an X session."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:331
msgid ""
"In case the upgrade aborts during X.Org installation, you should check if "
"any files are still left in <filename>/usr/X11R6/bin</filename>.  You can "
"then use <literal>dpkg -S</literal> to find out which Debian package "
"installed that file (if any), and remove such packages with <literal>dpkg "
"--remove</literal>.  Please make a note which packages you remove, so that "
"you can install substitute packages later on.  Before continuing with the "
"upgrade, all files in <filename>/usr/X11R6/bin</filename> need to be "
"removed."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:340
msgid ""
"Please read <ulink url=\"http://wiki.debian.org/Xorg69To7\"></ulink> for "
"more details and other issues."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:344
msgid ""
"If you experience problems with X.Org after restarting, it might be also "
"worth to restart the font server by running <literal>/etc/init.d/xfs "
"restart</literal>.  This happens due to "
"<filename>/etc/X11/fs/xfs.options</filename> containing a line with "
"<literal>no-restart-on-upgrade</literal>, but the font paths have changed."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:353
msgid "No support for 8-bit displays in many applications"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:355
msgid ""
"After the upgrade to the X.Org and the latest libraries, X terminals which "
"can only represent colors 8 bits depth will not work.  This is because the "
"Cairo 2D vector graphics library (<systemitem "
"role=\"package\">libcairo2</systemitem>)  doesn't have 8-bit pseudocolor "
"support.  This library is used by the GNOME and Xfce desktops as well as by "
"many desktop applications compiled with the Gtk2+ toolkit, such as "
"<systemitem role=\"package\">abiword</systemitem>."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:363
msgid ""
"Known systems that are affected by this include some Sun machines and X "
"terminals from Tektronix, NCD, IBM and SGI, as well as some other remote X "
"windowing systems.  You should configure these terminals to use 16-bit "
"colour, if possible."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:369
msgid ""
"More information is available in Freedesktop's <ulink "
"url=\"https://bugs.freedesktop.org/show_bug.cgi?id=4945\">bug #4945</ulink>."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:375
msgid "Upgrading from exim to exim4"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:377
msgid ""
"One of the packages that has been obsoleted by the &releasename; release is "
"the Mail Transfer Agent (MTA) <systemitem "
"role=\"package\">exim</systemitem>, which has been replaced by the "
"completely new package <systemitem role=\"package\">exim4</systemitem>."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:383
msgid ""
"<command>exim</command> (version 3.xx) has been unmaintained upstream for "
"years, and Debian has dropped support for that version as well.  If you are "
"still using <command>exim</command> 3.xx, please upgrade your <systemitem "
"role=\"package\">exim</systemitem> installation to <systemitem "
"role=\"package\">exim4</systemitem> manually.  Since <systemitem "
"role=\"package\">exim4</systemitem> is already part of &oldreleasename;, you "
"can choose to do the upgrade on your &oldreleasename; system before the "
"upgrade to &releasename;, or after the &releasename; upgrade at your "
"convenience.  Just remember that your old <systemitem "
"role=\"package\">exim</systemitem> package is not going to be upgraded and "
"that it won't get security support after support for &oldreleasename; has "
"been discontinued."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:395
msgid ""
"Note that, depending on your configuration of <systemitem "
"role=\"package\">debconf</systemitem>, you may not be asked any "
"configuration question during installation of <systemitem "
"role=\"package\">exim4</systemitem>.  If no questions are asked, the system "
"will default to a 'local delivery' setup.  Configuration is possible using "
"the command <literal>dpkg-reconfigure exim4-config</literal>."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:403
msgid ""
"The <systemitem role=\"package\">exim4</systemitem> packages in Debian are "
"extensively documented.  The package's home page is <ulink "
"url=\"http://wiki.debian.org/PkgExim4\"></ulink> on the Debian Wiki, and the "
"README file can be found at <ulink "
"url=\"http://pkg-exim4.alioth.debian.org/README/README.Debian.html\"></ulink> "
"and inside the packages as well."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:411
msgid ""
"The README file has a chapter about Packaging, which explains the different "
"package variations we offer, and it has a chapter about Updating from "
"<command>Exim</command> 3, which will help you in doing the actual "
"transition."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:418
msgid "Upgrading apache2"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:420
msgid ""
"Apache has been upgraded to the new version 2.2.  Although this shouldn't "
"impact the average user, there are some potential issues to be aware of."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:424
msgid ""
"<ulink url=\"http://httpd.apache.org/docs/2.2/upgrading.html\"></ulink> "
"contains the upstream changes.  Please read this page, and remember that "
"especially:"
msgstr ""

# type: Content of: <chapter><section><itemizedlist><listitem><para>
#: en/issues.dbk:430
msgid "all modules need to be recompiled"
msgstr ""

# type: Content of: <chapter><section><itemizedlist><listitem><para>
#: en/issues.dbk:435
msgid "authorization modules have been resorted and renamed"
msgstr ""

# type: Content of: <chapter><section><itemizedlist><listitem><para>
#: en/issues.dbk:440
msgid "some configuration options have been renamed"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:445
msgid ""
"Debian-specific changes include that the string SSL is no longer defined, as "
"ssl is now supported by the default package."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:449
msgid ""
"If you are using the experimental ITK MPM (from the <systemitem "
"role=\"package\">apache2-mpm-itk</systemitem> package), the cgi module will "
"not be correctly enabled by default.  To properly enable it, you will need "
"to manually disable <literal>mod_cgid</literal> and enable "
"<literal>mod_cgi</literal>:"
msgstr ""

# type: Content of: <chapter><section><screen>
#: en/issues.dbk:455
#, no-wrap
msgid ""
"\n"
"# cd /etc/apache2/mods-enabled\n"
"# rm cgid.conf cgid.load\n"
"# ln -s ../mods-available/cgi.load .\n"
"# /etc/init.d/apache2 force-reload\n"
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:464
msgid "Upgrading Zope and Plone"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:466
msgid ""
"Zope and all related products have been updated.  Many products were also "
"dropped from the distribution (either because they were obsoleted, or "
"because they are incompatible with the newer Zope, CMF or Plone)."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:471
msgid ""
"Unfortunately there is no easy and guaranteed way to upgrade a complex "
"<command>zope</command> or <command>plone</command> server.  Even though "
"Plone includes a migration tool, experience has shown that automatic "
"migrations can easily fail."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:477
msgid ""
"For this reason, users are recommended to set up their system so they can "
"continue to run the &oldreleasename; installation of Zope/Plone alongside "
"the new &releasename; versions while testing the migration."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:482
msgid ""
"The easiest and safest way to achieve this, is to make a copy of your "
"&oldreleasename; system to another hard disk or partition, and then upgrade "
"only one of the two copies.  You can then use <command>chroot</command> to "
"run the &oldreleasename; version in parallel to the &releasename; version."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:488
msgid ""
"It is not possible to have the old and new versions of Zope/Plone installed "
"together on an &releasename; system, partly because the old packages depend "
"on <systemitem role=\"package\">python2.3</systemitem> which cannot be "
"installed together with <systemitem role=\"package\">python2.4</systemitem>."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:496
msgid "Wildcard expansion (globbing) with GNU tar"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:498
msgid ""
"Previous versions of GNU <command>tar</command> assumed shell-style globbing "
"when extracting files from or listing an archive.  For example:"
msgstr ""

# type: Content of: <chapter><section><screen>
#: en/issues.dbk:501
#, no-wrap
msgid ""
"\n"
"tar xf foo.tar '*.c'\n"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:505
msgid ""
"would extract all files whose names end in '.c'.  This behavior was not "
"documented and was incompatible with traditional <command>tar</command> "
"implementations.  Therefore, starting from version 1.15.91, GNU "
"<command>tar</command> no longer uses globbing by default.  For example, the "
"above invocation is now interpreted as a request to extract from the archive "
"the file named '*.c'."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:513
msgid "See <filename>/usr/share/doc/tar/NEWS.gz</filename> for further information."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:518
msgid "NIS and Network Manager"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:520
msgid ""
"The version of <command>ypbind</command> included with <systemitem "
"role=\"package\">nis</systemitem> for &releasename; contains support for "
"Network Manager.  This support causes <command>ypbind</command> to disable "
"NIS client functionality when Network Manager reports that the computer is "
"disconnected from the network.  Since Network Manager will usually report "
"that the computer is disconnected when it is not in use, NIS users with NIS "
"client systems should ensure that Network Manager support is disabled on "
"those systems."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:529
msgid ""
"This can be done by either uninstalling the <systemitem "
"role=\"package\">network-manager</systemitem> package, or editing "
"<filename>/etc/default/nis</filename> to add <literal>-no-dbus</literal> to "
"<literal>YPBINDARGS</literal>."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:535
msgid ""
"The use of <literal>-no-dbus</literal> is the default for new installs of "
"Debian, but was not the default in previous releases."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:541
msgid "Deprecated insecure php configurations"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:543
msgid ""
"For many years, turning on the <literal>register_globals</literal> settings "
"in PHP has been known to be insecure and dangerous, and this option has "
"defaulted to off for some time now.  This configuration is now finally "
"deprecated on Debian systems as too dangerous.  The same applies to flaws in "
"<literal>safe_mode</literal> and <literal>open_basedir</literal>, which have "
"also been unmaintained for some time."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:551
msgid ""
"Starting with this release, the Debian security team does not provide "
"security support for a number of PHP configurations which are known to be "
"insecure.  Most importantly, issues resulting from "
"<literal>register_globals</literal> being turned on will no longer be "
"addressed."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:557
msgid ""
"If you run legacy applications that require "
"<literal>register_globals</literal>, enable it for the respective paths "
"only, e.g.  through the Apache configuration file.  More information is "
"available in the <filename>README.Debian.security</filename> file in the PHP "
"documentation directory (<filename>/usr/share/doc/php4</filename>, "
"<filename>/usr/share/doc/php5</filename>)."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:567
msgid "Security status of Mozilla products"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:569
msgid ""
"The Mozilla programs <systemitem role=\"package\">firefox</systemitem> and "
"<systemitem role=\"package\">thunderbird</systemitem> (rebranded in Debian "
"to <systemitem role=\"package\">iceweasel</systemitem> and <systemitem "
"role=\"package\">icedove</systemitem>, respectively), are important tools "
"for many users.  Unfortunately the upstream security policy is to urge users "
"to update to new upstream versions, which conflicts with Debian's policy of "
"not shipping large functional changes in security updates.  We cannot "
"predict it today, but during the lifetime of &releasename; the Debian "
"Security Team may come to a point where supporting Mozilla products is no "
"longer feasible and announce the end of security support for Mozilla "
"products.  You should take this into account when deploying Mozilla and "
"consider alternatives available in Debian if the absence of security support "
"would pose a problem for you."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:585
msgid "KDE desktop"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:587
msgid ""
"KDE media handling has changed in the version available in &releasename; "
"from using <filename>device:/</filename> to <filename>media:/</filename>.  "
"Some user configuration files might have stored "
"<filename>device:/</filename> links in them which should be adapted.  "
"Notably, "
"<filename>~/.kde/share/apps/konqsidebartng/virtual_folders/services</filename> "
"contains this reference and can be safely deleted as it will not be created "
"when setting up new users."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:596
msgid ""
"There have been many changes in the KDE desktop environment from the version "
"shipped in &oldreleasename; to the version in &releasename;, you can find "
"more information in the <ulink "
"url=\"http://www.kde.org/announcements/announce-3.5.php\">KDE 3.5 Release "
"Notes</ulink>."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:604
msgid "GNOME desktop changes and support"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:606
msgid ""
"If you used the GNOME desktop in &oldreleasename; you will not benefit from "
"some of the changes introduced in the default configuration in Debian for "
"&releasename;.  In some extreme cases the GNOME desktop might not properly "
"handle your old configuration and might not behave properly."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:612
msgid ""
"If you have not heavily invested in configuring your GNOME desktop you might "
"want to move the <filename>.gconf</filename> directory in user's home "
"directories to a different name (such as <filename>.gconf.old</filename>) so "
"that it gets recreated, with the default configuration for &releasename;, "
"upon starting a new session."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:619
msgid ""
"With the release of &releasename;, Debian no longer contains packages for "
"most of the obsolete version 1 release of GNOME, although some packages "
"remain in order to support some Debian packages which have not yet been "
"updated to GNOME 2.  Packages for GTK1.2 remain fully maintained."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:625
msgid ""
"There have been many changes in the GNOME desktop environment from the "
"version shipped in &oldreleasename; to the version in &releasename;, you can "
"find more information in the <ulink "
"url=\"http://www.gnome.org/start/2.14/notes/en/\">GNOME 2.14 Release "
"Notes</ulink>."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:633
msgid "Default editor"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:635
msgid ""
"If you were using <command>vim</command> as your default editor, this may be "
"changed to <command>nano</command> during the upgrade."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:639
msgid ""
"Administrators who wish to change the default editor for all users will have "
"to update the alternatives system using:"
msgstr ""

# type: Content of: <chapter><section><screen>
#: en/issues.dbk:642
#, no-wrap
msgid ""
"\n"
"# update-alternatives --config editor\n"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:646
msgid ""
"Users wishing to change the default editor can define the environment "
"variable <emphasis>EDITOR</emphasis> by introducing the following lines in "
"their own profiles:"
msgstr ""

# type: Content of: <chapter><section><screen>
#: en/issues.dbk:650
#, no-wrap
msgid ""
"\n"
"EDITOR=vi\n"
"export EDITOR\n"
"alias editor=$EDITOR\n"
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:658
msgid "Message of the day"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:660
msgid ""
"<filename>/etc/motd</filename> is now a symlink to "
"<filename>/var/run/motd</filename> which is rebuilt by "
"<command>/etc/init.d/bootmisc.sh</command> from a template, "
"<command>/etc/motd.tail</command>, at each reboot.  It means that changes "
"made to <filename>/etc/motd</filename> will be lost.  Changes made into "
"<filename>/etc/motd.tail</filename> are not automatically applied to "
"<filename>/etc/motd</filename> other than at reboot."
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:669
msgid ""
"Also, the EDITMOTD variable at <filename>/etc/default/rcS</filename> no "
"longer has any effect.  If you wish to disable updating of the motd, or want "
"to maintain your own content for the message of the day you just have to "
"point the <filename>/etc/motd</filename> symlink to a different file such as "
"<filename>/etc/motd.static</filename> and make your changes there."
msgstr ""

# type: Content of: <chapter><section><title>
#: en/issues.dbk:678
msgid "Not default support for unicode in emacs21*"
msgstr ""

# type: Content of: <chapter><section><para>
#: en/issues.dbk:680
msgid ""
"Emacs21 and emacs21-nox are not configured to use Unicode by default.  For "
"more information and a workaround please see <ulink "
"url=\"http://bugs.debian.org/419490\">Bug #419490</ulink>."
msgstr ""