Source strings

52 Strings 100%
Browse Translate
2,220 Words 100%
15,778 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
52 2,220 15,778
All strings Browse Translate Zen
52 2,220 15,778
Read-only strings Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
chapter08_pkgconf 0 0 0 0 0 0 0
chapter08_libxcrypt 0 0 0 0 0 0 0
chapter10_kernel_sysv 0 0 0 0 1 0 0
chapter10_kernel_systemd 0 0 0 0 1 0 0
chapter10_kernel_highmem 0 0 0 0 0 0 0
chapter10_kernel_nvme 0 0 0 0 0 0 0
chapter10_kernel_x2apic 0 0 0 0 0 0 0
chapter08_udev 0 0 0 0 0 0 0
chapter02_mounting 0 0 0 0 0 0 0
chapter07_introduction 0 0 0 0 1 0 0
Browse all components

Overview

Project website www.linuxfromscratch.org
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@git.linuxfromscratch.org:fr-lfs
Repository branch trunk
Last remote commit Automatic LFS commit based on ba1a9cf303ad4c6c94e4fd7f74871ffb357e367d 76aa972976
Julien Lepiller authored 10 hours ago
Last commit in Weblate Translated using Weblate (French) 65d75ab687
Weblate Admin authored 2 months ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask lfs/*/chapter08/pkgmgt.po
Translation file Not available
Last change None
Last author None
13 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 52 2,220 15,778
Translated 100% 52 100% 2,220 100% 15,778
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 52 100% 2,220 100% 15,778
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 4 changes 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 2 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes 3 changes 50 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

2,220
Hosted words
52
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
+100%
User avatar None

Source string added

  1. Linux From Scratch
  2. chapter08_pkgmgt
  3. English
If Glibc needs to be upgraded to a newer version, (e.g., from Glibc-2.36 to Glibc-&glibc-version;), some extra steps are needed to avoid breaking the system. Read <xref linkend='ch-system-glibc'/> for details.
2 months ago
User avatar None

Source string added

  1. Linux From Scratch
  2. chapter08_pkgmgt
  3. English
If the Linux kernel needs to be upgraded (for example, from 5.10.17 to 5.10.18 or 5.11.1), nothing else needs to be rebuilt. The system will keep working fine thanks to the well-defined interface between the kernel and userspace. Specifically, Linux API headers need not be upgraded along with the kernel. You will merely need to reboot your system to use the upgraded kernel.
2 months ago
User avatar None

Source string added

  1. Linux From Scratch
  2. chapter08_pkgmgt
  3. English
This scheme is used by the BLFS book to install some very large packages to make it easier to upgrade them. If you install more than a few packages, this scheme becomes unmanageable. And some packages (for example Linux API headers and Glibc) may not work well with this scheme. <emphasis role='bold'>Never use this scheme system-wide.</emphasis>
5 months ago
User avatar None

Source string added

  1. Linux From Scratch
  2. chapter08_pkgmgt
  3. English
Environment variables such as <envar>PATH</envar>, <envar>MANPATH</envar>, <envar>INFOPATH</envar>, <envar>PKG_CONFIG_PATH</envar>, <envar>CPPFLAGS</envar>, <envar>LDFLAGS</envar>, and the configuration file <filename>/etc/ld.so.conf</filename> may need to be expanded to include the corresponding subdirectories in <filename class='directory'>/opt/foo-x.y</filename>.
5 months ago
User avatar None

Source string added

  1. Linux From Scratch
  2. chapter08_pkgmgt
  3. English
This is a simplistic package management technique that does not need a special program to manage the packages. Each package is installed in a separate directory. For example, package foo-1.1 is installed in <filename class='directory'>/opt/foo-1.1</filename> and a symlink is made from <filename>/opt/foo</filename> to <filename class='directory'>/opt/foo-1.1</filename>. When a new version foo-1.2 comes along, it is installed in <filename class='directory'>/opt/foo-1.2</filename> and the previous symlink is replaced by a symlink to the new version.
5 months ago
User avatar None

Source string added

  1. Linux From Scratch
  2. chapter08_pkgmgt
  3. English
If an executable program or a shared library is overwritten, the processes using the code or data in that program or library may crash. The correct way to update a program or a shared library without causing the process to crash is to remove it first, then install the new version. The <command>install</command> command provided by <application>coreutils</application> has already implemented this, and most packages use that command to install binary files and libraries. This means that you won't be troubled by this issue most of the time. However, the install process of some packages (notably SpiderMonkey in BLFS) just overwrites the file if it exists; this causes a crash. So it's safer to save your work and close unneeded running processes before updating a package.
6 months ago
User avatar None

Source string added

  1. Linux From Scratch
  2. chapter08_pkgmgt
  3. English
If a package is (directly or indirectly) linked to both the old and new names of a shared library (for example, the package links to both <filename class='libraryfile'>libfoo.so.2</filename> and <filename class='libraryfile'>libbar.so.1</filename>, while the latter links to <filename class='libraryfile'>libfoo.so.3</filename>), the package may malfunction because the different revisions of the shared library present incompatible definitions for some symbol names. This can be caused by recompiling some, but not all, of the packages linked to the old shared library after the package providing the shared library is upgraded. To avoid the issue, users will need to rebuild every package linked to a shared library with an updated revision (e.g. libfoo.so.2 to libfoo.so.3) as soon as possible.
10 months ago
User avatar None

Source string added

  1. Linux From Scratch
  2. chapter08_pkgmgt
  3. English
If <application>OpenSSH</application> is being used to access the system and it is linked to the updated library, you must restart the <command>sshd</command> service, then logout, login again, and run the preceding command again to confirm that nothing is still using the deleted libraries.
11 months ago
User avatar None

Source string added

  1. Linux From Scratch
  2. chapter08_pkgmgt
  3. English
<userinput>grep -l '<replaceable>libfoo</replaceable>.*deleted' /proc/*/maps | tr -cd 0-9\\n | xargs -r ps u</userinput>
11 months ago
User avatar None

Source string added

  1. Linux From Scratch
  2. chapter08_pkgmgt
  3. English
Finally, the new system has to be made bootable via <xref linkend="ch-bootable-grub"/>.
a year ago
Browse all translation changes