Aquí va, a quien pueda dar una revisión, muchas gracias. -- http://igor.tamarapatino.org
# issues.po translation to spanish # Copyright (C) 2009-2021 Free Software Foundation, Inc. # This file is distributed under the same license as the release-notes. # # Copyright (C) Translators and reviewers (see below) of the Debian Spanish # translation team # - Translators: # Ricardo Cárdenes Medina # Juan Manuel García Molina # Javier Fernández-Sanguino Peña <[email protected]> # David Martínez Moreno # Fernando González de Requena <[email protected]>, 2009 # - Reviewers: # Martín Ferrari, 2007 # Laura Arjona, 2013 # Javier <[email protected]>, 2019 # Changes: # - Updated for lenny # Javier Fernández-Sanguino Peña, 2009 # - Updated for Squeeze # Javier Fernández-Sanguino Peña, 2011 # - Updated for Wheezy # Javier Fernández-Sanguino Peña, 2013 # - Updated for Jessie # Javier Fernández-Sanguino Peña, 2015 # - Updated for Stretch # Javier Fernández-Sanguino Peña, 2017 # - Updated for Buster # Javier Fernández-Sanguino Peña, 2019 # - Updated for Bullseye # Javier Fernández-Sanguino Peña, 2021 # Traductores, si no conoce el formato PO, merece la pena leer la # documentación de gettext, especialmente las secciones dedicadas a este # formato, por ejemplo ejecutando: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # Equipo de traducción al español, por favor lean antes de traducir # los siguientes documentos: # - El proyecto de traducción de Debian al español # http://www.debian.org/intl/spanish/ # especialmente las notas y normas de traducción en # http://www.debian.org/intl/spanish/notas # - La guía de traducción de po's de debconf: # /usr/share/doc/po-debconf/README-trans # o http://www.debian.org/intl/l10n/po-debconf/README-trans msgid "" msgstr "" "Project-Id-Version: release-notes 6.0\n" "Report-Msgid-Bugs-To: EMAIL@ADDRESS\n" "POT-Creation-Date: 2025-05-31 17:18+0200\n" "PO-Revision-Date: 2021-08-16 23:52+0200\n" "Last-Translator: YOUR NAME <E-MAIL@ADDRESS>\n" "Language: es\n" "Language-Team: Debian l10n Spanish <[email protected]>" "\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Generated-By: Babel 2.10.3\n"
#: ../issues.rst:4 msgid "Issues to be aware of for |RELEASENAME|" msgstr "Problemas que debe tener en cuenta para |RELEASENAME|" #: ../issues.rst:6 msgid "" "Sometimes, changes introduced in a new release have side-effects we " "cannot reasonably avoid, or they expose bugs somewhere else. This section" " documents issues we are aware of. Please also read the errata, the " "relevant packages' documentation, bug reports, and other information " "mentioned in :ref:`morereading`." msgstr "" "Algunas veces los cambios tienen efectos colaterales que no podemos " "evitar, o aparecen fallos en otro lugar. A continuación documentamos los" " problemas que conocemos. Puede leer también la fe de erratas, la " "documentación de los paquetes relevantes, los informes de fallos y otra " "información mencionada en :ref:`morereading`." #: ../issues.rst:15 msgid "Upgrade specific items for |RELEASENAME|" msgstr "Actualizar elementos específicos para |RELEASENAME|" #: ../issues.rst:17 msgid "" "This section covers items related to the upgrade from |OLDRELEASENAME| to" " |RELEASENAME|." msgstr "" "Esta sección cubre los elementos relacionados con la actualización de " "|OLDRELEASENAME| a |RELEASENAME|." #: ../issues.rst:22 msgid "" "From trixie, i386 is no longer supported as a regular architecture: there" " is no official kernel and no Debian installer for i386 systems. Fewer " "packages are available for i386 because many projects no longer support " "it. The architecture's sole remaining purpose is to support running " "legacy code, for example, by way of `multiarch " "<https://wiki.debian.org/Multiarch/HOWTO>`__ or a chroot." msgstr "" "Comenzando con trixie, i386 dejó de ser una arquitectura soportada: no hay" " un kernel oficial y no hay instalador de Debian para sistemas i386. " "Hay menos paquetes disponibles para i386 porque muchos proyectos ya " "no lo soportan. La única finalidad de la arquitectura es poder " "ejecutar legacy code, (N. del T. código heredado), por ejemplo, " "mediante `multiarch <https://wiki.debian.org/Multiarch/HOWTO>`__ o " "un chroot." #: ../issues.rst:29 msgid "" "Users running i386 systems should not upgrade to trixie. Instead, Debian " "recommends either reinstalling them as amd64, where possible, or retiring" " the hardware. `Cross-grading <https://wiki.debian.org/CrossGrading>`__ " "without a reinstall is a technically possible, but risky, alternative." msgstr "" "Los usuarios que ejecutan sistemas i386 no deben actualizar a trixie. " "En su lugar, Debian recomienda reinstalarlos como amd64, donde sea " "posible, o dejar de usar del hardware. Hacer `Cross-grading " "<https://wiki.debian.org/CrossGrading>`__ sin reinstalar es una " "alternativa técnica, aunque riesgosa." #: ../issues.rst:38 msgid "openssh-server no longer reads ~/.pam_environment" msgstr "openssh-server ya no lee ~/.pam_environment" #: ../issues.rst:40 msgid "" "The Secure Shell (SSH) daemon provided in the **openssh-server** package," " which allows logins from remote systems, no longer reads the user's " "``~/.pam_environment`` file by default; this feature has a `history of " "security problems <https://bugs.debian.org/1030119>`__ and has been " "deprecated in current versions of the Pluggable Authentication Modules " "(PAM) library. If you used this feature, you should switch from setting " "variables in ``~/.pam_environment`` to setting them in your shell " "initialization files (e.g. ``~/.bash_profile`` or ``~/.bashrc``) or some " "other similar mechanism instead." msgstr "" "El servicio SSH proporcionado en el paquete **openssh-server**, que " "permite iniciar sesiones desde sistemas remotos, ya no lee de forma " "predeterminada el archivo de usuario ``~/.pam_environment``; esta " "característica tiene un " "`historial de problemas de seguridad <https://bugs.debian.org/1030119>`__ " "y fue descontinuada en versiones actuales de la biblioteca de " "Pluggable Authentication Modules(N. del T. módulos de autenticación " "conectable) (PAM). Si usaba esta característica, debería mover la " "configuración de las variables de ``~/.pam_environment`` hacia " "sus archivos de inicio de sesión (p. ej. ``~/.bash_profile`` o " "``~/.bashrc``) o algún otro mecanismo similar." #: ../issues.rst:50 msgid "" "Existing SSH connections will not be affected, but new connections may " "behave differently after the upgrade. If you are upgrading remotely, it " "is normally a good idea to ensure that you have some other way to log " "into the system before starting the upgrade; see :ref:`recovery`." msgstr "" "Las conexiones SSH existentes no se verán afectadas, pero las nuevas " "conexiones pueden comportarse de manera diferente después de la " "actualización. Si está actualizando de forma remota, es bueno contar con " " alguna otra forma de iniciar sesión en el sistema antes de " "iniciar la actualización; más información en :ref:`recovery`." #: ../issues.rst:59 msgid "OpenSSH no longer supports DSA keys" msgstr "OpenSSH ya no soporta llaves DSA" #: ../issues.rst:61 msgid "" "Digital Signature Algorithm (DSA) keys, as specified in the Secure Shell " "(SSH) protocol, are inherently weak: they are limited to 160-bit private " "keys and the SHA-1 digest. The SSH implementation provided by the " "**openssh-client** and **openssh-server** packages has disabled support " "for DSA keys by default since OpenSSH 7.0p1 in 2015, released with Debian" " 9 (\"stretch\"), although it could still be enabled using the " "``HostKeyAlgorithms`` and ``PubkeyAcceptedAlgorithms`` configuration " "options for host and user keys respectively." msgstr "" "Las llaves de algoritmo de firma digital (DSA), como se especifica en el " "protocolo de seguridad SSH, son inherentemente débiles: se limitan a " "claves privadas de 160 bits y el resumen SHA-1. La implementación SSH " "proporcionada por los paquetes **openssh-client** y **openssh-server** " "ha deshabilitado el soporte para las llaves DSA de forma predeterminada " "desde OpenSSH 7.0p1 en 2015, lanzado con Debian 9 (\"stretch\"), aunque " "aún podría habilitarse utilizando las opciones de configuración " "``HostKeyAlgorithms`` y ``PubkeyAcceptedAlgorithms`` para las claves de " "máquina y usuario respectivamente." #: ../issues.rst:70 msgid "" "The only remaining uses of DSA at this point should be connecting to some" " very old devices. For all other purposes, the other key types supported" " by OpenSSH (RSA, ECDSA, and Ed25519) are superior." msgstr "" "Los únicos usos de DSA en este momento deberían ser conectarse a algunos " "dispositivos muy antiguos. Para todos los demás propósitos, los otros " "tipos de claves soportados por OpenSSH (RSA, ECDSA y Ed25519) son " "mejores." #: ../issues.rst:74 msgid "" "As of OpenSSH 9.8p1 in trixie, DSA keys are no longer supported even with" " the above configuration options. If you have a device that you can only" " connect to using DSA, then you can use the ``ssh1`` command provided by " "the **openssh-client-ssh1** package to do so." msgstr "" "Desde OpenSSH 9.8p1 en trixie, las llaves DSA ya no se soportan incluso " "con las opciones de configuración descritas anteriormente. Si tiene un " "dispositivo que solo puede conectarse usando DSA, puede usar la orden " "``ssh1`` proporcionada por el paquete **openssh-client-ssh1** para hacerlo." #: ../issues.rst:79 msgid "" "In the unlikely event that you are still using DSA keys to connect to a " "Debian server (if you are unsure, you can check by adding the ``-v`` " "option to the ``ssh`` command line you use to connect to that server and " "looking for the \"Server accepts key:\" line), then you must generate " "replacement keys before upgrading. For example, to generate a new " "Ed25519 key and enable logins to a server using it, run this on the " "client, replacing ``username@server`` with the appropriate user and host " "names:" msgstr "" "En el improbable caso de que siga usando llaves DSA para conectarse a un " "servidor Debian (si no está seguro, puede comprobar añadiendo la opción " "``-v`` a la línea de órdenes ``ssh`` que usa para conectarse a ese " "servidor y buscar la línea \"Server accepts key:\"), debe generar " "nuevas llaves para sustituirlas antes de actualizar. Por ejemplo, para " "generar una nueva llave Ed25519 y habilitar inicios en un servidor que " "la utilice, ejecute esto en el cliente, reemplazando ``username@server`` " "con el nombre de usuario y de máquina apropiados:" #: ../issues.rst:96 msgid "RabbitMQ no longer supports HA queues" msgstr "RabbitMQ ya no soporta colas HA" #: ../issues.rst:98 msgid "" "High-availability (HA) queues are no longer supported by **rabbitmq-" "server** starting in trixie. To continue with an HA setup, these queues " "need to be switched to \"quorum queues\"." msgstr "" "**rabbitmq-server** en trixie ya no soporta colas de alta disponibilidad. " "Para continuar con una configuración HA, debe cambiarse estas colas a " "\"colas quórum\"." #: ../issues.rst:102 msgid "" "If you have an OpenStack deployment, please switch the queues to quorum " "before upgrading. Please also note that beginning with OpenStack's " "\"Caracal\" release in trixie, OpenStack supports only quorum queues." msgstr "" "Si tiene una implementación de OpenStack, cambie las colas a quórum " "antes de actualizar. También tenga en cuenta que comenzando con la " "publicación de la versión \"Caracal\" en trixie, OpenStack solo soporta " "colas de quórum." #: ../issues.rst:110 msgid "RabbitMQ cannot be directly upgraded from bookworm" msgstr "RabbitMQ ya no se puede actualizar directamente desde bookworm" #: ../issues.rst:112 msgid "" "There is no direct, easy upgrade path for RabbitMQ from bookworm to " "trixie. Details about this issue can be found in `bug 1100165 " "<https://bugs.debian.org/1100165>`__." msgstr "" "No hay un camino de actualización directo y fácil para RabbitMQ desde " "trixie. Puede encontrar más detalles sobre este problema en " "`bug 1100165 <https://bugs.debian.org/1100165>`__." #: ../issues.rst:115 msgid "" "The recommended upgrade path is to completely wipe the rabbitmq database " "and restart the service (after the trixie upgrade). This may be done by " "deleting ``/var/lib/rabbitmq/mnesia`` and all of its contents." msgstr "" "La vía recomendada de actualización es borrar completamente la base de " "datos de rabbitmq y reiniciar el servicio (después de la actualización de " "trixie). Esto puede hacerlo borrando ``/var/lib/rabbitmq/mnesia`` y " "todo su contenido." #: ../issues.rst:123 msgid "Ping no longer runs with elevated privileges" msgstr "Ping ya no se ejecuta con privilegios elevados" #: ../issues.rst:125 msgid "" "Ping is no longer installed with access to the `CAP_NET_RAW` linux " "capability, but instead uses ``ICMP_PROTO`` datagram sockets for network " "communication. Access to these sockets is controlled based on the user's" " Unix group membership using the ``net.ipv4.ping_group_range`` sysctl. " "In normal installations, the **linux-sysctl-defaults** package will set " "this value to a broadly permissive value, allowing unprivileged users to " "use ping as expected, but some upgrade scenarios may not automatically " "install this package. See ``/usr/lib/sysctl.d/50-default.conf`` and `the " "kernel documentation <https://docs.kernel.org/networking/ip-sysctl.html"; "#ip-sysctl>__` for more information on the semantics of this variable." msgstr "" "Ping ya no se instala con acceso a facultad `CAP_NET_RAW` de linux, " "ahora usa los datagramas ``ICMP_PROTO`` para comunicarse en red. El " "acceso a estos sockets se controla en función de la pertenencia al " "grupo de usuarios Unix con sysctl ``net.ipv4.ping_group_range``. " "En instalaciones normales, el paquete **linux-sysctl-defaults** " "establecerá este valor a un valor ampliamente permisivo, permitiendo a " "los usuarios no privilegiados usar ping como se espera, pero algunos " "escenarios de actualización pueden no instalar automáticamente este " "paquete. Consulte ``/usr/lib/sysctl.d/50-default.conf`` y `la " "documentación del kernel <https://docs.kernel.org/networking/ip-"; "sysctl.html#ip-sysctl>`__ para obtener más información sobre la " "semántica de esta variable." #: ../issues.rst:142 msgid "Things to do post upgrade before rebooting" msgstr "Cosas a hacer después de la actualización y antes de reiniciar" #: ../issues.rst:144 msgid "" "When ``apt full-upgrade`` has finished, the \"formal\" upgrade is " "complete. For the upgrade to |RELEASENAME|, there are no special actions " "needed before performing a reboot." msgstr "" "Cuando haya terminado ``apt full-upgrade`` la actualización \"formal\" se" " habrá completado. No hay que hacer ninguna acción especial antes del " "siguiente reinicio del sistema tras la actualización a |RELEASENAME|." #: ../issues.rst:150 msgid "" "When ``apt full-upgrade`` has finished, the \"formal\" upgrade is " "complete, but there are some other things that should be taken care of " "*before* the next reboot." msgstr "" "Cuando haya terminado ``apt full-upgrade`` la actualización \"formal\" se" " habrá completado, pero hay ciertas cosas que deberá hacer *antes* del " "siguiente reinicio del sistema." #: ../issues.rst:163 msgid "Items not limited to the upgrade process" msgstr "Elementos no limitados durante el proceso de actualización" #: ../issues.rst:168 msgid "Limitations in security support" msgstr "Limitaciones en el soporte de seguridad" #: ../issues.rst:170 msgid "" "There are some packages where Debian cannot promise to provide minimal " "backports for security issues. These are covered in the following " "subsections." msgstr "" "Hay algunos paquetes para los que Debian no puede comprometerse a " "proporcionar versiones actualizadas resolviendo problemas de seguridad. " "La información de estos paquetes se cubre en las siguientes subsecciones." #: ../issues.rst:176 msgid "" "The package **debian-security-support** helps to track the security " "support status of installed packages." msgstr "" "El paquete **debian-security-support** ayuda a supervisar el estado de " "soporte de seguridad de los paquetes instalados en el sistema." #: ../issues.rst:182 msgid "Security status of web browsers and their rendering engines" msgstr "Estado de seguridad en los navegadores web y sus motores de render" #: ../issues.rst:184 msgid "" "Debian |RELEASE| includes several browser engines which are affected by a" " steady stream of security vulnerabilities. The high rate of " "vulnerabilities and partial lack of upstream support in the form of long " "term branches make it very difficult to support these browsers and " "engines with backported security fixes. Additionally, library " "interdependencies make it extremely difficult to update to newer upstream" " releases. Applications using the **webkit2gtk** source package (e.g. " "**epiphany**) are covered by security support, but applications using " "qtwebkit (source package **qtwebkit-opensource-src**) are not." msgstr "" "Debian |RELEASE| incluye varios motores de navegador que están afectados" " por un flujo continuo de vulnerabilidades de seguridad. La alta " "tasa de vulnerabilidades y la falta parcial de soporte de los paquetes " "originarios en forma de ramas de largo plazo hacen que sea muy difícil " "soportar estos navegadores y motores con correcciones de seguridad a los " "paquetes del sistema. Además, las interdependencias de las bibliotecas " "hacen que sea muy difícil actualizar a las versiones más recientes de " "los paquetes de origen. Las aplicaciones que utilizan el paquete fuente " "**webkit2gtk** (p. ej. **epiphany**) están cubiertos por soporte " "de seguridad, pero las aplicaciones que utilizan el paquete de qtwebkit " "(paquete fuente **qtwebkit-opensource-src**) no lo están." #: ../issues.rst:194 msgid "" "For general web browser use we recommend Firefox or Chromium. They will " "be kept up-to-date by rebuilding the current ESR releases for stable. The" " same strategy will be applied for Thunderbird." msgstr "" "Para la navegación web general se recomienda utilizar Firefox o Chromium." " Se mantendrán actualizadas recompilando las versiones ESR más recientes " "para estable. La misma estrategia se aplicará a Thunderbird." #: ../issues.rst:198 msgid "" "Once a release becomes ``oldstable``, officially supported browsers may " "not continue to receive updates for the standard period of coverage. For " "example, Chromium will only receive 6 months of security support in " "``oldstable`` rather than the typical 12 months." msgstr "" "Cuando una versión se convierte en ``oldstable``, los navegadores " "oficialmente soportados pueden no seguir recibiendo actualizaciones " "durante el período de cobertura estándar. Por ejemplo, Chromium solo " "recibirá 6 meses de soporte de seguridad en ``oldstable``, en lugar de " "los 12 meses típicos." #: ../issues.rst:206 msgid "Go- and Rust-based packages" msgstr "Paquetes basados en Go y Rust" #: ../issues.rst:208 msgid "" "The Debian infrastructure currently has problems with rebuilding packages" " of types that systematically use static linking. With the growth of the " "Go and Rust ecosystems it means that these packages will be covered by " "limited security support until the infrastructure is improved to deal " "with them maintainably." msgstr "" "La infraestructura de Debian en este momento tiene problemas para " "reconstruir paquetes que utilizan enlace estático de manera " "sistemática. Con el crecimiento del ecosistema de Go y Rust, esto significa " "que estos paquetes serán cubiertos por soporte limitado de seguridad hasta " "que la infraestructura se haya mejorado para manejarlos de manera " "mantenible." #: ../issues.rst:214 msgid "" "In most cases if updates are warranted for Go or Rust development " "libraries, they will only be released via regular point releases." msgstr "" "En la mayoría de de los casos, si se garantizan actualizaciones para las " "bibliotecas de desarrollo de Go o Rust, solo se liberarán mediante versiones" " cada cierto tiempo." #: ../issues.rst:220 msgid "Obsolescence and deprecation" msgstr "Obsolescencia y deprecación" #: ../issues.rst:225 msgid "Noteworthy obsolete packages" msgstr "Paquetes obsoletos notables" #: ../issues.rst:227 msgid "" "The following is a list of known and noteworthy obsolete packages (see " ":ref:`obsolete` for a description)." msgstr "" "A continuación ofrecemos una lista de los paquetes conocidos y notables " "que ahora están obsoletos (consulte :ref:`obsolete` para obtener una " "descripción)." #: ../issues.rst:230 msgid "The list of obsolete packages includes:" msgstr "La lista de paquetes obsoletos incluye:" #: ../issues.rst:232 msgid "" "The **libnss-gw-name** package has been removed from |RELEASENAME|. The " "upstream developer suggests using **libnss-myhostname** instead." msgstr "" "El paquete **libnss-gw-name** se eliminó de |RELEASENAME|. El " "desarrollador originario sugiere usar **libnss-myhostname** en su lugar." #: ../issues.rst:235 msgid "" "The **pcregrep** package has been removed from |RELEASENAME|. It can be " "replaced with ``grep -P`` (``--perl-regexp``) or ``pcre2grep`` (from " "**pcre2-utils**)." msgstr "" "El paquete **pcregrep** se eliminó de |RELEASENAME|. Puede reemplazarse " "con ``grep -P`` (``--perl-regexp``) o ``pcre2grep`` (from " "**pcre2-utils**)." #: ../issues.rst:242 msgid "Deprecated components for |RELEASENAME|" msgstr "Componentes obsoletos de |RELEASENAME|" #: ../issues.rst:244 msgid "" "With the next release of Debian |NEXTRELEASE| (codenamed " "|NEXTRELEASENAME|) some features will be deprecated. Users will need to " "migrate to other alternatives to prevent trouble when updating to Debian " "|NEXTRELEASE|." msgstr "" "Con la publicación de Debian |NEXTRELEASE| (nombre en clave " "|NEXTRELEASENAME|) algunas funcionalidades estarán obsoletas. Los " "usuarios deben migrar a otras alternativas para evitar problemas al " "actualizar a Debian |NEXTRELEASE|." #: ../issues.rst:248 msgid "This includes the following features:" msgstr "Esto incluye las siguientes funcionalidades:" #: ../issues.rst:250 msgid "" "The **libnss-docker** package is no longer developed upstream and " "requires version 1.21 of the Docker API. That deprecated API version is " "still supported by Docker Engine v26 (shipped by Debian trixie) but will " "be removed in Docker Engine v27+ (shipped by Debian forky). Unless " "upstream development resumes, the package will be removed in Debian " "forky." msgstr "" "El paquete **libnss-docker** ya no tiene desarrollo y requiere la " "versión 1.21 de la API de Docker. Esta versión de API obsoleta todavía " "está soportada por Docker Engine v26 (distribuida por Debian trixie) " "pero será eliminada en Docker Engine v27+ (distribuida por " "Debian forky). A menos que el desarrollo de la API se restablezca, el " "paquete será eliminado en Debian forky." #: ../issues.rst:257 msgid "" "The **openssh-client** and **openssh-server** packages currently support " "`GSS-API " "<https://en.wikipedia.org/wiki/Generic_Security_Services_Application_Program_Interface>`__" " authentication and key exchange, which is usually used to authenticate " "to `Kerberos <https://en.wikipedia.org/wiki/Kerberos_(protocol)>`__ " "services. This has caused some problems, especially on the server side " "where it adds new pre-authentication attack surface, and Debian's main " "OpenSSH packages will therefore stop supporting it starting with " "|NEXTRELEASENAME|." msgstr "" "Los paquetes **openssh-client** y **openssh-server** actualmente soportan " "autenticación e intercambio de llaves " " `GSS-API <https://en.wikipedia.org/wiki/Generic_Security_Services_Application_Program_Interface>`__ ," " que se usa normalmente para autenticarse ante servicios " "`Kerberos <https://en.wikipedia.org/wiki/Kerberos_(protocol)>`__. Esto " "ha causado algunos problemas, especialmente en el lado del servidor, donde" " añade una nueva superficie de ataque durante la pre-autenticación, y los " "paquetes principales de OpenSSH de Debian dejarán de soportarlos a partir de " "|NEXTRELEASENAME|." #: ../issues.rst:268 #: ../issues.rst:267 msgid "" "If you are using GSS-API authentication or key exchange (look for options" " starting with ``GSSAPI`` in your OpenSSH configuration files) then you " "should install the **openssh-client-gssapi** (on clients) or **openssh-" "server-gssapi** (on servers) package now. On |RELEASENAME|, these are " "empty packages depending on **openssh-client** and **openssh-server** " "respectively; on |NEXTRELEASENAME|, they will be built separately." msgstr "" "Si está usando autenticación o intercambio de llaves GSS-API (buscar opciones" " que comiencen con ``GSSAPI`` en sus archivos de configuración de OpenSSH), " "debe instalar el paquete **openssh-client-gssapi** (en los clientes) o " "**openssh-server-gssapi** (en los servidores) ahora. En |RELEASENAME|, estos " "paquetes están vacíos y dependen de **openssh-client** y **openssh-" "server** respectivamente; en |NEXTRELEASENAME|, se construirán por " "separado." #: ../issues.rst:275 msgid "" "sbuild-debian-developer-setup has been deprecated in favor of " "sbuild+unshare" msgstr "" "sbuild-debian-developer-setup ha sido descontinuado en favor de " "sbuild+unshare" #: ../issues.rst:277 msgid "" "**sbuild**, the tool to build Debian packages in a minimal environment, " "has had a major upgrade and should work out of the box now. As a result " "the package **sbuild-debian-developer-setup** is no longer needed and has" " been deprecated. You can try the new version with:" msgstr "" "**sbuild**, la herramienta para construir paquetes Debian en un " "entorno mínimo, ha tenido una actualización importante y debería " "funcionar ahora mismo. Como resultado, el paquete " "**sbuild-debian-developer-setup** ya no es necesario y ha sido " "descontinuado. Puede probar la nueva versión con:" #: ../issues.rst:290 msgid "No-longer-supported hardware" msgstr "Hardware dejado de soportar" #: ../issues.rst:292 msgid "" "For a number of \\`arch`-based devices that were supported in " "|OLDRELEASENAME|, it is no longer viable for Debian to build the required" " ``Linux`` kernel, due to hardware limitations. The unsupported devices " "are:" msgstr "" "Para una considerable cantidad de dispositivos basdos en arch que " "estaban soportados en |OLDRELEASENAME|, ya no es viable para Debian " "construir el kernel ``Linux``, debido a limitaciones de hardware. Los " "dispositivos no soportados son:" #: ../issues.rst:297 msgid "foo" msgstr "" #: ../issues.rst:299 msgid "" "Users of these platforms who wish to upgrade to |RELEASENAME| " "nevertheless should keep the |OLDRELEASENAME| APT sources enabled. Before" " upgrading they should add an APT preferences file containing:" msgstr "" "Los usuarios de las plataformas que desean actualizar a |RELEASENAME| " "todavía deben mantener los orígenes APT de |OLDRELEASENAME| habilitados. " "Antes de actualizar, deben agregar un archivo de preferencias APT que " "contenga:" #: ../issues.rst:309 msgid "" "The security support for this configuration will only last until " "|OLDRELEASENAME|'s End Of Life." msgstr "" "El soporte de seguridad para esta configuración solo durará hasta que " "finalice la vida útil de |OLDRELEASENAME|." #: ../issues.rst:315 msgid "Known severe bugs" msgstr "Fallos de gravedad conocidos" #: ../issues.rst:317 msgid "" "Although Debian releases when it's ready, that unfortunately doesn't mean" " there are no known bugs. As part of the release process all the bugs of " "severity serious or higher are actively tracked by the Release Team, so " "an `overview of those bugs <https://bugs.debian.org/cgi-"; "bin/[email protected];tag=&releasename" ";-can-defer>`__ that were tagged to be ignored in the last part of " "releasing |RELEASENAME| can be found in the `Debian Bug Tracking System " "<https://bugs.debian.org/>`__. The following bugs were affecting " "|RELEASENAME| at the time of the release and worth mentioning in this " "document:" msgstr "" "A pesar de que Debian libera cuando está listo, no significa que no haya " "fallos conocidos. Como parte del proceso de liberación de Debian, todos " "los fallos de gravedad seria o mayor se rastrean activamente por " "el equipo de liberación, por lo que se puede encontrar una `visualización " "de esos fallos <https://bugs.debian.org/cgi-bin/[email protected];tag=&releasename;-can-defer>`__ " "que se han etiquetado para ignorarse en la última parte de la liberación " "de |RELEASENAME| y que se encuentran en el " "`sistema de seguimiento de fallos de Debian <https://bugs.debian.org/>`__. " "Los fallos que afectaron a |RELEASENAME| en el momento de la " "liberación y que vale la pena mencionar en este documento son:" #: ../issues.rst:328 msgid "Bug number" msgstr "Número de fallo" #: ../issues.rst:328 msgid "Package (source or binary)" msgstr "Paquete (fuente o binario)" #: ../issues.rst:328 msgid "Description" msgstr "Descripción" #: ../issues.rst:331 msgid "`1032240`_" msgstr "`1032240`_" #: ../issues.rst:331 msgid "**akonadi-backend-mysql**" msgstr "**akonadi-backend-mysql**" #: ../issues.rst:331 msgid "akonadi server fails to start since it cannot connect to mysql database" msgstr "" "el servidor akonadi falla al iniciar dado que no puede conectarse a la " "base de datos mysql" #: ../issues.rst:336 msgid "`1032177`_" msgstr "`1032177`_" #: ../issues.rst:336 msgid "**faketime**" msgstr "**faketime**" #: ../issues.rst:336 msgid "faketime doesn't fake time (on i386)" msgstr "faketime no inventa la hora (en i386)" #: ../issues.rst:339 msgid "`918984`_" msgstr "`918984`_" #: ../issues.rst:339 msgid "**src:fuse3**" msgstr "**src:fuse3**" #: ../issues.rst:339 msgid "provide upgrade path fuse -> fuse3 for bookworm" msgstr "provee una ruta de actualización de fuse -> fuse3 para bookworm" #: ../issues.rst:343 msgid "`1016903`_" msgstr "`1016903`_" #: ../issues.rst:343 msgid "**g++-12**" msgstr "**g++-12**" #: ../issues.rst:343 msgid "tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)" msgstr "" "tree-vectorize: Código erróneo a nivel 02 (-fno-tree-vectorize " "está funcionando)" #: ../issues.rst:349 msgid "`1020284`_" msgstr "`1020284`_" #: ../issues.rst:349 ../issues.rst:353 msgid "**git-daemon-run**" msgstr "**git-daemon-run**" #: ../issues.rst:349 msgid "fails to purge: deluser -f: Unknown option: f" msgstr "falla al purgar: deluser -f: Unknown option: f" #: ../issues.rst:353 msgid "`919296`_" msgstr "`919296`_" #: ../issues.rst:353 msgid "" "fails with 'warning: git-daemon: unable to open supervise/ok: file does " "not exist'" msgstr "" "falla con 'warning: git-daemon: unable to open supervise/ok: file does " "not exist'" #: ../issues.rst:359 msgid "`1034752`_" msgstr "`1034752`_" #: ../issues.rst:359 msgid "**src:gluegen2**" msgstr "**src:gluegen2**" #: ../issues.rst:359 msgid "embeds non-free headers" msgstr "incluye encabezados non-free" #~ msgid "A “merged-``/usr``” is now required" #~ msgstr "" #~ msgid "" #~ "Debian has adopted a filesystem layout," #~ " referred to as “merged-``/usr``”, which" #~ " no longer includes the legacy " #~ "directories ``/bin``, ``/sbin``, ``/lib``, or" #~ " optional variants such as ``/lib64``. " #~ "In the new layout, the legacy " #~ "directories are replaced with symlinks " #~ "to the corresponding locations ``/usr/bin``," #~ " ``/usr/sbin``, ``/usr/lib``, and ``/usr/lib64``." #~ " This means that, for example, both" #~ " ``/bin/bash`` and ``/usr/bin/bash`` will " #~ "launch ``bash``." #~ msgstr "" #~ msgid "" #~ "Systems that rely on a “base " #~ "layer” that is not directly writable " #~ "(such as `WSL1 " #~ "<https://wiki.debian.org/InstallingDebianOn/Microsoft/Windows/SubsystemForLinux>`__" #~ " images or container systems using " #~ "multi-layer `overlayfs " #~ "<https://en.wikipedia.org/wiki/OverlayFS>`__ filesystems) " #~ "cannot be safely converted and should" #~ " either be replaced (e.g., by " #~ "installing a new WSL1 image from " #~ "the store) or have each individual " #~ "layer upgraded (e.g., by upgrading the" #~ " base Debian layer of the overlayfs" #~ " independently) rather than dist-upgraded." #~ msgstr "" #~ msgid "" #~ "For further information, see `The Case" #~ " for the /usr merge " #~ "<https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/>`__" #~ " and `the Debian Technical Committee " #~ "resolution <&url-bts;994388#110>`__." #~ msgstr "" #~ msgid "" #~ "Debian |RELEASE| includes several browser " #~ "engines which are affected by a " #~ "steady stream of security vulnerabilities. " #~ "The high rate of vulnerabilities and " #~ "partial lack of upstream support in " #~ "the form of long term branches " #~ "make it very difficult to support " #~ "these browsers and engines with " #~ "backported security fixes. Additionally, " #~ "library interdependencies make it extremely" #~ " difficult to update to newer " #~ "upstream releases. Applications using the " #~ "**webkit2gtk** source package (e.g. epiphany)" #~ " are covered by security support, but" #~ " applications using qtwebkit (source " #~ "package **qtwebkit-opensource-src**) are " #~ "not." #~ msgstr "" #~ msgid "" #~ "``dash``, which by default provides the" #~ " system shell ``/bin/sh`` in Debian, " #~ "has switched to treating the circumflex" #~ " (``^``) as a literal character, as" #~ " was always the intended POSIX-" #~ "compliant behavior. This means that in" #~ " bookworm ``[^0-9]`` no longer means " #~ "“not 0 to 9” but “0 to 9 " #~ "and ``^``”." #~ msgstr "" #~ msgid "Non-free firmware moved to its own component in the archive" #~ msgstr "" #~ msgid "" #~ "As described in :ref:`archive-areas`, " #~ "non-free firmware packages are now " #~ "served from a dedicated archive " #~ "component, called ``non-free-firmware``. " #~ "To ensure installed non-free firmware" #~ " packages receive proper upgrades, changes" #~ " to the APT configuration are " #~ "required. Assuming the ``non-free`` " #~ "component was only added to the " #~ "APT sources-list to install firmware," #~ " the updated APT source-list entry" #~ " could look like:" #~ msgstr "" #~ msgid "" #~ "If you were pointed to this " #~ "chapter by ``apt`` you can prevent " #~ "it from continuously notifying you about" #~ " this change by creating an :url-" #~ "man-stable:`apt.conf(5)` file named " #~ "``/etc/apt/apt.conf.d/no-bookworm-firmware.conf`` " #~ "with the following content:" #~ msgstr "" #~ msgid "Changes to packages that set the system clock" #~ msgstr "" #~ msgid "" #~ "The **ntp** package, which used to " #~ "be the default way to set the " #~ "system clock from a Network Time " #~ "Protocol (NTP) server, has been replaced" #~ " by **ntpsec**." #~ msgstr "" #~ msgid "" #~ "Most users will not need to take" #~ " any specific action to transition " #~ "from **ntp** to **ntpsec**." #~ msgstr "" #~ msgid "" #~ "In bookworm there are also several " #~ "other packages that provide a similar" #~ " service. The Debian default is now" #~ " **systemd-timesyncd**, which may be " #~ "adequate for users who only need " #~ "an ``ntp`` client to set their " #~ "clock. bookworm also includes **chrony** " #~ "and **openntpd** which support more " #~ "advanced features, such as operating " #~ "your own NTP server." #~ msgstr "" #~ msgid "Puppet configuration management system upgraded to 7" #~ msgstr "" #~ msgid "" #~ "Puppet has been upgraded from 5 to" #~ " 7, skipping the Puppet 6 series " #~ "altogether. This introduces major changes " #~ "to the Puppet ecosystem." #~ msgstr "" #~ msgid "" #~ "The classic Ruby-based Puppet Master " #~ "5.5.x application has been deprecated " #~ "upstream and is no longer available " #~ "in Debian. It is replaced by " #~ "Puppet Server 7.x, provided by the " #~ "**puppetserver** package. The package is " #~ "automatically installed as a dependency " #~ "of the transitional **puppet-master** " #~ "package." #~ msgstr "" #~ msgid "" #~ "In some cases, Puppet Server is a" #~ " drop-in replacement for Puppet " #~ "Master, but you should review the " #~ "configuration files available under " #~ "``/etc/puppet/puppetserver`` to ensure the new" #~ " defaults are suitable for your " #~ "deployment. In particular the legacy " #~ "format for the ``auth.conf`` file is " #~ "deprecated, see the `auth.conf documentation" #~ " " #~ "<https://www.puppet.com/docs/puppet/7/server/config_file_auth.html>`__" #~ " for details." #~ msgstr "" #~ msgid "" #~ "The recommended approach is to upgrade" #~ " the server before clients. The " #~ "Puppet 7 Server is `backwards compatible" #~ " with older clients " #~ "<https://www.puppet.com/docs/puppet/7/server/compatibility_with_puppet_agent.html>`__;" #~ " a Puppet 5 Server can still " #~ "handle upgraded agents but cannot " #~ "register new Puppet 7 agents. So " #~ "if you deploy new Puppet 7 agents" #~ " before upgrading the server, you " #~ "will not be able to add them " #~ "to the fleet." #~ msgstr "" #~ msgid "" #~ "The **puppet** package has been replaced" #~ " by the **puppet-agent** package and" #~ " is now a transitional package to " #~ "ensure a smooth upgrade." #~ msgstr "" #~ msgid "" #~ "Finally, the **puppetdb** package was " #~ "removed in bullseye but is reintroduced" #~ " in bookworm." #~ msgstr "" #~ msgid "youtube-dl replaced with yt-dlp" #~ msgstr "" #~ msgid "" #~ "The popular tool **youtube-dl**, which" #~ " can download videos from a large " #~ "variety of websites (including, but not" #~ " limited to, YouTube) is no longer" #~ " included in Debian. Instead, it has" #~ " been replaced with an empty " #~ "transitional package that pulls in the" #~ " **yt-dlp** package instead. **yt-" #~ "dlp** is a fork of **youtube-dl**" #~ " where new development is currently " #~ "happening." #~ msgstr "" #~ msgid "" #~ "There are no compatibility wrappers " #~ "provided, so you'll need to modify " #~ "your scripts and personal behavior to" #~ " call ``yt-dlp`` instead of " #~ "``youtube-dl``. The functionality should be" #~ " mostly the same, although some " #~ "options and behavioral details have " #~ "changed. Be sure to check :url-" #~ "man-stable:`yt-dlp.1` for details, and " #~ "in particular :url-man-stable:`yt-" #~ "dlp.1.html#Differences_in_default_behavior`." #~ msgstr "" #~ msgid "Fcitx versions no longer co-installable" #~ msgstr "" #~ msgid "" #~ "The packages **fcitx** and **fcitx5** " #~ "provide version 4 and version 5 of" #~ " the popular Fcitx Input Method " #~ "Framework. Following upstream's recommendation, " #~ "they can no longer be co-installed" #~ " on the same operating system. Users" #~ " should determine which version of " #~ "Fcitx is to be kept if they " #~ "had co-installed **fcitx** and " #~ "**fcitx5** previously." #~ msgstr "" #~ msgid "" #~ "Before the upgrade, users are strongly" #~ " encouraged to purge all related " #~ "packages for the unwanted Fcitx version" #~ " (``fcitx-*`` for Fcitx 4, and " #~ "``fcitx5-*`` for Fcitx 5). When the " #~ "upgrade is finished, consider executing " #~ "the ``im-config`` again to select " #~ "the desired input method framework to" #~ " be used in the system." #~ msgstr "" #~ msgid "" #~ "You can read more background information" #~ " in `the announcement posted on the" #~ " mailing list <https://lists.debian.org/debian-"; #~ "chinese-gb/2021/12/msg00000.html>`__ (text written " #~ "in Simplified Chinese)." #~ msgstr "" #~ msgid "MariaDB package names no longer include version numbers" #~ msgstr "" #~ msgid "" #~ "Unlike bullseye that had the MariaDB " #~ "version in package names (e.g. " #~ "**mariadb-server-10.5** and **mariadb-" #~ "client-10.5**), in bookworm the equivalent " #~ "MariaDB 10.11 package names are fully" #~ " versionless (e.g. **mariadb-server** or" #~ " **mariadb-client**). The MariaDB version" #~ " is still visible in the package " #~ "version metadata." #~ msgstr "" #~ msgid "" #~ "There is at least one known " #~ "upgrade scenario (`Bug #1035949 " #~ "<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035949>`_)" #~ " where the transition to versionless " #~ "package names fails: running" #~ msgstr "" #~ msgid "" #~ "may fail when **mariadb-client-10.5** " #~ "and the file ``/usr/bin/mariadb-admin`` " #~ "in it is removed before the " #~ "MariaDB server SysV init service has " #~ "issued a shutdown, which uses " #~ "``mariadb-admin``. The workaround is to " #~ "run" #~ msgstr "" #~ msgid "before running" #~ msgstr "" #~ msgid "." #~ msgstr "" #~ msgid "" #~ "For more information about the package" #~ " name changes in MariaDB, see " #~ "`/usr/share/doc/mariadb-server/NEWS.Debian.gz " #~ "<https://salsa.debian.org/mariadb-team/mariadb-"; #~ "server/-/blob/280369f034bedae714af2f26111d1d9d1659f142/debian" #~ "/mariadb-server.NEWS>`__." #~ msgstr "" #~ msgid "Changes to system logging" #~ msgstr "" #~ msgid "" #~ "The **rsyslog** package is no longer " #~ "needed on most systems and you may" #~ " be able to remove it." #~ msgstr "" #~ msgid "" #~ "Many programs produce log messages to" #~ " inform the user of what they " #~ "are doing. These messages can be " #~ "managed by systemd's \"journal\" or by" #~ " a \"syslog daemon\" such as " #~ "``rsyslog``." #~ msgstr "" #~ msgid "" #~ "In |OLDRELEASENAME|, **rsyslog** was installed" #~ " by default and the systemd journal" #~ " was configured to forward log " #~ "messages to rsyslog, which writes " #~ "messages into various text files such" #~ " as ``/var/log/syslog``." #~ msgstr "" #~ msgid "" #~ "From |RELEASENAME|, **rsyslog** is no " #~ "longer installed by default. If you " #~ "do not want to continue using " #~ "``rsyslog``, after the upgrade you can" #~ " mark it as automatically installed " #~ "with" #~ msgstr "" #~ msgid "and then an" #~ msgstr "" #~ msgid "" #~ "will remove it, if possible. If " #~ "you have upgraded from older Debian " #~ "releases, and not accepted the default" #~ " configuration settings, the journal may" #~ " not have been configured to save " #~ "messages to persistent storage: instructions" #~ " for enabling this are in :url-" #~ "man-stable:`journald.conf(5)`." #~ msgstr "" #~ msgid "" #~ "If you decide to switch away from" #~ " **rsyslog** you can use the " #~ "``journalctl`` command to read log " #~ "messages, which are stored in a " #~ "binary format under ``/var/log/journal``. For" #~ " example," #~ msgstr "" #~ msgid "shows the most recent log messages in the journal and" #~ msgstr "" #~ msgid "shows new messages as they are written (similar to running" #~ msgstr "" #~ msgid ")." #~ msgstr "" #~ msgid "rsyslog changes affecting log analyzers such as logcheck" #~ msgstr "" #~ msgid "" #~ "**rsyslog** now defaults to \"high " #~ "precision timestamps\" which may affect " #~ "other programs that analyze the system" #~ " logs. There is further information " #~ "about how to customize this setting " #~ "in :url-man-stable:`rsyslog.conf(5)`." #~ msgstr "" #~ msgid "" #~ "The change in timestamps may require " #~ "locally-created **logcheck** rules to be" #~ " updated. ``logcheck`` checks messages in" #~ " the system log (produced by " #~ "``systemd-journald`` or ``rsyslog``) against " #~ "a customizable database of regular " #~ "expressions known as rules. Rules that" #~ " match the time the message was " #~ "produced will need to be updated " #~ "to match the new ``rsyslog`` format. " #~ "The default rules, which are provided" #~ " by the **logcheck-database** package, " #~ "have been updated, but other rules, " #~ "including those created locally, may " #~ "require updating to recognize the new" #~ " format. See `/usr/share/doc/logcheck-" #~ "database/NEWS.Debian.gz " #~ "<https://salsa.debian.org/debian/logcheck/-/blob/debian/1.4.0/debian"; #~ "/logcheck-database.NEWS>`__ for a script to" #~ " help update local ``logcheck`` rules." #~ msgstr "" #~ msgid "rsyslog creates fewer log files" #~ msgstr "" #~ msgid "" #~ "**rsyslog** has changed which log files" #~ " it creates, and some files in " #~ "``/var/log`` can be deleted." #~ msgstr "" #~ msgid "" #~ "If you are continuing to use " #~ "**rsyslog** (see `Changes to system " #~ "logging <#changes-to-system-logging>`__), " #~ "some log files in ``/var/log`` will " #~ "no longer be created by default. " #~ "The messages that were written to " #~ "these files are also in " #~ "``/var/log/syslog`` but are no longer " #~ "created by default. Everything that used" #~ " to be written to these files " #~ "will still be available in " #~ "``/var/log/syslog``." #~ msgstr "" #~ msgid "The files that are no longer created are:" #~ msgstr "" #~ msgid "``/var/log/mail.{info,warn,err}``" #~ msgstr "" #~ msgid "" #~ "These files contained messages from the" #~ " local mail transport agent (MTA), " #~ "split up by priority." #~ msgstr "" #~ msgid "" #~ "As ``/var/log/mail.log`` contains all mail " #~ "related messages, these files (and their" #~ " rotated counterparts) can be deleted " #~ "safely. If you were using those " #~ "files to monitor anomalies, a suitable" #~ " alternative might be something like " #~ "logcheck." #~ msgstr "" #~ msgid "``/var/log/lpr.log``" #~ msgstr "" #~ msgid "" #~ "This file contained log messages " #~ "relating to printing. The default print" #~ " system in debian is **cups** which" #~ " does not use this file, so " #~ "unless you installed a different " #~ "printing system this file (and its " #~ "rotated counterparts) can be deleted." #~ msgstr "" #~ msgid "``/var/log/{messages,debug,daemon.log}``" #~ msgstr "" #~ msgid "" #~ "These files (and their rotated " #~ "counterparts) can be deleted. Everything " #~ "that used to be written to these" #~ " files will still be in " #~ "``/var/log/syslog``." #~ msgstr "" #~ msgid "slapd upgrade may require manual intervention" #~ msgstr "" #~ msgid "" #~ "OpenLDAP 2.5 is a major new " #~ "release and includes several incompatible " #~ "changes as described in `the upstream" #~ " release announcement " #~ "<https://git.openldap.org/openldap/openldap/-/raw/OPENLDAP_REL_ENG_2_5/ANNOUNCEMENT>`__." #~ " Depending on the configuration, the " #~ "``slapd`` service might remain stopped " #~ "after the upgrade, until necessary " #~ "configuration updates are completed." #~ msgstr "" #~ msgid "The following are some of the known incompatible changes:" #~ msgstr "" #~ msgid "" #~ "The :url-man-oldstable:`slapd-bdb(5)` " #~ "and :url-man-oldstable:`slapd-hdb(5)` " #~ "database backends have been removed. If" #~ " you are using one of these " #~ "backends under |OLDRELEASENAME|, it is " #~ "strongly recommended to migrate to the" #~ " :url-man-stable:`slapd-mdb(5)` backend " #~ "*before* upgrading to |RELEASENAME|." #~ msgstr "" #~ msgid "" #~ "The :url-man-oldstable:`slapd-shell(5)` " #~ "database backend has been removed." #~ msgstr "" #~ msgid "" #~ "The :url-man-stable:`slapo-ppolicy(5)` " #~ "overlay now includes its schema compiled" #~ " into the module. The old external" #~ " schema, if present, conflicts with " #~ "the new built-in one." #~ msgstr "" #~ msgid "" #~ "The contrib password module pw-argon2" #~ " (see :url-man-oldstable:`slapd-pw-" #~ "argon2.5`) has been renamed to :url-" #~ "man-stable:`argon2`." #~ msgstr "" #~ msgid "" #~ "Instructions for completing the upgrade " #~ "and resuming the ``slapd`` service can" #~ " be found in " #~ "`/usr/share/doc/slapd/README.Debian.gz " #~ "<https://sources.debian.org/src/openldap/bookworm/debian/slapd.README.Debian/>`__." #~ " You should also consult `the " #~ "upstream upgrade notes " #~ "<https://openldap.org/doc/admin25/appendix-upgrading.html>`__." #~ msgstr "" #~ msgid "GRUB no longer runs os-prober by default" #~ msgstr "" #~ msgid "" #~ "For a long time, **grub** has used" #~ " the **os-prober** package to detect" #~ " other operating systems installed on " #~ "a computer so that it can add " #~ "them to the boot menu. Unfortunately," #~ " that can be problematic in certain" #~ " cases (e.g. where guest virtual " #~ "machines are running), so this has " #~ "now been disabled by default in " #~ "the latest upstream release." #~ msgstr "" #~ msgid "" #~ "If you are using GRUB to boot " #~ "your system and want to continue " #~ "to have other operating systems listed" #~ " on the boot menu, you can " #~ "change this. Either edit the file " #~ "``/etc/default/grub``, ensure you have the " #~ "setting ``GRUB_DISABLE_OS_PROBER=false`` and re-" #~ "run ``update-grub``, or run" #~ msgstr "" #~ msgid "to change this and other GRUB settings in a more user-friendly way." #~ msgstr "" #~ msgid "GNOME has reduced accessibility support for screen readers" #~ msgstr "" #~ msgid "" #~ "Many ``GNOME`` apps have switched from" #~ " the ``GTK3`` graphics toolkit to " #~ "``GTK4``. Sadly, this has made many " #~ "apps much less usable with screen " #~ "readers such as **orca**." #~ msgstr "" #~ msgid "" #~ "If you depend on a screen reader" #~ " you should consider switching to a" #~ " different desktop such as `Mate " #~ "<https://mate-desktop.org>`__, which has " #~ "better accessibility support. You can do" #~ " this by installing the **mate-" #~ "desktop-environment** package. Information about" #~ " how to use Orca under Mate is" #~ " available `here " #~ "<https://wiki.debian.org/Accessibility/Orca#MATE>`__." #~ msgstr "" #~ msgid "Baseline for 32-bit PC is now i686" #~ msgstr "" #~ msgid "" #~ "Debian's support for 32-bit PC (known" #~ " as the Debian architecture i386) now" #~ " no longer covers any i586 processor." #~ " The new minimum requirement is i686." #~ " This means that the i386 " #~ "architecture now requires the \"long " #~ "NOP\" (NOPL) instruction, while bullseye " #~ "still supported some i586 processors " #~ "without that instruction (e.g. the \"AMD" #~ " Geode\")." #~ msgstr "" #~ msgid "" #~ "If your machine is not compatible " #~ "with this requirement, it is recommended" #~ " that you stay with bullseye for " #~ "the remainder of its support cycle." #~ msgstr "" #~ msgid "Changes to polkit configuration" #~ msgstr "" #~ msgid "" #~ "For consistency with upstream and other" #~ " distributions, the ``polkit`` (formerly " #~ "``PolicyKit``) service, which allows " #~ "unprivileged programs to access privileged " #~ "system services, has changed the syntax" #~ " and location for local policy rules." #~ " You should now write local rules " #~ "for customizing the security policy in" #~ " `JavaScript <https://wikipedia.org/wiki/JavaScript>`__, " #~ "and place them at " #~ "``/etc/polkit-1/rules.d/*.rules``. Example rules " #~ "using the new format can be found" #~ " in ``/usr/share/doc/polkitd/examples/``, and " #~ ":url-man-unstable:`polkit.8.html#AUTHORIZATION_RULES` " #~ "has further information." #~ msgstr "" #~ msgid "" #~ "Previously, rules could be written in" #~ " ``pkla`` format, and placed in " #~ "subdirectories of ``/etc/polkit-1/localauthority`` " #~ "or ``/var/lib/polkit-1/localauthority``. However, " #~ "``.pkla`` files should now be considered" #~ " deprecated, and will only continue " #~ "to work if the **polkitd-pkla** " #~ "package is installed. This package will" #~ " usually be installed automatically when" #~ " you upgrade to bookworm, but it " #~ "is likely not to be included in" #~ " future Debian releases, so any local" #~ " policy overrides will need to be " #~ "migrated to the JavaScript format." #~ msgstr "" #~ msgid "A \"merged-``/usr``\" is now required" #~ msgstr "" #~ msgid "" #~ "Debian has adopted a filesystem layout," #~ " referred to as \"merged-``/usr``\", which" #~ " no longer includes the legacy " #~ "directories ``/bin``, ``/sbin``, ``/lib``, or" #~ " optional variants such as ``/lib64``. " #~ "In the new layout, the legacy " #~ "directories are replaced with symlinks " #~ "to the corresponding locations ``/usr/bin``," #~ " ``/usr/sbin``, ``/usr/lib``, and ``/usr/lib64``." #~ " This means that, for example, both" #~ " ``/bin/bash`` and ``/usr/bin/bash`` will " #~ "launch ``bash``." #~ msgstr "" #~ msgid "" #~ "For systems installed as buster or " #~ "bullseye there will be no change, " #~ "as the new filesystem layout was " #~ "already the default in these releases." #~ " However, the older layout is no " #~ "longer supported, and systems using it" #~ " will be converted to the new " #~ "layout when they are upgraded to " #~ "bookworm." #~ msgstr "" #~ msgid "" #~ "The conversion to the new layout " #~ "should have no impact on most " #~ "users. All files are automatically moved" #~ " to their new locations even if " #~ "they were installed locally or come " #~ "from packages not provided by Debian," #~ " and hardcoded paths such as " #~ "``/bin/sh`` continue to work. There are," #~ " however, some potential issues:" #~ msgstr "" #~ msgid "will give wrong answers for files moved to the new locations:" #~ msgstr "" #~ msgid "will not identify that ``bash`` came from a package. (But" #~ msgstr "" #~ msgid "still works as expected.)" #~ msgstr "" #~ msgid "" #~ "Local software not provided by Debian" #~ " may not support the new layout " #~ "and may, for example, rely on " #~ "``/usr/bin/name`` and ``/bin/name`` being two" #~ " different files. This is not " #~ "supported on merged systems (including " #~ "new installations since buster), so any" #~ " such software must be fixed or " #~ "removed before the upgrade." #~ msgstr "" #~ msgid "" #~ "Systems that rely on a \"base " #~ "layer\" that is not directly writable" #~ " (such as `WSL1 " #~ "<https://wiki.debian.org/InstallingDebianOn/Microsoft/Windows/SubsystemForLinux>`__" #~ " images or container systems using " #~ "multi-layer `overlayfs " #~ "<https://en.wikipedia.org/wiki/OverlayFS>`__ filesystems) " #~ "cannot be safely converted and should" #~ " either be replaced (e.g., by " #~ "installing a new WSL1 image from " #~ "the store) or have each individual " #~ "layer upgraded (e.g., by upgrading the" #~ " base Debian layer of the overlayfs" #~ " independently) rather than dist-upgraded." #~ msgstr "" #~ msgid "" #~ "For further information, see `The Case" #~ " for the /usr merge " #~ "<https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/>`__" #~ " and `the Debian Technical Committee " #~ "resolution <https://bugs.debian.org/cgi-"; #~ "bin/bugreport.cgi?bug=994388#110>`__." #~ msgstr "" #~ msgid "Unsupported upgrades from buster fail on ``libcrypt1``" #~ msgstr "" #~ msgid "" #~ "Debian officially supports upgrades only " #~ "from one stable release to the " #~ "next, e.g. from bullseye to bookworm." #~ " Upgrades from buster to bookworm are" #~ " not supported, and will fail due " #~ "to `Bug #993755 <https://bugs.debian.org/cgi-"; #~ "bin/bugreport.cgi?bug=993755>`__ with the following" #~ " error:" #~ msgstr "" #~ msgid "" #~ "It is however possible to manually " #~ "recover from this particular situation " #~ "by forcibly installing the new " #~ "libcrypt1:" #~ msgstr "" #~ msgid "Python Interpreters marked externally-managed" #~ msgstr "" #~ msgid "" #~ "The Debian provided python3 interpreter " #~ "packages (**python3.11** and **pypy3**) are" #~ " now marked as being externally-" #~ "managed, following `PEP-668 " #~ "<https://peps.python.org/pep-0668/>`__. The version " #~ "of **python3-pip** provided in Debian " #~ "follows this, and will refuse to " #~ "manually install packages on Debian's " #~ "python interpreters, unless the ``--break-" #~ "system-packages`` option is specified." #~ msgstr "" #~ msgid "" #~ "If you need to install a Python" #~ " application (or version) that isn't " #~ "packaged in Debian, we recommend that" #~ " you install it with ``pipx`` (in " #~ "the **pipx** Debian package). ``pipx`` " #~ "will set up an environment isolated " #~ "from other applications and system " #~ "Python modules, and install the " #~ "application and its dependencies into " #~ "that." #~ msgstr "" #~ msgid "" #~ "If you need to install a Python" #~ " library module (or version) that " #~ "isn't packaged in Debian, we recommend" #~ " installing it into a virtualenv, " #~ "where possible. You can create " #~ "virtualenvs with the ``venv`` Python " #~ "stdlib module (in the **python3-venv** " #~ "Debian package) or the ``virtualenv`` " #~ "Python 3rd-party tool (in the " #~ "**virtualenv** Debian package). For example," #~ " instead of running ``pip install " #~ "--user foo``, run: ``mkdir -p ~/.venvs" #~ " && python3 -m venv ~/.venvs/foo &&" #~ " ~/.venvs/foo/bin/python -m pip install " #~ "foo`` to install it in a dedicated" #~ " virtualenv." #~ msgstr "" #~ msgid "See ``/usr/share/doc/python3.11/README.venv`` for more details." #~ msgstr "" #~ msgid "Limited hardware-accelerated video encoding/decoding support in VLC" #~ msgstr "" #~ msgid "" #~ "The VLC video player supports " #~ "hardware-accelerated video decoding and " #~ "encoding via VA-API and VDPAU. " #~ "However, VLC's support for VA-API " #~ "is tightly related to the version " #~ "of FFmpeg. Because FFmpeg was upgraded" #~ " to the 5.x branch, VLC's VA-" #~ "API support has been disabled. Users " #~ "of GPUs with native VA-API support" #~ " (e.g., Intel and AMD GPUs) may " #~ "experience high CPU usage during video" #~ " playback and encoding." #~ msgstr "" #~ msgid "" #~ "Users of GPUs offering native VDPAU " #~ "support (e.g., NVIDIA with non-free " #~ "drivers) are not affected by this " #~ "issue." #~ msgstr "" #~ msgid "" #~ "Support for VA-API and VDPAU can" #~ " be checked with ``vainfo`` and " #~ "``vdpauinfo`` (each provided in a Debian" #~ " package of the same name)." #~ msgstr "" #~ msgid "systemd-resolved has been split into a separate package" #~ msgstr "" #~ msgid "" #~ "The new **systemd-resolved** package " #~ "will not be installed automatically on" #~ " upgrades. If you were using the " #~ "``systemd-resolved`` system service, please" #~ " install the new package manually " #~ "after the upgrade, and note that " #~ "until it has been installed, DNS " #~ "resolution might no longer work since" #~ " the service will not be present " #~ "on the system. Installing this package" #~ " will automatically give systemd-resolved" #~ " control of ``/etc/resolv.conf``. For more" #~ " information about systemd-resolved, " #~ "consult the official `documentation " #~ "<https://www.freedesktop.org/software/systemd/man/systemd-"; #~ "resolved.service.html>`__. Note that systemd-" #~ "resolved was not, and still is " #~ "not, the default DNS resolver in " #~ "Debian. If you have not configured " #~ "your machine to use systemd-resolved " #~ "as the DNS resolver, no action is" #~ " required." #~ msgstr "" #~ msgid "systemd-boot has been split into a separate package" #~ msgstr "" #~ msgid "" #~ "The new **systemd-boot** package will" #~ " not be installed automatically on " #~ "upgrades. If you were using " #~ "``systemd-boot``, please install this new" #~ " package manually, and note that " #~ "until you do so, the older version" #~ " of systemd-boot will be used " #~ "as the bootloader. Installing this " #~ "package will automatically configure " #~ "systemd-boot as the machine's bootloader." #~ " The default boot loader in Debian" #~ " is still GRUB. If you have not" #~ " configured the machine to use " #~ "systemd-boot as the bootloader, no " #~ "action is required." #~ msgstr "" #~ msgid "systemd-journal-remote no longer uses GnuTLS" #~ msgstr "" #~ msgid "" #~ "The optional `systemd-journal-gatewayd " #~ "<https://www.freedesktop.org/software/systemd/man/systemd-"; #~ "journal-remote.service.html#--trust=>`__ and " #~ "`systemd-journal-remote " #~ "<https://www.freedesktop.org/software/systemd/man/systemd-"; #~ "journal-gatewayd.service.html#--trust=>`__ services are" #~ " now built without GnuTLS support, " #~ "which means the ``--trust`` option is" #~ " no longer provided by either " #~ "program, and an error will be " #~ "raised if it is specified." #~ msgstr "" #~ msgid "Extensive changes in adduser for bookworm" #~ msgstr "" #~ msgid "" #~ "There have been several changes in " #~ "**adduser**. The most prominent change " #~ "is that ``--disabled-password`` and " #~ "``--disabled-login`` are now functionally " #~ "identical. For further details, please " #~ "read the ``/usr/share/doc/adduser/NEWS.Debian.gz``." #~ msgstr "" #~ msgid "Predictable naming for Xen network interfaces" #~ msgstr "" #~ msgid "" #~ "The predictable naming logic in systemd" #~ " for network interfaces has been " #~ "extended to generate stable names from" #~ " Xen netfront device information. This " #~ "means that instead of the former " #~ "system of names assigned by the " #~ "kernel, interfaces now have stable names" #~ " of the form ``enX#``. Please adapt" #~ " your system before rebooting after " #~ "the upgrade. Some more information can" #~ " be found on the `NetworkInterfaceNames " #~ "wiki page <https://wiki.debian.org/NetworkInterfaceNames"; #~ "#bookworm-xen>`__." #~ msgstr "" #~ msgid "Change in dash handling of circumflex" #~ msgstr "" #~ msgid "" #~ "``dash``, which by default provides the" #~ " system shell ``/bin/sh`` in Debian, " #~ "has switched to treating the circumflex" #~ " (``^``) as a literal character, as" #~ " was always the intended POSIX-" #~ "compliant behavior. This means that in" #~ " bookworm ``[^0-9]`` no longer means " #~ "\"not 0 to 9\" but \"0 to 9" #~ " and ^\"." #~ msgstr "" #~ msgid "netcat-openbsd supports abstract sockets" #~ msgstr "" #~ msgid "" #~ "The ``netcat`` utility for reading and" #~ " writing data across network connections" #~ " supports abstract sockets (see :url-" #~ "man-stable:`unix.7.html#Abstract_sockets`, and uses " #~ "them by default in some circumstances." #~ msgstr "" #~ msgid "" #~ "By default, ``netcat`` is provided by" #~ " **netcat-traditional**. However, if " #~ "``netcat`` is provided by the " #~ "**netcat-openbsd** package and you are " #~ "using an ``AF_UNIX`` socket, then this" #~ " new default applies. In this case" #~ " the ``-U`` option to ``nc`` will " #~ "now interpret an argument starting with" #~ " an ``@`` as requesting an abstract" #~ " socket rather than as a filename " #~ "beginning with an ``@`` in the " #~ "current directory. This can have " #~ "security implications because filesystem " #~ "permissions can no longer be used " #~ "to control access to an abstract " #~ "socket. You can continue to use a" #~ " filename starting with an ``@`` by" #~ " prefixing the name with ``./`` or" #~ " by specifying an absolute path." #~ msgstr "" #~ msgid "" #~ "The **libnss-ldap** package has been " #~ "removed from |RELEASENAME|. Its " #~ "functionalities are now covered by " #~ "**libnss-ldapd** and **libnss-sss**." #~ msgstr "" #~ msgid "" #~ "The **libpam-ldap** package has been " #~ "removed from |RELEASENAME|. Its replacement" #~ " is **libpam-ldapd**." #~ msgstr "" #~ msgid "" #~ "The **fdflush** package has been removed" #~ " from |RELEASENAME|. In its stead, " #~ "please use ``blockdev --flushbufs`` from " #~ "**util-linux**." #~ msgstr "" #~ msgid "" #~ "The **libgdal-perl** package has been" #~ " removed from |RELEASENAME|, because the" #~ " Perl binding for GDAL is no " #~ "longer supported upstream. If you need" #~ " Perl support for GDAL, you can " #~ "migrate to the FFI interface provided" #~ " by the **Geo::GDAL::FFI** package, " #~ "available on CPAN. You will have " #~ "to build your own binaries as " #~ "documented on the `BookwormGdalPerl Wiki " #~ "page <https://wiki.debian.org/BookwormGdalPerl>`__." #~ msgstr "" #~ msgid "" #~ "Development of the NSS service " #~ "``gw_name`` stopped in 2015. The " #~ "associated package **libnss-gw-name** " #~ "may be removed in future Debian " #~ "releases. The upstream developer suggests " #~ "using **libnss-myhostname** instead." #~ msgstr "" #~ msgid "" #~ "**dmraid** has not seen upstream " #~ "activity since end 2010 and has " #~ "been on life support in Debian. " #~ "bookworm will be the last release " #~ "to ship it, so please plan " #~ "accordingly if you're using **dmraid**." #~ msgstr "" #~ msgid "" #~ "**request-tracker4** has been superseded " #~ "by **request-tracker5** in this release," #~ " and will be removed in future " #~ "releases. We recommend that you plan " #~ "to migrate from **request-tracker4** to" #~ " **request-tracker5** during the lifetime" #~ " of this release." #~ msgstr "" #~ msgid "" #~ "The **isc-dhcp** suite has been " #~ "`deprecated <https://www.isc.org/blogs/isc-dhcp-"; #~ "eol/>`__ by the `ISC " #~ "<https://www.isc.org/>`__. The `Debian Wiki " #~ "<https://wiki.debian.org/>`__ has a list of" #~ " alternative implementations, see the `DHCP" #~ " Client <https://wiki.debian.org/DHCP_Client>`__ and" #~ " `DHCP Server <https://wiki.debian.org/DHCP_Server>`__" #~ " pages for the latest. If you " #~ "are using NetworkManager or systemd-" #~ "networkd, you can safely remove the " #~ "**isc-dhcp-client** package as they " #~ "both ship their own implementation. If" #~ " you are using the **ifupdown** " #~ "package, you can experiment with udhcpc" #~ " as a replacement. The ISC recommends" #~ " the **Kea** package as a replacement" #~ " for DHCP servers." #~ msgstr "" #~ msgid "" #~ "The security team will support the " #~ "**isc-dhcp** package during the bookworm" #~ " lifetime, but the package will " #~ "likely be unsupported in the next " #~ "stable release, see `bug #1035972 " #~ "(isc-dhcp EOL'ed) <https://bugs.debian.org/cgi-"; #~ "bin/bugreport.cgi?bug=1035972>`__ for more details." #~ msgstr ""
