[MAJ] ddp://release-notes/source/locales/fr/LC_MESSAGES/issues.po

To: jipege@debian.org
Cc: debian-l10n-french@lists.debian.org
Subject: [MAJ] ddp://release-notes/source/locales/fr/LC_MESSAGES/issues.po
From: Baptiste Jammet <baptiste@mailoo.org>
Date: Sat, 21 Jun 2025 15:48:04 +0200
Message-id: <[🔎] 20250621154804.66d51a34@endor.maison>
In-reply-to: <[🔎] 20250621152522.227cf740@endor.maison>
References: <[🔎] 20250621152522.227cf740@endor.maison>

Bonjour, 

Jean-Pierre, est tu d'accord de reprendre la traduction de cette page ?
Si non, merci d'envoyer un TAF.

Baptiste

>Pour info, le format d'origine à changé de xml à rst, et la
>construction est maintenant faite avec Sphinx. J'invite les
>traducteurs à lire le fichier README.translators pour prendre
>connaissance de la nouvelle méthode de construction.
>
>Le dépôt est toujours le même
>(https://salsa.debian.org/ddp-team/release-notes/)
>
>Enfin, les constructions automatiques sont publiées après chaque envoi
>: https://ddp-team.pages.debian.net/release-notes/fr/html/index.html

# translation of issues.po to French
# Translation of Debian release notes to French
# Copyright (C) 2005-2012 Debian French l10n team
# <debian-l10n-french@lists.debian.org>
# This file is distributed under the same license as the Debian release
# notes.
#
# Translators:
# Denis Barbier, -2004
# FrÃ©dÃ©ric Bothamy <frederic.bothamy@free.fr>, 2004-2007.
# Simon Paillard <simon.paillard@resel.enst-bretagne.fr>, 2008-2009.
# Christian Perrier <bubulle@debian.org>, 2009.
# Thomas Blein <tblein@tblein.eu>, 2011.
# David PrÃ©vot <david@tilapin.org>, 2011-2013.
# Thomas Vincent <thomas@vinc-net.fr>, 2013-2015.
# Baptiste Jammet <baptiste@mailoo.org>, 2019.
# Thomas Vincent <tvincent@debian.org>, 2021.
# Jean-Pierre Giraud <jean-pierregiraud@neuf.fr>, 2021-2023.
msgid ""
msgstr ""
"Project-Id-Version:  issues\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
"POT-Creation-Date: 2025-06-21 11:49+0200\n"
"PO-Revision-Date: 2023-06-14 12:18+0200\n"
"Last-Translator: Jean-Pierre Giraud <jean-pierregiraud@neuf.fr>\n"
"Language: fr\n"
"Language-Team: French <debian-l10n-french@lists.debian.org>\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 "ProblÃ¨mes Ã  connaÃ®tre pour |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 ""
"Parfois, des changements ont des effets de bord que nous ne pouvons pas "
"raisonnablement Ã©viter sans nous exposer Ã  des bogues Ã  un autre endroit."
" Cette section documente les problÃ¨mes que nous connaissons. Veuillez "
"Ã©galement lire l'errata, la documentation des paquets concernÃ©s, les "
"rapports de bogues et les autres sources d'informations mentionnÃ©es dans "
"la :ref:`morereading`."

#: ../issues.rst:15
msgid "Upgrade specific items for |RELEASENAME|"
msgstr "Mise Ã  niveau d'Ã©lÃ©ments spÃ©cifiques pour |RELEASENAME|"

#: ../issues.rst:17
msgid ""
"This section covers items related to the upgrade from |OLDRELEASENAME| to"
" |RELEASENAME|."
msgstr ""
"Cette section concerne les Ã©lÃ©ments liÃ©s Ã  la mise Ã  niveau de "
"|OLDRELEASENAME| vers |RELEASENAME|"

#: ../issues.rst:23
msgid "Reduced support for i386"
msgstr ""

#: ../issues.rst:25
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 ""

#: ../issues.rst:32
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 ""

#: ../issues.rst:41
msgid "openssh-server no longer reads ~/.pam_environment"
msgstr ""

#: ../issues.rst:43
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 ""

#: ../issues.rst:53
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 ""

#: ../issues.rst:62
msgid "OpenSSH no longer supports DSA keys"
msgstr ""

#: ../issues.rst:64
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 ""

#: ../issues.rst:73
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 ""

#: ../issues.rst:77
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 ""

#: ../issues.rst:82
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 ""

#: ../issues.rst:98
msgid "The last, lastb and lastlog commands have been replaced"
msgstr ""

#: ../issues.rst:100
msgid ""
"The **util-linux** package no longer provides the ``last`` or ``lastb`` "
"commands, and the **login** package no longer provides ``lastlog``. These"
" commands provided information about previous login attempts using "
"``/var/log/wtmp``, ``/var/log/btmp``, ``/var/run/utmp`` and "
"``/var/log/lastlog``, but these files will not be usable after 2038 "
"because they do not allocate enough space to store the login time (the "
"`Year 2038 Problem <https://theyear2038problem.com/>`__), and the "
"upstream developers do not want to change the file formats.  Most users "
"will not need to replace these commands with anything, but the **util-"
"linux** package provides a ``lslogins`` command which can tell you when "
"accounts were last used."
msgstr ""

#: ../issues.rst:112
msgid ""
"There are two direct replacements available: ``last`` can be replaced by "
"``wtmpdb`` from the **wtmpdb** package (the **libpam-wtmpdb** package "
"also needs to be installed) and ``lastlog`` can be replaced by "
"``lastlog2`` from the **lastlog2** package (**libpam-lastlog2** also "
"needs to be installed). If you want to use these, you will need to "
"install the new packages after the upgrade, see the `util-linux "
"NEWS.Debian <https://salsa.debian.org/debian/util-";
"linux/-/blob/debian/unstable/debian/NEWS>`__ for further information. The"
" command ``lslogins --failed`` provides similar information to ``lastb``."
msgstr ""

#: ../issues.rst:123
msgid ""
"If you do not install **wtmpdb** then we recommend you remove old log "
"files ``/var/log/wtmp*``. If you do install **wtmpdb** it will upgrade "
"``/var/log/wtmp`` and you can read older wtmp files with ``wtmpdb import "
"-f <dest>``.  There is no tool to read ``/var/log/lastlog*`` or "
"``/var/log/btmp*`` files: they can be deleted after the upgrade."
msgstr ""

#: ../issues.rst:132
msgid "RabbitMQ no longer supports HA queues"
msgstr ""

#: ../issues.rst:134
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 ""

#: ../issues.rst:138
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 ""

#: ../issues.rst:146
msgid "RabbitMQ cannot be directly upgraded from bookworm"
msgstr ""

#: ../issues.rst:148
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 ""

#: ../issues.rst:151
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 ""

#: ../issues.rst:159
msgid "MariaDB major version upgrades only work reliably after a clean shutdown"
msgstr ""

#: ../issues.rst:161
msgid ""
"MariaDB does not support error recovery across major versions. For "
"example if a MariaDB 10.11 server experienced an abrupt shutdown due to "
"power loss or software defect, the database needs to be restarted with "
"the same MariaDB 10.11 binaries so it can do successful error recovery "
"and reconcile the data files and log files to roll-forward or revert "
"transactions that got interrupted."
msgstr ""

#: ../issues.rst:167
msgid ""
"If you attempt to do crash recovery with MariaDB 11.8 using the data "
"directory from a crashed MariaDB 10.11 instance, the newer MariaDB server"
" will refuse to start."
msgstr ""

#: ../issues.rst:171
msgid ""
"To ensure a MariaDB Server is shut down cleanly before going into major "
"version upgrade, stop the service with"
msgstr ""

#: ../issues.rst:178
msgid ""
"followed by checking server logs for ``Shutdown complete`` to confirm "
"that flushing all data and buffers to disk completed successfully."
msgstr ""

#: ../issues.rst:181
msgid ""
"If it didn't shut down cleanly, restart it to trigger crash recovery, "
"wait, stop again and verify that second stop was clean."
msgstr ""

#: ../issues.rst:184
msgid ""
"For additional information about how to make backups and other relevant "
"information for system administrators, please see `/usr/share/doc"
"/mariadb-server/README.Debian.gz "
"<https://sources.debian.org/src/mariadb/trixie/debian/mariadb-";
"server.README.Debian/>`__."
msgstr ""

#: ../issues.rst:193
msgid "Ping no longer runs with elevated privileges"
msgstr ""

#: ../issues.rst:195
msgid ""
"The default version of ping (provided by **iputils-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 ""

#: ../issues.rst:213
msgid "Significant changes to libvirt packaging"
msgstr ""

#: ../issues.rst:215
msgid ""
"The **libvirt-daemon** package, which provides an API and toolkit for "
"managing virtualization platforms, has been overhauled in trixie. Each "
"driver and storage backend now comes in a separate binary package, which "
"enables much greater flexibility."
msgstr ""

#: ../issues.rst:220
msgid ""
"Care is taken during upgrades from bookworm to retain the existing set of"
" components, but in some cases functionality might end up being "
"temporarily lost. We recommend that you carefully review the list of "
"installed binary packages after upgrading to ensure that all the expected"
" ones are present; this is also a great time to consider uninstalling "
"unwanted components."
msgstr ""

#: ../issues.rst:227
msgid ""
"In addition, some conffiles might end up marked as \"obsolete\" after the"
" upgrade. The ``/usr/share/doc/libvirt-common/NEWS.Debian.gz`` file "
"contains additional information on how to verify whether your system is "
"affected by this issue and how to address it."
msgstr ""

#: ../issues.rst:236
msgid "Things to do post upgrade before rebooting"
msgstr "Choses Ã  faire avant de redÃ©marrer aprÃ¨s la mise Ã  niveau"

#: ../issues.rst:238
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 ""
"Lorsque ``apt full-upgrade`` a terminÃ©, la mise Ã  niveau \"formelle\" est"
" terminÃ©e. Pour la mise Ã  niveau vers |RELEASENAME| il n'y a rien de "
"particulier Ã  faire avant de redÃ©marrer."

#: ../issues.rst:244
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 ""
"Lorsque ``apt full-upgrade`` a terminÃ©, la mise Ã  niveau \"formelle\" est"
" terminÃ©e, mais certaines choses devraient Ãªtre prises en compte *avant* "
"un redÃ©marrage."

#: ../issues.rst:257
msgid "Items not limited to the upgrade process"
msgstr "Ã?lÃ©ments non limitÃ©s au processus de mise Ã  niveau"

#: ../issues.rst:262
msgid "Limitations in security support"
msgstr "Limitations de la prise en charge de sÃ©curitÃ©"

#: ../issues.rst:264
msgid ""
"There are some packages where Debian cannot promise to provide minimal "
"backports for security issues. These are covered in the following "
"subsections."
msgstr ""
"Il existe certains paquets pour lesquels Debian ne peut pas garantir de "
"rÃ©troportages minimaux pour les problÃ¨mes de sÃ©curitÃ©. Cela est dÃ©veloppÃ©"
" dans les sous-sections suivantes."

#: ../issues.rst:270
msgid ""
"The package **debian-security-support** helps to track the security "
"support status of installed packages."
msgstr ""
"Le paquet **debian-security-support** aide Ã  suivre lâ??Ã©tat de la prise en"
" charge du suivi de sÃ©curitÃ© des paquets installÃ©s."

#: ../issues.rst:276
msgid "Security status of web browsers and their rendering engines"
msgstr "Ã?tat de sÃ©curitÃ© des navigateurs web et de leurs moteurs de rendu"

#: ../issues.rst:278
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| inclut plusieurs moteurs de navigateur web qui sont "
"affectÃ©s par un flot continu de vulnÃ©rabilitÃ©s de sÃ©curitÃ©. Ce taux Ã©levÃ©"
" de vulnÃ©rabilitÃ©s ainsi que le manque partiel de prise en charge amont "
"sous la forme de branches maintenues Ã  long terme rendent difficiles les "
"corrections de sÃ©curitÃ© rÃ©troportÃ©es. De plus, les interdÃ©pendances des "
"bibliothÃ¨ques rendent extrÃªmement difficile la mise Ã  niveau vers une "
"nouvelle version. Les applications utilisant le paquet source "
"**webkit2gtk** (par exemple, **epiphany**) sont couvertes par la prise en"
" charge de sÃ©curitÃ©, mais les applications utilisant qtwebkit (paquet "
"source **qtwebkit-opensource-src**) ne les sont pas."

#: ../issues.rst:288
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 ""
"Pour une utilisation classique, nous recommandons les navigateurs Firefox"
" ou Chromium. Ceux-ci seront maintenus Ã  jour en recompilant les versions"
" ESR actuelles pour stable. La mÃªme stratÃ©gie sera appliquÃ©e pour "
"Thunderbird."

#: ../issues.rst:292
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 ""
"Une fois qu'une version devient ``oldstable``, les navigateurs pris en "
"charge officiellement ne continuent pas Ã  recevoir des mises Ã  jour "
"durant la pÃ©riode normale de couverture. Par exemple, Chromium ne recevra"
" que pendant six mois une prise en charge de sÃ©curitÃ© dans ``Oldstable`` "
"au lieu des douze mois habituels."

#: ../issues.rst:300
msgid "Go- and Rust-based packages"
msgstr "Paquets basÃ©s sur Go et Rust"

#: ../issues.rst:302
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 ""
"Lâ??infrastructure de Debian a actuellement des problÃ¨mes pour recompiler "
"correctement les types de paquets qui ont systÃ©matiquement recours aux "
"liens statiques. Avec la croissance de lâ??Ã©cosystÃ¨me de Go et de Rust cela"
" signifie que ces paquets seront couverts par une prise en charge de "
"sÃ©curitÃ© limitÃ©e jusquâ??Ã  ce que lâ??infrastructure soit amÃ©liorÃ©e pour "
"pouvoir les gÃ©rer durablement."

#: ../issues.rst:308
msgid ""
"In most cases if updates are warranted for Go or Rust development "
"libraries, they will only be released via regular point releases."
msgstr ""
"Dans la plupart des cas, si les mises Ã  jour sont justifiÃ©es pour les "
"bibliothÃ¨ques de dÃ©veloppement de Go ou de Rust, elles ne viendront que "
"des mises Ã  jour intermÃ©diaires normales."

#: ../issues.rst:314
msgid "Obsolescence and deprecation"
msgstr "Obsolescence et dÃ©prÃ©ciation"

#: ../issues.rst:319
msgid "Noteworthy obsolete packages"
msgstr "Paquets obsolÃ¨tes"

#: ../issues.rst:321
msgid ""
"The following is a list of known and noteworthy obsolete packages (see "
":ref:`obsolete` for a description)."
msgstr ""
"La liste suivante contient des paquets connus et obsolÃ¨tes (voir "
":ref:`obsolete` pour une description)."

#: ../issues.rst:324
msgid "The list of obsolete packages includes:"
msgstr "La liste des paquets obsolÃ¨tes contientÂ :"

#: ../issues.rst:326
#, fuzzy
msgid ""
"The **libnss-gw-name** package has been removed from |RELEASENAME|. The "
"upstream developer suggests using **libnss-myhostname** instead."
msgstr ""
"Le dÃ©veloppement du service NSS ``gw_name`` s'est arrÃªtÃ© en 2015. Le "
"paquet associÃ© **libnss-gw-name** est susceptible d'Ãªtre supprimÃ© dans "
"une prochaine version de Debian. Le dÃ©veloppeur amont suggÃ¨re d'utiliser "
"**libnss-myhostname** Ã  la place."

#: ../issues.rst:329
msgid ""
"The **pcregrep** package has been removed from |RELEASENAME|. It can be "
"replaced with ``grep -P`` (``--perl-regexp``) or ``pcre2grep`` (from "
"**pcre2-utils**)."
msgstr ""

#: ../issues.rst:336
msgid "Deprecated components for |RELEASENAME|"
msgstr "Composants dÃ©prÃ©ciÃ©s pour |RELEASENAME|"

#: ../issues.rst:338
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 ""
"Avec la prochaine publication de Debian |NEXTRELEASE| (nom de code "
"|NEXTRELEASENAME|), certaines fonctionnalitÃ©s seront dÃ©conseillÃ©es. Les "
"utilisateurs devront migrer vers des alternatives pour Ã©viter les "
"problÃ¨mes lors de la mise Ã  jour vers DebianÂ |NEXTRELEASE|."

#: ../issues.rst:342
msgid "This includes the following features:"
msgstr "Cela comprend les fonctionnalitÃ©s suivantesÂ :"

#: ../issues.rst:344
msgid ""
"The **sudo-ldap** package will be removed in forky. The Debian sudo team "
"has decided to discontinue it due to maintenance difficulties and limited"
" use. New and existing systems should use **libsss-sudo** instead."
msgstr ""

#: ../issues.rst:349
msgid ""
"Upgrading Debian trixie to forky without completing this migration may "
"result in the loss of intended privilege escalation."
msgstr ""

#: ../issues.rst:352
msgid ""
"For further details, please refer to `bug 1033728 "
"<https://bugs.debian.org/1033728>`__ and to the NEWS file in the **sudo**"
" package."
msgstr ""

#: ../issues.rst:356
msgid ""
"The **sudo_logsrvd** feature, used for sudo input/output logging, may be "
"removed in Debian forky unless a maintainer steps forward. This component"
" is of limited use within the Debian context, and maintaining it adds "
"unnecessary complexity to the basic sudo package."
msgstr ""

#: ../issues.rst:361
msgid ""
"For ongoing discussions, see `bug 1101451 "
"<https://bugs.debian.org/1101451>`__ and the NEWS file in the **sudo** "
"package."
msgstr ""

#: ../issues.rst:365
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 ""

#: ../issues.rst:372
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 ""

#: ../issues.rst:382
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 ""

#: ../issues.rst:390
msgid ""
"sbuild-debian-developer-setup has been deprecated in favor of "
"sbuild+unshare"
msgstr ""

#: ../issues.rst:392
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 ""

#: ../issues.rst:401
msgid "The **fcitx** packages have been deprecated in favor of **fcitx5**"
msgstr ""

#: ../issues.rst:403
msgid ""
"The **fcitx** input method framework, also known as **fcitx4** or **fcitx"
" 4.x**, is no longer maintained upstream. As a result, all related input "
"method packages are now deprecated. The package **fcitx** and packages "
"with names beginning with **fcitx-** will be removed in Debian "
"|NEXTRELEASENAME|."
msgstr ""

#: ../issues.rst:408
msgid ""
"Existing **fcitx** users are encouraged to switch to **fcitx5** following"
" the `fcitx upstream migration guide <https://fcitx-";
"im.org/wiki/Upgrade_from_Fcitx_4>`__ and `Debian Wiki page "
"<https://wiki.debian.org/I18n/Fcitx5>`__."
msgstr ""

#: ../issues.rst:415
msgid "No-longer-supported hardware"
msgstr "MatÃ©riel plus pris en charge"

#: ../issues.rst:417
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 ""
"Pour un certain nombre de pÃ©riphÃ©riques basÃ©s sur \"Â architectureÂ \" et "
"pris en charge dans |OLDRELEASENAME|, il nâ??est plus possible pour Debian "
"de compiler le noyau ``Linux`` nÃ©cessaire Ã  cause de limitations "
"matÃ©rielles. Les pÃ©riphÃ©riques qui ne sont plus pris en charge sontÂ :"

#: ../issues.rst:422
msgid "foo"
msgstr "toto"

#: ../issues.rst:424
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 ""
"Les utilisateurs de ces plateformes souhaitant tout de mÃªme faire la mise"
" Ã  niveau vers |RELEASENAME| devraient conserver activÃ©es les sources APT"
" de |OLDRELEASENAME|. Avant la mise Ã  niveau, ils devraient ajouter un "
"fichier de prÃ©fÃ©rence APT contenantÂ :"

#: ../issues.rst:434
msgid ""
"The security support for this configuration will only last until "
"|OLDRELEASENAME|'s End Of Life."
msgstr ""
"La prise en charge de la sÃ©curitÃ© pour cette configuration ne durera que "
"jusquâ??Ã  la fin de vie de |OLDRELEASENAME|."

#: ../issues.rst:440
msgid "Known severe bugs"
msgstr "Bogues sÃ©vÃ¨res connus"

#: ../issues.rst:442
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/pkgreport.cgi?users=release.debian.org@packages.debian.org;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 ""
"Bien que Debian ne publie que quand elle est prÃªte, cela ne signifie pas "
"malheureusement qu'il n'y a pas de bogues connus. Dans le cadre du "
"processus de publication, tous les bogues de sÃ©vÃ©ritÃ© sÃ©rieuse ou plus "
"Ã©levÃ©e sont activement suivis par l'Ã©quipe de publication, aussi une `vue"
" d'ensemble de ces bogues <https://bugs.debian.org/cgi-";
"bin/pkgreport.cgi?users=release.debian.org@packages.debian.org;tag=&releasename"
";-can-defer>`__ qui ont Ã©tÃ© marquÃ©s comme devant Ãªtre ignorÃ©s dans la "
"partie finale du processus de publication de |RELEASENAME| est disponible"
" dans le `systÃ¨me de suivi de bogues de Debian "
"<https://bugs.debian.org/>`__. Les bogues suivants affectent "
"|RELEASENAME| au moment de la publication et mÃ©ritent d'Ãªtre mentionnÃ©s "
"dans ce documentÂ :"

#: ../issues.rst:453
msgid "Bug number"
msgstr "NumÃ©ro de bogue"

#: ../issues.rst:453
msgid "Package (source or binary)"
msgstr "Paquet (source ou binaire)"

#: ../issues.rst:453
msgid "Description"
msgstr "Description"

#: ../issues.rst:456
msgid "`1032240`_"
msgstr ""

#: ../issues.rst:456
msgid "**akonadi-backend-mysql**"
msgstr ""

#: ../issues.rst:456
msgid "akonadi server fails to start since it cannot connect to mysql database"
msgstr ""
"le serveur akonadi Ã©choue Ã  dÃ©marrer puisqu'il ne peut pas se connecter Ã "
" la base de donnÃ©es mysql"

#: ../issues.rst:461
msgid "`1032177`_"
msgstr ""

#: ../issues.rst:461
msgid "**faketime**"
msgstr ""

#: ../issues.rst:461
msgid "faketime doesn't fake time (on i386)"
msgstr "faketime ne produit pas de fausses dates (sur i386)"

#: ../issues.rst:464
msgid "`918984`_"
msgstr ""

#: ../issues.rst:464
msgid "**src:fuse3**"
msgstr ""

#: ../issues.rst:464
#, fuzzy
msgid "provide upgrade path fuse -> fuse3 for bookworm"
msgstr "fournit une mise Ã  niveau du chemin de fuse -&gt; fuse3 pour Bookworm"

#: ../issues.rst:468
msgid "`1016903`_"
msgstr ""

#: ../issues.rst:468
msgid "**g++-12**"
msgstr ""

#: ../issues.rst:468
msgid "tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working)"
msgstr "tree-vectorizeÂ : code erronÃ© au niveau 02 (-fno-tree-vectorize fonctionne)"

#: ../issues.rst:474
msgid "`1034752`_"
msgstr ""

#: ../issues.rst:474
msgid "**src:gluegen2**"
msgstr ""

#: ../issues.rst:474
msgid "embeds non-free headers"
msgstr "intÃ¨gre des en-tÃªtes non-libres"

#~ msgid "A â??merged-``/usr``â?? is now required"
#~ msgstr ""

#~ msgid "Non-free firmware moved to its own component in the archive"
#~ msgstr ""
#~ "Microprogrammes non libres dÃ©placÃ©s vers "
#~ "leur composant propre dans l'archive"

#~ 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 ""
#~ "Comme dÃ©crit dans la :ref:`archive-"
#~ "areas`, les paquets de microprogrammes "
#~ "non libres sont maintenant fournis Ã  "
#~ "partir d'un composant de l'archive qui"
#~ " leur est dÃ©diÃ©, appelÃ© ``non-"
#~ "free-firmware``. Afin d'Ãªtre sÃ»r que "
#~ "les paquets de microprogrammes non "
#~ "libres bÃ©nÃ©ficient de mises Ã  niveau "
#~ "appropriÃ©es, des modifications dans la "
#~ "configuration d'APT sont nÃ©cessaires. En "
#~ "supposant que le composant ``non-free``"
#~ " a Ã©tÃ© seulement ajoutÃ© au fichier"
#~ " sources-list d'APT pour installer "
#~ "les microprogrammes, l'entrÃ©e de la "
#~ "liste de source d'APT pourrait "
#~ "ressembler Ã  celaÂ :"

#~ 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 ""
#~ "Si vous Ãªtes orientÃ© vers ce "
#~ "chapitre par ``apt``, vous pouvez Ã©viter"
#~ " qu'il vous informe en permanence de"
#~ " cette modification en crÃ©ant un "
#~ "fichier d':url-man-stable:`apt.conf(5)` nommÃ©"
#~ " ``/etc/apt/apt.conf.d/no-bookworm-firmware.conf`` "
#~ "dont le contenu est le suivant."

#~ msgid "Changes to packages that set the system clock"
#~ msgstr "Modifications des paquets qui rÃ¨glent l'horloge systÃ¨me"

#~ 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 ""
#~ "Le paquet **ntp**, qui Ã©tait le "
#~ "moyen par dÃ©faut pour rÃ©gler l'horloge"
#~ " systÃ¨me Ã  partir d'un serveur NTP"
#~ " (Â«Â Network Time ProtocolÂ Â»), a "
#~ "Ã©tÃ© remplacÃ© par le paquet **ntpsec**."

#~ msgid ""
#~ "Most users will not need to take"
#~ " any specific action to transition "
#~ "from **ntp** to **ntpsec**."
#~ msgstr ""
#~ "La plupart des utilisateurs n'auront pas"
#~ " besoin d'entreprendre une action "
#~ "spÃ©cifique pour migrer de **ntp** Ã  "
#~ "**ntpsec**."

#~ 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 ""
#~ "Dans Bookworm, il y a d'autres "
#~ "paquets qui fournissent un service "
#~ "Ã©quivalent. Dans Debian, le paquet par"
#~ " dÃ©faut est maintenant **systemd-"
#~ "timesyncd** et il peut Ãªtre suffisant"
#~ " pour les utilisateurs qui ont "
#~ "seulement besoin d'un client ``ntp`` "
#~ "pour rÃ©gler l'horloge. Bookworm inclut "
#~ "aussi les paquets **chrony** et "
#~ "**openntpd** qui prennent en charge des"
#~ " fonctionnalitÃ©s plus Ã©voluÃ©es telles que"
#~ " l'exploitation de leur propre serveur "
#~ "NTP."

#~ msgid "Puppet configuration management system upgraded to 7"
#~ msgstr "SystÃ¨me de gestion de configuration Puppet mis Ã  niveau vers la sÃ©rieÂ 7"

#~ msgid ""
#~ "Puppet has been upgraded from 5 to"
#~ " 7, skipping the Puppet 6 series "
#~ "altogether. This introduces major changes "
#~ "to the Puppet ecosystem."
#~ msgstr ""
#~ "Puppet a Ã©tÃ© mis Ã  niveau de "
#~ "la sÃ©rieÂ 5 Ã  la sÃ©rieÂ 7, "
#~ "sautant la sÃ©rie PuppetÂ 6 purement "
#~ "et simplement. Cela introduit des "
#~ "changements majeurs dans l'Ã©cosystÃ¨me de "
#~ "Puppet."

#~ 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 ""
#~ "L'application classique Puppet MasterÂ 5.5.x"
#~ " basÃ©e sur Ruby a Ã©tÃ© dÃ©clarÃ©e "
#~ "obsolÃ¨te par l'amont et n'est plus "
#~ "disponible dans Debian. Elle est "
#~ "remplacÃ©e par Puppet ServerÂ 7.x, fournie"
#~ " par le paquet **puppetserver**. Le "
#~ "paquet est automatiquement installÃ© comme "
#~ "dÃ©pendance du paquet de transition "
#~ "**puppet-master**."

#~ 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 ""
#~ "Dans certains cas, Puppet server est "
#~ "un remplaÃ§ant pur et simple de "
#~ "Puppet Master, mais vous devriez revoir"
#~ " les fichiers de configuration disponibles"
#~ " dans ``/etc/puppet/puppetserver`` pour Ãªtre "
#~ "sÃ»r que la configuration par dÃ©faut "
#~ "est adaptÃ©e Ã  votre dÃ©ploiement. En "
#~ "particulier, l'ancien format du fichier "
#~ "``auth.conf`` est obsolÃ¨te, consultez la "
#~ "`documentation d'auth.conf "
#~ "<https://www.puppet.com/docs/puppet/7/server/config_file_auth.html>`__"
#~ " pour plus de dÃ©tails."

#~ 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 ""
#~ "L'approche recommandÃ©e est de mettre Ã "
#~ " niveau le serveur avant les clients."
#~ " Le serveur PuppetÂ 7 est "
#~ "`rÃ©trocompatible avec les anciens clients "
#~ "<https://www.puppet.com/docs/puppet/7/server/compatibility_with_puppet_agent.html>`__"
#~ "Â ; un serveur PuppetÂ 5 peut "
#~ "encore gÃ©rer des agents mis Ã  "
#~ "niveau, mais ne peut pas enregistrer "
#~ "de nouveaux agents PuppetÂ 7. Aussi, "
#~ "si vous dÃ©ployez de nouveaux agents "
#~ "PuppetÂ 7 avant de mettre Ã  niveau"
#~ " le serveur, vous ne pourrez pas "
#~ "les ajouter Ã  votre parc."

#~ msgid ""
#~ "The **puppet** package has been replaced"
#~ " by the **puppet-agent** package and"
#~ " is now a transitional package to "
#~ "ensure a smooth upgrade."
#~ msgstr ""
#~ "Le paquet **puppet** a Ã©tÃ© remplacÃ© "
#~ "par le paquet **puppet-agent** et "
#~ "est maintenant un paquet de transition"
#~ " pour assurer une mise Ã  niveau "
#~ "en douceur."

#~ msgid ""
#~ "Finally, the **puppetdb** package was "
#~ "removed in bullseye but is reintroduced"
#~ " in bookworm."
#~ msgstr ""
#~ "Finalement, le paquet **puppetdb** avait "
#~ "Ã©tÃ© retirÃ© de Bullseye, mais est "
#~ "rÃ©introduit dans Bookworm."

#~ msgid "youtube-dl replaced with yt-dlp"
#~ msgstr "youtube-dl remplacÃ© par yt-dlp"

#~ 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 ""
#~ "L'outil populaire **youtube-dl** qui "
#~ "permet de tÃ©lÃ©charger des vidÃ©os Ã  "
#~ "partir d'une grande variÃ©tÃ© de sites "
#~ "web (y compris, mais pas seulement, "
#~ "YouTube) n'est plus inclus dans Debian."
#~ " Il a Ã©tÃ© remplacÃ© par un "
#~ "paquet de transition vide qui installe"
#~ " le paquet **yt-dlp** Ã  la "
#~ "place. **yt-dlp** est un projet "
#~ "dÃ©rivÃ© de **youtube-dl** oÃ¹ actuellement"
#~ " un nouveau dÃ©veloppement est en "
#~ "cours."

#~ 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 ""
#~ "Aucune enveloppe de compatibilitÃ© n'est "
#~ "fournie, aussi vous devrez modifier vos"
#~ " scripts et votre comportement pour "
#~ "appeler ``yt-dlp`` Ã  la place de"
#~ " ``youtube-dl``. Ses fonctionnalitÃ©s "
#~ "devraient Ãªtre identiques pour la "
#~ "plupart bien que certains dÃ©tails du "
#~ "comportement et certaines options aient "
#~ "Ã©tÃ© modifiÃ©s. Prenez soin de vÃ©rifier"
#~ " la :url-man-stable:`yt-dlp.1` de "
#~ "``yt-dlp`` et en particulier la "
#~ "section :url-man-stable:`yt-"
#~ "dlp.1.html#Differences_in_default_behavior`."

#~ msgid "Fcitx versions no longer co-installable"
#~ msgstr "Les diffÃ©rentes versions de Fcitx ne sont plus co-installables"

#~ 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 ""
#~ "Les paquets **fcitx** et **fcitx5** "
#~ "fournissent les versionsÂ 4 etÂ 5 du"
#~ " cadriciel populaire de mÃ©thode de "
#~ "saisie Fcitx. Suivant les recommandations "
#~ "de l'amont, elles ne peuvent plus "
#~ "Ãªtre installÃ©es ensemble sur le mÃªme "
#~ "systÃ¨me d'exploitation. Les utilisateurs "
#~ "doivent dÃ©terminer quelle version de "
#~ "Fcitx sera conservÃ©e s'ils ont installÃ©"
#~ " auparavant Ã  la fois **fcitx** et"
#~ " **fcitx5**."

#~ 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 ""
#~ "Avant la mise Ã  niveau, les "
#~ "utilisateurs sont fortement encouragÃ©s Ã  "
#~ "purger tous les paquets liÃ©s de la"
#~ " version de Fcitx non dÃ©sirÃ©e "
#~ "(``fcitx-*`` pour FcitxÂ 4 et "
#~ "``fcitx5-*`` pour FcitxÂ 5). Quand la "
#~ "mise Ã  niveau est achevÃ©e, il faut"
#~ " envisager d'exÃ©cuter de nouveau la "
#~ "commande ``im-config`` pour choisir le"
#~ " cadriciel de mÃ©thode de saisie "
#~ "souhaitÃ© Ã  utiliser sur le systÃ¨me."

#~ 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 ""
#~ "Vous en saurez plus sur le "
#~ "contexte en lisant `l'annonce publiÃ©e "
#~ "dans la liste de diffusion "
#~ "<https://lists.debian.org/debian-chinese-";
#~ "gb/2021/12/msg00000.html>`__ (texte en chinois "
#~ "simplifiÃ©)."

#~ msgid "MariaDB package names no longer include version numbers"
#~ msgstr "Les noms de paquet de MariaDB ne comprennent plus de numÃ©ro de version"

#~ 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 ""
#~ "Ã? la diffÃ©rence de Bullseye oÃ¹ la"
#~ " version de MariaDB Ã©tait dans le "
#~ "nom des paquets (par exemple "
#~ "**mariadb-server-10.5** et **mariadb-"
#~ "client-10.5**), dans Bookworm, les noms "
#~ "de paquet Ã©quivalents de MariaDBÂ 10.11"
#~ " ne comportent aucune mention de "
#~ "version (par exemple **mariadb-server** "
#~ "ou **mariadb-client**). La version de"
#~ " MariaDB est toujours visible dans "
#~ "les mÃ©tadonnÃ©es de version de paquet."

#~ 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 ""
#~ "Il y a au moins un scÃ©nario "
#~ "de mise Ã  niveau connu `(bogue nÂº"
#~ "Â 1035949) <https://bugs.debian.org/cgi-";
#~ "bin/bugreport.cgi?bug=1035949>`_ oÃ¹ la transition"
#~ " vers les noms de paquet sans "
#~ "version Ã©choueÂ : l'exÃ©cution de'"

#~ 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 ""
#~ "peut Ã©chouer quand **mariadb-client-10.5** "
#~ "et le fichier ``/usr/bin/mariadb-admin`` "
#~ "qu'il contient sont supprimÃ©s avant que"
#~ " le service de dÃ©marrage SysV du "
#~ "serveur MariaDB ait Ã©mis une commande"
#~ " d'arrÃªt qui utilise ``mariadb-admin``. "
#~ "Le palliatif est d'exÃ©cuter"

#~ msgid "before running"
#~ msgstr "avant d'exÃ©cuter"

#~ 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 ""
#~ "Pour plus d'informations sur la "
#~ "modification des noms de paquet dans "
#~ "MariaDB, consultez `/usr/share/doc/mariadb-"
#~ "server/NEWS.Debian.gz <https://salsa.debian.org/mariadb-";
#~ "team/mariadb-"
#~ "server/-/blob/280369f034bedae714af2f26111d1d9d1659f142/debian"
#~ "/mariadb-server.NEWS>`__."

#~ msgid "Changes to system logging"
#~ msgstr "Modifications de la journalisation du systÃ¨me"

#~ msgid ""
#~ "The **rsyslog** package is no longer "
#~ "needed on most systems and you may"
#~ " be able to remove it."
#~ msgstr ""
#~ "Le paquet **rsyslog** n'est plus "
#~ "nÃ©cessaire sur la plupart des systÃ¨mes"
#~ " et vous pouvez le supprimer."

#~ 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 ""
#~ "De nombreux programmes produisent des "
#~ "messages de journalisation pour informer "
#~ "l'utilisateur de ce qu'ils font. Ces "
#~ "messages peuvent Ãªtre gÃ©rÃ©s par un "
#~ "\"journal\" de systemd ou par un "
#~ "\"dÃ©mon syslog\" comme ``rsyslog``."

#~ 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 ""
#~ "Dans |OLDRELEASENAME|, **rsyslog** Ã©tait "
#~ "installÃ© par dÃ©faut et le journal "
#~ "de systemd Ã©tait configurÃ© pour "
#~ "transmettre les messages de journalisation "
#~ "Ã  rsyslog qui Ã©crit les messages "
#~ "dans divers fichiers texte tels que "
#~ "``/var/log/syslog``."

#~ 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 ""
#~ "Depuis |RELEASENAME|, **rsyslog** n'est plus"
#~ " installÃ© par dÃ©faut. Si vous ne "
#~ "voulez pas continuer Ã  utiliser "
#~ "``rsyslog``, aprÃ¨s la mise Ã  niveau "
#~ "vous pouvez le marquer comme installÃ©"
#~ " automatiquement avec la commande"

#~ msgid "and then an"
#~ msgstr "puis un"

#~ 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 ""
#~ "le retirera si c'est possible. Si "
#~ "vous avez effectuÃ© une mise Ã  "
#~ "niveau Ã  partir de versions plus "
#~ "anciennes de Debian et si vous "
#~ "n'acceptez pas les rÃ©glages de la "
#~ "configuration par dÃ©faut, le journal "
#~ "peut ne pas Ãªtre configurÃ© pour "
#~ "enregistrer les messages dans un "
#~ "stockage permanentÂ : vous trouverez des"
#~ " instructions pour activer cela dans "
#~ ":url-man-stable:`journald.conf(5)`."

#~ 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 ""
#~ "Si vous choisissez d'abandonner **rsyslog**,"
#~ " vous pouvez utiliser la commande "
#~ "``journalctl`` pour lire les messages de"
#~ " journalisation qui sont stockÃ©s au "
#~ "format binaire dans ``/var/log/journal``. Par"
#~ " exemple,"

#~ msgid "shows the most recent log messages in the journal and"
#~ msgstr "montre les messages les plus rÃ©cents dans le journal et"

#~ msgid "shows new messages as they are written (similar to running"
#~ msgstr ""
#~ "montre les nouveaux messages au moment"
#~ " de leur Ã©criture (semblable Ã  "
#~ "l'exÃ©cution de"

#~ msgid ")."
#~ msgstr ")."

#~ msgid "rsyslog changes affecting log analyzers such as logcheck"
#~ msgstr ""
#~ "Modifications de rsyslog affectant les "
#~ "analyseurs de journaux tels que logcheck"

#~ 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 ""
#~ "**rsyslog** adopte dorÃ©navant par dÃ©faut "
#~ "les \"horodatages haute prÃ©cision\", ce "
#~ "qui peut affecter les autres programmes"
#~ " qui analysent les journaux systÃ¨me. "
#~ "Vous trouverez plus d'informations sur "
#~ "la maniÃ¨re de personnaliser ce rÃ©glage"
#~ " dans :url-man-stable:`rsyslog.conf(5)`."

#~ 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 ""
#~ "La modification des horodatages peut "
#~ "nÃ©cessiter la mise Ã  jour des "
#~ "rÃ¨gles de **logcheck** crÃ©Ã©es localement. "
#~ "``logcheck`` vÃ©rifie les messages dans "
#~ "le journal systÃ¨me (produits par "
#~ "``systemd-journald`` ou ``rsyslog``) par "
#~ "rapport Ã  une base de donnÃ©es "
#~ "personnalisable d'expressions rationnelles connues"
#~ " sous le nom de rÃ¨gles. Les "
#~ "rÃ¨gles qui cherchent une correspondance "
#~ "avec l'heure de production du message"
#~ " devront Ãªtre mises Ã  jour pour "
#~ "une correspondance avec le nouveau "
#~ "format de ``rsyslog``. Les rÃ¨gles par"
#~ " dÃ©faut, fournies par le paquet "
#~ "**logcheck-database**, ont Ã©tÃ© mises Ã  "
#~ "jour, mais d'autres rÃ¨gles, y compris"
#~ " celles crÃ©Ã©es localement, peuvent "
#~ "nÃ©cessiter une mise Ã  jour pour "
#~ "reconnaÃ®tre le nouveau format. Consultez "
#~ "`/usr/share/doc/logcheck-database/NEWS.Debian.gz "
#~ "<https://salsa.debian.org/debian/logcheck/-/blob/debian/1.4.0/debian";
#~ "/logcheck-database.NEWS>`__ pour un script "
#~ "qui aide Ã  mettre Ã  jour les "
#~ "rÃ¨gles locales de ``logcheck``."

#~ msgid "rsyslog creates fewer log files"
#~ msgstr "rsyslog crÃ©e moins de fichiers journaux"

#~ msgid ""
#~ "**rsyslog** has changed which log files"
#~ " it creates, and some files in "
#~ "``/var/log`` can be deleted."
#~ msgstr ""
#~ "**rsyslog** a modifiÃ© le choix des "
#~ "fichiers de journal qu'il crÃ©ait, et "
#~ "certains fichiers dans ``/var/log`` peuvent"
#~ " Ãªtre supprimÃ©s."

#~ 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 ""
#~ "Si vous continuez Ã  utiliser **rsyslog**"
#~ " (consultez `Changes to system logging "
#~ "<#changes-to-system-logging>`__), certains "
#~ "fichiers de journal dans ``/var/log`` ne"
#~ " seront plus crÃ©Ã©s par dÃ©faut. Les"
#~ " messages qui Ã©taient Ã©crits dans ces"
#~ " fichiers sont aussi dans "
#~ "``/var/log/syslog``, mais ne sont plus "
#~ "crÃ©Ã©s par dÃ©faut. Tout ce qui "
#~ "Ã©tait Ã©crit habituellement dans ces "
#~ "fichiers sera encore disponible dans "
#~ "``/var/log/syslog``."

#~ msgid "The files that are no longer created are:"
#~ msgstr "Les fichiers qui ne sont plus crÃ©Ã©s sontÂ :"

#~ msgid "``/var/log/mail.{info,warn,err}``"
#~ msgstr "``/var/log/mail.{info,warn,err}``"

#~ msgid ""
#~ "These files contained messages from the"
#~ " local mail transport agent (MTA), "
#~ "split up by priority."
#~ msgstr ""
#~ "Ces fichiers contenaient les messages de"
#~ " l'agent local de transport de "
#~ "courrier Ã©lectronique (Â«Â MTAÂ Â»), triÃ©s"
#~ " par prioritÃ©."

#~ 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 ""
#~ "Comme ``/var/log/mail.log`` contient tous les"
#~ " messages concernant le courrier, ces "
#~ "fichiers et leurs homologues issus de"
#~ " la rotation peuvent Ãªtre supprimÃ©s "
#~ "sans risque. Si vous utilisez ces "
#~ "fichiers pour surveiller les anomalies, "
#~ "quelque chose comme logcheck pourrait "
#~ "Ãªtre une alternative appropriÃ©e."

#~ 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 ""
#~ "Ce fichier contenait les messages de "
#~ "journalisation relatifs Ã  l'impression. Le "
#~ "systÃ¨me d'impression par dÃ©faut dans "
#~ "Debian est **cups** qui n'utilise pas"
#~ " ce fichierÂ ; aussi, Ã  moins "
#~ "que vous ayez installÃ© un systÃ¨me "
#~ "d'impression diffÃ©rent, ce fichier et "
#~ "ses homologues issus de la rotation "
#~ "peuvent Ãªtre supprimÃ©s."

#~ msgid "``/var/log/{messages,debug,daemon.log}``"
#~ msgstr "``/var/log/{messages,debug,daemon.log}``"

#~ 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 ""
#~ "Ces fichiers et leurs homologues issus"
#~ " de la rotation peuvent Ãªtre "
#~ "supprimÃ©s. Tout ce qui Ã©tait "
#~ "habituellement Ã©crit dans ces fichiers "
#~ "sera toujours dans ``/var/log/syslog``."

#~ msgid "slapd upgrade may require manual intervention"
#~ msgstr "La mise Ã  niveau de slapd peut nÃ©cessiter une intervention manuelle"

#~ 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 ""
#~ "OpenLDAPÂ 2.5 est une nouvelle version"
#~ " majeure et comprend plusieurs "
#~ "modifications incompatibles dÃ©crites dans "
#~ "`l'annonce de publication amont "
#~ "<https://git.openldap.org/openldap/openldap/-/raw/OPENLDAP_REL_ENG_2_5/ANNOUNCEMENT>`__."
#~ " En fonction de la configuration, le"
#~ " service ``slapd`` pourrait demeurer arrÃªtÃ©"
#~ " aprÃ¨s la mise Ã  niveau, jusqu'Ã  "
#~ "ce que les mises Ã  jour de "
#~ "la configuration soient finalisÃ©es."

#~ msgid "The following are some of the known incompatible changes:"
#~ msgstr "Voici quelques modifications incompatibles connuesÂ :"

#~ 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 ""
#~ "Les dorsaux pour la base de "
#~ "donnÃ©es :url-man-oldstable:`slapd-bdb(5)` "
#~ "et :url-man-oldstable:`slapd-hdb(5)` ont"
#~ " Ã©tÃ© retirÃ©s. Si vous utilisez un "
#~ "de ces dorsaux dans |OLDRELEASENAME|, il"
#~ " est fortement recommandÃ© de migrer "
#~ "vers le dorsal :url-man-stable"
#~ ":`slapd-mdb(5)` *avant* la mise Ã  "
#~ "niveau vers |RELEASENAME|."

#~ msgid ""
#~ "The :url-man-oldstable:`slapd-shell(5)` "
#~ "database backend has been removed."
#~ msgstr ""
#~ "Le dorsal de base de donnÃ©es "
#~ ":url-man-oldstable:`slapd-shell(5)` a Ã©tÃ©"
#~ " retirÃ©."

#~ 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 ""
#~ "La surcouche :url-man-stable:`slapo-"
#~ "ppolicy(5)` inclut maintenant dans le "
#~ "module son schÃ©ma compilÃ©. L'ancien "
#~ "schÃ©ma externe, s'il est prÃ©sent, est"
#~ " en conflit avec celui nouvellement "
#~ "construit."

#~ msgid ""
#~ "The contrib password module pw-argon2"
#~ " (see :url-man-oldstable:`slapd-pw-"
#~ "argon2.5`) has been renamed to :url-"
#~ "man-stable:`argon2`."
#~ msgstr ""
#~ "Le module de mot de passe issu "
#~ "de contribution :url-man-oldstable:`slapd-"
#~ "pw-argon2.5` a Ã©tÃ© renommÃ© :url-"
#~ "man-stable:`argon2`."

#~ 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 ""
#~ "Des instructions pour finaliser la mise"
#~ " Ã  niveau et reprendre le service "
#~ "``slapd`` peuvent Ãªtre trouvÃ©es dans "
#~ "`/usr/share/doc/slapd/README.Debian.gz "
#~ "<https://sources.debian.org/src/openldap/bookworm/debian/slapd.README.Debian/>`__."
#~ " Vous pouvez aussi consulter les "
#~ "`notes de mise Ã  niveau de l'amont"
#~ " <https://openldap.org/doc/admin25/appendix-";
#~ "upgrading.html>`__."

#~ msgid "GRUB no longer runs os-prober by default"
#~ msgstr "GRUB n'exÃ©cute plus os-prober par dÃ©faut"

#~ 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 ""
#~ "Depuis longtemps, **grub** a utilisÃ© le"
#~ " paquet **os-prober** pour dÃ©tecter "
#~ "les autres systÃ¨mes d'exploitation installÃ©s"
#~ " afin qu'il puisse les ajouter au "
#~ "menu d'amorÃ§age. Malheureusement, cela peut"
#~ " Ãªtre problÃ©matique dans certains cas "
#~ "(par exemple lorsque des machines "
#~ "virtuelles invitÃ©es sont en service), "
#~ "aussi cela a Ã©tÃ© dÃ©sactivÃ© par "
#~ "dÃ©faut dans la derniÃ¨re publication "
#~ "amont."

#~ 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 ""
#~ "Si vous utilisez GRUB pour amorcer "
#~ "votre machine et dÃ©sirez continuer Ã  "
#~ "avoir d'autres systÃ¨mes d'exploitation listÃ©s"
#~ " sur votre menu d'amorÃ§age, vous "
#~ "pouvez changer cela. Soit vous Ã©ditez"
#~ " le fichier ``/etc/default/grub``, assurez-"
#~ "vous d'avoir le rÃ©glage "
#~ "``GRUB_DISABLE_OS_PROBER= false`` et exÃ©cutez "
#~ "Ã  nouveau la commande ``update-grub``,"
#~ " soit vous exÃ©cutez"

#~ msgid "to change this and other GRUB settings in a more user-friendly way."
#~ msgstr ""
#~ "pour changer cela et d'autres "
#~ "configuration de GRUB d'une maniÃ¨re plus"
#~ " conviviale."

#~ msgid "GNOME has reduced accessibility support for screen readers"
#~ msgstr ""
#~ "GNOME a rÃ©duit sa prise en charge"
#~ " de l'accessibilitÃ© pour les lecteurs "
#~ "d'Ã©cran"

#~ 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 ""
#~ "Beaucoup d'applications ``GNOME`` sont passÃ©es"
#~ " de la boÃ®te Ã  outils graphiques "
#~ "``GTK3`` Ã  ``GTK4``. Malheureusement, cela "
#~ "a rendu de nombreuses applications "
#~ "beaucoup moins utilisables avec des "
#~ "lecteurs d'Ã©cran tels que **orca**."

#~ 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 ""
#~ "Si vous dÃ©pendez d'un lecteur d'Ã©cran,"
#~ " vous devriez envisager de migrer "
#~ "pour un bureau diffÃ©rent tel que "
#~ "`Mate <https://mate-desktop.org>`__, qui "
#~ "dispose d'une meilleure prise en charge"
#~ " de l'accessibilitÃ©. Vous pouvez faire "
#~ "cela en installant le paquet **mate-"
#~ "desktop-environment**. Des informations pour"
#~ " l'utilisation de Orca avec Mate sont"
#~ " disponibles `sur le wiki "
#~ "<https://wiki.debian.org/Accessibility/Orca#MATE>`__."

#~ msgid "Baseline for 32-bit PC is now i686"
#~ msgstr "La base de rÃ©fÃ©rence 32-bit PC est maintenant i686"

#~ 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 ""
#~ "La prise en charge par Debian de"
#~ " 32-bit PC (connu comme l'architecture "
#~ "Debian i386) ne couvre plus les "
#~ "processeurs i586. Le nouveau prÃ©requis "
#~ "minimal est i686. Cela signifie que "
#~ "dÃ©sormais l'architecture i386 requiert "
#~ "l'instruction \"Â long NOPÂ \" (NOPL), "
#~ "tandis que Bullseye pend encore en "
#~ "charge certains processeurs i586 sans "
#~ "cette instruction (par exemple l'\"Â AMD"
#~ " GeodeÂ \")."

#~ 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 ""
#~ "Si votre machine n'est pas compatible"
#~ " avec ce prÃ©requis, il vous est "
#~ "recommandÃ© de garder Bullseye pour le"
#~ " reste de son cycle de prise en"
#~ " charge."

#~ msgid "Changes to polkit configuration"
#~ msgstr "Modifications de la configuration de polkit"

#~ 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 ""
#~ "Dans un souci d'homogÃ©nÃ©itÃ© avec l'amont"
#~ " et d'autres distributions, le service "
#~ "``polkit`` (anciennement ``PolicyKit``), qui "
#~ "permet Ã  des programmes non privilÃ©giÃ©s"
#~ " d'accÃ©der Ã  des services systÃ¨me "
#~ "privilÃ©giÃ©s, a changÃ© de syntaxe et "
#~ "d'emplacement pour les rÃ¨gle de "
#~ "politique locales. Il est maintenant "
#~ "possible d'Ã©crire des rÃ¨gles locales "
#~ "pour personnaliser la politique de "
#~ "sÃ©curitÃ© en `JavaScript "
#~ "<https://wikipedia.org/wiki/JavaScript>`__, puis de "
#~ "les placer dans ``/etc/polkit-1/rules.d/*.rules``."
#~ " Vous trouverez des exemples de "
#~ "rÃ¨gles utilisant le nouveau format dans"
#~ " ``/usr/share/doc/polkitd/examples/``, et :url-"
#~ "man-unstable:`polkit.8.html#AUTHORIZATION_RULES` contient "
#~ "des informations complÃ©mentaires."

#~ 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 ""
#~ "Auparavant, les rÃ¨gles pouvait Ãªtre "
#~ "Ã©crites au format ``pkla`` et placÃ©es"
#~ " dans les sous-rÃ©pertoires de "
#~ "``/etc/polkit-1/localauthority`` ou de "
#~ "``/var/lib/polkit-1/localauthority``. Toutefois, les "
#~ "fichiers ``.pkla`` devraient dÃ©sormais Ãªtre"
#~ " considÃ©rÃ©s comme obsolÃ¨tes et ils ne"
#~ " continueront Ã  fonctionner que si le"
#~ " paquet **polkitd-pkla** est installÃ©. "
#~ "Ce paquet sera gÃ©nÃ©ralement installÃ© "
#~ "automatiquement lors de la mise Ã  "
#~ "niveau vers Bookworm, mais il est "
#~ "probable qu'il ne sera plus inclus "
#~ "dans les publications de Debian Ã  "
#~ "venir, aussi toutes les surcharges de"
#~ " politique locales auront besoin d'Ãªtre "
#~ "converties au format JavaScript."

#~ 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 ""
#~ "Debian a adoptÃ© une organisation de "
#~ "systÃ¨me de fichiers, appelÃ©e \"``/usr`` "
#~ "fusionnÃ©\" qui n'inclut plus les anciens"
#~ " rÃ©pertoires ``/bin``, ``/sbin``, ``/lib`` "
#~ "ou les variantes optionnelles comme "
#~ "``/lib64``. Dans la nouvelle organisation, "
#~ "les anciens rÃ©pertoires sont remplacÃ©s "
#~ "par des liens symboliques vers les "
#~ "emplacements correspondants ``/usr/bin``, "
#~ "``/usr/sbin``, ``/usr/lib`` et ``/usr/lib64``. "
#~ "Cela signifie, par exemple, qu'Ã  la "
#~ "fois ``/bin/bash`` et ``/usr/bin/bash`` "
#~ "chargeront ``bash``."

#~ 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 ""
#~ "Pour les systÃ¨mes installÃ©s sous Buster"
#~ " ou Bullseye, il n'y aura pas "
#~ "de modification dans la mesure oÃ¹ "
#~ "la nouvelle organisation du systÃ¨me de"
#~ " fichiers est dÃ©jÃ  celle par dÃ©faut"
#~ " dans ces versions. NÃ©anmoins, l'ancienne"
#~ " organisation n'est plus prise en "
#~ "charge et les systÃ¨mes qui l'utilisent"
#~ " seront convertis Ã  la nouvelle "
#~ "organisation lors de la mise Ã  "
#~ "niveau vers Bookworm."

#~ 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 ""
#~ "La conversion vers la nouvelle "
#~ "organisation ne devrait pas avoir "
#~ "d'impact pour la plupart des "
#~ "utilisateurs. Tous les fichiers sont "
#~ "dÃ©placÃ©s automatiquement vers leur nouvel "
#~ "emplacement mÃªme s'ils ont Ã©tÃ© installÃ©s"
#~ " localement ou proviennent de paquets "
#~ "non fournis par Debian et les "
#~ "chemins codÃ©s en dur tels que "
#~ "``/bin/sh`` continuent Ã  fonctionner. Il "
#~ "existe cependant quelques problÃ¨mes potentiels"
#~ "Â :"

#~ msgid "will give wrong answers for files moved to the new locations:"
#~ msgstr ""
#~ "donnera des rÃ©ponses erronÃ©es pour les"
#~ " fichiers dÃ©placÃ©s dans leur nouvel "
#~ "emplacementÂ :"

#~ msgid "will not identify that ``bash`` came from a package. (But"
#~ msgstr "ne considÃ©rera pas que ``bash`` vient d'un paquet. (Mais"

#~ msgid "still works as expected.)"
#~ msgstr "fonctionne encore comme prÃ©vu.)"

#~ 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 ""
#~ "Des logiciels locaux non fournis par "
#~ "Debian peuvent ne pas prendre en "
#~ "charge la nouvelle organisation et "
#~ "peuvent, par exemple compter sur le "
#~ "fait que ``/usr/bin/name`` et ``/bin/name``"
#~ " sont des fichiers diffÃ©rents. Cela "
#~ "n'est pas pris en charge par les"
#~ " systÃ¨mes fusionnÃ©s (y compris les "
#~ "nouvelles installations depuis Buster), aussi"
#~ " les programmes de ce type doivent"
#~ " Ãªtre corrigÃ©s ou supprimÃ©s avant la"
#~ " mise Ã  niveau."

#~ 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 ""
#~ "Les systÃ¨mes qui reposent sur une "
#~ "\"couche de base\" qui n'est pas "
#~ "directement accessible en Ã©criture (comme "
#~ "les images `WSL1 "
#~ "<https://wiki.debian.org/InstallingDebianOn/Microsoft/Windows/SubsystemForLinux>`__"
#~ " ou les systÃ¨mes de conteneur "
#~ "utilisant des systÃ¨mes de fichiers "
#~ "`overlayfs <https://en.wikipedia.org/wiki/OverlayFS>`__ "
#~ "multicouches) ne peuvent pas Ãªtre "
#~ "convertis sans risque et doivent soit"
#~ " Ãªtre remplacÃ©s (par exemple en "
#~ "installant une nouvelle image WSL1Ã  "
#~ "partir du magasin) ou avoir une "
#~ "mise Ã  niveau de chaque niveau "
#~ "individuel (par exemple en mettant Ã  "
#~ "niveau la couche de base de Debian"
#~ " de l'overlays indÃ©pendamment) plutÃ´t que"
#~ " de faire l'objet d'un dist-upgrade."

#~ 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 ""
#~ "Pour plus d'information, consultez `The "
#~ "Case for the /usr merge "
#~ "<https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/>`__"
#~ " et `la rÃ©solution du ComitÃ© "
#~ "technique de Debian <https://bugs.debian.org/cgi-";
#~ "bin/bugreport.cgi?bug=994388#110>`__."

#~ 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 "InterprÃ©teurs Python marquÃ©s comme gÃ©rÃ©s en externe"

#~ 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 ""
#~ "Les paquets de l'interprÃ©teur python3 "
#~ "fournis par Debian (**python3.11** et "
#~ "**pypy3**) sont dÃ©sormais marquÃ©s comme "
#~ "ayant une gestion externe, suivant la"
#~ " `PEP-668 <https://peps.python.org/pep-0668/>`__. La"
#~ " version de **python3-pip** fournie par "
#~ "Debian suit cela et refusera d'installer"
#~ " manuellement des paquets sur les "
#~ "interprÃ©teurs Python de Debian, Ã  moins"
#~ " que l'option ``--break-system-packages``"
#~ " ne soit spÃ©cifiÃ©e."

#~ 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 ""
#~ "Si vous avez besoin d'installer une "
#~ "application Python (ou une version) qui"
#~ " n'est pas empaquetÃ©e par Debian, "
#~ "nous vous recommandons de l'installer "
#~ "avec ``pipx`` (prÃ©sent dans le paquet"
#~ " Debian **pipx**). ``pipx`` configurera un"
#~ " environnement isolÃ© des autres application"
#~ " et des modules Python du systÃ¨me,"
#~ " et installe l'application et ses "
#~ "dÃ©pendances Ã  l'intÃ©rieur."

#~ 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 ""
#~ "Si vous avez besoin d'installer un "
#~ "module de bibliothÃ¨que (ou une version)"
#~ " qui n'est pas empaquetÃ© dans Debian,"
#~ " nous vous recommandons de l'installer "
#~ "dans un environnement virtuel quand "
#~ "c'est possible. Vous pouvez crÃ©er des"
#~ " environnements virtuels avec le module "
#~ "stdlib Python ``venv`` (du paquet Debian"
#~ " **python3-venv**) ou avec l'outil Python"
#~ " tierce ``virtualenv`` (du paquet Debian"
#~ " **virtualenv**). Par exemple, plutÃ´t que"
#~ " d'exÃ©cuter ``pip install --user foo``, "
#~ "exÃ©cutezÂ ``mkdir -p ~/.venvs && python3"
#~ " -m venv ~/.venvs/foo && "
#~ "~/.venvs/foo/bin/python -m pip install foo``"
#~ " pour l'installer dans un environnement "
#~ "virtuel dÃ©diÃ©."

#~ msgid "See ``/usr/share/doc/python3.11/README.venv`` for more details."
#~ msgstr ""
#~ "Consultez ``/usr/share/doc/python3.11/README.venv`` pour"
#~ " plus de dÃ©tails."

#~ msgid "Limited hardware-accelerated video encoding/decoding support in VLC"
#~ msgstr ""
#~ "Limitation de la prise en charge "
#~ "dans VLC de l'encodage et du "
#~ "dÃ©codage vidÃ©o avec accÃ©lÃ©ration matÃ©rielle"

#~ 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 ""
#~ "Le lecteur de vidÃ©os VLC prend en"
#~ " charge l'encodage et le dÃ©codage "
#~ "vidÃ©o avec accÃ©lÃ©ration matÃ©rielle au "
#~ "moyen de VA-API et VDPAU. "
#~ "NÃ©anmoins, la prise en charge de "
#~ "VLC pour VA-API est Ã©troitement "
#~ "liÃ©e Ã  la version de FFmpeg. Comme"
#~ " FFmpeg a Ã©tÃ© mis Ã  niveau vers"
#~ " la brancheÂ 5.x, la prise en "
#~ "charge de VA-API de VLC a "
#~ "Ã©tÃ© dÃ©sactivÃ©e. Les utilisateurs de "
#~ "processeurs graphiques offrant une prise "
#~ "en charge native de VA-API (par"
#~ " exemple, les processeurs graphiques Intel"
#~ " et AMD) peuvent Ãªtre confrontÃ©s Ã "
#~ " une utilisation Ã©levÃ©e du processeur "
#~ "durant la lecture et l'encodage de "
#~ "vidÃ©os."

#~ msgid ""
#~ "Users of GPUs offering native VDPAU "
#~ "support (e.g., NVIDIA with non-free "
#~ "drivers) are not affected by this "
#~ "issue."
#~ msgstr ""
#~ "Les utilisateurs de processeurs graphiques "
#~ "offrant une prise en charge native "
#~ "de VDPAU (par exemple, NVIDIA avec "
#~ "des pilotes non libres) ne sont "
#~ "pas affectÃ©s par ce problÃ¨me."

#~ 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 ""
#~ "La prise en charge de VA-API "
#~ "et VDPAU peut Ãªtre vÃ©rifiÃ©e avec "
#~ "les commandes ``vainfo`` et ``vdpauinfo`` "
#~ "(chacune fournie par un paquet Debian"
#~ " de mÃªme nom)."

#~ msgid "systemd-resolved has been split into a separate package"
#~ msgstr "systemd-resolved a Ã©tÃ© sÃ©parÃ© dans un paquet indÃ©pendant"

#~ 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 ""
#~ "Le nouveau paquet **systemd-resolved** "
#~ "ne sera pas installÃ© automatiquement "
#~ "lors des mises Ã  niveau. Si vous"
#~ " utilisez le service systÃ¨me ``systemd-"
#~ "resolved``, veuillez installer le nouveau "
#~ "paquet manuellement aprÃ¨s la mise Ã  "
#~ "niveau et noter que jusqu'Ã  ce que"
#~ " le paquet soit installÃ©, la "
#~ "rÃ©solution DNS pourrait ne plus "
#~ "fonctionner dans la mesure oÃ¹ le "
#~ "service ne sera pas installÃ© sur "
#~ "le systÃ¨me. L'installation de ce paquet"
#~ " donnera automatiquement Ã  systemd-resolved"
#~ " le contrÃ´le de ``/etc/resolv.conf``. Pour"
#~ " plus d'informations sur systemd-resolved,"
#~ " consultez la `documentation "
#~ "<https://www.freedesktop.org/software/systemd/man/systemd-";
#~ "resolved.service.html>`__ officielle. Notez que "
#~ "systemd-resolved n'Ã©tait pas et n'est"
#~ " toujours pas le rÃ©solveur DNS par"
#~ " dÃ©faut dans Debian. Si vous n'avez"
#~ " pas configurÃ© votre machine pour "
#~ "utiliser systemd-resolved comme rÃ©solveur "
#~ "DNS, aucune action n'est nÃ©cessaire."

#~ msgid "systemd-boot has been split into a separate package"
#~ msgstr "systemd-boot a Ã©tÃ© sÃ©parÃ© dans un paquet indÃ©pendant"

#~ 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 ""
#~ "Le nouveau paquet **systemd-boot** ne"
#~ " sera pas installÃ© automatiquement lors "
#~ "des mises Ã  niveau. Si vous "
#~ "utilisez le service systÃ¨me ``systemd-"
#~ "boot``, veuillez installer ce nouveau "
#~ "paquet manuellement aprÃ¨s la mise Ã  "
#~ "niveau et noter que jusqu'Ã  ce que"
#~ " vous l'ayez fait, l'ancienne version "
#~ "de systemd-boot sera utilisÃ©e comme "
#~ "chargeur d'amorÃ§age. L'installation de ce "
#~ "paquet configurera automatiquement systemd-"
#~ "boot comme chargeur d'amorÃ§age de la "
#~ "machine. Le chargeur d'amorÃ§age par "
#~ "dÃ©faut de Debian est toujours GRUB. "
#~ "Si vous n'avez pas configurÃ© la "
#~ "machine pour qu'elle utilise systemd-"
#~ "boot comme chargeur d'amorÃ§age, aucune "
#~ "action n'est nÃ©cessaire."

#~ msgid "systemd-journal-remote no longer uses GnuTLS"
#~ msgstr "systemd-journal-remote n'utilise plus GnuTLS"

#~ 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 ""
#~ "Les services optionnels `systemd-journal-"
#~ "gatewayd <https://www.freedesktop.org/software/systemd/man";
#~ "/systemd-journal-remote.service.html#--trust=>`__ et"
#~ " `systemd-journal-remote "
#~ "<https://www.freedesktop.org/software/systemd/man/systemd-";
#~ "journal-gatewayd.service.html#--trust=>`__ sont "
#~ "maintenant construits sans la prise en"
#~ " charge de GnuTLS, ce qui signifie"
#~ " que l'option ``--trust`` n'est plus "
#~ "fournie par aucun de ces programmes "
#~ "et une erreur sera dÃ©clenchÃ©e si "
#~ "l'option est spÃ©cifiÃ©e."

#~ msgid "Extensive changes in adduser for bookworm"
#~ msgstr "Changements importants dans adduser pour Bookworm"

#~ 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 ""
#~ "Il y a eu plusieurs modifications "
#~ "dans **adduser**. La plus importante est"
#~ " que ``--disabled-password`` et "
#~ "``--disabled-login`` sont dÃ©sormais identiques"
#~ " fonctionnellement. Pour davantage de "
#~ "dÃ©tails, consultez le fichier "
#~ "``/usr/share/doc/adduser/NEWS.Debian.gz``."

#~ msgid "Predictable naming for Xen network interfaces"
#~ msgstr "Nommage prÃ©visible des interfaces rÃ©seau de Xen"

#~ 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 ""
#~ "La logique de nommage prÃ©visible dans"
#~ " ``systemd`` des interfaces rÃ©seau a "
#~ "Ã©tÃ© Ã©tendu pour gÃ©nÃ©rer des noms "
#~ "stables Ã  partir des informations de "
#~ "pÃ©riphÃ©rique de Xen-netfront. Cela "
#~ "signifie qu'Ã  la place de l'ancien "
#~ "systÃ¨me de noms assignÃ©s par le "
#~ "noyau, les interfaces ont dÃ©sormais des"
#~ " noms stables de la forme ``enX#``."
#~ " Vous devez adapter votre systÃ¨me "
#~ "avant de redÃ©marrer aprÃ¨s la mise "
#~ "Ã  niveau. Vous trouverez davantage "
#~ "d'informations sur la `page "
#~ "NetworkInterfaceNames du wiki "
#~ "<https://wiki.debian.org/NetworkInterfaceNames#bookworm-xen>`__."

#~ msgid "Change in dash handling of circumflex"
#~ msgstr "Modification du traitement de l'accent circonflexe par dash"

#~ 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 ""
#~ "``dash``, qui fournit par l'interprÃ©teur "
#~ "de commandes par dÃ©faut du systÃ¨me "
#~ "``/bin/sh`` dans Debian, est passÃ© Ã  "
#~ "un traitement de l'accent circonflexe "
#~ "(``^``) comme caractÃ¨re littÃ©ral, comme "
#~ "cela toujours Ã©tÃ© le comportement "
#~ "attendu conforme Ã  POSIX. Cela signifie"
#~ " que dans Bookworm ``[^0-9]`` ne "
#~ "signifie plus \"pas de 0 Ã  \" "
#~ "mais \"de 0 Ã  9 et ^\"."

#~ msgid "netcat-openbsd supports abstract sockets"
#~ msgstr "netcat-openbsd prend en charge les sockets abstraits"

#~ 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 ""
#~ "L'utilitaire ``netcat`` qui permet de "
#~ "lire et d'Ã©crire des donnÃ©es Ã  "
#~ "travers des connexions rÃ©seau prend en"
#~ " charge les :url-man-"
#~ "stable:`unix.7.html#Abstract_sockets` et les utilise"
#~ " par dÃ©faut dans certaines circonstances."

#~ 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 ""
#~ "Par dÃ©faut, ``netcat`` est fourni par"
#~ " **netcat-traditional**. NÃ©anmoins, si "
#~ "``netcat`` est fourni par le paquet "
#~ "**netcat-openbsd** et si vous utilisez"
#~ " un socket ``AF_UNIX``, alors ce "
#~ "nouveau comportement par dÃ©faut s'applique."
#~ " Dans ce cas,l'option ``-U`` pour "
#~ "``nc`` interprÃ©tera maintenant un argument "
#~ "dÃ©butant par une ``@`` comme demandant"
#~ " un socket abstrait plutÃ´t que comme"
#~ " un nom de fichier dÃ©butant par "
#~ "une ``@`` dans le rÃ©pertoire en "
#~ "cours. Cela peut avoir des implications"
#~ " de sÃ©curitÃ© parce que les "
#~ "permissions du systÃ¨me de fichiers ne"
#~ " peuvent plus Ãªtre utilisÃ©es pour "
#~ "contrÃ´ler l'accÃ¨s Ã  un socket abstrait."
#~ " Vous pouvez continuer Ã  utiliser un"
#~ " nom de fichier dÃ©butant par une "
#~ "``@`` en prÃ©fixant le nom avec "
#~ "``./`` ou en spÃ©cifiant un chemin "
#~ "absolu."

#~ msgid ""
#~ "The **libnss-ldap** package has been "
#~ "removed from |RELEASENAME|. Its "
#~ "functionalities are now covered by "
#~ "**libnss-ldapd** and **libnss-sss**."
#~ msgstr ""
#~ "Le paquet **libnss-ldap** a Ã©tÃ© "
#~ "supprimÃ© de |RELEASENAME|. Ses fonctionnalitÃ©s"
#~ " sont maintenant couvertes par **libnss-"
#~ "ldapd** et **libnss-sss**."

#~ msgid ""
#~ "The **libpam-ldap** package has been "
#~ "removed from |RELEASENAME|. Its replacement"
#~ " is **libpam-ldapd**."
#~ msgstr ""
#~ "Le paquet **libpam-ldap** a Ã©tÃ© "
#~ "supprimÃ© de |RELEASENAME|. Son successeur "
#~ "est **libpam-ldapd**."

#~ msgid ""
#~ "The **fdflush** package has been removed"
#~ " from |RELEASENAME|. In its stead, "
#~ "please use ``blockdev --flushbufs`` from "
#~ "**util-linux**."
#~ msgstr ""
#~ "Le paquet **fdflush** a Ã©tÃ© supprimÃ© "
#~ "de |RELEASENAME|. Ã? sa place veuillez"
#~ " utiliser ``blockdev --flushbufs`` provenant "
#~ "de **util-linux**."

#~ 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 ""
#~ "Le paquet **libgdal-perl** a Ã©tÃ© "
#~ "retirÃ© de |RELEASENAME| parce que la "
#~ "liaison Perl pour GDAL n'est plus "
#~ "prise en charge par l'amont. Si "
#~ "vous avez besoin de la prise en"
#~ " charge de Perl pour GDAL, vous "
#~ "pouvez migrer vers l'interface FFI "
#~ "fournie par le paquet **Geo::GDAL::FFI** "
#~ "disponible dans le CPAN. Vous devrez "
#~ "construire vos propres binaires comme "
#~ "cela est documentÃ© sur la `page "
#~ "BookwormGdalPerl du Wiki "
#~ "<https://wiki.debian.org/BookwormGdalPerl>`__."

#~ 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 ""
#~ "**dmraid** n'a pas connu d'activitÃ© "
#~ "amont depuis la fin de 2010 et "
#~ "est moribond dans Debian. Bookworm sera"
#~ " la derniÃ¨re publication Ã  le "
#~ "fournir, aussi veuillez prendre vos "
#~ "dispositions en consÃ©quence si vous "
#~ "utilisez **dmraid**."

#~ 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 ""
#~ "**request-tracker4** a Ã©tÃ© remplacÃ© par"
#~ " **request-tracker5** dans cette "
#~ "publication et sera supprimÃ© dans les"
#~ " publications Ã  venir. Il est "
#~ "recommandÃ© de prÃ©voir une migration de"
#~ " request-tracker4 Ã  request-tracker5 "
#~ "pendant la durÃ©e de cette publication."

#~ 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 ""

#~ 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 ""

#~ msgid "`1020284`_"
#~ msgstr ""

#~ msgid "**git-daemon-run**"
#~ msgstr ""

#~ msgid "fails to purge: deluser -f: Unknown option: f"
#~ msgstr "Ã©choue Ã  purgerÂ : deluser -fÂ : Unknown option: f"

#~ msgid "`919296`_"
#~ msgstr ""

#~ msgid ""
#~ "fails with 'warning: git-daemon: unable"
#~ " to open supervise/ok: file does not"
#~ " exist'"
#~ msgstr ""
#~ "Ã©choue avec l'avertissementÂ : 'warning: "
#~ "git-daemon: unable to open supervise/ok:"
#~ " file does not exist'"

Reply to:

Follow-Ups:
- [ITT] ddp://release-notes/source/locales/fr/LC_MESSAGES/issues.po
  - From: Jean-Pierre Giraud <jipege@debian.org>

References:
- Notes de publication
  - From: Baptiste Jammet <baptiste@mailoo.org>

Prev by Date: [MAJ] ddp://release-notes/source/locales/fr/LC_MESSAGES/old-stuff.po
Next by Date: [MAJ] ddp://release-notes/source/locales/fr/LC_MESSAGES/upgrading.po
Previous by thread: [LCFC] ddp://release-notes/source/locales/fr/LC_MESSAGES/old-stuff.po
Next by thread: [ITT] ddp://release-notes/source/locales/fr/LC_MESSAGES/issues.po
Index(es):
- Date
- Thread